search

atom / whitespace

Atom whitespace package
MIT License
94 stars 67 forks source link

Trailing spaces are removed even if the feature is disabled #152

Closed pmilx closed 7 years ago

pmilx commented 7 years ago

Description

Trailing spaces are removed even if the feature is disabled or if the whole core package 'whitespace' is disabled.

Steps to Reproduce

  1. Default behavior (Atom version 1.16.0 x64) - core package 'whitespace' is present by default.
  2. Happening in ES6 template string:

For example:

const example = sample text ;

When saved all trailing spaces after 'sample text' are removed.

Expected behavior: Trailing spaces are not automatically removed if the features is disabled (or if package 'whitespace' is disabled).

Actual behavior: Trailing whitespaces are always removed when file is saved.

Reproduces how often: Everytime.

Versions

Atom : 1.16.0 Electron: 1.3.13 Chrome : 52.0.2743.82 Node : 6.5.0

Win 10

Additional Information

N/A

winstliu commented 7 years ago

Does this happen in safe mode?

pmilx commented 7 years ago

Hi,

No it doesn’t happen in safe mode…

Thanks for your support!

Petr

From: Wliu [mailto:notifications@github.com] Sent: Friday, April 28, 2017 5:53 PM To: atom/whitespace whitespace@noreply.github.com Cc: Petr Milanov petr@ipfabric.io; Author author@noreply.github.com Subject: Re: [atom/whitespace] Trailing spaces are removed even if the feature is disabled (#152)

Does this happen in safe mode?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/atom/whitespace/issues/152#issuecomment-298035592, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aa2N_1K9y8VY_xnOU472oUlmGth0cAKcks5r0gtVgaJpZM4NLmf8.

winstliu commented 7 years ago

Thank you for reaching out!

Because this doesn't reproduce in Safe Mode, it would seem that what you're reporting isn't being caused by Atom itself but by a community package you have installed. It may be that there is still a bug in Atom. If so, we'll need the maintainer of the package that is causing the problem to help track that down.

What we need you to do is to figure out what community package is causing the problem. Some people have reported that using the package-cop package has been helpful, you may want to try it. Once you've determined what package is causing the problem, The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme so you can file this issue there.