You mean 'G' command ?
I write a single script to get quickfix autoscroll, problem seems have been
solved
by 'normal G' with 'windo'.but the cursor seems a little strange:
1. blinks in a strange frequency: sometimes fast and sometimes slow
2. 'moving cursor to quickfix window and back' is
Xavier de Gaye wrote:
> On 06/05/2016 04:11 PM, Bram Moolenaar wrote:
> >> Xavier de Gaye wrote:
> >>
> >>> Two pyclewn tests fail after patch 7.4.1891. It seems that not all
> 'insert'
> >>> function messages are matched with a reply from Vim after this patch.
> >>> This happens with a
I would reply to my first message if googlegroups would let me see it...
after I posted, the warnings stopped (g)
--
--
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
Patch 7.4.1905 (after 7.4.1903)
Problem:Some compilers can't handle a double semicolon.
Solution: Remove one semicolon.
Files: src/ex_cmds.c
*** ../vim-7.4.1904/src/ex_cmds.c 2016-06-06 21:07:48.383578685 +0200
--- src/ex_cmds.c 2016-06-06 21:37:15.511554377 +0200
skywind wrote:
> Since redirecting the job output to quickfix, I need quickfix window
> can scroll to the last line when a new text line added to quickfix.
>
> So I can always see the latest output of a long time running job in
> realtime.
>
> Previously I used `clast` after `caddexpr` in the
Patch 7.4.1904 (after 7.4.1903)
Problem:Build fails.
Solution: Add missing changes.
Files: src/vim.h
*** ../vim-7.4.1903/src/vim.h 2016-06-04 18:49:15.382070039 +0200
--- src/vim.h 2016-06-05 22:32:46.372697060 +0200
***
*** 1063,1069
#define OPENLINE_COM_LIST
Patch 7.4.1903
Problem:When writing viminfo merging current history with history in
viminfo may drop recent history entries.
Solution: Add new format for viminfo lines, use it for history entries. Use
a timestamp for ordering the entries. Add test_settime().
> The only pending action, as far as I'm concerned, but may be it's
> already possible through other means: can we have a addqfline(line)
> VimL function that applies to the line in order to extract all
> data relevant for the quickfix list/window and add that data to the
> quickfix list?
My
for a while now, and forgive me for not knowing exactly how long, I've
been getting warnings from GTK every time I start gvim:
-
(gvim:24943): Gtk-WARNING **: Theme directory actions/48 of theme breeze
Hi Bram,
> The problem I still have in the todo list is that a callback would be
> invoked recursively. Do you still see that problem?
I wouldn't say it was called recursively. Just re-entered. Like when we
re-enter a sigaction that hasn't finished when its signal is emitted multiple
times
10 matches
Mail list logo
