+03:00 Alexey Radkov :
> Hi Dominique.
>
> The situation this patch tries to fix appears when there are conceals
> _and_ cuc or colorcolumn is wrapped. I can reproduce it with the vim
> command you provided for the help files by narrowing the window width (no
> matter terminal or
Hi Dominique.
Thank you for testing this. The patch was missing a simple test in the
macro FIX_FOR_BOGUSCOLS. I added that in a new patch attached: now it
should work.
Cheers.
2015-07-12 5:33 GMT+03:00 Dominique Pellé :
> Dominique Pellé wrote:
>
> > Christian Brabandt wrote:
> >
> >> Hi Bram
e content of showbreaks are
counted as columns too: this make both printing column number at status
line and positioning of colorcolumn wrong (in my opinion), though it was
probably done by design (strange nevertheless).
2015-07-05 19:49 GMT+03:00 Bram Moolenaar :
>
> Alexey Radkov wrote:
Alas. Not so simple. This fix may break correct wrapping: see top 2 wrapped
lines in the attached image. Needs further investigations.
2015-07-04 0:43 GMT+03:00 Alexey Radkov :
> Hi.
>
> Here is a little patch that fixes broken visualization of cursorcolumn and
> colorcolumn when th
Here is a good solution that works for me:
http://www.nerdyweekly.com/posts/enable-italic-text-vim-tmux-gnome-terminal/
(see section 'vim')
2014-12-30 17:10 GMT+03:00 Jens Schweikhardt :
> All,
>
> it is my understanding (and please correct me) that the cterm has no
> support for italics being
use screen cells under
> any circumstances for the reasons explained above.
> 3. I think that things like Conque may also benefit from this, but they do
> not need screen cells as well.
>
> On July 4, 2014 6:00:06 PM GMT+03:00, Alexey Radkov <
> alexey.rad...@gmail.com> wrote:
&g
-07-04 14:05 GMT+04:00 Bram Moolenaar :
>
> Alexey Radkov wrote:
>
> > Now it accepts len in screen cells.
>
> Hmm, that's confusing. Suppose a script isolates a word that it wants
> to highlight. Then it's easy to locate the start of the word and the
> le
Now it accepts len in screen cells.
Cheers, Alexey.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subsc
Hi Christian.
2014-07-01 22:00 GMT+04:00 Christian Brabandt :
> Hi
>
> Disclaimer: I haven't looked into matchaddpo() yet, but plan to use it in
> several
> plugins I maintain.
>
> On Di, 01 Jul 2014, Bram Moolenaar wrote:
>
> > lcd wrote:
> >
> > > The initial motivation for adding the match
2014-07-01 22:51 GMT+04:00 LCD 47 :
> On 1 July 2014, Christian Brabandt wrote:
> [...]
> > BTW: what happens to the highlighting after one changes the
> > buffer? E.g. if I add a matchaddpos() at line 5, column 5 and
> > afterwards add a line below 3, will then line 6, column 5 be
> > highlighte
Never knew about this option. Thanks for the hint!
Setting scrolloff=200 really makes cursor fixed at the center of the window
and looks that the patch does not break anything in this case too: i
checked 1. braces on the same line, 2. braces on different lines, matching
paren is visible, 3. braces
and seems not to
break anything because matchparen never scrolls the window.
Cheers, Alexey.
2014-06-28 12:25 GMT+04:00 Alexey Radkov :
> Yet another patch update: properly initialize buffer b_mod_xlines = 0 when
> setting b_mod_set in match_add() and match_delete().
>
>
> 2014-
Yet another patch update: properly initialize buffer b_mod_xlines = 0 when
setting b_mod_set in match_add() and match_delete().
2014-06-27 21:23 GMT+04:00 Alexey Radkov :
> Update, Forgot parens in the patch.
>
>
> 2014-06-27 21:22 GMT+04:00 Alexey Radkov :
>
> Update, Fo
Update, Forgot parens in the patch.
2014-06-27 19:31 GMT+04:00 Alexey Radkov :
> Here is a better patch:
>
> matchaddpos() is unable to adjust highlights just like matchadd(), so the
> previous patch will bring the issue with Syntastic back. But we can check
> if buffer was chan
Update, Forgot parens in the patch.
2014-06-27 21:22 GMT+04:00 Alexey Radkov :
> Update, Forgot parens in the patch.
>
>
> 2014-06-27 19:31 GMT+04:00 Alexey Radkov :
>
> Here is a better patch:
>>
>> matchaddpos() is unable to adjust highlights just like matcha
matchparen fast.
2014-06-27 15:42 GMT+04:00 Alexey Radkov :
> I found the reason of this: patch 7.3.1203:
>
> набор изм-й: 4916:ba328b4a990e
> метка: v7-3-1203
> автор: Bram Moolenaar
> дата: Sat Jun 15 23:00:30 2013 +0200
> файлы: src/s
. Same line on the bottom: fast.
Cheers, Alexey.
2014-06-26 21:55 GMT+04:00 Alexey Radkov :
> Meanwhile i found an obvious reproducible effect: horizontal navigation
> (e.g. to the left and to the right) along a heavily loaded by parentheses
> line differs in speed which depends on whe
redraw at the slowest speed and this should prove that the
effect is really due to wrong/unexpected redrawing area (i.e. its bottom
line lasts to the bottom of the window/screen).
Cheers, Alexey.
2014-06-25 13:08 GMT+04:00 Alexey Radkov :
> Ok, I'll do this during this or the n
Ok, I'll do this during this or the next week.
Cheers, Alexey.
2014-06-23 23:11 GMT+04:00 Bram Moolenaar :
>
> Alexey Radkov wrote:
>
> > Here is some small improvements for the patch:
> >
> > src/window.c, match_add():
> > - removed unnecessary (after a
ter for Unicode texts like Cyrillics, i changed doc to
reflect this.
Cheers, Alexey.
2014-06-19 19:35 GMT+04:00 Alexey Radkov :
> Using alloc_clear() instead alloc() in match_add() proved to be a very
> good fix: sometimes i could have a segfault on vim's start without it
> (tod
Using alloc_clear() instead alloc() in match_add() proved to be a very good
fix: sometimes i could have a segfault on vim's start without it (today i
was lucky to catch a core dump on an older patch and gdb showed that the
reason was uninitialized m->pos array).
Also this allows removing line
m->
Hi all.
Indeed, variable nmatched may appear uninitialized in this implementation.
Dominique's patch is good for fixing this.
Cheers, Alexey.
2014-06-18 5:42 GMT+04:00 John Marriott :
> On 18-Jun-2014 8:35 AM, Dominique Pellé wrote:
>
>> ...
>> I can now reproduce the bug: current line not bei
Here is latest patch (with the failing test).
2014-06-02 18:08 GMT+04:00 Alexey Radkov :
>
>
>
> 2014-06-02 0:01 GMT+04:00 Bram Moolenaar :
>
>
>> Alexey Radkov wrote:
>>
>> > A new version: next_search_hl_pos() moved into next_search_hl().
>> > A
2014-06-02 0:01 GMT+04:00 Bram Moolenaar :
>
> Alexey Radkov wrote:
>
> > A new version: next_search_hl_pos() moved into next_search_hl().
> > A number of fixes added.
> > Docs were added too, here is an excerpt:
> >
> > matchaddpos({group}, {pos}[, {
.
Example: >
:highlight MyGroup ctermbg=green guibg=green
:let m = matchaddpos("MyGroup", [[23, 24], 34])
<Deletion of the pattern: >
:call matchdelete(m)
Still no tests, will add them soon.
2014-05-31 17:06 GMT+04:00 Alexey Radkov :
Hi Bram.
See my comments below.
2014-05-31 15:43 GMT+04:00 Bram Moolenaar :
>
> Alexey Radkov wrote:
>
> > This is a preliminary implementation of matchaddpos() that requires a
> list
> > of positions. See changes in matchparen.vim as example of using it. It
>
, docs etc.,
implement suggestions and send changes.
(Btw i do not understand difference between NUL and NULL, what should i use
and where?)
Cheers, Alexey.
2014-05-28 18:06 GMT+04:00 Alexey Radkov :
> Thanks, now i understand it. I am making another patch...
>
>
> 2014-05-28 17:36 GMT+
Thanks, now i understand it. I am making another patch...
2014-05-28 17:36 GMT+04:00 Павлов Николай Александрович :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>
> On May 28, 2014 3:11:51 PM GMT+03:00, Alexey Radkov <
> alexey.rad...@gmail.com> wro
would be implemented by the matchaddpos() function.
2014-05-28 14:19 GMT+04:00 Bram Moolenaar :
>
> Alexey Radkov wrote:
>
> > Hi all.
> >
> > My home computer is
> >
> > Linux 3.14.4-200.fc20.x86_64 x86_64 x86_64 x86_64 GNU/Linux
> >
> > running
A new patch fixes the issues: now it checks if b_mod_set is already set and do
not overwrite b_mod_top and b_mod_bot in this case.
среда, 28 мая 2014 г., 10:17:08 UTC+4 пользователь Alexey Radkov написал:
> Unfortunately this patch works badly when entering new lines before matched
>
Unfortunately this patch works badly when entering new lines before matched
paren: consequent new lines show artifacts and matched pair does not change if
cursor moved.
среда, 28 мая 2014 г., 1:40:26 UTC+4 пользователь Alexey Radkov написал:
> Hi all.
>
> My home computer is
>
&g
Hi vim_dev!
Thinking about possible enhancements in vim 7.4 i found that it would be
probably useful to implement two new autocmd events: ModeEnter and ModeLeave
which arguments would be the name of the mode being entered / left. Currently
there are two similar autocmds InsertEnter and InsertLe
nt
tab. In this case i must use explicit loop through all windows, whereas at
the first glance bufwinnr('NERD_tree*') was looking very promising.
Cheers, Alexey.
2013/2/11 Vlad Irnov
> On 2/8/13, Alexey Radkov wrote:
> > Even an easier test:
> >
> > 1. Op
Even an easier test:
1. Open a C file
2. Open another C file in another tab
3. :echo bufwinnr('*.c') -> -1. Wrong.
2013/2/8 Alexey Radkov
> Hi,
>
> :help bufwinnr says:
>
> "Only deals with the current tab page."
>
> Recently i found that this behav
Hi,
:help bufwinnr says:
"Only deals with the current tab page."
Recently i found that this behaviour is broken if the argument of
bufwinnr() is regexp pattern and there are more than one tabs open. I found
that in following experiment:
1. Open vim with some file.
2. Open NERD_tree plugin (its
Hi Charles.
Thank you!
2012/11/14 Charles Campbell
> Alexey Radkov wrote:
>
>> Hi.
>>
>> I found another issue with vim sources syntax highlights.
>>
>> In the following code:
>>
>> fun! VimwikiLinkHandler(link)
>> let link = a:link
&g
s\+\)\=link\>\|\" end="$"
contains=vimHiGroup,vimGroup,vimHLGroup,vimNotation
+syn regionvimHiLinkcontained oneline matchgroup=vimCommand
start="\(\\|\\)"
end="$"contains=vimHiGroup,vimGroup,vimHLGroup,vimNotation
syn cluster vimFuncBodyList
-- Forwarded message --
From: Alexey Radkov
Date: 2012/11/11
Subject: some vim syntax fixes for multi-lined commands
To: vim-...@vim.org
(missed vim_dev@googlegroups recipient)
Hi.
Here are some fixes for errors in vim syntax highlight for multi-lined
commands found when
Hi.
Here are some fixes for errors in vim syntax highlight for multi-lined
commands found when looking through my .vimrc and other vim sources. I used
to keep lines in sources short (78 columns for vim) so i often used line
breaks.
The patch against current hg version (also attached):
--- runti
Thank you!
After patch 7.3.534 it works fine.
Cheers, Alexey.
2012/5/29 Alexey Radkov
> Here is variant with buffer allocated on stack (patch attached):
>
>
> static char_u *
> do_insert_char_pre(c)
> int c;
> {
> char_u*res = NULL;
> #ifdef FEA
));
set_vim_var_string(VV_CHAR, NULL, -1); /* clear v:char */
--textlock;
return res;
}
2012/5/29 Alexey Radkov
> Btw it is expensive to allocate memory for 'char_u* old' in the latest
> patch. Instead it makes sense to do something like in eval.c in function
> set_vim_var_char(
Btw it is expensive to allocate memory for 'char_u* old' in the latest
patch. Instead it makes sense to do something like in eval.c in function
set_vim_var_char() where a buffer is allocated on stack.
2012/5/28 Alexey Radkov
> I found a better solution.
>
> The problematic
-res = NULL;
-
+if (old && strcmp(old, get_vim_var_str(VV_CHAR)))
+res = vim_strsave(get_vim_var_str(VV_CHAR));
+
+vim_free(old);
set_vim_var_string(VV_CHAR, NULL, -1); /* clear v:char */
--textlock;
Cheers, Alexey.
2012/5/28 Alexey Radkov
> Just found t
Just found that automatic line break when textwidth is set is also broken.
2012/5/28 Bram Moolenaar
>
> Alexey Radkov wrote:
>
> > It is simple.
> >
> > Open some C/C++ code in vim (after patch 461), then
> >
> > :set cinoptions=:0(0+2s"this does
or '*' it will
always trigger and prevent autoindent of cindent! I am not sure that the
patch that i sent is completely correct: it just fixes the problem for me.
Cheers, Alexey.
2012/5/28 Bram Moolenaar
>
> Alexey Radkov wrote:
>
> > Recently i updated vim from patch 44
Hi.
Recently i updated vim from patch 444 to 515 as official Fedora package
update. After that i found that autoindent for {} is brogen. After some
research i found that it got broken in patch 461
6734 7.3.461 InsertCharPre event not always triggered
This patch, as it says, was introduced f
, effect of losing extra syntax
highlighting defined in TagHighlight script i use: setting syntax in the
end of patched dbext#DB_auBufDelete() turns on only basic syntax, and
autocmds for BufEnter defined in TagHighlight are not triggered.
Thank you, Alexey.
2011/11/19 Bram Moolenaar
>
>
uot;Result"
endif
return res_buf_name
endfunction
" }}}
" orientationToggle {{{
function! dbext#DB_orientationToggle(...)
let sql = s:dbext_prev_sql
let refresh= 0
let curr_bufnr = s:dbext_prev_bufnr
So we just put 'setlocal bufhidd
() to flag close_buffer(prevbuf) not to 'del_buf' or
'wipe_buf' and not to syntax_clear() in buf_freeall().
Cheers, Alexey.
2011/11/18 Alexey Radkov
> There is no issue with '#' in
>
>
> autocmd BufReadPost * if &modeline == 1 | call dbext#DB_checkModeline()
indow from normal buffer.
Cheers, Alexey.
2011/11/16 Alexey Radkov
> Here is the latest patch attached where i fixed those segfaults: this was
> really stupid to me to change first character in a static buffer, i just
> did not know how b_p_bh was using memory.
>
> Syntax also wo
highlighting is OK and buffer is not
unloaded. Also i checked that folds are kept and all the same for quitting
from quickfix window.
Cheers, Alexey.
2011/11/15 Alexey Radkov
> Thank you all, guys, for response.
>
> Actually the patch i attached is not perfect: it may lead to segfaults i
/11/15 Thilo Six
> Alexey Radkov wrote the following on 14.11.2011 20:41
>
> Hello Alexey,
>
> -- --
> > You will be returned to the original file, but... Now there is no
> > syntax highlight and ':ls' will show that there is no current buffer!
> >
Hi.
I found a bug in buffer unloading algorithm due to kind of
misconception between how close_buffer() treats buffer unloading data
(checking first character in b_p_bl[] in passed buffer) and situations
when this function can be called. The bug is triggered in rare cases
when
1). a user makes ':
53 matches
Mail list logo
