search

wsdjeg / vim-fetch

Make Vim handle line and column numbers in file names with a minimum of fuss
http://www.vim.org/scripts/script.php?script_id=5089
MIT License
312 stars 17 forks source link

Occasionally file decoding breaks #25

Open Avi-D-coder opened 4 years ago

Avi-D-coder commented 4 years ago

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. Screenshot_20191110_074120

Avi-D-coder commented 4 years ago

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.

Rafflesiaceae commented 1 year ago

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.

I'm pretty sure this can be closed @wsdjeg