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

Multiple arguments should be opened as multiple buffers #18

Open
ghost opened this issue Nov 8, 2017 · 4 comments
Open

Multiple arguments should be opened as multiple buffers #18

ghost opened this issue Nov 8, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Nov 8, 2017

This is more useful behaviour than matching against every regex.

E.g. if I have

$ v -l
2	~/.../json/navigation.json
1	~/.../app.js
0	~/.../sass/theme.sass

I want v app the to start vim with two buffers, one of ~/.../app.js and the other of ~/.../sass/theme.sass.

@shmup
Copy link

shmup commented Nov 8, 2017

That is more useful for you but in no way is that just generally more useful

$ v -l
2	~/foo/bar/nav.py
1	~/cat/dog/bar.py
0	~/pls/no/nav.py

I want to v bar nav and know I'm getting the right file, not open two in my buffers.

@ghost
Copy link
Author

ghost commented Nov 8, 2017

Regardless, with your current program, there's no way around opening multiple buffers.

However, you always have the option of v 'bar.*nav' for targeting specific files.

What if I have a file called barnav tho duh duh

v 'bar/nav'

I feel like the multiple buffers is much more useful, v doesn't even provide this functionality in any shape or form yet.

@shmup
Copy link

shmup commented Nov 8, 2017

What if I have a file called barnav tho

Today I am being edge case man

@ghost
Copy link
Author

ghost commented Nov 8, 2017

then change the regex, my point still stands (doesn't your suggested v bar nav match barnav too? what point are you trying to make...)

@ghost ghost mentioned this issue Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant