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

Navigating by word in notepad reports incorrectly when encountering space followed by certain symbols #1656

Closed
nvaccessAuto opened this Issue Jul 8, 2011 · 4 comments

Comments

Projects
None yet
2 participants
@nvaccessAuto

nvaccessAuto commented Jul 8, 2011

Reported by tspivey on 2011-07-08 07:28
In notepad, navigate this by word:

/l /nfl /ndl /np

It treats the entire string as a word, instead of stopping at the slashes.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Jul 8, 2011

Comment 1 by jteh on 2011-07-08 08:11
It seems that uniscribe doesn't treat a space followed by a slash as a word break, but Edit controls do.
Changes:
Changed title from "Navigating by word in notepad treats entire string as word" to "Navigating by word in notepad reports incorrectly when encountering space followed by slash"

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Sep 6, 2011

Comment 2 by jteh on 2011-09-06 22:11
#1753 notes that this also occurs with "."; e.g. "a .b"
Changes:
Changed title from "Navigating by word in notepad reports incorrectly when encountering space followed by slash" to "Navigating by word in notepad reports incorrectly when encountering space followed by certain symbols"

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 6, 2012

Comment 3 by jteh on 2012-04-06 12:32
This really is annoying and I doubt any editable text field would follow the apparent default uniscribe behaviour.
Changes:
Milestone changed from None to 2012.2

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 18, 2012

Comment 5 by jteh on 2012-04-18 10:16
Fixed in e73058f.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment