Re: jumping to errors in non-existent files

On Fri, Oct 1, 2010 at 7:30 PM, Jeff Perry <jeffsp@gmail.com> wrote:
>
> When I run my program from within vim
>
>      :./xyz
>
> and the program errors out with a runtime error, e.g.:
>
>     myprog: myprog.cpp:123: assertion 'x==1' failed
>
> vim tries to interpret the the output and jump to the offending line number.
>
> The problem is that in the example above it incorrectly interprets the filename as "myprog: myprog.cpp", so it opens a file with that name, which doesn't exist, and then tries to jump to line 123 in that non-existent file.
>
> My question is:  Where in vim is this behaviour specified and how can I tweak it to do the right thing?

See :help errorformat

Try,
:set efm=%*[^\ ]%f:%l:%m

--
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

jumping to errors in non-existent files

When I run my program from within vim

     :./xyz

and the program errors out with a runtime error, e.g.:

    myprog: myprog.cpp:123: assertion 'x==1' failed

vim tries to interpret the the output and jump to the offending line number.

The problem is that in the example above it incorrectly interprets the filename as "myprog: myprog.cpp", so it opens a file with that name, which doesn't exist, and then tries to jump to line 123 in that non-existent file.

My question is:  Where in vim is this behaviour specified and how can I tweak it to do the right thing?

--
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

cscope for directory names with spaces

Hello

Anyone has a solution for using cscope if your projects reside in a
directory whose name includes spaces ?

Looks like cscope outputs in vim:
E609: Cscope error: cscope: cannot read trailer offset from
file cscope.out

This issue is making me so nervous, it is so stupid to be unable to
search source code for this name-with-spaces reason.

Any ideas ?

Thank you,
Timothy Madden

--
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

How to get rid of folds in a session ?

Hello

I use a session for my project at work. The problem is if I ever use
folding in one of my tabs (perhaps to get an overview of my file at some
point) and save the session, than even if I open all the folds, reset
the fold method to manual, and save the session, the folds are always
there next day when I open the session again !

How can I get rid of them in my session ? As of now, I always think
twice before using folding in any of the files, because if I use them
for once, then they will persist in my session until I close the file ...

Thank you,
Timothy Madden

--
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

RE: Pain at Vim Tips wiki

Tony Mechelynck wrote:
> I notice that the "official" reason for removal of the Monaco
> skin is that "it is too complex" and that "elements on a wiki
> page could collide with each other in unexpected ways". That
> didn't prevent them from removing my beloved CologneBlue
> skin, already some time ago. OTOH I see a lot of talk about
> removing the Monaco skin, but the Monobook skin (which is
> supposedly "simpler") is totally left unmentioned. I'm
> crossing fingers and knocking on wood in the forlorn hope
> that this skin, at least, will remain as an option for
> logged-in users, but I won't mention it on that staff blog
> lest they become conscious of its existence and take it away
> too. (I already needed to re-opt-in to it twice after my
> login cookie had expired.)

No, after November 4 there will be NO chance of Monobook or any
other skin working, other than the new Wikia skin.

There is one exception. Monobook will be kept for Uncyclopedia,
a parody of Wikipedia: http://uncyclopedia.wikia.com/

> From what you're saying, I suppose that even if we found
> some other hosting space, installed Wikimedia software on it
> (and "our" choice of Wikimedia skins), and then migrated the
> existing wiki pages while deleting all old pages one by one
> in the process, some "well-intentioned" wikia meddler admin
> would quietly restore everything from history...

Yes, Wikia will simply revert any attempts to significantly
remove material, so they own us completely.

John

--
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

Re: gvim, how to search tab by name and then go to this tab?

On 30.09.2010 23:26, Simon Ruderich wrote:
> On Thu, Sep 30, 2010 at 11:24:52PM +0800, Zac Lee wrote:
>> gvim, how to search tab by name and then go to this tab?
>
> You shouldn't use tabs like in other text editors. To quote
> vimgor (the bot) in #vim:
>
> tabs
> Tab pages are not buffers, don't try to force them to act
> like buffers. Consider tab pages like viewports, layouts, or
> workspaces. Trying to setup 1 tab page == 1 buffer is an
> exercise in futility. Do ':set hidden' and get started. Get
> FuzzyFinder, LustyExplorer or BufExplorer to make getting
> around your buffers easier. See
> http://vim.wikia.com/wiki/Category:Tabs for more info.
>
> buffers
> For a quick intro to vim's windows, buffers, and tabs, see
> http://img200.imageshack.us/img200/9031/windowsv.png and
> http://vim.pastey.net/115548 See also ':help tab-page-intro'
> and ':help windows-intro'
>
> Better use buffers and tabs only if you need different "views" on
> some buffers in a window.

And how do I work with multiple open files like other editors ?

Timothy Madden

--
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

Re: Pain at Vim Tips wiki

Hi John :)

Well, I find these kind of changes plainly rude. And yes, I know that
sometimes it is the price you pay for having a good, free, reliable
service, but I still can't help thinking the same: rude.

--
Raúl "DervishD" Núñez de Arenas Coronado
Linux Registered User 88736 | http://www.dervishd.net
The revolution will not be televised

--
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