Can vim be made to start with selected files already open?

[Eric Weir]

After starting vim I take a bit of time to load the base files I normally work with. It would be a minor convenience if vim could be made to start with these files already loaded. 

Can it be done? How?

Thanks,

------------------------------------------------------------------------------------------

Eric Weir

Decatur, GA  USA

[hidden email]

"Imagining the other is a powerful antidote to fanaticism and hatred." 

- Amos Oz

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[MarcWeber]

Excerpts from Eric Weir's message of Thu May 24 13:14:40 +0200 2012:
>
> After starting vim I take a bit of time to load the base files I
> normally work with. It would be a minor convenience if vim could be
> made to start with these files already loaded.

Option 1)
  github.com/MarcWeber/vim-addon-local-vimrc
  Then just put
  e foo.vim
  e bar.vim

  into the local .vimrc file.

Option 2)
:mksession and then source it

Option 3) use most recently used file plugin such as tmru
Then opening those files is a lot faster

Option 4)
Use faster ways to open files such as glob open provided in sample rc of
vim-addon-manager - or do :r! find then gf on a path ..

...

Additionally you may want to use tag files or gnu idutils to find the
file you're looking for faster.

I'm pretty sure there are many more options.

Marc Weber

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Michael Henry-5]

On 05/24/2012 07:14 AM, Eric Weir wrote:
>
> After starting vim I take a bit of time to load the base files
> I normally work with. It would be a minor convenience if vim
> could be made to start with these files already loaded.

There are lots of ways, and I'm sure others might suggest some
of them.  I routinely save my state before exiting Vim using
something like this::

  :mksession ~/SomeSessionName.vim
 
When I restart Vim, I manually reload my session like this::

  :source ~/SomeSessionName.vim

On the command line of Vim, you can specify a file to "source",
so you could do::

  vim -S ~/SomeSessionName.vim

If you get your set of open files and windows the way you like
them, you can save them with :mksession, then you can launch Vim
with ``-S`` to reload that sessions, using whatever means best
suits you and your environment (e.g., a shell script, alias,
batch file, desktop shortcut, etc.).

Michael Henry

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Tim Gray]

On May 24, 2012 at 07:14 AM -0400, Eric Weir wrote:
>After starting vim I take a bit of time to load the base files I
>normally work with. It would be a minor convenience if vim could be
>made to start with these files already loaded.

It's a bit different from what you are talking about, but you might want
to check out vim-session [1].  It let's you easily save everything in
your current session with a single command:

     SaveSession name

Then you can close it with:

     CloseSession name

And when you restart vim and you want your windows and files back
exactly like they were:

     OpenSession name

You can have multiple sessions saved as well.  It's built upon the
:mksession command.  It's very straightforward to use.

[1]: http://www.vim.org/scripts/script.php?script_id=3150

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Eric Weir]

On May 24, 2012, at 7:26 AM, Marc Weber wrote:

> Excerpts from Eric Weir's message of Thu May 24 13:14:40 +0200 2012:
>>
>> After starting vim I take a bit of time to load the base files I
>> normally work with. It would be a minor convenience if vim could be
>> made to start with these files already loaded.
>
> Option 1)
>  github.com/MarcWeber/vim-addon-local-vimrc
>  Then just put
>  e foo.vim
>  e bar.vim
>
>  into the local .vimrc file.

Thank you Marc. You forget that I'm an idiot. I understand very little of the language you guys speak. I read the readme for this but I understood very little of it either. This is not backhanded criticism. Just stating the facts. I appreciate your generosity, and when I do understand you're always very helpful.

> Option 2)
> :mksession and then source it

Others have made this suggestion. I'll be checking it out.

> Option 3) use most recently used file plugin such as tmru
> Then opening those files is a lot faster

I gave this a look. A bit uncertain whether it addresses my need.  

> Option 4)
> Use faster ways to open files such as glob open provided in sample rc of
> vim-addon-manager - or do :r! find then gf on a path ..

Again, Marc, I'm an idiot.

------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA
[hidden email]

