On 22 May 2013, Christian Brabandt wrote:
> Hi LCD!
>
> On Mi, 22 Mai 2013, LCD 47 wrote:
> > On 22 May 2013, LCD 47 wrote:
> > [...]
> > > Excellent, thank you! I'll play with it for a while, then
> > > post my conclusions.
> >
> > There seems to be a bug in getlocstack(), it misses
Hi LCD!
On Mi, 22 Mai 2013, LCD 47 wrote:
> On 22 May 2013, LCD 47 wrote:
> [...]
> > Excellent, thank you! I'll play with it for a while, then post my
> > conclusions.
>
> There seems to be a bug in getlocstack(), it misses the first entry.
> Example: after a single run of syntastic ch
On 21 May 2013, Christian Brabandt wrote:
[...]
> getlocstack() returns the location list stack as list
> getlocstackptr() returns the current position in the location list stack
> getloctitle() returns a list of titles for the location list stack
> getqfstack() returns the q
On 21 May 2013, Christian Brabandt wrote:
>
> On Mi, 22 Mai 2013, LCD 47 wrote:
>
> > I see. Can you please post that as a single patch, against a
> > well-defined version of Vim? There are several versions floating around
> > by now, and figguring out which pieces are still current and wh
On Mi, 22 Mai 2013, LCD 47 wrote:
> I see. Can you please post that as a single patch, against a
> well-defined version of Vim? There are several versions floating around
> by now, and figguring out which pieces are still current and which are
> obsolete is, well, too complex a task for my
On 21 May 2013, Christian Brabandt wrote:
> Hi vim-dev!
>
> On Di, 21 Mai 2013, Christian Brabandt wrote:
>
> > Hi LCD!
> >
> > On Di, 21 Mai 2013, LCD 47 wrote:
> >
> > > On 21 May 2013, Christian Brabandt wrote:
> > > [...]
> > > > Attached is an updated patch. It adds the following functio
Hi vim-dev!
On Di, 21 Mai 2013, Christian Brabandt wrote:
> Hi LCD!
>
> On Di, 21 Mai 2013, LCD 47 wrote:
>
> > On 21 May 2013, Christian Brabandt wrote:
> > [...]
> > > Attached is an updated patch. It adds the following functions:
> > >
> > > getlocstack() returns the location list st
Hi LCD!
On Di, 21 Mai 2013, LCD 47 wrote:
> On 21 May 2013, Christian Brabandt wrote:
> [...]
> > Attached is an updated patch. It adds the following functions:
> >
> > getlocstack() returns the location list stack as list
> > getlocstackptr() returns the current position in the locati
On 21 May 2013, Christian Brabandt wrote:
[...]
> Attached is an updated patch. It adds the following functions:
>
> getlocstack() returns the location list stack as list
> getlocstackptr() returns the current position in the location list stack
> getloctitle() returns a list of ti
On Do, 16 Mai 2013, LCD 47 wrote:
> On 15 May 2013, Christian Brabandt wrote:
> > Hi LCD!
> >
> > On Mi, 15 Mai 2013, LCD 47 wrote:
> >
> > > (1) getqfstack() / getlocstack() should simply return a list of
> > > loclists;
> > > (2) there should be a separate function for getting (and perha
On 15 May 2013, Christian Brabandt wrote:
> Hi LCD!
>
> On Mi, 15 Mai 2013, LCD 47 wrote:
>
> > (1) getqfstack() / getlocstack() should simply return a list of
> > loclists;
> > (2) there should be a separate function for getting (and perhaps
> > another one for setting) the stack pointe
Hi LCD!
On Mi, 15 Mai 2013, LCD 47 wrote:
> (1) getqfstack() / getlocstack() should simply return a list of
> loclists;
> (2) there should be a separate function for getting (and perhaps another
> one for setting) the stack pointer in these lists, namely a number
> in range 0 .. len(l
Christian Brabandt wrote:
> Hi Bram!
>
> On So, 12 Mai 2013, Bram Moolenaar wrote:
>
> >
> > Christian Brabandt wrote:
> >
> > > On So, 12 Mai 2013, Bram Moolenaar wrote:
> > >
> > > > Wouldn't it be better to have the entries and the titles in a list?
> > >
> > > We could do this as well.
On 14 May 2013, Christian Brabandt wrote:
> Here is an updated patch, containing setlocstack()/setqfstack() function
> and which also includes the title list suggestion. For some reason, the
> stack returned by getqfstack()/getlocstack() looks a little bit weird:
>
> Here an example for an empt
On Di, 14 Mai 2013, Christian Brabandt wrote:
> > Hmm, that's doable, but not simple. What if the returned structure
> > changes? It's probably better to add setlocstac().
>
> Here is an updated patch, containing setlocstack()/setqfstack() function
> and which also includes the title list sug
> :for id in range(10)
> exe printf("call setqflist(a.entry%d, '', a.title%d)", id,id)
> endfor
Even in this example lists would be more appropriate in place of `entry%d` keys.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
Hi Bram!
On So, 12 Mai 2013, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On So, 12 Mai 2013, Bram Moolenaar wrote:
> >
> > > Wouldn't it be better to have the entries and the titles in a list?
> >
> > We could do this as well. I don't mind.
> >
> > > If getqfstack() is to be us
Christian Brabandt wrote:
> On So, 12 Mai 2013, Bram Moolenaar wrote:
>
> > Wouldn't it be better to have the entries and the titles in a list?
>
> We could do this as well. I don't mind.
>
> > If getqfstack() is to be used to restore, how does one do that restore?
>
> The idea is to do somet
Hi Bram!
On So, 12 Mai 2013, Bram Moolenaar wrote:
> Wouldn't it be better to have the entries and the titles in a list?
We could do this as well. I don't mind.
> If getqfstack() is to be used to restore, how does one do that restore?
The idea is to do something like
" get location list stack
Christian Brabandt wrote:
> Bram,
> here is a patch, that returns the complete quickfix/location list stack.
> This is needed, so plugin writers can correctly handle quickfix and
> location lists.
> Currently, there is no way, to set the quickfix lists back to their
> original values (without
Bram,
here is a patch, that returns the complete quickfix/location list stack.
This is needed, so plugin writers can correctly handle quickfix and
location lists.
Currently, there is no way, to set the quickfix lists back to their
original values (without running through the complete stack (usin
21 matches
Mail list logo
