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
In addition to #98, multi-line editing seems to be broken, with the cursor jumping to wrong lines etc if scrolling is involved. Example: At the bottom screen line, recall a command from history that is longer than one line, move left one character and enter something. Cursor then jumps one line up, overwriting wrong part of the command line.
Further, reading the source, it seems that some parts of readcommandEnhanced() are generally not designed to to handle more than two lines of input.
The text was updated successfully, but these errors were encountered:
…vVars, memory corruption in set command (#104)
* update version strings and history
* fix NASM segment attribute redefinition warning
* OpenWatcom 1.9 warning fixes
* add binary extensions to .gitignore
* fix#102 multi-line command line editing
* make sure executable name contains quotation marks if needed
* fix memory leak in expandEnvVars and memory corruption in set command
adapt to messed up indentation
In addition to #98, multi-line editing seems to be broken, with the cursor jumping to wrong lines etc if scrolling is involved. Example: At the bottom screen line, recall a command from history that is longer than one line, move left one character and enter something. Cursor then jumps one line up, overwriting wrong part of the command line.
Further, reading the source, it seems that some parts of readcommandEnhanced() are generally not designed to to handle more than two lines of input.
The text was updated successfully, but these errors were encountered: