GitLab

New text.dat string:
- EditExtDescriptionQ

Removed text.dat string:
DeleteExtDescriptionQ

Was passing the address string twice, so the port appeared as an invalid number.

Altere reported via IRC:
!ERROR -1 (113) connecting to passthru socket

It might be helpful to know the address the passthru socket is bound to and the connection is being attempted on, so log that with the error.

This is the likely cause of Phil's reported errors when removing files:
access=-110 info=smb_removefile name not found

The only way I was able to reproduce these errors was to attempt to remove the same file multiple times in the same file listing. In other worse, use 'R', remove a file, then 'P'revious back to the first file and try to remove it again. Or to remove it a file from the batch flag prompt and then attempt to remove it again. <shrug>

This eliminates any ambiguity about what exact version was in use when each error is logged.

CID 330960, 330967, 330988

If the file doesn't already have a description, f->desc may be NULL.
Remove the redundant user name in the "removed file" log message.

This may have contributed to plt's file editing woes.

Fix issue reported by Jay Crutti.

CID 331582

Make it the default.

#pragma clang causes an error
__attribute__ not supported

This uses the 720x400 with 9x16 character cell that always made
BBSs look so terrible.

I do, so you should too!

This fixes issues where "leftovers" from the previous mode would
remain in a new screen mode.

Also, include math.h

Sheesh.

Simplest way is to use the alt-left/right snapping.

Which required a new ciolib option of course.
Only usable in X11 mode at present, though it may land for SDL
this weekend.

Also, we don't need to use pointers for the scaling.

Since we have all odd numbers thanks to the pointy scaler, and we
have 2x thanks to xBR, we should now be able to build any integer
scaling from a combination of those two scalers.

This, of course, assumes you have enough CPU and RAM to actually
do the scaling you want... powers of two will likely be the worst
case for scaling.

Also, do pointy scaling before xBR.

I haven't played with this chat pager in *years*! The lowest tones were inaudible (raise the range from 0-800Hz to 400-1200Hz).
Increase the msgabort() tone from 1 to 10ms, sounds like those computerized voice recognition phone systems now.

Remove the redundant "<user> paged you to chat" notifications (and log message) when turning *off* the chat pager.

by adding a 'clear' argument to msgabort() that defaults to false. Pass true to check-and-clear.
checkline() is a NO-OP, so start eliminating "calls" to it.