Marcin Szamotulski wrote:

> I wrote a patch to reuse an argument list from different window.
> I think it is useful to have a way of setting an argument list from
> a different window [tab page].  One scenario where it is useful is when
> a window has global argument list and one makes a ':split|argl' and
> after a while one would like to reuse the new local argument list somewhere
> else.  With the attached patch one can:
> 
> :call usearglist({winnr} [, {tabnr}])
> 
> to use the argument list from window number {winnr} (in tab page
> {tabnr}) in the current window.
> 
> The function returns 0 on success and -1 on error (window or tab page not
> found).

Hmm, it's a bit strange to have this as a function.  Otherwise setting
the argument list is done with commands.  E.g. :argglobal is similar,
but always switches to the global argument list.

We could use :{nr}arglocal instead.  The question is where the user gets
the {nr} from.  When using arglistid() this requires using :exe.  I
think we need a command to list all the arglists.

For a user who actually uses multiple arglists it would indeed be useful
to list the ones that are in use.  With a summary of the file names, and
which window/tab they are used in.


-- 
Your company is doomed if your primary product is overhead transparencies.
                                (Scott Adams - The Dilbert principle)

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

-- 
-- 
You received this message from the "vim_dev" 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 because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to