date:20170113

Re: Fixed CSS's class name highlight was broken in some cases

2017-01-13 Fir de Conversatie Ryuichi Hayashida

2017年1月14日土曜日 5時53分05秒 UTC+9 Bram Moolenaar:
> Ryuichi Hayashida wrote:
> 
> > Hi Jules, Bram, and team
> > 
> > I found that highlight of CSS's class names is broken in below cases:
> > 
> > - class name is one character
> > - class name starts with under score
> > 
> > I fixed them. Please find attached css.vim.patch.
> > 
> > Repro: Execute below shell commands
> > 
> > -
> > 
> > $ cat <<-EOS > test.css
> > ._foo {
> >   margin: 0;
> > }
> > 
> > .a {
> >   margin: 0;
> > }
> > EOS
> > 
> > $ vim test.css
> > 
> > -
> 
> I believe a class name can also start with a dash:
> 
> .-foo {
>   margin: 0;
> }
> 
> The suggested pattern is:
> 
> -\=[_a-zA-Z][_a-zA-Z0-9-]*
> 
> -- 
> hundred-and-one symptoms of being an internet addict:
> 266. You hear most of your jokes via e-mail instead of in person.
> 
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org///

Thank you for your review.
I confirmed that you're correct with CSS spec.

https://www.w3.org/TR/CSS21/grammar.html#scanner

> ident -?{nmstart}{nmchar}*

I fixed my patch and attached it to this mail.

-- 
-- 
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/d/optout.
diff --git a/runtime/syntax/css.vim b/runtime/syntax/css.vim
index 3dc3f5c..a66cbdc 100644
--- a/runtime/syntax/css.vim
+++ b/runtime/syntax/css.vim
@@ -56,7 +56,7 @@ syn match cssSelectorOp2 "[~|^$*]\?=" contained
 syn region cssAttributeSelector matchgroup=cssSelectorOp start="\[" end="]" contains=cssUnicodeEscape,cssSelectorOp2,cssStringQ,cssStringQQ
 
 " .class and #id
-syn match cssClassName "\.[A-Za-z][A-Za-z0-9_-]\+" contains=cssClassNameDot
+syn match cssClassName "\.-\=[A-Za-z_][A-Za-z0-9_-]*" contains=cssClassNameDot
 syn match cssClassNameDot contained '\.'
 
 try

Patch 8.0.0178

2017-01-13 Fir de Conversatie Bram Moolenaar


Patch 8.0.0178
Summary:command count test fails on MS-Windows
Problem:test_command_count may fail when a previous test interferes, seen
on MS-Windows.
Solution:   Run it separately.
Files:  src/testdir/test_alot.vim, src/testdir/Make_all.mak


*** ../vim-8.0.0177/src/testdir/test_alot.vim   2017-01-10 16:12:11.732767042 
+0100
--- src/testdir/test_alot.vim   2017-01-13 22:23:01.568320362 +0100
***
*** 3,9 
  
  source test_assign.vim
  source test_autocmd.vim
- source test_command_count.vim
  source test_cursor_func.vim
  source test_delete.vim
  source test_execute_func.vim
--- 3,8 
*** ../vim-8.0.0177/src/testdir/Make_all.mak2017-01-08 13:25:47.626339783 
+0100
--- src/testdir/Make_all.mak2017-01-13 22:24:29.235638037 +0100
***
*** 144,149 
--- 144,150 
test_channel.res \
test_charsearch.res \
test_cmdline.res \
+   test_command_count.res \
test_crypt.res \
test_cscope.res \
test_diffmode.res \
*** ../vim-8.0.0177/src/version.c   2017-01-13 21:59:59.327172086 +0100
--- src/version.c   2017-01-13 22:28:46.097636259 +0100
***
*** 766,767 
--- 766,769 
  {   /* Add new patch number below this line */
+ /**/
+ 178,
  /**/

-- 
hundred-and-one symptoms of being an internet addict:
268. You get up in the morning and go online before getting your coffee.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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/d/optout.

Patch 8.0.0177

2017-01-13 Fir de Conversatie Bram Moolenaar


Patch 8.0.0177
Problem:When opening a buffer on a directory and inside a try/catch then
the BufEnter event is not triggered.
Solution:   Return NOTDONE from readfile() for a directory and deal with the
three possible return values. (Justin M. Keyes, closes #1375,
closes #1353)
Files:  src/buffer.c, src/ex_cmds.c, src/ex_docmd.c, src/fileio.c,
src/memline.c, src/testdir/test_autocmd.vim


*** ../vim-8.0.0176/src/buffer.c2016-12-01 17:48:24.910803059 +0100
--- src/buffer.c2017-01-13 21:51:38.871157464 +0100
***
*** 113,128 
 * it can be changed there. */
if (!readonlymode && !bufempty())
changed();
!   else if (retval != FAIL)
unchanged(curbuf, FALSE);
  
  #ifdef FEAT_AUTOCMD
  # ifdef FEAT_EVAL
!   apply_autocmds_retval(EVENT_STDINREADPOST, NULL, NULL, FALSE,
curbuf, );
  # else
!   apply_autocmds(EVENT_STDINREADPOST, NULL, NULL, FALSE, curbuf);
  # endif
  #endif
  }
  return retval;
--- 113,131 
 * it can be changed there. */
if (!readonlymode && !bufempty())
changed();
!   else if (retval == OK)
unchanged(curbuf, FALSE);
  
  #ifdef FEAT_AUTOCMD
+   if (retval == OK)
+   {
  # ifdef FEAT_EVAL
!   apply_autocmds_retval(EVENT_STDINREADPOST, NULL, NULL, FALSE,
curbuf, );
  # else
!   apply_autocmds(EVENT_STDINREADPOST, NULL, NULL, FALSE, curbuf);
  # endif
+   }
  #endif
  }
  return retval;
***
*** 294,300 
  #endif
 )
changed();
! else if (retval != FAIL && !read_stdin && !read_fifo)
unchanged(curbuf, FALSE);
  save_file_ff(curbuf); /* keep this fileformat */
  
--- 297,303 
  #endif
 )
changed();
! else if (retval == OK && !read_stdin && !read_fifo)
unchanged(curbuf, FALSE);
  save_file_ff(curbuf); /* keep this fileformat */
  
***
*** 328,334 
  # endif
  #endif
  
! if (retval != FAIL)
  {
  #ifdef FEAT_AUTOCMD
/*
--- 331,337 
  # endif
  #endif
  
! if (retval == OK)
  {
  #ifdef FEAT_AUTOCMD
/*
*** ../vim-8.0.0176/src/ex_cmds.c   2016-12-14 21:41:56.997414047 +0100
--- src/ex_cmds.c   2017-01-13 21:51:38.875157432 +0100
***
*** 1313,1319 
if (otmp != NULL)
{
if (readfile(otmp, NULL, line2, (linenr_T)0, (linenr_T)MAXLNUM,
!   eap, READ_FILTER) == FAIL)
{
  #if defined(FEAT_AUTOCMD) && defined(FEAT_EVAL)
if (!aborting())
--- 1313,1319 
if (otmp != NULL)
{
if (readfile(otmp, NULL, line2, (linenr_T)0, (linenr_T)MAXLNUM,
!   eap, READ_FILTER) != OK)
{
  #if defined(FEAT_AUTOCMD) && defined(FEAT_EVAL)
if (!aborting())
*** ../vim-8.0.0176/src/ex_docmd.c  2017-01-07 20:39:49.970046560 +0100
--- src/ex_docmd.c  2017-01-13 21:51:38.879157400 +0100
***
*** 8857,8863 
  eap->line2, (linenr_T)0, (linenr_T)MAXLNUM, eap, 0);
  
}
!   if (i == FAIL)
{
  #if defined(FEAT_AUTOCMD) && defined(FEAT_EVAL)
if (!aborting())
--- 8857,8863 
  eap->line2, (linenr_T)0, (linenr_T)MAXLNUM, eap, 0);
  
}
!   if (i != OK)
{
  #if defined(FEAT_AUTOCMD) && defined(FEAT_EVAL)
if (!aborting())
*** ../vim-8.0.0176/src/fileio.c2016-09-25 20:51:25.399154303 +0200
--- src/fileio.c2017-01-13 21:59:36.599352568 +0100
***
*** 210,216 
   * READ_KEEP_UNDO  don't clear undo info or read it from a file
   * READ_FIFO  read from fifo/socket instead of a file
   *
!  * return FAIL for failure, OK otherwise
   */
  int
  readfile(
--- 210,216 
   * READ_KEEP_UNDO  don't clear undo info or read it from a file
   * READ_FIFO  read from fifo/socket instead of a file
   *
!  * return FAIL for failure, NOTDONE for directory (failure), or OK
   */
  int
  readfile(
***
*** 450,462 
  # endif
)
{
if (S_ISDIR(perm))
filemess(curbuf, fname, (char_u *)_("is a directory"), 0);
else
filemess(curbuf, fname, (char_u *)_("is not a file"), 0);
msg_end();
msg_scroll = msg_save;
!   return FAIL;
}
  #endif
  #if defined(MSWIN)
--- 450,467 
  # endif
)
{
+   int retval = FAIL;
+ 
if (S_ISDIR(perm))
+   {
filemess(curbuf, fname, (char_u *)_("is a directory"), 0);
+   retval =

Re: Fixed CSS's class name highlight was broken in some cases

2017-01-13 Fir de Conversatie Bram Moolenaar


Ryuichi Hayashida wrote:

> Hi Jules, Bram, and team
> 
> I found that highlight of CSS's class names is broken in below cases:
> 
> - class name is one character
> - class name starts with under score
> 
> I fixed them. Please find attached css.vim.patch.
> 
> Repro: Execute below shell commands
> 
> -
> 
> $ cat <<-EOS > test.css
> ._foo {
>   margin: 0;
> }
> 
> .a {
>   margin: 0;
> }
> EOS
> 
> $ vim test.css
> 
> -

I believe a class name can also start with a dash:

.-foo {
  margin: 0;
}

The suggested pattern is:

-\=[_a-zA-Z][_a-zA-Z0-9-]*

-- 
hundred-and-one symptoms of being an internet addict:
266. You hear most of your jokes via e-mail instead of in person.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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/d/optout.

Re: [vim/vim] Do `BufEnter` for directories. (#1375)

2017-01-13 Fir de Conversatie Bram Moolenaar


Justin M. Keyes wrote:

> Abuse NOTDONE to give some nuance to the return value of readfile(), so
> that open_buffer() can distinguish between "general failure" and "failed
> because the path is a directory".
> 
> Before this change, Vim *already* creates a new buffer when a directory
> is edited. So there's no reason it should not raise BufEnter, that was
> an implementation detail of readfile().
> 
> Most of the changes in this commit merely preserve the old semantics.
> The "implicit" change that we actually are interested in, is this line
> in `open_buffer()`, where `` being non-FAIL allows EVENT_BUFENTER
> to be applied:
> 
> apply_autocmds_retval(EVENT_BUFENTER, NULL, NULL, FALSE, curbuf, );
> 
> Closes #1353

Thanks.  I tried writing a test, but since the tests are executed inside
a try/catch a new style test doesn't fail even before this patch.

-- 
XML is a nice language for computers.  Not for humans.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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/d/optout.

Why can't we have setlocal formatprg?

2017-01-13 Fir de Conversatie bradford

I just discovered a great tool that allows me to format my javascript code.  I 
want that tool available for just javascript -- when I switch to a scratch 
buffer, I want default formatting for text.  Unfortunately, formatprg is 
global.  When looking through some of the plugin code in the main vim 
repository, I see people trying to setlocal on it.  Why can't we have setlocal 
on formatprg?

I also see formatexpr, which can be local, but its behavior is very different 
and harder for me to just drop in a program that behaves the same for gq_, 
gqap, etc...  In other words, I have to learn how to use vimscript to set this 
up.  setlocal 
formatexpr=setline(v:lnum,systemlist('myprog',getline(v:lnum,v:count))) is 
close, but not.

-- 
-- 
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/d/optout.

Re: [vim/vim] <C-]> issue using Portuguese-Brazil keyboard layout (#1378)

2017-01-13 Fir de Conversatie Tony Mechelynck

On Fri, Jan 13, 2017 at 6:31 PM, Eduardo Sousa
 wrote:
> When I'm using a portuguese keyboard layout, and I press , vim
> identifies it as , which makes me unable to navigate help files using
> this kind of keyboards

Finding a specific control key for a nonalphabetic character on a
keyboard for a language other than English is not always obvious.
Hitting Ctrl together with whatever it is that you hit to get ] will
not necessarily get you the 0x1D byte which means Ctrl-] for Vim. For
instance, on my Belgian keyboard, ] is AltGr-$ and Ctrl-] is not
Ctrl-$ but Ctrl-AltGr-$

But even if you don't know what to hit to get something that Vim will
interpret as Ctrl-], there is an easy workaround, as follows:

  map  
  map!  

By adding the above two lines to your vimrc then restarting Vim,
hitting F9 will give you what Ctrl-] is supposed to do, i.e., follow a
help link or find a tag in Normal mode, and teminate an abbreviation
in Insert or Command-line mode. (Of course if F9 is already taken you
can use any other key, preferably some F or Shift-F key.)

Best regards,
Tony.

-- 
-- 
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/d/optout.

Re: [bug] vim+tmux: current line changes when using mouse to switch between buffers

2017-01-13 Fir de Conversatie James McCoy

On Jan 13, 2017 7:38 AM, "Jon Seidel"  wrote:

I use vim in a tmux window a lot. And when I open a session (using
OpenSession) I usually have a number of buffers open.

I use the mouse to switch between buffers; when I click in a buffer with
the mouse, the the text in the buffer "bounces" around and leaves the
cursor on a different line than the one I clicked on.


What does ":set ttymouse?" report?

Cheers,
James

-- 
-- 
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/d/optout.

Re: [bug] vim+tmux: current line changes when using mouse to switch between buffers

2017-01-13 Fir de Conversatie Kazunobu Kuriyama

2017-01-13 7:10 GMT+09:00 Jon Seidel :

> I use vim in a tmux window a lot. And when I open a session (using
> OpenSession) I usually have a number of buffers open.
>
> I use the mouse to switch between buffers; when I click in a buffer with
> the mouse, the the text in the buffer "bounces" around and leaves the
> cursor on a different line than the one I clicked on.
>
> Once I'm in the buffer, I am able to use the mouse to click on other lines
> and that works normally - where I click is where the cursor is placed.
>
> I also see the buffer shift up or down randomly but regularly while it's
> just sitting there. Only happens once and things quiet down.
>
> This has happened in all 8.0 versions I've tried and never happened in the
> various 7.x versions I've used with tmux.
>
> I plan to report this to tmux as well.
>
> My tmux version: 2.3
>

I'm also using Vim 8.0 with tmux 2.3 on OS X 10.11.6.

I tried to reproduce the said bug but hadn't seen the behavior described
above.

So, I think it would also be better to think of the possibility of temporal
failure of the trackpad, which can be caused by anything that changes the
characteristics of the capacitor consisting of one's fingers and the
trackpad. e.g., high humidity, invisible stain on the contact surfaces, or
static electricity charged on one's fingers...

Best regards,
Kazunobu Kuriyama

-- 
-- 
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/d/optout.

Re: [vim/vim] <C-]> issue using Portuguese-Brazil keyboard layout (#1378)

2017-01-13 Fir de Conversatie Charles E Campbell

Eduardo Sousa wrote:
>
> When I'm using a portuguese keyboard layout, and I press ||, vim
> identifies it as ||, which makes me unable to navigate help files
> using this kind of keyboards
>
>
Hello:

First, I have no idea what a portuguese keyboard layout is like.  I
doubt that vim is modifying what  is producing on its own; rather,
I suspect that your keyboard generates a  instead on its own. 
However,  you could make a nmap to do what you want:

  nmap  :echo "it works!"

If pressing  gives you the "it works" message, then:

  nno  

ought to work.

Regards,
Chip Campbell

-- 
-- 
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/d/optout.

Re: [bug] vim+tmux: current line changes when using mouse to switch between buffers

2017-01-13 Fir de Conversatie Tony Mechelynck

On Thu, Jan 12, 2017 at 11:10 PM, Jon Seidel  wrote:
> I use vim in a tmux window a lot. And when I open a session (using 
> OpenSession) I usually have a number of buffers open.
>
> I use the mouse to switch between buffers; when I click in a buffer with the 
> mouse, the the text in the buffer "bounces" around and leaves the cursor on a 
> different line than the one I clicked on.


Where does it "bounce" to? Maybe to the last place it was when you
were in that window? ("window" in the Vim sense, not in the OS sense)
— If that's the case, then I think it is normal; click again and
you'll go wherever you click.

Or click on a statusline to change windows (and the cursor should go
wherever it was last in that window), then click to some text
character in the newly current window (or use hjkl or a search or fFtT
etc.) to move the cursor to where you want to do your next edit.

(continued)

>
> Once I'm in the buffer, I am able to use the mouse to click on other lines 
> and that works normally - where I click is where the cursor is placed.
>
> I also see the buffer shift up or down randomly but regularly while it's just 
> sitting there. Only happens once and things quiet down.
>
> This has happened in all 8.0 versions I've tried and never happened in the 
> various 7.x versions I've used with tmux.
>
> I plan to report this to tmux as well.
>
> My tmux version: 2.3
>
> My vim version (through HomeBrew on OSX ElCapitan, 10.11.6):
> vim --version
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 11 2017 22:50:08)
> MacOS X (unix) version
> Included patches: 1-172
> Compiled by Homebrew
> Huge version without GUI.  Features included (+) or not (-):


Have you tried using gvim? It is (of course) free from any weirdness
that might be caused by terminals, and interacts much more predictably
with the mouse and with (non-printing) movement and function keys.


> +acl +file_in_path+mouse_sgr   +tag_old_static
> +arabic  +find_in_path-mouse_sysmouse  -tag_any_white
> +autocmd +float   +mouse_urxvt -tcl
> -balloon_eval+folding +mouse_xterm +termguicolors
> -browse  -footer  +multi_byte  +terminfo
> ++builtin_terms  +fork()  +multi_lang  +termresponse
> +byte_offset -gettext -mzscheme+textobjects
> +channel -hangul_input+netbeans_intg   +timers
> +cindent +iconv   +num64   +title
> -clientserver+insert_expand   +packages-toolbar
> +clipboard   +job +path_extra  +user_commands
> +cmdline_compl   +jumplist+perl+vertsplit
> +cmdline_hist+keymap  +persistent_undo +virtualedit
> +cmdline_info+lambda  +postscript  +visual
> +comments+langmap +printer +visualextra
> +conceal +libcall +profile +viminfo
> +cryptv  +linebreak   +python  +vreplace
> +cscope  +lispindent  -python3 +wildignore
> +cursorbind  +listcmds+quickfix+wildmenu
> +cursorshape +localmap+reltime +windows
> +dialog_con  -lua +rightleft   +writebackup
> +diff+menu+ruby-X11
> +digraphs+mksession   +scrollbind  -xfontset
> -dnd +modify_fname+signs   -xim
> -ebcdic  +mouse   +smartindent -xpm
> +emacs_tags  -mouseshape  +startuptime -xsmp
> +eval+mouse_dec   +statusline  -xterm_clipboard
> +ex_extra-mouse_gpm   -sun_workshop-xterm_save
> +extra_search-mouse_jsbterm   +syntax
> +farsi   +mouse_netterm   +tag_binary
>system vimrc file: "$VIM/vimrc"
>  user vimrc file: "$HOME/.vimrc"
>  2nd user vimrc file: "~/.vim/vimrc"
>   user exrc file: "$HOME/.exrc"
>defaults file: "$VIMRUNTIME/defaults.vim"
>   fall-back for $VIM: "/usr/local/share/vim"
> Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X_UNIX  -g -O2 
> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> Linking: clang   -L. -fstack-protector -L/usr/local/lib 
> -L/usr/local/opt/libyaml/lib -L/usr/local/opt/openssl/lib 
> -L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim-lncurses 
> -liconv -framework Cocoa   -mmacosx-version-min=10.11 
> -fstack-protector-strong -L/usr/local/lib  
> -L/usr/local/Cellar/perl/5.24.0_1/lib/perl5/5.24.0/darwin-thread-multi-2level/CORE
>  -lperl -lm -lutil -lc -F/usr/local/opt/python/Frameworks -framework Python   
> -lruby.2.4.0 -lobjc


Best regards,
Tony.

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

[bug] vim+tmux: current line changes when using mouse to switch between buffers

2017-01-13 Fir de Conversatie Jon Seidel

I use vim in a tmux window a lot. And when I open a session (using OpenSession) 
I usually have a number of buffers open.

I use the mouse to switch between buffers; when I click in a buffer with the 
mouse, the the text in the buffer "bounces" around and leaves the cursor on a 
different line than the one I clicked on.

Once I'm in the buffer, I am able to use the mouse to click on other lines and 
that works normally - where I click is where the cursor is placed.

I also see the buffer shift up or down randomly but regularly while it's just 
sitting there. Only happens once and things quiet down.

This has happened in all 8.0 versions I've tried and never happened in the 
various 7.x versions I've used with tmux.

I plan to report this to tmux as well.

My tmux version: 2.3

My vim version (through HomeBrew on OSX ElCapitan, 10.11.6):
vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 11 2017 22:50:08)
MacOS X (unix) version
Included patches: 1-172
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl +file_in_path+mouse_sgr   +tag_old_static
+arabic  +find_in_path-mouse_sysmouse  -tag_any_white
+autocmd +float   +mouse_urxvt -tcl
-balloon_eval+folding +mouse_xterm +termguicolors
-browse  -footer  +multi_byte  +terminfo
++builtin_terms  +fork()  +multi_lang  +termresponse
+byte_offset -gettext -mzscheme+textobjects
+channel -hangul_input+netbeans_intg   +timers
+cindent +iconv   +num64   +title
-clientserver+insert_expand   +packages-toolbar
+clipboard   +job +path_extra  +user_commands
+cmdline_compl   +jumplist+perl+vertsplit
+cmdline_hist+keymap  +persistent_undo +virtualedit
+cmdline_info+lambda  +postscript  +visual
+comments+langmap +printer +visualextra
+conceal +libcall +profile +viminfo
+cryptv  +linebreak   +python  +vreplace
+cscope  +lispindent  -python3 +wildignore
+cursorbind  +listcmds+quickfix+wildmenu
+cursorshape +localmap+reltime +windows
+dialog_con  -lua +rightleft   +writebackup
+diff+menu+ruby-X11
+digraphs+mksession   +scrollbind  -xfontset
-dnd +modify_fname+signs   -xim
-ebcdic  +mouse   +smartindent -xpm
+emacs_tags  -mouseshape  +startuptime -xsmp
+eval+mouse_dec   +statusline  -xterm_clipboard
+ex_extra-mouse_gpm   -sun_workshop-xterm_save
+extra_search-mouse_jsbterm   +syntax
+farsi   +mouse_netterm   +tag_binary
   system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
  user exrc file: "$HOME/.exrc"
   defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X_UNIX  -g -O2 
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -fstack-protector -L/usr/local/lib 
-L/usr/local/opt/libyaml/lib -L/usr/local/opt/openssl/lib 
-L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim-lncurses -liconv 
-framework Cocoa   -mmacosx-version-min=10.11 -fstack-protector-strong 
-L/usr/local/lib  
-L/usr/local/Cellar/perl/5.24.0_1/lib/perl5/5.24.0/darwin-thread-multi-2level/CORE
 -lperl -lm -lutil -lc -F/usr/local/opt/python/Frameworks -framework Python   
-lruby.2.4.0 -lobjc

-- 
-- 
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/d/optout.

Fixed CSS's class name highlight was broken in some cases

2017-01-13 Fir de Conversatie Ryuichi Hayashida

Hi Jules, Bram, and team

I found that highlight of CSS's class names is broken in below cases:

- class name is one character
- class name starts with under score

I fixed them. Please find attached css.vim.patch.

Repro: Execute below shell commands

-

$ cat <<-EOS > test.css
._foo {
  margin: 0;
}

.a {
  margin: 0;
}
EOS

$ vim test.css

-

My environment:

- macOS 10.12
- Vim 8.0-114 (MacVim)


Thanks,
Hayashida

-- 
-- 
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/d/optout.
diff --git a/runtime/syntax/css.vim b/runtime/syntax/css.vim
index 3dc3f5c..a66cbdc 100644
--- a/runtime/syntax/css.vim
+++ b/runtime/syntax/css.vim
@@ -56,7 +56,7 @@ syn match cssSelectorOp2 "[~|^$*]\?=" contained
 syn region cssAttributeSelector matchgroup=cssSelectorOp start="\[" end="]" contains=cssUnicodeEscape,cssSelectorOp2,cssStringQ,cssStringQQ
 
 " .class and #id
-syn match cssClassName "\.[A-Za-z][A-Za-z0-9_-]\+" contains=cssClassNameDot
+syn match cssClassName "\.[A-Za-z_][A-Za-z0-9_-]*" contains=cssClassNameDot
 syn match cssClassNameDot contained '\.'
 
 try

Re: Fixed CSS's class name highlight was broken in some cases

Patch 8.0.0178

Patch 8.0.0177

Re: Fixed CSS's class name highlight was broken in some cases

Re: [vim/vim] Do `BufEnter` for directories. (#1375)

Why can't we have setlocal formatprg?

Re: [vim/vim] <C-]> issue using Portuguese-Brazil keyboard layout (#1378)

Re: [bug] vim+tmux: current line changes when using mouse to switch between buffers

Re: [bug] vim+tmux: current line changes when using mouse to switch between buffers

Re: [vim/vim] <C-]> issue using Portuguese-Brazil keyboard layout (#1378)

Re: [bug] vim+tmux: current line changes when using mouse to switch between buffers

[bug] vim+tmux: current line changes when using mouse to switch between buffers

Fixed CSS's class name highlight was broken in some cases

13 matches

Site Navigation

Mail list logo

Footer information