Re: Patch 8.0.1123

2017-09-18 Fir de Conversatie Christian Brabandt

On Mo, 18 Sep 2017, Bram Moolenaar wrote:

> Seems you run into a bug.  I don't see these problems.  Try these
> commands:
> 
>   amenu WinBar.Next :echo 'next'
>   amenu WinBar.Prev :echo 'prev'
>   amenu WinBar.Cont :echo 'cont'
> 

So WinBar is the important part?


> Don't you get a window toolbar right away?
> Perhaps some plugin is interfering?

No. Try this:

vim --clean -c 'packadd termdebug' -c 'Termdebug'

Note, the main window is empty and no toolbar is drawn.

Note also, the cmdheight seems to be 2, but is actually only 1.

The toolbar isn't drawn on neither tmux inside a putty term, 
gnome-terminal nor gvim

Toolbar will be drawn as soon as you press 'o' in the main window to 
enter a new line in insert mode. Also the toolbar vanishes as soon as 
you press  or type :redraw!

If you have a file open in the main window, press 'j' until Vim scrolls 
down. Then the toolbar will be drawn. Press k to go up again. When Vim 
starts to scroll upward, the toolbar will remain at its current position 
and not be drawn at the new top line.

Version is 8.0.1127

Christian
-- 
Galletti: Schweigt, wir sind ja noch alle dumme Jungen.
Schüler: Ich nicht, Herr Professor.
Galletti: Aber ich!

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

2017-09-18 Fir de Conversatie Bram Moolenaar

Christian Brabandt wrote:

> On So, 17 Sep 2017, Bram Moolenaar wrote:
> 
> > Patch 8.0.1123
> > Problem:Cannot define a toolbar for a window.
> > Solution:   Add a window-local toolbar.
> > Files:  src/syntax.c, src/proto/syntax.pro, src/structs.h, src/menu.c,
> > src/proto/menu.pro, src/testdir/test_winbar.vim, src/Makefile,
> > src/normal.c, src/testdir/Make_all.mak, src/if_perl.xs,
> > src/eval.c, src/evalfunc.c, src/window.c, src/ui.c,
> > src/terminal.c, src/screen.c,
> > runtime/pack/dist/opt/termdebug/plugin/termdebug.vim,
> > runtime/doc/gui.txt, runtime/doc/terminal.txt
> 
> I feel like I am missing information how to add a toolbar to other 
> windows as well. I looked at the patch, and couldn't find out how you 
> added those toolbar commands to actually appear at the main window.
> 
> I just tried out latest Vim to see how this works and it looks like the 
> toolbar will only get displayed, once the window actually starts to 
> scroll, e.g. a redraw of the first line will show those toolbar 
> commands. Unfortunately, a  will remove the toolbar again.
> 
> At first this was confusing, because I expected a toolbar and nothing 
> showed up, until after I started to scroll the window (using the 
> cursor).
> 
> Also after scrolling up and down a bit the toolbar also scrolls a bit 
> and appears in the middle of the window.

Seems you run into a bug.  I don't see these problems.  Try these
commands:

amenu WinBar.Next :echo 'next'
amenu WinBar.Prev :echo 'prev'
amenu WinBar.Cont :echo 'cont'

Don't you get a window toolbar right away?
Perhaps some plugin is interfering?

-- 
hundred-and-one symptoms of being an internet addict:
159. You get excited whenever discussing your hard drive.

 /// 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] indentkeys regression introduced in 8.0.1041 (#2114)

2017-09-18 Fir de Conversatie Bram Moolenaar

Christian (?) wrote:

> On Mo, 18 Sep 2017, Bram Moolenaar wrote:
> 
> > I'll have a look
> > 
> > Christian
> 
> Interesting. The original mail from github already had this header:
> 
> ,
> | From: Bram Moolenaar 
> `
> 
> Seems like this is a github issue?

Either that or I'm schizophrenic :-)

-- 
hundred-and-one symptoms of being an internet addict:
160. You get in the elevator and double-click the button for the floor
 you want.

 /// 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] indentkeys regression introduced in 8.0.1041 (#2114)

2017-09-18 Fir de Conversatie Christian Brabandt

On Mo, 18 Sep 2017, Bram Moolenaar wrote:

> I'll have a look
> 
> Christian

Interesting. The original mail from github already had this header:

,
| From: Bram Moolenaar 
`

Seems like this is a github issue?

Christian
-- 
Wenn das bloße Lesen die Leser so ausbildete: so müßte man im
6. Jahrtausend zehn mal besser schreiben als im 2. Jahrtausend.
-- Jean Paul

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

2017-09-18 Fir de Conversatie Christian Brabandt

On So, 17 Sep 2017, Bram Moolenaar wrote:

> Patch 8.0.1123
> Problem:Cannot define a toolbar for a window.
> Solution:   Add a window-local toolbar.
> Files:  src/syntax.c, src/proto/syntax.pro, src/structs.h, src/menu.c,
> src/proto/menu.pro, src/testdir/test_winbar.vim, src/Makefile,
> src/normal.c, src/testdir/Make_all.mak, src/if_perl.xs,
> src/eval.c, src/evalfunc.c, src/window.c, src/ui.c,
> src/terminal.c, src/screen.c,
> runtime/pack/dist/opt/termdebug/plugin/termdebug.vim,
> runtime/doc/gui.txt, runtime/doc/terminal.txt

I feel like I am missing information how to add a toolbar to other 
windows as well. I looked at the patch, and couldn't find out how you 
added those toolbar commands to actually appear at the main window.

I just tried out latest Vim to see how this works and it looks like the 
toolbar will only get displayed, once the window actually starts to 
scroll, e.g. a redraw of the first line will show those toolbar 
commands. Unfortunately, a  will remove the toolbar again.

At first this was confusing, because I expected a toolbar and nothing 
showed up, until after I started to scroll the window (using the 
cursor).

Also after scrolling up and down a bit the toolbar also scrolls a bit 
and appears in the middle of the window.

Christian
-- 
Heute: Tag, an dem man gute Vorsätze faßt.
Morgen: Frühester Termin für ihre Verwirklichung.
-- Ron Kritzfeld

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

2017-09-18 Fir de Conversatie Bram Moolenaar

Patch 8.0.1127
Problem:Test_peek_and_get_char fails on 32 bit system. (Eliminate
Riesebieter)
Solution:   Avoid an integer overflow. (James McCoy, closes #2116)
Files:  src/ex_cmds2.c


*** ../vim-8.0.1126/src/ex_cmds2.c  2017-09-16 20:54:47.094560435 +0200
--- src/ex_cmds2.c  2017-09-18 21:47:11.749997206 +0200
***
*** 1090,1104 
  static timer_T*first_timer = NULL;
  static long   last_timer_id = 0;
  
! # ifdef WIN3264
! #  define GET_TIMEDIFF(timer, now) \
!   (long)(((double)(timer->tr_due.QuadPart - now.QuadPart) \
!  / (double)fr.QuadPart) * 1000)
! # else
! #  define GET_TIMEDIFF(timer, now) \
!   (timer->tr_due.tv_sec - now.tv_sec) * 1000 \
!  + (timer->tr_due.tv_usec - now.tv_usec) / 1000
! # endif
  
  /*
   * Insert a timer in the list of timers.
--- 1090,1113 
  static timer_T*first_timer = NULL;
  static long   last_timer_id = 0;
  
! static long
! timer_time_left(timer_T *timer, proftime_T *now)
! {
! #  ifdef WIN3264
! LARGE_INTEGER fr;
! 
! if (now->QuadPart > timer->tr_due.QuadPart)
!   return 0;
! QueryPerformanceFrequency();
! return (long)(((double)(timer->tr_due.QuadPart - now->QuadPart)
!  / (double)fr.QuadPart) * 1000);
! #  else
! if (now->tv_sec > timer->tr_due.tv_sec)
!   return 0;
! return (timer->tr_due.tv_sec - now->tv_sec) * 1000
!   + (timer->tr_due.tv_usec - now->tv_usec) / 1000;
! #  endif
! }
  
  /*
   * Insert a timer in the list of timers.
***
*** 1196,1212 
  int   did_one = FALSE;
  int   need_update_screen = FALSE;
  long  current_id = last_timer_id;
- # ifdef WIN3264
- LARGE_INTEGER   fr;
- # endif
  
  /* Don't run any timers while exiting or dealing with an error. */
  if (exiting || aborting())
return next_due;
  
- # ifdef WIN3264
- QueryPerformanceFrequency();
- # endif
  profile_start();
  for (timer = first_timer; timer != NULL && !got_int; timer = timer_next)
  {
--- 1205,1215 
***
*** 1214,1220 
  
if (timer->tr_id == -1 || timer->tr_firing || timer->tr_paused)
continue;
!   this_due = GET_TIMEDIFF(timer, now);
if (this_due <= 1)
{
int save_timer_busy = timer_busy;
--- 1217,1223 
  
if (timer->tr_id == -1 || timer->tr_firing || timer->tr_paused)
continue;
!   this_due = timer_time_left(timer, );
if (this_due <= 1)
{
int save_timer_busy = timer_busy;
***
*** 1266,1272 
&& timer->tr_emsg_count < 3)
{
profile_setlimit(timer->tr_interval, >tr_due);
!   this_due = GET_TIMEDIFF(timer, now);
if (this_due < 1)
this_due = 1;
if (timer->tr_repeat > 0)
--- 1269,1275 
&& timer->tr_emsg_count < 3)
{
profile_setlimit(timer->tr_interval, >tr_due);
!   this_due = timer_time_left(timer, );
if (this_due < 1)
this_due = 1;
if (timer->tr_repeat > 0)
***
*** 1344,1352 
  dictitem_T*di;
  long  remaining;
  proftime_Tnow;
- # ifdef WIN3264
- LARGE_INTEGER   fr;
- #endif
  
  if (dict == NULL)
return;
--- 1347,1352 
***
*** 1356,1365 
  dict_add_nr_str(dict, "time", (long)timer->tr_interval, NULL);
  
  profile_start();
! # ifdef WIN3264
! QueryPerformanceFrequency();
! # endif
! remaining = GET_TIMEDIFF(timer, now);
  dict_add_nr_str(dict, "remaining", (long)remaining, NULL);
  
  dict_add_nr_str(dict, "repeat",
--- 1356,1362 
  dict_add_nr_str(dict, "time", (long)timer->tr_interval, NULL);
  
  profile_start();
! remaining = timer_time_left(timer, );
  dict_add_nr_str(dict, "remaining", (long)remaining, NULL);
  
  dict_add_nr_str(dict, "repeat",
*** ../vim-8.0.1126/src/version.c   2017-09-18 21:23:02.938622902 +0200
--- src/version.c   2017-09-18 21:46:17.906315415 +0200
***
*** 763,764 
--- 763,766 
  {   /* Add new patch number below this line */
+ /**/
+ 1127,
  /**/

-- 
hundred-and-one symptoms of being an internet addict:
156. You forget your friend's name but not her e-mail address.

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

Patch 8.0.1126

2017-09-18 Fir de Conversatie Bram Moolenaar

Patch 8.0.1126
Problem:Endless resize when terminal showing in two buffers. (Hirohito
Higashi)
Solution:   Set a flag to prevent resizing the window.
Files:  src/terminal.c


*** ../vim-8.0.1125/src/terminal.c  2017-09-17 23:02:17.176074400 +0200
--- src/terminal.c  2017-09-18 21:19:31.007890281 +0200
***
*** 39,44 
--- 39,45 
   *
   * TODO:
   * - Shift-Tab does not work.
+  * - click in Window toolbar of other window: save/restore Insert and Visual
   * - Redirecting output does not work on MS-Windows, 
Test_terminal_redir_file()
   *   is disabled.
   * - implement term_setsize()
***
*** 98,103 
--- 99,107 
  job_T *tl_job;
  buf_T *tl_buffer;
  
+ /* Set when setting the size of a vterm, reset after redrawing. */
+ int   tl_vterm_size_changed;
+ 
  /* used when tl_job is NULL and only a pty was created */
  int   tl_tty_fd;
  char_u*tl_tty_in;
***
*** 2016,2031 
  
  term->tl_rows = rows;
  term->tl_cols = cols;
! FOR_ALL_WINDOWS(wp)
  {
!   if (wp->w_buffer == term->tl_buffer)
{
!   win_setheight_win(rows, wp);
!   win_setwidth_win(cols, wp);
}
  }
- 
- redraw_buf_later(term->tl_buffer, NOT_VALID);
  return 1;
  }
  
--- 2020,2040 
  
  term->tl_rows = rows;
  term->tl_cols = cols;
! if (term->tl_vterm_size_changed)
!   /* Size was set by vterm_set_size(), don't set the window size. */
!   term->tl_vterm_size_changed = FALSE;
! else
  {
!   FOR_ALL_WINDOWS(wp)
{
!   if (wp->w_buffer == term->tl_buffer)
!   {
!   win_setheight_win(rows, wp);
!   win_setwidth_win(cols, wp);
!   }
}
+   redraw_buf_later(term->tl_buffer, NOT_VALID);
  }
  return 1;
  }
  
***
*** ,2227 
--- 2231,2237 
}
}
  
+   term->tl_vterm_size_changed = TRUE;
vterm_set_size(vterm, rows, cols);
ch_log(term->tl_job->jv_channel, "Resizing terminal to %d lines",
 rows);
*** ../vim-8.0.1125/src/version.c   2017-09-18 20:31:37.596757010 +0200
--- src/version.c   2017-09-18 21:20:28.747544859 +0200
***
*** 763,764 
--- 763,766 
  {   /* Add new patch number below this line */
+ /**/
+ 1126,
  /**/

-- 
Although the scythe isn't pre-eminent among the weapons of war, anyone who
has been on the wrong end of, say, a peasants' revolt will know that in
skilled hands it is fearsome.
-- (Terry Pratchett, Mort)

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

2017-09-18 Fir de Conversatie Bram Moolenaar

Hirohito Higashi wrote:

> > > 2017-9-18(Mon) 3:32:52 UTC+9 Bram Moolenaar:
> > > > Patch 8.0.1119
> > > > Problem:Quitting a split terminal window kills the job. (Yasuhiro
> > > > Matsumoto)
> > > > Solution:   Only stop terminal job if it is the last window.
> > > > Files:  src/buffer.c, src/testdir/test_terminal.vim
> > > [...]
> > > 
> > > This patch hangs by doing the following operation.
> > > 
> > > $ vim --clean
> > > :term
> > > v
> > 
> > Works fine for me.  Is this on MS-Windows perhaps?
> 
> My env.:
> OS: fedora 25 (x64)
> Vim: 8.0.1123 (./configure --enable-gui=gnome2 --enable-fail-if-missing)
> 
> Both CUI(vim --clean) and GUI(vim --clean -g) will occur.
> 
> In the case of GUI, it may occur even at s

It depends on the Vim window size, if the two windows showing the same
terminal have a different size.  I'll make a patch.

-- 
hundred-and-one symptoms of being an internet addict:
152. You find yourself falling for someone you've never seen or hardly
 know, but, boy can he/she TYPE!!

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

2017-09-18 Fir de Conversatie Bram Moolenaar

Patch 8.0.1125
Problem:Wrong window height when splitting window with window toolbar.
Solution:   Add or subtract the window toolbar height.
Files:  src/window.c


*** ../vim-8.0.1124/src/window.c2017-09-17 23:02:17.176074400 +0200
--- src/window.c2017-09-18 20:27:19.566268119 +0200
***
*** 1098, 
{
/* set height and row of new window to full height */
wp->w_winrow = tabline_height();
!   win_new_height(wp, curfrp->fr_height - (p_ls > 0));
wp->w_status_height = (p_ls > 0);
}
else
{
/* height and row of new window is same as current window */
wp->w_winrow = oldwin->w_winrow;
!   win_new_height(wp, oldwin->w_height);
wp->w_status_height = oldwin->w_status_height;
}
frp->fr_height = curfrp->fr_height;
--- 1098,1119 
{
/* set height and row of new window to full height */
wp->w_winrow = tabline_height();
!   win_new_height(wp, curfrp->fr_height - (p_ls > 0)
! #ifdef FEAT_MENU
!   - wp->w_winbar_height
! #endif
!   );
wp->w_status_height = (p_ls > 0);
}
else
{
/* height and row of new window is same as current window */
wp->w_winrow = oldwin->w_winrow;
!   win_new_height(wp, oldwin->w_height
! #ifdef FEAT_MENU
!   + oldwin->w_winbar_height
! #endif
!   );
wp->w_status_height = oldwin->w_status_height;
}
frp->fr_height = curfrp->fr_height;
***
*** 1163,1169 
win_new_height(wp, new_size);
if (flags & (WSP_TOP | WSP_BOT))
{
!   int new_fr_height = curfrp->fr_height - new_size;
  
if (!((flags & WSP_BOT) && p_ls == 0))
new_fr_height -= STATUS_HEIGHT;
--- 1171,1181 
win_new_height(wp, new_size);
if (flags & (WSP_TOP | WSP_BOT))
{
!   int new_fr_height = curfrp->fr_height - new_size
! #ifdef FEAT_MENU
!   + wp->w_winbar_height
! #endif
!   ;
  
if (!((flags & WSP_BOT) && p_ls == 0))
new_fr_height -= STATUS_HEIGHT;
***
*** 2855,2861 
  {
/* Simple case: just one window. */
win_new_height(topfrp->fr_win,
!   height - topfrp->fr_win->w_status_height);
  }
  else if (topfrp->fr_layout == FR_ROW)
  {
--- 2867,2877 
  {
/* Simple case: just one window. */
win_new_height(topfrp->fr_win,
!   height - topfrp->fr_win->w_status_height
! #ifdef FEAT_MENU
!   - topfrp->fr_win->w_winbar_height
! #endif
!   );
  }
  else if (topfrp->fr_layout == FR_ROW)
  {
***
*** 3201,3207 
  static void
  frame_fix_height(win_T *wp)
  {
! wp->w_frame->fr_height = wp->w_height + wp->w_status_height;
  }
  
  /*
--- 3217,3227 
  static void
  frame_fix_height(win_T *wp)
  {
! wp->w_frame->fr_height = wp->w_height + wp->w_status_height
! #ifdef FEAT_MENU
!   + wp->w_winbar_height
! #endif
!   ;
  }
  
  /*
*** ../vim-8.0.1124/src/version.c   2017-09-18 20:00:58.495584481 +0200
--- src/version.c   2017-09-18 20:08:28.484924406 +0200
***
*** 763,764 
--- 763,766 
  {   /* Add new patch number below this line */
+ /**/
+ 1125,
  /**/

-- 
hundred-and-one symptoms of being an internet addict:
151. You find yourself engaged to someone you've never actually met,
 except through e-mail.

 /// 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: MZSCHEME_VER nomenclature

2017-09-18 Fir de Conversatie Bram Moolenaar

Ken Takata wrote:

> 2017/9/18 Mon 3:07:09 UTC+9 Steve Hall wrote:
> > On Sat, Sep 16, 2017 at 9:28 PM, Ken Takata  wrote:
> > > 2017/9/17 Sun 4:05:18 UTC+9 Steve Hall wrote:
> > > > What is the MZSCHEME_VER variable nomenclature?
> > > 
> > > As I wrote in src/INSTALLpc.txt, 
> > 
> > Ah, was looking in the make files, :help mzscheme, if_mzsch, and
> > everywhere else but there.
> 
> I should have updated the makefiles not only src/INSTALLpc.txt.
> Please find the attached patch.

I'll include it, thanks.

> > > it is used for the dll name.
> > 
> > I see.
> > 
> > > There's no easy way to detect the name automatically.
> > 
> > Would it help for me to forward the 6.8 and 6.10 names to include in
> > the docs? Thanks again for your help.
> 
> I haven't installed 6.10, so I don't know the name of it.  If you have already
> installed it, could you report the name here?
> 
> 6.8 was 3m_a1zjsw.  I thought I checked the name when answering your old mail:
> https://groups.google.com/d/msg/vim_dev/6UbysTiI2oU/LOWRVxUXAwAJ

-- 
You are not really successful until someone claims he sat
beside you in school.

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

2017-09-18 Fir de Conversatie Bram Moolenaar

Patch 8.0.1124
Problem:Use of MZSCHEME_VER is unclear.
Solution:   Add a comment. (Ken Takata)
Files:  src/Make_cyg_ming.mak, src/Make_mvc.mak


*** ../vim-8.0.1123/src/Make_cyg_ming.mak   2017-09-01 18:41:22.829711616 
+0200
--- src/Make_cyg_ming.mak   2017-09-18 19:59:21.516158123 +0200
***
*** 221,226 
--- 221,228 
  #   MZSCHEME=[Path to MzScheme directory] (Set inside Make_cyg.mak or 
Make_ming.mak)
  #   DYNAMIC_MZSCHEME=yes (to load the MzScheme DLL dynamically)
  #   MZSCHEME_VER=[MzScheme version] (default is 3m_a0solc (6.6))
+ # Used for the DLL file name. E.g.:
+ # C:\Program Files (x86)\Racket\lib\libracket3m_XX.dll
  #   MZSCHEME_DEBUG=no
  ifdef MZSCHEME
  ifndef DYNAMIC_MZSCHEME
*** ../vim-8.0.1123/src/Make_mvc.mak2017-09-01 18:41:22.829711616 +0200
--- src/Make_mvc.mak2017-09-18 19:59:21.516158123 +0200
***
*** 47,53 
  # MzScheme interface:
  #   MZSCHEME=[Path to MzScheme directory]
  #   DYNAMIC_MZSCHEME=yes (to load the MzScheme DLLs dynamically)
! #   MZSCHEME_VER=[version, 205_000, ...] (default is 3m_a0solc (6.6))
  #   MZSCHEME_DEBUG=no
  #
  # Perl interface:
--- 47,55 
  # MzScheme interface:
  #   MZSCHEME=[Path to MzScheme directory]
  #   DYNAMIC_MZSCHEME=yes (to load the MzScheme DLLs dynamically)
! #   MZSCHEME_VER=[MzScheme version] (default is 3m_a0solc (6.6))
! # Used for the DLL file name. E.g.:
! # C:\Program Files (x86)\Racket\lib\libracket3m_XX.dll
  #   MZSCHEME_DEBUG=no
  #
  # Perl interface:
*** ../vim-8.0.1123/src/version.c   2017-09-17 23:02:17.180074376 +0200
--- src/version.c   2017-09-18 19:59:48.068001054 +0200
***
*** 763,764 
--- 763,766 
  {   /* Add new patch number below this line */
+ /**/
+ 1124,
  /**/

-- 
hundred-and-one symptoms of being an internet addict:
150. You find yourself counting emoticons to get to sleep.

 /// 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: MZSCHEME_VER nomenclature

2017-09-18 Fir de Conversatie Steve Hall
On Sun, Sep 17, 2017 at 9:14 PM, Ken Takata  wrote:
>
> I haven't installed 6.10, so I don't know the name of it.  If you
> have already installed it, could you report the name here?

6.6  3m_a0solc
6.8  3m_a1zjsw
6.10 3m_a36fs8

All three build for me.

-- 
Steve Hall  [ digitect dancingpaper com ]
Cream for Vim  http://cream.SourceForge.net

-- 
-- 
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] needless key after :terminal on Windows GUI (#1924)

2017-09-18 Fir de Conversatie Cesar Romani

On 03/08/2017 01:45 p.m., Bram Moolenaar (Vim Github Repository) wrote:
> Closed #1924  via e9c21ae
> 
.

>

But, what is the solution? I'm also having the same problem with the
newest vim.

Regards,

--
Cesar

--
--
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: Test failure building 8.0.1111

2017-09-18 Fir de Conversatie Elimar Riesebieter
* James McCoy  [2017-09-17 23:41 -0400]:

> On Sun, Sep 17, 2017 at 09:00:19PM +0200, Bram Moolenaar wrote:
> > 
> > Elimar Riesebieter wrote:
> > 
> > > > > > > on a  32bit (i386) system I get:
> > > > > > > 
> > > > > > > Found errors in Test_peek_and_get_char():
> > > > > > > function RunTheTest[24]..Test_peek_and_get_char line 7: Expected 
> > > > > > > 97 but got 3
> > > > > > > Found errors in Test_stop_all_in_callback():
> > > > > > > function RunTheTest[24]..Test_stop_all_in_callback line 3: 
> > > > > > > Expected 1 but got 2
> > > > > > > 
> > > > > > > 
> > > > > > > On a 64bit (amd64) system the build went fine.
> > > > > > 
> > > > > > Strange, I have not seen that fail.  Is it just flaky perhaps?
> > > > > 
> > > > > A simple
> > > > > 
> > > > > ./configure && make && make test
> > > > > 
> > > > > in a clean source tree (meanwhile v8.0.1118) gives the same error.
> > > > 
> > > > What kind of system is this?
> > > 
> > > Linux 4.9.50, i386
> > 
> > I don't have a 32 bit Linux system, I hope someone else can look into
> > this.
> 
> This should be fixed by .

I can confirm that the tests run fine with this commit on both i386
and ppc.
Thanks!

Elimar
-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche

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

2017-09-18 Fir de Conversatie h_east
Hi Bram,

2017-9-18(Mon) 18:08:21 UTC+9 Bram Moolenaar:
> Hirohito Higashi wrote:
> 
> > 2017-9-18(Mon) 3:32:52 UTC+9 Bram Moolenaar:
> > > Patch 8.0.1119
> > > Problem:Quitting a split terminal window kills the job. (Yasuhiro
> > > Matsumoto)
> > > Solution:   Only stop terminal job if it is the last window.
> > > Files:  src/buffer.c, src/testdir/test_terminal.vim
> > [...]
> > 
> > This patch hangs by doing the following operation.
> > 
> > $ vim --clean
> > :term
> > v
> 
> Works fine for me.  Is this on MS-Windows perhaps?

My env.:
OS: fedora 25 (x64)
Vim: 8.0.1123 (./configure --enable-gui=gnome2 --enable-fail-if-missing)

Both CUI(vim --clean) and GUI(vim --clean -g) will occur.

In the case of GUI, it may occur even at s

--
Best regards,
Hirohito Higashi (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.


Re: Patch 8.0.1119

2017-09-18 Fir de Conversatie Bram Moolenaar

Hirohito Higashi wrote:

> 2017-9-18(Mon) 3:32:52 UTC+9 Bram Moolenaar:
> > Patch 8.0.1119
> > Problem:Quitting a split terminal window kills the job. (Yasuhiro
> > Matsumoto)
> > Solution:   Only stop terminal job if it is the last window.
> > Files:  src/buffer.c, src/testdir/test_terminal.vim
> [...]
> 
> This patch hangs by doing the following operation.
> 
> $ vim --clean
> :term
> v

Works fine for me.  Is this on MS-Windows perhaps?

-- 
hundred-and-one symptoms of being an internet addict:
148. You find it easier to dial-up the National Weather Service
 Weather/your_town/now.html than to simply look out the window.

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