You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this case nvim src/lib.rs:121:23 broke everything, but nvim src/lib.rs:121:23: and nvim src/lib.rs:121:22 worked. Sometimes the trailing colon causes breaks to. The files are standard UTF-8 ASCII characters only.
The text was updated successfully, but these errors were encountered:
To reproduce run nvim --> afile:1:1 a file called afile:1:1 will recreated it will be corrupt. If you then run the correct command nvim afile:1:1 you will open that corrupt file.
In this case nvim src/lib.rs:121:23 broke everything, but nvim src/lib.rs:121:23: and nvim src/lib.rs:121:22 worked. Sometimes the trailing colon causes breaks to.
What does breaking mean here? In what way does it break?
To reproduce run nvim --> afile:1:1 a file called afile:1:1 will recreated it will be corrupt. If you then run the correct command nvim afile:1:1 you will open that corrupt file.
I don't see anything wrong here, you are redirecting the raw terminal output of nvim -- to a new file afile:1:1 and then opening the file with nvim. I can't tell what you expected to happen instead, but there's no issue here.
In this case
![Screenshot_20191110_074120](https://user-images.githubusercontent.com/29133776/68544149-31904800-038e-11ea-8f77-8a156f1a93e0.png)
nvim src/lib.rs:121:23
broke everything, butnvim src/lib.rs:121:23:
andnvim src/lib.rs:121:22
worked. Sometimes the trailing colon causes breaks to. The files are standard UTF-8 ASCII characters only.The text was updated successfully, but these errors were encountered: