Re: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

2016-12-12 Fir de Conversatie ouidacisneros via vim_dev 


On Tue, 12/13/16, itchyny  wrote:

 Subject: Re: stl, stlnc of fillchars are not always applied, depends on 
difference between StatusLine and StatusLineNC
 To: "vim_dev" 
 Cc: neknekneknek.ky...@gmail.com
 Date: Tuesday, December 13, 2016, 7:20 AM
 
 On Tuesday, December 13,
 2016 at 1:26:30 AM UTC+9, Ozaki Kiichi wrote:
 > It is better to add it for an unit
 test.
 > 
 > maka -C src
 test_fillchars
 
 
 Thank you for your notice, it's surely
 useful.
 Here is the latest patch.
 
 https://gist.github.com/itchyny/936f5c7e7f6396bf2f6afbe246206d47
 
 Regards,
 Ken
 Hamada (aka itchyny)
 
 -- 
 -- 
 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.
 vand si girul tacit al strainatatii  guvernul Petru Groza s-a lansat intr-o 
campanie fara precedent impotriva opozitiei. Procesele politice din anii 
1946-1947 au constituit o noua etapa a prigoanei comuniste in Romania. Se 
urmarea  practic  exterminarea fizica a tuturor adversarilor politici ai 
regimului comunist. Tribunalele poporului au judecat si condamnat drept 
criminali de razboi  fosti functionari superiori si membrii ai guvernului 
Antonescu. Astfel  au fost condamnati  intre altii  generalul Constantin 
Voiculescu  guvernatorul Basarabiei  generalul Calotescu  guvernatorul in 
nordul Bucovinei. intre 7 si 18 mai 1946  in cadrul asa-zisului proces al marii 
tradarii nationale  - o sinistra inscenare juridica regizata de comunisti - au 
fost judecati si condamnati la moarte  printre altii  Ion si Mihai Antonescu  
Lucretiu Patrascanu  propunand regelui Minai I respingerea cererii de gratiere. 
Cei doi  alaturi de Constantin Vasilius\ Gheorghe Alexianu  au fost executati 
la 1 iunie 1946. in noiembrie 1946  sub aceeasi acuzatie  de criminal de razboi 
  a fost condamnat si generalul A dea  unul dintre participantii la actul din 
23 august 1944.

-- 
-- 
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: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

2016-12-12 Fir de Conversatie itchyny 
On Tuesday, December 13, 2016 at 1:26:30 AM UTC+9, Ozaki Kiichi wrote:
> It is better to add it for an unit test.
> 
> maka -C src test_fillchars


Thank you for your notice, it's surely useful.
Here is the latest patch.

https://gist.github.com/itchyny/936f5c7e7f6396bf2f6afbe246206d47

Regards,
Ken Hamada (aka itchyny)

-- 
-- 
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] gtk3 gui substantially slower than gtk2 (#1199)

2016-12-12 Fir de Conversatie malvinaconaway via vim_dev 


On Tue, 12/13/16, Matěj Cepl  wrote:

 Subject: Re: [vim/vim] gtk3 gui substantially slower than gtk2 (#1199)
 To: "vim/vim" 
 Date: Tuesday, December 13, 2016, 2:12 AM
 
 This seemed to get quite horribly
 worse in v8.0.0130. I have had almost a dozen
 previous builds with Gtk3 and this seems to be exceptionally
 worse.
 
 —
 You are receiving this because you are subscribed to this
 thread.
 Reply to this email directly, view
 it on GitHub
 
 
   
   
 
  
 
 
  
 
 
 
 -- 
 
 -- 
 
 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.
 rebuia sa fie programul revolutiei din 1848? El era dezvoltarea progresiva a 
revolutiei

-- 
-- 
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] Add v:argv variable (#1322)

2016-12-12 Fir de Conversatie Dmitri Vereshchagin 
* Gary Johnson  [2016-12-13 01:45]:
> argc() and argv() aren't sufficient?

No.  These functions work with *files* in the argument list of the
current window.

-- 
Dmitri Vereshchagin

-- 
-- 
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: Questions about vim_iswordc() and vim_iswordp()

2016-12-12 Fir de Conversatie selzerolivia via vim_dev 


On Mon, 12/12/16, Ozaki Kiichi  wrote:

 Subject: Re: Questions about vim_iswordc() and vim_iswordp()
 To: "vim_dev" 
 Cc: gclient.g...@gmail.com
 Date: Monday, December 12, 2016, 11:59 PM
 
 > They should both
 respect 'iskeyword' for characters up to 255.
 > So it looks like vim_iswordp() needs to be
 fixed.
 > 
 
 Thank you. OK, my above patch has reflected
 this fix.
 
 -- 
 -- 
 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.
 robleme indisolubil legate una de cealalta: echilibrul de putere in vestul 
Europei

-- 
-- 
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] Add v:argv variable (#1322)

2016-12-12 Fir de Conversatie Gary Johnson 
On 2016-12-12, Dmitri Vereshchagin wrote:
> It may be useful to have access to the command line arguments as a List stored
> in v:argv variable. For example one may use it to check if Vim was invoked
> without any arguments and open file browser automatically
> 
> " ~/.vim/after/plugin/netrw.vim
> 
> if !exists(':Explore') || !empty(v:argv)
>   finish
> endif
> 
> augroup after_netrw
>   autocmd!
>   autocmd VimEnter * Explore | autocmd! after_netrw
> augroup END

argc() and argv() aren't sufficient?

Regards,
Gary

-- 
-- 
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: [patch] broken link pi_logipat.txt in runtime/doc/help.txt

2016-12-12 Fir de Conversatie Bram Moolenaar 

Dominique wrote:

> In Vim main help page (runtime/doc/help.txt),
> there is a link |pi_logipat.txt| which is broken.
> 
> Fixed in attached patch.

Thanks!


-- 
In a world without walls and borders, who needs windows and gates?

 /// 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: [patch] broken link pi_logipat.txt in runtime/doc/help.txt

2016-12-12 Fir de Conversatie Dominique Pellé 
Charles E Campbell  wrote:

> Dominique Pellé wrote:
>> Hi
>>
>> In Vim main help page (runtime/doc/help.txt),
>> there is a link |pi_logipat.txt| which is broken.
>>
>> Fixed in attached patch.
>>
> Thank you, Dominique -- I'll include that change.  It is a leftover from
> its incorporation as a part of vim.

Good. Thanks!

Having found this broken link, I searched for others and
found another one in runtime/doc/usr_22.txt.
It says:

qListing Bookmarks and History..|netrw-q|

It should probably be:

qb...Listing Bookmarks and History..|netrw-qb|

Regards
Dominique

-- 
-- 
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: Questions about vim_iswordc() and vim_iswordp()

2016-12-12 Fir de Conversatie Ozaki Kiichi 
> They should both respect 'iskeyword' for characters up to 255.
> So it looks like vim_iswordp() needs to be fixed.
> 

Thank you. OK, my above patch has reflected this fix.

-- 
-- 
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: [patch] broken link pi_logipat.txt in runtime/doc/help.txt

2016-12-12 Fir de Conversatie Charles E Campbell 
Dominique Pellé wrote:
> Hi
>
> In Vim main help page (runtime/doc/help.txt),
> there is a link |pi_logipat.txt| which is broken.
>
> Fixed in attached patch.
>
Thank you, Dominique -- I'll include that change.  It is a leftover from
its incorporation as a part of vim.

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.

[patch] improved completion of :syntax command

2016-12-12 Fir de Conversatie Dominique Pellé 
Hi

Attached patch adds completion for:

:syntax spell
:syntax sync

Regards
Dominique

-- 
-- 
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/src/syntax.c b/src/syntax.c
index 75ede36..fe8fe33 100644
--- a/src/syntax.c
+++ b/src/syntax.c
@@ -6383,7 +6383,9 @@ syntax_present(win_T *win)
 static enum
 {
 EXP_SUBCMD,	/* expand ":syn" sub-commands */
-EXP_CASE	/* expand ":syn case" arguments */
+EXP_CASE,	/* expand ":syn case" arguments */
+EXP_SPELL,	/* expand ":syn spell" arguments */
+EXP_SYNC	/* expand ":syn sync" arguments */
 } expand_what;
 
 /*
@@ -6434,6 +6436,10 @@ set_context_in_syntax_cmd(expand_T *xp, char_u *arg)
 		xp->xp_context = EXPAND_NOTHING;
 	else if (STRNICMP(arg, "case", p - arg) == 0)
 		expand_what = EXP_CASE;
+	else if (STRNICMP(arg, "spell", p - arg) == 0)
+		expand_what = EXP_SPELL;
+	else if (STRNICMP(arg, "sync", p - arg) == 0)
+		expand_what = EXP_SYNC;
 	else if (  STRNICMP(arg, "keyword", p - arg) == 0
 		|| STRNICMP(arg, "region", p - arg) == 0
 		|| STRNICMP(arg, "match", p - arg) == 0
@@ -6445,8 +6451,6 @@ set_context_in_syntax_cmd(expand_T *xp, char_u *arg)
 }
 }
 
-static char *(case_args[]) = {"match", "ignore", NULL};
-
 /*
  * Function given to ExpandGeneric() to obtain the list syntax names for
  * expansion.
@@ -6454,9 +6458,31 @@ static char *(case_args[]) = {"match", "ignore", NULL};
 char_u *
 get_syntax_name(expand_T *xp UNUSED, int idx)
 {
-if (expand_what == EXP_SUBCMD)
-	return (char_u *)subcommands[idx].name;
-return (char_u *)case_args[idx];
+switch (expand_what)
+{
+	case EXP_SUBCMD:
+	return (char_u *)subcommands[idx].name;
+	case EXP_CASE:
+	{
+	static char *case_args[] = {"match", "ignore", NULL};
+	return (char_u *)case_args[idx];
+	}
+	case EXP_SPELL:
+	{
+	static char *spell_args[] =
+		{"toplevel", "notoplevel", "default", NULL};
+	return (char_u *)spell_args[idx];
+	}
+	case EXP_SYNC:
+	{
+	static char *sync_args[] =
+		{"ccomment", "clear", "fromstart", 
+		 "linebreaks=", "linecont", "lines=", "match",
+		 "maxlines=", "minlines=", "region", NULL};
+	return (char_u *)sync_args[idx];
+	}
+}
+return NULL;
 }
 
 #endif /* FEAT_CMDL_COMPL */
diff --git a/src/testdir/test_syntax.vim b/src/testdir/test_syntax.vim
index 7cb67e6..23ef154 100644
--- a/src/testdir/test_syntax.vim
+++ b/src/testdir/test_syntax.vim
@@ -150,6 +150,12 @@ func Test_syntax_completion()
   call feedkeys(":syn case \\\"\", 'tx')
   call assert_equal('"syn case ignore match', @:)
 
+  call feedkeys(":syn spell \\\"\", 'tx')
+  call assert_equal('"syn spell default notoplevel toplevel', @:)
+
+  call feedkeys(":syn sync \\\"\", 'tx')
+  call assert_equal('"syn sync ccomment clear fromstart linebreaks= linecont lines= match maxlines= minlines= region', @:)
+
   call feedkeys(":syn list \\\"\", 'tx')
   call assert_match('^"syn list Boolean Character ', @:)

[patch] broken link pi_logipat.txt in runtime/doc/help.txt

2016-12-12 Fir de Conversatie Dominique Pellé 
Hi

In Vim main help page (runtime/doc/help.txt),
there is a link |pi_logipat.txt| which is broken.

Fixed in attached patch.

Regards
Dominique

-- 
-- 
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/doc/pi_logipat.txt b/runtime/doc/pi_logipat.txt
index d2eac80..f8d6662 100644
--- a/runtime/doc/pi_logipat.txt
+++ b/runtime/doc/pi_logipat.txt
@@ -1,4 +1,4 @@
-*logiPat.txt*	Logical PatternsJun 22, 2015
+*pi_logipat.txt*	Logical Patterns			Jun 22, 2015
 
 Author:  Charles E. Campbell  
 Copyright: (c) 2004-2015 by Charles E. Campbell	*logiPat-copyright*

Re: Questions about vim_iswordc() and vim_iswordp()

2016-12-12 Fir de Conversatie Bram Moolenaar 

Ozaki Kiichi wrote:

> > when c == 0xA0, p == "\xC2\xA0", and 'iskeyword' includes 160
> > 
> > (e.g. iskeyword=@,48-57,_,128-167,224-235 (default on windows))
> > 
> > then: vim_iswordc(c) == 1, but vim_iswordp(p) == 0.
> 
> After all, in the above case, should vim_iswordc(c) and vim_iswordp(p) be
> whether TRUE or FALSE?

They should both respect 'iskeyword' for characters up to 255.
So it looks like vim_iswordp() needs to be fixed.

-- 
hundred-and-one symptoms of being an internet addict:
108. While reading a magazine, you look for the Zoom icon for a better
 look at a photograph.

 /// 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: Questions about vim_iswordc() and vim_iswordp()

2016-12-12 Fir de Conversatie Ozaki Kiichi 
> when c == 0xA0, p == "\xC2\xA0", and 'iskeyword' includes 160
> 
> (e.g. iskeyword=@,48-57,_,128-167,224-235 (default on windows))
> 
> then: vim_iswordc(c) == 1, but vim_iswordp(p) == 0.

After all, in the above case, should vim_iswordc(c) and vim_iswordp(p) be
whether TRUE or FALSE?

-- 
-- 
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: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

2016-12-12 Fir de Conversatie Ozaki Kiichi 
> Sorry, there's no need to add the test in Makefile because I added into 
> test_alot.vim. I fixed the patch.

It is better to add it for an unit test.

maka -C src test_fillchars

-- 
-- 
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: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

2016-12-12 Fir de Conversatie itchyny 
> Thank you Bram. I've got the point.
> How about this patch? 
> I noticed the note in syntax.txt but still believe that the patch solves the 
> strange behavior
> that most people will not configure what's going on until look into the 
> source code.
> 

Sorry, there's no need to add the test in Makefile because I added into 
test_alot.vim. I fixed the patch.


diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 2138f02..9da27a8 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -4991,8 +4991,6 @@ SpellRare Word that is recognized by the spellchecker as 
one that is
 StatusLine status line of current window
*hl-StatusLineNC*
 StatusLineNC   status lines of not-current windows
-   Note: if this is equal to "StatusLine" Vim will use "^^^" in
-   the status line of the current window.
*hl-TabLine*
 TabLinetab pages line, not active tab page label
*hl-TabLineFill*
diff --git a/src/globals.h b/src/globals.h
index 0b6abb0..81b0177 100644
--- a/src/globals.h
+++ b/src/globals.h
@@ -1190,8 +1190,8 @@ EXTERN intlcs_conceal INIT(= ' ');
 #if defined(FEAT_WINDOWS) || defined(FEAT_WILDMENU) || defined(FEAT_STL_OPT) \
|| defined(FEAT_FOLDING)
 /* Characters from 'fillchars' option */
-EXTERN int fill_stl INIT(= ' ');
-EXTERN int fill_stlnc INIT(= ' ');
+EXTERN int fill_stl INIT(= NUL);
+EXTERN int fill_stlnc INIT(= NUL);
 #endif
 #if defined(FEAT_WINDOWS) || defined(FEAT_FOLDING)
 EXTERN int fill_vert INIT(= ' ');
diff --git a/src/screen.c b/src/screen.c
index ee61a01..c4ec1a9 100644
--- a/src/screen.c
+++ b/src/screen.c
@@ -10532,13 +10532,11 @@ fillchar_status(int *attr, int is_curwin)
*attr = hl_attr(HLF_SNC);
fill = fill_stlnc;
 }
-/* Use fill when there is highlighting, and highlighting of current
- * window differs, or the fillchars differ, or this is not the
- * current window */
-if (*attr != 0 && ((hl_attr(HLF_S) != hl_attr(HLF_SNC)
-   || !is_curwin || ONE_WINDOW)
-   || (fill_stl != fill_stlnc)))
+/* Use fill when there is highlighting */
+if (fill != NUL && *attr != 0)
return fill;
+if (ONE_WINDOW)
+   return ' ';
 if (is_curwin)
return '^';
 return '=';
diff --git a/src/testdir/test_alot.vim b/src/testdir/test_alot.vim
index d24b97f..abee0eb 100644
--- a/src/testdir/test_alot.vim
+++ b/src/testdir/test_alot.vim
@@ -14,6 +14,7 @@ source test_expand_dllpath.vim
 source test_feedkeys.vim
 source test_file_perm.vim
 source test_fileformat.vim
+source test_fillchars.vim
 source test_filter_cmd.vim
 source test_filter_map.vim
 source test_fnamemodify.vim
diff --git a/src/testdir/test_fillchars.vim b/src/testdir/test_fillchars.vim
new file mode 100644
index 000..b8d5cde
--- /dev/null
+++ b/src/testdir/test_fillchars.vim
@@ -0,0 +1,38 @@
+function! Test_fillchars_stl_stlnc_vert()
+  set laststatus=2 statusline=\  fillchars=stl:~,stlnc:_,vert:* nosplitright
+  highlight StatusLine ctermbg=8 ctermfg=15 cterm=NONE guibg=#808080 
guifg=#ff gui=NONE
+  highlight StatusLineNC ctermbg=8 ctermfg=7 cterm=NONE guibg=#808080 
guifg=#c0c0c0 gui=NONE
+  only! | vnew
+  redrawstatus!
+  call assert_equal('~', nr2char(screenchar(winheight(0) + 1, 2)))
+  call assert_equal('_', nr2char(screenchar(winheight(0) + 1, winwidth(0) + 
3)))
+  echo assert_equal('*', nr2char(screenchar(1, winwidth(0) + 1)))
+endfunction
+
+function! Test_fillchars_stl_stlnc_one_window()
+  set laststatus=2 statusline=\  fillchars=stl:~,stlnc:_ nosplitright
+  highlight StatusLine ctermbg=8 ctermfg=15 cterm=NONE guibg=#808080 
guifg=#ff gui=NONE
+  only!
+  redrawstatus!
+  call assert_equal('~', nr2char(screenchar(winheight(0) + 1, 2)))
+endfunction
+
+function! Test_fillchars_same_stl_stlnc_same_highlight()
+  set laststatus=2 statusline=\  fillchars=stl:_,stlnc:_ nosplitright
+  highlight StatusLine ctermbg=8 ctermfg=7 cterm=NONE guibg=#808080 
guifg=#c0c0c0 gui=NONE
+  highlight StatusLineNC ctermbg=8 ctermfg=7 cterm=NONE guibg=#808080 
guifg=#c0c0c0 gui=NONE
+  only! | vnew
+  redrawstatus!
+  call assert_equal('_', nr2char(screenchar(winheight(0) + 1, 2)))
+  call assert_equal('_', nr2char(screenchar(winheight(0) + 1, winwidth(0) + 
3)))
+endfunction
+
+function! Test_fillchars_stl_stlnc_highlights_cleared()
+  set laststatus=2 statusline=\  fillchars=stl:~,stlnc:_ nosplitright
+  highlight clear StatusLine
+  highlight clear StatusLineNC
+  only! | vnew
+  redrawstatus!
+  call assert_equal('^', nr2char(screenchar(winheight(0) + 1, 2)))
+  call assert_equal('=', nr2char(screenchar(winheight(0) + 1, winwidth(0) + 
3)))
+endfunction

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are

Re: [vim/vim] set complete ignores priority order (#1316)

2016-12-12 Fir de Conversatie h_east 
Hi All,

2016-12-12(Mon) 21:58:29 UTC+9 Lifepillar:
> I think noinsert or noselect is ignored only when completeopt includes menu 
> instead of menuone.
> 
> 
> That would be more acceptable for me, too. My plugin requires menuone, so it 
> would not be affected.

Hmm, Your requires item is `menu`, isn't it?

I think that it isn't a good design to change the behavior of only `menuone`.
Rather than making that change, it is better to not change the current behavior.

...Or, add a new value to 'completeopt'...
For example, "forceinsertone" ...

I will not proactively act on this proposal. But I also want to hear opinions 
from other people.

Thanks.
--
Best regards,
Hirohito Higashi (a.k.a. h_east)

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