Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next-Bookmark command doesn't reset current-column for follow-on actions #14137

Closed
alankilborn opened this issue Sep 12, 2023 · 0 comments
Closed
Labels

Comments

@alankilborn
Copy link
Contributor

Steps to Reproduce the Issue

  1. Create this text:
gggg h i j k bug
llll m n o p
qqqq r s t u v

a b c D E F G H I J K L M bug
d e f g h i j k l m n o p
  1. Do a Mark operation for bug; checkmark only Bookmark line / Wrap around / Normal
  2. Move caret to line 1 column 1
  3. Press Shift+Alt+down two times
  4. Press * three times to obtain:
    image
  5. Press F2 to move to the next bookmark on line 5 -- (a single) caret will be in column 1 of line 5 after:
    image
  6. Press Shift+Alt+down (once)

Actual Behavior

a b and d e on lines 5-6 are (incorrectly) selected:

image

Expected Behavior

No text should be selected, but a skinny caret should be in col 1 of lines 5 and 6, like this:
image

Conclusion

If the Next Bookmark command is going to move the caret to column 1 of the subsequent bookmarked line, the code should also call SCI_CHOOSECARETX to "register" that column change.

Debug Information

Notepad++ v8.5.6 (64-bit)
Build time : Aug 15 2023 - 15:29:28
Path : C:\NotepadPlusPlus\Misc_NoBackup\Releases\npp.8.5.6\npp.8.5.6.portable.x64\notepad++.exe
Command Line : -titleAdd="8.5.6 64-bit" -multiInst
Admin mode : OFF
Local Conf mode : ON
Cloud Config : OFF
OS Name : Windows 11 Pro (64-bit)
OS Version : 22H2
OS Build : 22621.2134
Current ANSI codepage : 1252
Plugins :
mimeTools (2.9)
NppConverter (4.5)
NppExport (0.4)
PythonScript (3.0.16)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants