Re: [patch] windows font antialiasing styles
Hi mattn,
thanks for review. Good point, I'm going to use #ifdef
CLEARTYPE_QUALITY instead of WINVER. Regarding the feature-list - you
mean to add has('has_cleartype') only for cleartype feature so the
users are able to detect cleartype ability of their build and use same
.vimrc on machines with/without it (yep that makes sense to me)? In
original code antialiasing is always on if Windows provide it as
PROOF_QUALITY was used instead of DEFAULT_QUALITY so it's hard to tell
in runtime. Could you please send me pointer to source file where I
can do the feature-list change? I seem a little lost in Vim codebase.
:)
Also, is there any register of Exxx error identifiers? How I can
allocate one (simply grep and sort and take highest one?).
Thanks
On Fri, Mar 15, 2013 at 6:43 AM, mattn mattn...@gmail.com wrote:
One more request.
You've better to add part of feature-list like has('font_antialias'). :)
Thanks for your work.
--
--
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 subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an
email to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Ondrej Balaz
e-mail: bl...@blami.net
GSM: (+420)-724-308-083
jabber: bl...@blami.net
skype: blami_
twitter: http://twitter.com/blami
--
--
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 subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: . fails to repeat the last executed operator with :normal v
On Saturday, March 16, 2013 6:37:18 AM UTC+1, Kana Natsuno wrote: Don't you have any idea about this problem? On Saturday, March 16, 2013 12:06:50 PM UTC+1, glts wrote: Here are the contents of the redo buffer when ... The repeat.vim plugin was created to solve this problem but it doesn't work for omaps neither. I don't know if you saw it but there is some discussion here: https://github.com/tpope/vim-repeat/issues/8 In my opinion, the redo buffer should be the same in both of your examples, namely d:call Select()\n. But since there is only one redo buffer and you can call functions/:normal recursively, there's always the chance of it being overwritten. Folks, would it make sense to add another top-level redo buffer? This would be left untouched by nested :normal commands. -- -- 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 subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: . fails to repeat the last executed operator with :normal v
On Sun, Mar 17, 2013 at 8:03 PM, glts wrote:
The repeat.vim plugin was created to solve this problem but it doesn't
work for omaps neither. I don't know if you saw it but there is some
discussion here:
https://github.com/tpope/vim-repeat/issues/8
I already saw the discussion, because several people asked me about
repeatability of custom text objects implemented with vim-textobj-user
and most of them also told me the link.
But I don't believe that repeat.vim is a right solution for the problem.
repeat.vim is to enable repeatability for custom operators which take
extra arguments such as a {target} for ys{motion}{target} provided by
surround.vim. Repeatability of custom motions and custom text objects
should be covered by another layer. Especially, the solution posted
in the discussion
https://github.com/tpope/vim-repeat/issues/8#issuecomment-13951082
does not work with custom operators using repeat.vim.
In my opinion, the redo buffer should be the same in both of your
examples, namely d:call Select()\n. But since there is only one redo
buffer and you can call functions/:normal recursively, there's always
the chance of it being overwritten.
Folks, would it make sense to add another top-level redo buffer? This
would be left untouched by nested :normal commands.
Thank you for the summary. It seems to be reasonable for me, but there
might be drawbacks about compatibility or difficulty for further
maintenance. I'd like to hear others' opinions.
--
--
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 subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Feature Request] Support for semantic highlighting.
Hello all,
Have plans to do a semantic highlighting support? For example, look at this cpp
source code:
#define SQR(i) ((i)*(i))
int sqr(int i) { return i * i; }
int main() {
{
class sqr{};
sqr foo = sqr();
}
int (*bar)(int) = sqr;
return bar(SQR(2));
}
SQR, sqr, sqr in scope and bar, are highlighted with different colors in
KDevelop. However, in VIM, all these identifiers have same color. CMIIW, there
is no way (include plugin) to do this in VIM. Would vim provide a API to color
each identifier in the source code? So someone (maybe me) will write a vim
plugin to parser the C++ code and help vim to highlight it.
Regards,
Tianjiao
--
--
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 subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.3.864
On 2013-03-16 Saturday at 21:35 +0100 Bram Moolenaar wrote: Patch 7.3.864 (after 7.3.862) Problem:Can't build without the mouse feature. Solution: Add an #ifdef. (Ike Devolder) Files:src/misc1.c This is great, thanks. Now vim builds with _all_ mouse-related features disabled … :) VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Mar 17 2013 12:19:55) Included patches: 1-865 Modified by Gentoo-7.3.865-odvx1@systomanalyson.not_s/o/e/g Compiled by odvx1@systomanalyson.not_s/o/e/g Huge version without GUI. Features included (+) or not (-): -arabic -farsi -mouse_netterm +syntax +autocmd +file_in_path-mouse_sgr +tag_binary -balloon_eval+find_in_path-mouse_sysmouse +tag_old_static -browse +float -mouse_urxvt -tag_any_white ++builtin_terms +folding -mouse_xterm -tcl +byte_offset -footer +multi_byte +terminfo +cindent +fork() +multi_lang +termresponse -clientserver+gettext -mzscheme+textobjects -clipboard -hangul_input-netbeans_intg +title +cmdline_compl +iconv +path_extra -toolbar +cmdline_hist+insert_expand +perl+user_commands +cmdline_info+jumplist-persistent_undo +vertsplit +comments+keymap -printer +virtualedit +conceal +langmap +profile +visual -cryptv +libcall +python +visualextra +cscope +linebreak -python3 +viminfo +cursorbind +lispindent +quickfix+vreplace +cursorshape +listcmds+reltime +wildignore +dialog_con +localmap-rightleft +wildmenu +diff-lua -ruby+windows +digraphs+menu+scrollbind +writebackup -dnd +mksession +signs -X11 -ebcdic +modify_fname+smartindent -xfontset +emacs_tags -mouse -sniff -xim +eval-mouse_dec +startuptime -xsmp +ex_extra-mouse_gpm +statusline -xterm_clipboard +extra_search-mouse_jsbterm -sun_workshop-xterm_save system vimrc file: /etc/vim/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /usr/share/vim Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=native -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: x86_64-pc-linux-gnu-gcc -Wl,-E -Wl,-O1 -Wl,--as-needed -L/usr/local/lib -Wl,--as-needed -o vim-lm -lcurses -ldl -Wl,-E -Wl,-O1 -Wl,--as-needed -L/usr/lib64/perl5/5.12.3/x86_64-linux/CORE -lperl -lnsl -ldl -lm -lcrypt -lutil -lc -L/usr/lib/python2.7/config -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -- Roland Eggner pgpHByIipgmKA.pgp Description: PGP signature
Re: Patch 7.3.864
Op zondag 17 maart 2013 19:09:36 schreef Roland Eggner: On 2013-03-16 Saturday at 21:35 +0100 Bram Moolenaar wrote: Patch 7.3.864 (after 7.3.862) Problem:Can't build without the mouse feature. Solution: Add an #ifdef. (Ike Devolder) Files: src/misc1.c This is great, thanks. Now vim builds with _all_ mouse-related features disabled … :) VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Mar 17 2013 12:19:55) Included patches: 1-865 Modified by Gentoo-7.3.865-odvx1@systomanalyson.not_s/o/e/g Compiled by odvx1@systomanalyson.not_s/o/e/g Huge version without GUI. Features included (+) or not (-): -arabic -farsi -mouse_netterm +syntax +autocmd +file_in_path-mouse_sgr +tag_binary -balloon_eval+find_in_path-mouse_sysmouse +tag_old_static -browse +float -mouse_urxvt -tag_any_white ++builtin_terms +folding -mouse_xterm -tcl +byte_offset -footer +multi_byte +terminfo +cindent +fork() +multi_lang +termresponse -clientserver+gettext -mzscheme+textobjects -clipboard -hangul_input-netbeans_intg +title +cmdline_compl +iconv +path_extra -toolbar +cmdline_hist+insert_expand +perl+user_commands +cmdline_info+jumplist-persistent_undo +vertsplit +comments+keymap -printer +virtualedit +conceal +langmap +profile +visual -cryptv +libcall +python +visualextra +cscope +linebreak -python3 +viminfo +cursorbind +lispindent +quickfix+vreplace +cursorshape +listcmds+reltime +wildignore +dialog_con +localmap-rightleft +wildmenu +diff-lua -ruby+windows +digraphs+menu+scrollbind +writebackup -dnd +mksession +signs -X11 -ebcdic +modify_fname+smartindent -xfontset +emacs_tags -mouse -sniff -xim +eval-mouse_dec +startuptime -xsmp +ex_extra-mouse_gpm +statusline -xterm_clipboard +extra_search-mouse_jsbterm -sun_workshop-xterm_save system vimrc file: /etc/vim/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /usr/share/vim Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=native -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: x86_64-pc-linux-gnu-gcc -Wl,-E -Wl,-O1 -Wl,--as-needed -L/usr/local/lib -Wl,--as-needed -o vim-lm -lcurses -ldl -Wl,-E -Wl,-O1 -Wl,--as-needed -L/usr/lib64/perl5/5.12.3/x86_64-linux/CORE -lperl -lnsl -ldl -lm -lcrypt -lutil -lc -L/usr/lib/python2.7/config -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -- Roland Eggner I don't really have issues with the cli version here: VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Mar 16 2013 22:40:51) Included patches: 1-865 Compiled by BlackEagle Huge version without GUI. Features included (+) or not (-): +arabic +file_in_path+mouse_sgr +tag_binary +autocmd +find_in_path-mouse_sysmouse +tag_old_static -balloon_eval+float +mouse_urxvt -tag_any_white -browse +folding +mouse_xterm -tcl ++builtin_terms -footer +multi_byte +terminfo +byte_offset +fork() +multi_lang +termresponse +cindent +gettext -mzscheme+textobjects -clientserver-hangul_input-netbeans_intg +title -clipboard +iconv +path_extra -toolbar +cmdline_compl +insert_expand +perl/dyn+user_commands +cmdline_hist+jumplist+persistent_undo +vertsplit +cmdline_info+keymap +postscript +virtualedit +comments+langmap +printer +visual +conceal +libcall +profile +visualextra +cryptv +linebreak +python/dyn +viminfo +cscope +lispindent +python3/dyn +vreplace +cursorbind +listcmds+quickfix+wildignore +cursorshape +localmap+reltime +wildmenu +dialog_con +lua/dyn +rightleft +windows +diff+menu+ruby/dyn+writebackup +digraphs+mksession +scrollbind -X11 -dnd +modify_fname+signs -xfontset -ebcdic +mouse +smartindent -xim +emacs_tags -mouseshape -sniff -xsmp +eval+mouse_dec +startuptime -xterm_clipboard +ex_extra+mouse_gpm +statusline -xterm_save +extra_search-mouse_jsbterm -sun_workshop +farsi +mouse_netterm +syntax system vimrc file: /etc/vimrc user vimrc file: $HOME/.vimrc
Complete function refresh:always bug
The refresh:always option for user complete functions seems to be bugged. Based on the description in the help file I expected the competion function called every time a character was added to the leader. Instead, the popup menu disappears and a -- User defined completion (^U^N^P) Back at original message is displayed. Pressing another key causes completion mode to be exited. A video demonstration: http://www.youtube.com/watch?v=gtBQwtN7P5s Using a build from between 7.3.311 (which was when this feature was introduced) and 7.3.403 results in the behavior I expected: http://www.youtube.com/watch?v=SEV1CXJhK18 The current behavior began starting with 7.3.404, which attempted to fix issues with the redo buffer when refresh:always is used. I've attached a patch (refresh_always_fix.diff) that reverts the change made in 7.3.404 (as well as 7.3.561) and attempts to fix the original redo buffer problem differently. I've tried to test this change, and as far as I can tell everything is working correctly. While creating this patch I also found encountered some unsual behavior when using refresh:always. Specific there are two issues: 1. when using completeopt+=longest it can be impossible to add text to the leader because it gets erased immediately 2. the completion list is automatically filtered to candidates whose prefix matches the leader. I've attached a patch to handle each of these cases. For the completopt+=longest issue, it just ignores option when refresh:always is set. For the filtering issue, the patch causes every candidate to be included in the completion list when refresh:always is set. I think the complete longest thing being an issue is debatable since its technically doing what its supposed to, but I think the vim should definitely leave any filtering to the completion function since it gets called every time the list should change. I've also attached the vimscript with the completion function I sourced at the start of each video if you want to try it youself. -- -- 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 subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. refresh_always_fix.diff Description: Binary data filtering_fix.diff Description: Binary data compl_get_longest_fix.diff Description: Binary data refresh_always_example.vim Description: Binary data
