We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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)
That as long as I've not manually called save, point should remain where it is unless I move it myself.
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.
https://pastebin.com/VzJfcB7P
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
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
System Information
https://pastebin.com/VzJfcB7P
The text was updated successfully, but these errors were encountered: