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

Editor Automatically Replacing Special Characters. #53495

Closed
rwatts3 opened this issue Jul 3, 2018 · 4 comments
Closed

Editor Automatically Replacing Special Characters. #53495

rwatts3 opened this issue Jul 3, 2018 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster

Comments

@rwatts3
Copy link

rwatts3 commented Jul 3, 2018

  • VSCode Version: Insiders 1.25
  • OS Version: Win 7

Steps to Reproduce:

  1. Special Characters such as ' or html characters within the editor
  2. Notice changes when diffing files for svn or git even if the file was not physically altered.

Does this issue occur when all extensions are disabled?: Yes

@vscodebot vscodebot bot added editor editor-find Editor find operations labels Jul 3, 2018
@rwatts3
Copy link
Author

rwatts3 commented Jul 3, 2018

This appears to be happening from the core editor somewhere around the sprint leading to 1.25.
I held off on submitting the issue thinking it would be resolved. However there are several projects where a line was changed without my input.

This is certainly a problem as it's not ideal to commit line changes that i'm not intending to implement. And I am therefore having to go back and check every project i've worked on in the past weeks as well as double check just about every file prior to making a commit to ensure that lines characters were not changed without my intention.

@alexdima
Copy link
Member

@rwatts3 Do you have a lot of files with mixed line endings in your projects? We normalize line endings inside a file (i.e. if some lines in the same file use CRLF and some other lines in the same file use LF we will count which one is predominant and normalize that when you change and save the file). But only in the case where you edit the file...

Can you include some steps to help me reproduce?

@alexdima alexdima added info-needed Issue requires more information from poster and removed editor editor-find Editor find operations labels Jul 26, 2018
@rwatts3
Copy link
Author

rwatts3 commented Jul 26, 2018

Hi I think this may be different from my initial stated problem.
But what you've just described certainly raises a concern for me.

I work in an environment where there are numerous developers over 100 different individuals that may checkout a project and conduct their work at any given point in time.

Not all of those developers are going to have a uniformed line ending setting. However I'm finding it really hard to believe why it would be a good idea to automatically tally up and select one without my direct approval or confirmation especially on something that will be committed and submitted to a repository and you generally do not see or notice that type of change.

This is very dangerous and I think it should be changed.

For example had I realized this was happening it could have solved an issue I had several weeks ago with a python script.

My co-worker sent me a python script to run that he committed to the repository and it completely failed when I attempted to run it. He uses sublime which didn't change his line endings automatically for him. I opened his script, and for some reason the line endings were changed and it took me 2 days to discover this change. It wasn't until I opened the script in sublime that I realized it worked.

I just don't see the benefit in changing files without a prompt for approval in the editor.

@alexdima
Copy link
Member

Duplicate of #127

@alexdima alexdima marked this as a duplicate of #127 Jul 27, 2018
@alexdima alexdima added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 27, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Sep 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

2 participants