"What is man without the beasts? If all the beasts were gone,
men would die from a great loneliness of spirit."

- Chief Seattle






--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Eric Weir]

On May 24, 2012, at 7:26 AM, Michael Henry wrote:

> On 05/24/2012 07:14 AM, Eric Weir wrote:
>>
>> After starting vim I take a bit of time to load the base files
>> I normally work with. It would be a minor convenience if vim
>> could be made to start with these files already loaded.
>
> There are lots of ways, and I'm sure others might suggest some
> of them.  I routinely save my state before exiting Vim using
> something like this::
>
>  :mksession ~/SomeSessionName.vim
>
> When I restart Vim, I manually reload my session like this::
>
>  :source ~/SomeSessionName.vim
>
> On the command line of Vim, you can specify a file to "source",
> so you could do::
>
>  vim -S ~/SomeSessionName.vim

Thanks, Henry. Gave this a try. Does exactly what I want. Wish there were a shorthand way to execute the commands, but it's pretty simple otherwise.

> If you get your set of open files and windows the way you like
> them, you can save them with :mksession, then you can launch Vim
> with ``-S`` to reload that sessions, using whatever means best
> suits you and your environment (e.g., a shell script, alias,
> batch file, desktop shortcut, etc.).

I take it all these involve use of the terminal. I've never started vim [MacVim] from terminal. Curious about the last three options, though.

------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA
[hidden email]

"Everywhere the crisis of the private financial system
has been transformed into a tale of slovenly and overweening government
that perpetuates and is perpetuated by a dependent and demanding population."

- Marilynne Robinson



--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[scott-268]

On Tue, Jun 05, 2012 at 05:12:13PM -0400, Eric Weir wrote:

> On May 24, 2012, at 7:26 AM, Marc Weber wrote:

> > Excerpts from Eric Weir's message of Thu May 24 13:14:40 +0200 2012:
> >>
> >> After starting vim I take a bit of time to load the base files I
> >> normally work with. It would be a minor convenience if vim could be
> >> made to start with these files already loaded.
> >
> > Option 1)
> >  github.com/MarcWeber/vim-addon-local-vimrc
> >  Then just put
> >  e foo.vim
> >  e bar.vim
> >
> >  into the local .vimrc file.

> Thank you Marc. You forget that I'm an idiot. I understand very little of the language you guys speak. I read the readme for this but I understood very little of it either. This is not backhanded criticism. Just stating the facts. I appreciate your generosity, and when I do understand you're always very helpful.

> > Option 2)
> > :mksession and then source it

> Others have made this suggestion. I'll be checking it out.

The thing I don't like about session files is they save a whole lot
more than just the buffer list.  Every setting is saved, and if
between uses you change something in your .vimrc, it will be over-
ridden by the session file.

My favorite way of addressing this is to create two modules specific
to the project.  First, for example, I would create a module 'fb' on
my ~/bin path and make it executable.  It would contain something
simple like

    #!/bin/bash
    gvim -S ~/.vim/foobar.vim

Then in my ~/.vim path I would create a module called foobar.vim
containing the list of files I want to start with for the foobar
project, as follows:

    badd foo.vim
    badd bar.vim

This gives you control over what opens, uses the settings in your
.vimrc, and leaves vim alone to be used for other projects without
those files being opened

> > Option 3) use most recently used file plugin such as tmru
> > Then opening those files is a lot faster

> I gave this a look. A bit uncertain whether it addresses my need.  

I try to avoid all plugins -- they are a source of unexpected
behavior.

sc

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Eric Weir]

On May 24, 2012, at 8:24 AM, Tim Gray wrote:

> On May 24, 2012 at 07:14 AM -0400, Eric Weir wrote:
>> After starting vim I take a bit of time to load the base files I normally work with. It would be a minor convenience if vim could be made to start with these files already loaded.
>
> It's a bit different from what you are talking about, but you might want to check out vim-session [1].  It let's you easily save everything in your current session with a single command:
>
> [...]
>
> [1]: http://www.vim.org/scripts/script.php?script_id=3150

Looks interesting, Tim. Soon as I can get vim-addons-manager to install it I'll give it a try. At this point at least the built-in :mksession does what I wanted to do. The advantage of this for me is that I could have it automatically load a default saved session.

Thanks,
------------------------------------------------------------------------------------------
Eric Weir
[hidden email]

"Human coexistence and social life constitute the good common to us all
from which and thanks to which all cultural and social goods derive."

- Zygmunt Bauman

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Ben Fritz]

On Tuesday, June 5, 2012 4:33:17 PM UTC-5, sc wrote:
>
> The thing I don't like about session files is they save a whole lot
> more than just the buffer list.  Every setting is saved, and if
> between uses you change something in your .vimrc, it will be over-
> ridden by the session file.
>

:help 'sessionoptions'

>
> I try to avoid all plugins -- they are a source of unexpected
> behavior.
>

That seems a bit extreme. While I like making my own customizations when I can, if someone else has already solved a difficult problem I'd rather use their solution and send them fixes if I find problems, than struggle to come up with a partial solution that fails in corner cases they've already worked out.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Eric Weir]

On May 24, 2012, at 7:26 AM, Michael Henry wrote:

> There are lots of ways, and I'm sure others might suggest some
> of them.  I routinely save my state before exiting Vim using
> something like this::
>
>  :mksession ~/SomeSessionName.vim
>
> When I restart Vim, I manually reload my session like this::
>
>  :source ~/SomeSessionName.vim

Weird. When I do :mksession ~\startup.vim a second time, i.e., after having quit vim and restarting, I get a message saying the file exists and to add "!" to overwrite. When I do that, however, the file gets saved as startup.vim! Then on the next source it loads the previous session, not the last one.

------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA
[hidden email]

"Style is truth."

- Ray Bradbury

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[MarcWeber]

> Thank you Marc. You forget that I'm an idiot. I understand very little
> of the language you guys speak. I read the readme for this but I
> understood very little of it either. This is not backhanded criticism.
> Just stating the facts. I appreciate your generosity, and when I do
> understand you're always very helpful.

mkdir my-dir
echo 'e /tmp/foo.txt' >  my-dir/.vimrc
cd my-dir
vim

Then Vim will ask:
(Do you want to source my-dir/.vimrc? [y/n])

But it'll ask this once only.

 
> > Option 4)
> > Use faster ways to open files such as glob open provided in sample rc of
> > vim-addon-manager - or do :r! find then gf on a path ..

fast glob implementation (requires tlib library):

  fun! FastGlob(glob)
    let g = '^'.a:glob.'$'
    let replace = {'**': '.*','*': '[^/\\]*','.': '\.'}
    let g = substitute(g, '\(\*\*\|\*\|\.\)', '\='.string(replace).'[submatch(1)]','g')
    let cmd = 'find | grep -e '.shellescape(g)
    " let exclude = a:exclude_pattern == ''? '' : ' | grep -v -e '.shellescape(a:exclude_pattern)
    " let cmd .= exclude
    return system(cmd)
  endf
  noremap \go :exec 'e '. fnameescape(tlib#input#List('s','select file', split(FastGlob(input('glob pattern, curr dir:','**/*')),"\n") ))<cr>


  :r! find
  This command just runs finds and insterts its output into the currernt
  buffer. r means read. Then you can use / ? vim search and gf to open
  the files being represented as names in the current buffer by.


If you say "I'm an idiot" you speak a language I don't understand. It
does not tell me where to start explaining what I'm talking about.

Marc Weber

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Christian Brabandt]

On Wed, June 6, 2012 01:02, Eric Weir wrote:

>
> On May 24, 2012, at 7:26 AM, Michael Henry wrote:
>
>> There are lots of ways, and I'm sure others might suggest some
>> of them.  I routinely save my state before exiting Vim using
>> something like this::
>>
>>  :mksession ~/SomeSessionName.vim
>>
>> When I restart Vim, I manually reload my session like this::
>>
>>  :source ~/SomeSessionName.vim
>
> Weird. When I do :mksession ~\startup.vim a second time, i.e., after
> having quit vim and restarting, I get a message saying the file exists and
> to add "!" to overwrite. When I do that, however, the file gets saved as
> startup.vim! Then on the next source it loads the previous session, not
> the last one.

