Friday, April 10, 2015

Re: quickfix information

On Friday, April 10, 2015 at 1:42:20 PM UTC-5, LCD 47 wrote:
> > I think the quickfix window title (:help w:quickfix_title) is also
> > saved with the list in recent versions of Vim.
>
> It isn't. The (relatively) recent patch about w:quickfix_title
> resolves a bug, where an existing w:quickfix_title would get erased by
> some operations. It has nothing to do with the actual contents of the
> quickfix lists / loclists.
>

What I meant was, :colder and :cnewer will somehow restore the w:quickfix_title as you cycle through the lists. In that way the title is "saved with the list".

I can't find the patch right now, did this make it in? I remember wanting to have this function.

> > You *might* be able to take advantage of this (especially since
> > project name and compilation mode would probably be useful in the
> > quickfix title as well).
> >
> > But maybe taking advantage of this would actually require the patch
> > from this todo item:
> >
> > Patch to allow setting w:quickfix_title via setqflist() and setloclist()
> > functions. (Christian Brabandt, 2013 May 8, update May 21)
>
> This allows you to set w:quickfix_title, which is later displayed
> on the status bar of the quickfix window. It doesn't allow you to save
> arbitrary data to quickfix lists / loclists.
>

Ah, but as long as you are OK with that information showing up in the title, if you can set w:quickfix_title to an arbitrary string, then you *can* store arbitrary data associated with a given quickfix list.

For example, if you set the w:quickfix_title to "make of PROJECT=myproj CONFIG=configname" then it would be easy to extract the desired information from the title.

It would have the effect of changing the quickfix title, so perhaps that isn't the best way to accomplish the task at hand; but it may work without any new changes to Vim.

It would be a nice addition, if we already have a w:quickfix_title variable that is associated with a given quickfix list (somehow), to have a dict variable of some kind also associated with the list, for the sake of storing arbitrary user (plugin) data. Then plugins could store enough information to re-run the command that created the list, for example.

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

No comments: