Trailing whitespaces trimmed with `Keep Markdown Line Break Whitespace` option
See original GitHub issueHi everyone,
I know this has been a topic of discussion some months ago (see #115 and the FAQ), however it is not clear to me whether the package is in sync with the whitespace
package option Keep Markdown Line Break Whitespace
.
I have been discussing this with the whitespace
maintainers here and from our test it seems that the problem is related with this package which does not “parse” the Keep Markdown Line Break Whitespace
option.
This new option should avoid users to add
'*':
# all current config
'.md.text':
whitespace:
removeTrailingWhitespace: false
in the config.cson
. Am I right?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How do you remove trailing spaces in all files except ...
removes trailing white space when files are saved, or Shift + Alt + F is used to format a file, but this breaks...
Read more >Trailing whitespace in Markdown (.md) files is not removed on ...
Uncheck "Always keep trailing spaces on caret line". ... The trailing whitespaces are not removed and they show up as big ugly red...
Read more >What's the simplest way to strip trailing whitespace from all ...
Use a keybinding to strip all trailing whitespace ... Removes superfluous white space from the end of a line function!
Read more >Trailing Spaces - Visual Studio Marketplace
VS Code provides a way to automate deletion of trailing spaces by using the Trim Trailing Whitespace command. Depending on your settings, ...
Read more >How do I automatically trim trailing whitespace with Notepad++?
Under the "Macro" menu there's an option for "Trim trailing and save". If you need to do a regular expression it may be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It is related to this issue on the whitespace package. It checks whether the document scope matches that set by Atom’s default language-gfm package, and not for the default scope from language-markdown.
I can make/submit the PR that’s suggested in that thread, but it will have to wait until I’m less busy with my normal work. If that PR is accepted, it should indeed remove the need for the setting you quoted.
PR has been merged. I expect it to be part of the next update of Atom