我在天马彩票平台输了三十万I use Bash. When I'm looking for files, often I'll do the following:
find -name stackexchange.hs
我在天马彩票平台输了三十万And often the results will look like:
/youre/the/man/now/dog/stackexchange.hs /you/are/no/longer/the/dog/dog/stackexchange.hs /this/is/the/file/i/want/stackexchange.hs
Then I'll want to do one of the following:
- Option 1: Open the last item in the list of results in vim.
- Option 2: Open the Nth item in the list of results in vim.
Currently, I cut-and-paste with the mouse. Which brings me to my question:
- Is there an easy, one-liner to accomplish options 1&2? Note that this is occurring after the
- Is there a way to capture N-lines from stdout in some kind of bash vector/array?
$ find -name am_i_really_all_alone.txt ./borges/library/you_are_not_alone.txt ./borges/library/am_i_really_all_alone.txt $ vim (N)
我在天马彩票平台输了三十万(syntax and semantics may differ, but you get the point)
There seem to be several similar questions. Here are my perceived我在天马彩票平台输了三十万 differences (I am open to enlightenment):
- "Open File Found with find Command" focuses on creating a one-line to pipe a file name from
vim(or whatever). In my case, I want to
findfirst, pipe later (so to speak). My capture / usage happens strictly after.
- "Reuse Last Output From Command Lind" seems bang-on, but seems to simply repeat the command and doesn't speak to capturing the Nth line of output. Quite frankly, it scares me.
- "Capture Multi-Line Output of a Bash Builtin" is close, but not quite there.
- "What is the exact difference between terminal, shell, tty, console, etc." this one is really just a good read.
Thank you for your help! Having used *nix/BSD when I was a teenager in the 90s and getting scared away by calling my burnout, acid-head neighbour to help me install drivers for my plug-and-play sound card, I'm relieved to discuss command-line minutiae with (perceivably) less frightening individuals. It feels good to be back.