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

Tie ws-butler-keep-whitespace-before-point to auto-save-visited-mode #7516

Open
4 tasks done
meedstrom opened this issue Oct 21, 2023 · 0 comments · May be fixed by #7843
Open
4 tasks done

Tie ws-butler-keep-whitespace-before-point to auto-save-visited-mode #7516

meedstrom opened this issue Oct 21, 2023 · 0 comments · May be fixed by #7843
Labels
is:bug Something isn't working as intended needs-triage Issue hasn't been assessed yet

Comments

@meedstrom
Copy link

meedstrom commented Oct 21, 2023

I confirm that...

  • I have searched the issue tracker, documentation, FAQ, Discourse, and Google, in case this issue has already been reported/resolved.

  • I have read "How to Debug Issues", and will use it to provide as much information about this issue as possible.

  • The issue can be reproduced on the latest available commit of Doom.

  • The issue can be reproduced on a stable release of Emacs, such as 27, 28, or 29. (Unstable versions end in .50, .60, or .9x)

Expected behavior

That as long as I've not manually called save, point should remain where it is unless I move it myself.

Current behavior

When auto-save-visited-mode is enabled, I constantly lose the space at the end of line that I'm typing.

This was pretty frustrating until I figured it out the fix some years back -- I'm sorry I'm only now filing the bug report.

Steps to reproduce

  1. M-x auto-save-visited-mode RET
  2. Open a new file.
  3. Type something and enter a space. Pause, as if to think what to type next :-)
  4. Watch point move after 5 seconds.

System Information

https://pastebin.com/VzJfcB7P

@meedstrom meedstrom added is:bug Something isn't working as intended needs-triage Issue hasn't been assessed yet labels Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:bug Something isn't working as intended needs-triage Issue hasn't been assessed yet
Projects
Status: Unreviewed
Development

Successfully merging a pull request may close this issue.

1 participant