You need to add the ! to the mksession command, not to the file name ;)

regards,
Christian

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Christian Brabandt]

On Wed, June 6, 2012 06:41, Marc Weber wrote:

>> Thank you Marc. You forget that I'm an idiot. I understand very little
>> of the language you guys speak. I read the readme for this but I
>> understood very little of it either. This is not backhanded criticism.
>> Just stating the facts. I appreciate your generosity, and when I do
>> understand you're always very helpful.
>
> mkdir my-dir
> echo 'e /tmp/foo.txt' >  my-dir/.vimrc
> cd my-dir
> vim
>
> Then Vim will ask:
> (Do you want to source my-dir/.vimrc? [y/n])
>
> But it'll ask this once only.
>
>
>> > Option 4)
>> > Use faster ways to open files such as glob open provided in sample rc
>> of
>> > vim-addon-manager - or do :r! find then gf on a path ..
>
> fast glob implementation (requires tlib library):
>
>   fun! FastGlob(glob)
>     let g = '^'.a:glob.'$'
>     let replace = {'**': '.*','*': '[^/\\]*','.': '\.'}
>     let g = substitute(g, '\(\*\*\|\*\|\.\)',
> '\='.string(replace).'[submatch(1)]','g')
>     let cmd = 'find | grep -e '.shellescape(g)
>     " let exclude = a:exclude_pattern == ''? '' : ' | grep -v -e
> '.shellescape(a:exclude_pattern)
>     " let cmd .= exclude
>     return system(cmd)
>   endf
>   noremap \go :exec 'e '. fnameescape(tlib#input#List('s','select file',
> split(FastGlob(input('glob pattern, curr dir:','**/*')),"\n") ))<cr>

I think you'll be faster, not to use an extra grep command, but rather
use finds -name/-regex switch

regards,
Christian

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Christian Brabandt]

On Tue, June 5, 2012 23:39, Eric Weir wrote:
> I'll give it a try. At this point at least the built-in :mksession does
> what I wanted to do. The advantage of this for me is that I could have it
> automatically load a default saved session.

You seem to be fine with session files, but I think, I also mention
that you can store the buffer list in your .viminfo file, if you add
the '%' to the 'viminfo' setting. Additionally, you can always edit
the file you have previously edited using the :oldfiles command.

For more info on both of this, read
:h 21.3

regards,
Christian

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[孔晓泉]

maybe you can alias vimf='vim -o5 xx.file1 file2 file3 file4' ,then
you type vimf

2012/6/6 Christian Brabandt <[hidden email]>:

> On Tue, June 5, 2012 23:39, Eric Weir wrote:
>> I'll give it a try. At this point at least the built-in :mksession does
>> what I wanted to do. The advantage of this for me is that I could have it
>> automatically load a default saved session.
>
> You seem to be fine with session files, but I think, I also mention
> that you can store the buffer list in your .viminfo file, if you add
> the '%' to the 'viminfo' setting. Additionally, you can always edit
> the file you have previously edited using the :oldfiles command.
>
> For more info on both of this, read
> :h 21.3
>
> regards,
> Christian
>
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Michael Henry-5]

On 06/06/2012 03:57 AM, Christian Brabandt wrote:

> On Wed, June 6, 2012 01:02, Eric Weir wrote:
>>
>> On May 24, 2012, at 7:26 AM, Michael Henry wrote:
>>
>>> :mksession ~/SomeSessionName.vim
>>
>> Weird. When I do :mksession ~\startup.vim a second time, i.e., after
>> having quit vim and restarting, I get a message saying the file exists and
>> to add "!" to overwrite. When I do that, however, the file gets saved as
>> startup.vim! Then on the next source it loads the previous session, not
>> the last one.
>
> You need to add the ! to the mksession command, not to the file name ;)

Yes, I typically use the "!" as Christian suggests.  Since I
generally save my state to a single session file, I have it in
my Vim command-line history.  So I really just press ":mk" and
then press the up-arrow key to recall the most recent
":mksession" command, which in my case is::

  :mksession! ~/vim/Session.vim

Similarly, my most common use of the :source command is to
restore the above session, so I use command-line history to
bring it back.  I press ":so" and the up-arrow, and the first
recalled command is almost always::

  :source ~/vim/Session.vim

I keep session files by convention in ~/vim.  If you intend to
use the same session file routinely, I think you'd find that
it's pretty quick to use the history as I do.  But you could
also define your own custom commands to do it, perhaps by adding
something like the following to your ~/.vimrc::

  command! SS mksession! ~/vim/Session.vim

Then you could do :SS to save a session.  You could add a
similar command to restore (or load) a session::

  command! LS source ~/vim/Session.vim

Even if you define your own commands, I recommend trying the
command-line history feature.  It's very useful to be able to
find the most recent command of a given type.  For example,
after a global replace operation like this::

  :%s/old text/new text/g

I frequently want to do a similar operation.  Pressing ":%" and
the up-arrow lets me find and adjust a previous command that's
similar to what I want without retyping it all again.  (If you
want to repeat the previous replacement exactly, Vim has the
two-character "g&" sequence that's faster.  Similar comments
apply for other specific commands, but the history mechanism is
pretty useful in general.)

Also, as mentioned by Ben Fritz, you can adjust what is saved in
a session file by ":mksession".  In my ~/.vimrc, I have the
following:

  set sessionoptions=blank,buffers,curdir,folds,help,resize,slash
            \,tabpages,unix,winpos,winsize

This keeps my session files from having Vim options that would
typically be in the ~/.vimrc, while preserving things like the
window layout, the cursor positions in the buffers, etc.

Michael Henry

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Michael Henry-5]

On 06/05/2012 05:21 PM, Eric Weir wrote:
>> If you get your set of open files and windows the way you like
>> them, you can save them with :mksession, then you can launch Vim
>> with ``-S`` to reload that sessions, using whatever means best
>> suits you and your environment (e.g., a shell script, alias,
>> batch file, desktop shortcut, etc.).
>
> I take it all these involve use of the terminal. I've never
> started vim [MacVim] from terminal. Curious about the last
> three options, though.

I listed a bunch of options without knowing your environment,
but since you're on a Mac, you could use a shell script, an
alias, or an icon on your desktop.  The icon might be your
preferred approach.  If you can make a copy your MacVim icon,
you can adjust the command line to include the extra couple of
arguments.  I don't have a Mac; perhaps someone else can give
more specific advice on the mechanics of cloning an icon and
changing the command-line.  You'd be looking to change from
the original command line (guessing here)::

  /usr/bin/mvim

to something like this::

  /usr/bin/mvim -S ~/vim/Session.vim

Then, when you launch MacVim with this new icon, your previously
saved session will be restored.

Michael Henry

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Eric Weir]

First, I want to thank everyone who responded on this thread, and to apologize for taking so long to get around to responding. After raising the issue, other things became higher priority, and I just didn't have time to respond to all the interesting suggestions.

In the interim I did encounter one of the problems with 'mksession' that was mentioned, i.e., that it preserves all your vim settings as of the time it was executed, and when the file is sourced it will override any changes to the settings subsequent to executing 'mksession'. In trying to diagnose a problem I was having I was experimenting with disabling plugins or changing items in my .vimrc relating to them, then restarting vim. At first I continued sourcing the 'mksession' file after restarting, till I realized it was overwriting the changes I had made. So I'd like to find a method that avoids this problem.

On Jun 6, 2012, at 4:24 AM, Christian Brabandt wrote:

> On Tue, June 5, 2012 23:39, Eric Weir wrote:
>> I'll give it a try. At this point at least the built-in :mksession does
>> what I wanted to do. The advantage of this for me is that I could have it
>> automatically load a default saved session.
>
> You seem to be fine with session files, but I think, I also mention
> that you can store the buffer list in your .viminfo file, if you add
> the '%' to the 'viminfo' setting. Additionally, you can always edit
> the file you have previously edited using the :oldfiles command.
>
> For more info on both of this, read
> :h 21.3

I'm guessing that saving the buffer list will avoid the problem I describe above, but also that I wouldn't want to save everything in the buffer, just a few items. ? But I will check it out. Thanks for the suggestion.

------------------------------------------------------------------------------------------
Eric Weir
[hidden email]

"Any assurance economists pretend to with
regard to cause and effect is merely a pose."

- Emanuel Derman






--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Eric Weir]

On Jun 6, 2012, at 12:41 AM, Marc Weber wrote:

>> Thank you Marc. You forget that I'm an idiot. I understand very little
>> of the language you guys speak. I read the readme for this but I
>> understood very little of it either. This is not backhanded criticism.
>> Just stating the facts. I appreciate your generosity, and when I do
>> understand you're always very helpful.
>
> mkdir my-dir
> echo 'e /tmp/foo.txt' >  my-dir/.vimrc
> cd my-dir
> vim
>
> Then Vim will ask:
> (Do you want to source my-dir/.vimrc? [y/n])
>
> But it'll ask this once only.

Thanks, Marc. Not sure I understand. It would create a temporary .vimrc? Not sure how it helps me. I just want to load a few files---always the same few files---as simply as possible immediately after starting vim. Most of the time. Not all the time. Also, I gather it's done from terminal. I rarely use terminal, and never to start vim.

>>> Option 4)
>>> Use faster ways to open files such as glob open provided in sample rc of
>>> vim-addon-manager - or do :r! find then gf on a path ..
>
> fast glob implementation (requires tlib library):
>
>  fun! FastGlob(glob)
>    let g = '^'.a:glob.'$'
>    let replace = {'**': '.*','*': '[^/\\]*','.': '\.'}
>    let g = substitute(g, '\(\*\*\|\*\|\.\)', '\='.string(replace).'[submatch(1)]','g')
>    let cmd = 'find | grep -e '.shellescape(g)
>    " let exclude = a:exclude_pattern == ''? '' : ' | grep -v -e '.shellescape(a:exclude_pattern)
>    " let cmd .= exclude
>    return system(cmd)
>  endf
>  noremap \go :exec 'e '. fnameescape(tlib#input#List('s','select file', split(FastGlob(input('glob pattern, curr dir:','**/*')),"\n") ))<cr>
>
>
>  :r! find
>  This command just runs finds and insterts its output into the currernt
>  buffer. r means read. Then you can use / ? vim search and gf to open
>  the files being represented as names in the current buffer by.

I think maybe I wasn't clear in describing what I want to do. As mentioned above, I just want to load an identified set of files, usually the same set of files, as simply as possible immediately after after starting vim. The situation is not one of having to identify or locate files. But of loading files whose names and locations I know.

Previously I've been doing this by navigating to the files using the Ex or Tex commands, which, when there are four or five files, is unnecessarily complicated and time-consuming.

> If you say "I'm an idiot" you speak a language I don't understand. It
> does not tell me where to start explaining what I'm talking about.

You are right. I will be more specific in the future.

Regards,
------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA
[hidden email]

"Style is truth."

- Ray Bradbury

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

[Eric Weir]

On Jun 6, 2012, at 4:47 AM, 孔晓泉 wrote:

> maybe you can alias vimf='vim -o5 xx.file1 file2 file3 file4' ,then
> you type vimf

Thanks for the suggestion. Is it really that simple? If so, it might meet my need. Would I need to include the path to the files? And what does the "-o5" part do?

I looked for help with aliases in the Oualline book, but didn't find anything. Help brought up "antialias," nothing on "alias." [I'm sure it's there somewhere. I just need to look harder.]
------------------------------------------------------------------------------------------
Eric Weir
[hidden email]

"Any assurance economists pretend to with
regard to cause and effect is merely a pose."

- Emanuel Derman






--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php