Closed richardgobeli closed 5 months ago
The cursor position problem is not reproducible on my computer - or I am using the program completely different to you.
Getting lisp-quiet commands at the end looks like a hickup during communication with maxima. Will try to look where that can go wrong...
The cursor position issue, I think happens after some editing like lines being removed and reinserted at different positions.
This version today.
Sometimes loading a file, I get the lisp-quiet stuff at the end. This is still happening.
Maybe this is the same bug:
Start by evaluating 6 (useless) lines:
Select the last 5 lines:
Delete them:
Click somewhere below the cursor, where the deleted lines were before:
The cursor is now in a place where it shouldn't be allowed, and nothing can be typed at that location.
Yes, that is the same bug, which happens after some editing of the worksheet.
Hello,
this is just to confirm that I have the same problem. Latest wxMaxima (24.02.2) on an up to date Windows 10, recently installed from scratch.
Bye,
Denis
The fix for the https://github.com/wxMaxima-developers/wxmaxima/issues/1911 fixes this issue also.
When that bug arrived I hoped it would provide me with the last few puzzle pieces for finding out where this bug comes from...
It is like it is counting wrong to find the end of the file or display. It will not let me position the cursor at the end of the last statement.
I need to position before that last statement and then scroll with the down arrow to the end or execute the last statement to get to the end of the file.
This is from yesterday's version. It must have been a bad load. My work computer seems to work OK. Sometimes loading a file, I get the lisp-quiet stuff at the end.