Thursday, September 18, 2014

Re: Parse an error log and go to the line indicated as being the error?

>On Thu, Sep 18, 2014 at 2:46 PM, David Woodfall <dave@dawoodfall.net> wrote:
>
>> Thanks by the way.
>>
>> Solved that by removing sed and tee at the end of the ucc command in
>> my make script.
>>
>> One little niggle remains. After make there is and extra screen that
>> prints:
>>
>> (1 of 137): --------------------Core--------------------^M
>> Press ENTER or type command to continue
>>
>> On a successful build. It means having to press return twice to get
>> back to my file.
>
>You are welcome! Sorry about top-posting in my previous note. Gmail
>makes it inconvenient to bottom-post, and sometimes I forget.
>
>Try
>
>:set cmdheight=5
>
>If that works, then you can try more reasonable values, like 2 or 3,
>to see what works.

Yep. I like it at 1 as I prefer more space for editing, so I made a
function:

if !exists("*MakeUT2")
function! MakeUT2()
write
set cmdheight=3
make
set cmdheight=1
endfun
endif

Thanks

-Dave

>:helpgrep Press ENTER
>
>HTH
>--
>Benji Fisher

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

Post a Comment