You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its rather annoying that errors in a command can't be corrected like the can in a regular shell - you're forced to delete characters until you get to the error, then retype the rest of the command. Or not even errors - perhaps you want to select a long command from the command history and change one detail about it - can't do that either.
This is not a new limitation, and its not a limitation unique to Kermit 95 - C-Kermit can't do this either.
There is some discussion about this in the C-Kermit To-Do List (see the section titled "Interactive command parser").
If this is attempted at some point, it should probably be #ifdef'd to OS2 to start with as its going to rely on a bunch of K95-specific APIs for moving the cursor around - proper terminal emulation isn't currently fully supported on the command screen.
IKSD may add some complication too - the K95-specific APIs for moving the cursor around won't work over telnet so if K95 is running as IKSD (or over stdin/stdout for that matter) it should instead probably attempt ANSI escapes.
The text was updated successfully, but these errors were encountered:
Its rather annoying that errors in a command can't be corrected like the can in a regular shell - you're forced to delete characters until you get to the error, then retype the rest of the command. Or not even errors - perhaps you want to select a long command from the command history and change one detail about it - can't do that either.
This is not a new limitation, and its not a limitation unique to Kermit 95 - C-Kermit can't do this either.
There is some discussion about this in the C-Kermit To-Do List (see the section titled "Interactive command parser").
If this is attempted at some point, it should probably be #ifdef'd to OS2 to start with as its going to rely on a bunch of K95-specific APIs for moving the cursor around - proper terminal emulation isn't currently fully supported on the command screen.
IKSD may add some complication too - the K95-specific APIs for moving the cursor around won't work over telnet so if K95 is running as IKSD (or over stdin/stdout for that matter) it should instead probably attempt ANSI escapes.
The text was updated successfully, but these errors were encountered: