#3570 Daily versions problems with up/down cursor movement

severe bug

Since jedit4.5pre1install.jar from 2011-08-29_12-01-45 (including this version), the cursor movements up and down are strange. With soft wrap on, every time the cursor changes line (new number in the gutter) it disappears from view but if the line is wrapped, it reappears on the next visible (but still the same number) line. If the cursor reaches upper or lower boundary of editpane and the cursor is still moved up/down, the visible text in editpane does not track the cursor and remains the same. The PgDn/PgUp movements do not have this problem and move the text in the editpane.



  • Matthieu Casanova

    Could you give an example, I cannot reproduce that.

  • sbarex

    sbarex - 2011-09-02

    Same problem with version of 2011-09-01.
    These are some problems:
    - If the current line is very long, typing it over the right edge of the window does not scroll the cursor accordingly and then disappears over the edge while continuing to write (while scroll bars are adapted to the new window size), you must use the arrow keys to view the cursor;
    - If you put the cursor on the last line of a file and this is the lower limit of the window, adding new rows to the page does not scroll the view.
    - If we make changes to a row, scroll the page so that the modified line does not appear on the screen and press ctrl-z, changes are undone and the cursor is repositioned on the line of the last change but the view is not scrolled to the old position.
    - Finally, when you type, the system does not highlight the matching brackets, but they are highlighted when you stand next to using the arrow keys.


  • tvojeho

    tvojeho - 2011-09-02

    It seem to me that it has something to do with macros. I have a heavily customized jedit installation, and some time in the past I have remapped the basic cursor movements to macros in order to deal with the sometimes popping up NPEs. For instance, Right Arrow, which is originally mapped to the command "Go To Next Character", I have remapped to a following macro:

    int lineNo = textArea.getCaretLine(); // Get current line number
    if(!textArea.displayManager.isLineVisible(lineNo)) // Scroll if current line is not visible
    try {
    } catch (NullPointerException npe) {
    VFSManager.waitForRequests(); // Wait
    try {
    } catch (NullPointerException npe) {
    // Print out the exception that occurred in status bar
    view.status.setMessageAndClear("Exception occurred...");

    It is perhaps crude, but it helped me avoid some NPE notices. But even if the macro consists only of the single command "textArea.goToNextCharacter(false);", the current problem remains, but if I remap "Go To Next Character" directly to Right Arrow in the Shortcuts dialog, then the text scrolls OK.


  • sbarex

    sbarex - 2011-09-02

    I do not have remapped the keys with macros so maybe the problem is not strictly related to them.

    Another anomaly is in the search system. If you initiate a search with the find panel, after closing it is usually possible to continue to search pressing C+g (or CS+g). But If you select some text, it automatically becomes the search criteria replacing the one previously set in the panel.

  • potchie

    potchie - 2011-09-03

    I've been having the same issue since updating yesterday.

    Simple steps to reproduce:

    Issue 1
    1) Open a new document
    2) Press and hold enter until more lines than are visible are created
    3) Notice that the document no longer scrolls down. the focus remains

    Issue 2
    1) In the same document, place the cursor on line 1 (ctrl-home) and enter any text
    2) Place the cursor on the last line, making sure that you can no longer see line 1
    3) Undo your last change (remove the text entered on line 1)
    4) Notice that the document doesn't scroll the change into view

    For some reason I am no longer able to reproduce the clipboard issue, although I haven't updated jEdit since I first saw that issue.


  • Matthieu Casanova

    There was a problem with one change I made, it was fixed now

  • Matthieu Casanova

    • status: open --> closed-fixed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks