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

update point after backspacing and yanking while isearch is active #1643

Conversation

SequentialDesign
Copy link
Contributor

update point after backspacing and yanking while isearch is active

|
;; one test is what you need

(| is the point) with this patch, if you search for "ee" and then backspace, the point will move to the end of the word "one". in Lem currently, if you search for "ee" and then backspace, the point will stay after "ee", when I feel it should be at the end of "one" since the search string has changed. this patch also works when reverse searching

|
;; one test is what you need

(| is the point) with this patch, if "one test" is the current kill string and you yank, the point will move to after "one test". in Lem currently, the point will not move after yanking, which i don't think is natural

|
;; one test is what you need

(| is the point) with this patch, if you search for "ee" and then backspace, the point will move to the end of the word "one".   in Lem currently, if you search for "ee" and then backspace, the point will stay after "ee", when I feel it should be at the end of "one" since the search string has changed.  this patch also works when reverse searching

|
;; one test is what you need

(| is the point)  with this patch, if  "one test" is the current kill string and you yank, the point will move to after "one test".  in Lem currently, the point will not move after yanking, which i don't think is natural
@cxxxr cxxxr merged commit 7029aee into lem-project:main Nov 27, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants