Johnston D Johnston wrote:

> On Wed, 24 Dec 2003 15:00:03 +0100,
> Bram Moolenaar <Bram@...> wrote:
> > Mark Waggoner wrote:
> [...]
> > > I needed to modify this to be:
> > >
> > >    perlcppflags=`$vi_cv_path_perl -Mlib=$srcdir -MExtUtils::Embed \
> > >      -e 'ccflags;perl_inc;print"\n"' | sed -e 's/-fno[^ ]*//'`
> >
> > Why doesn't Perl add a newline after the text it writes to stdout?
> > Anyway, that's how it is.
>
> It's a *good* thing that Perl doesn't add a newline.  The output of the
> subs ccflags(), perl_inc(), ldopts(), &c. was designed to be "glued"
> into a cc command line, such as:
>
> cc -o prog prog.c `perl -MExtUtils::Embed -e ccflags -e ldopts`
>
> Naturally, you wouldn't want newlines in the middle of your cc command.

If you use backticks like that, the shell will remove the (trailing)
newline for you.  Most commands add line breaks, thus the shell removes
them.

Try this with a short "file" that contains line breaks:

	 echo `cat file`

It will display a single line.

Thus Perl should add a newline in that output.

--
From "know your smileys":
  *<|:-) Santa Claus (Ho Ho Ho)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Hi,

attached is a bugreport I received via the Debian BTS. I could
reproduce it here.

Regards, Norbert

Package: vim
Version: 1:6.1-320+1
Severity: normal

When '.${file}.sw[a-p]' exist, and ${file} is edited, Wim use
'.${file}.svz' as a swap file, but when trying to recover ${file}, this
swap file is not read.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux bateleur.arcanes 2.4.21-bateleur #1 SMP mer jui 30 14:21:14 CEST
2003 i686
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro

Versions of packages vim depends on:
ii  dpkg                      1.10.18        Package maintenance system for Deb
ii  libc6                     2.3.2.ds1-10   GNU C Library: Shared libraries an
ii  libgpmg1                  1.19.6-12.1    General Purpose Mouse Library [lib
ii  libncurses5               5.3.20030719-1 Shared libraries for terminal hand

-- no debconf information


--
pierre.thierry@...
OpenPGP 0xD9D50D8A

Norbert Tretkowski wrote:

> attached is a bugreport I received via the Debian BTS. I could
> reproduce it here.

[...]

> When '.${file}.sw[a-p]' exist, and ${file} is edited, Wim use
> '.${file}.svz' as a swap file, but when trying to recover ${file}, this
> swap file is not read.

This is a known limitation.  When opening a file Vim doesn't check all
possible swap file extensions, it would slow down opening a file too
much.

You can recover a file by passing the name of the swap file:

	 vim -r .file.svz

Note that this situation mostly only happens when you get a warning for
"file already being edited".  Thus the user has been warned.  Unless
.file.swp is not a Vim swap file.

--
There's no place like $(HOME)!

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.155
Problem:    Win32: Using ":tjump www" in a help file gives two results.
	     (Dave Roberts)
Solution:   Ignore differences between slashes and backslashes when checking
	     for identical tag matches.
Files:     src/tag.c


*** ../vim-6.2.154/src/tag.c Sun Oct 12 16:52:45 2003
--- src/tag.c Mon Dec 15 20:36:00 2003
***************
*** 1861,1866 ****
--- 1861,1871 ----
  			 {
  			     p[0] = mtt;
  			     STRCPY(p + 1, tag_fname);
+ #ifdef BACKSLASH_IN_FILENAME
+ 			    /* Ignore differences in slashes, avoid adding
+ 			     * both path/file and path\file. */
+ 			    slash_adjust(p + 1);
+ #endif
  			     s = p + 1 + STRLEN(tag_fname) + 1;
   #ifdef FEAT_EMACS_TAGS
  			     if (is_etag)
*** ../vim-6.2.154/src/version.c Wed Nov 12 20:56:23 2003
--- src/version.c Mon Dec 29 19:47:28 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     155,
   /**/

--
I AM THANKFUL...
...for the mess to clean after a party because it means I have
been surrounded by friends.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.156 (after 6.2.125)
Problem:    Win32: Netbeans fails to build, EINTR is not defined.
Solution:   Redefine EINTR to WSAEINTR. (Mike Williams)
Files:     src/netbeans.c


*** ../vim-6.2.155/src/netbeans.c Fri Oct 17 12:13:28 2003
--- src/netbeans.c Wed Dec 24 12:42:27 2003
***************
*** 32,37 ****
--- 32,41 ----
    * errno... */
   # define sock_errno WSAGetLastError()
   # define ECONNREFUSED WSAECONNREFUSED
+ # ifdef EINTR
+ #  undef EINTR
+ # endif
+ # define EINTR WSAEINTR
   # define sock_write(sd, buf, len) send(sd, buf, len, 0)
   # define sock_read(sd, buf, len) recv(sd, buf, len, 0)
   # define sock_close(sd) closesocket(sd)
*** ../vim-6.2.155/src/version.c Mon Dec 29 19:48:35 2003
--- src/version.c Mon Dec 29 19:57:43 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     156,
   /**/

--
The primary purpose of the DATA statement is to give names to constants;
instead of referring to pi as 3.141592653589793 at every appearance, the
variable PI can be given that value with a DATA statement and used instead
of the longer form of the constant.  This also simplifies modifying the
program, should the value of pi change.
	 -- FORTRAN manual for Xerox Computers

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.157
Problem:    Using "%p" in 'errorformat' gives a column number that is too
	     high.
Solution:   Set the flag to use the number as a virtual column.  (Lefteris
	     Koutsoloukas)
Files:     src/quickfix.c


*** ../vim-6.2.156/src/quickfix.c Thu Sep 11 21:15:02 2003
--- src/quickfix.c Wed Dec 24 13:39:46 2003
***************
*** 476,482 ****
--- 476,486 ----
  		 if ((i = (int)fmt_ptr->addr[6]) > 0)  /* %r */
  		     tail = regmatch.startp[i];
  		 if ((i = (int)fmt_ptr->addr[7]) > 0)  /* %p */
+ 	 {
  		     col = (int)(regmatch.endp[i] - regmatch.startp[i] + 1);
+ 		    if (*((char_u *)regmatch.startp[i]) != TAB)
+ 		 use_virt_col = TRUE;
+ 	 }
  		 if ((i = (int)fmt_ptr->addr[8]) > 0)  /* %v */
  		 {
  		     col = (int)atol((char *)regmatch.startp[i]);
*** ../vim-6.2.156/src/version.c Mon Dec 29 20:14:44 2003
--- src/version.c Mon Dec 29 20:20:46 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     157,
   /**/

--
I AM THANKFUL...
...for a lawn that needs mowing, windows that need cleaning
and gutters that need fixing because it means I have a home.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.158
Problem:    The sed command on Solaris and HPUX doesn't work for a line that
	     doesn't end in a newline.
Solution:   Add a newline when feeding text to sed. (Mark Waggoner)
Files:     src/configure.in, src/auto/configure


*** ../vim-6.2.157/src/auto/configure Sun Nov  2 15:37:11 2003
--- src/auto/configure Wed Dec 24 14:10:23 2003
***************
*** 1572,1578 ****
         vi_cv_perllib=`$vi_cv_path_perl -MConfig -e 'print $Config{privlibexp}'`

               perlcppflags=`$vi_cv_path_perl -Mlib=$srcdir -MExtUtils::Embed \
! 	      -e 'ccflags;perl_inc' | sed -e 's/-fno[^ ]*//'`
         if test "X$perlcppflags" != "X"; then
  	 PERL_CFLAGS="$perlcppflags"
         fi
--- 1582,1588 ----
         vi_cv_perllib=`$vi_cv_path_perl -MConfig -e 'print $Config{privlibexp}'`

               perlcppflags=`$vi_cv_path_perl -Mlib=$srcdir -MExtUtils::Embed \
! 	      -e 'ccflags;perl_inc;print"\n"' | sed -e 's/-fno[^ ]*//'`
         if test "X$perlcppflags" != "X"; then
  	 PERL_CFLAGS="$perlcppflags"
         fi
*** ../vim-6.2.157/src/configure.in Sun Nov  2 15:37:11 2003
--- src/configure.in Wed Dec 24 14:09:32 2003
***************
*** 313,319 ****
         AC_SUBST(vi_cv_perllib)
         dnl Remove "-fno-something", it breaks using cproto.
         perlcppflags=`$vi_cv_path_perl -Mlib=$srcdir -MExtUtils::Embed \
! 	      -e 'ccflags;perl_inc' | sed -e 's/-fno[[^ ]]*//'`
         if test "X$perlcppflags" != "X"; then
  	 PERL_CFLAGS="$perlcppflags"
         fi
--- 314,320 ----
         AC_SUBST(vi_cv_perllib)
         dnl Remove "-fno-something", it breaks using cproto.
         perlcppflags=`$vi_cv_path_perl -Mlib=$srcdir -MExtUtils::Embed \
! 	      -e 'ccflags;perl_inc;print"\n"' | sed -e 's/-fno[[^ ]]*//'`
         if test "X$perlcppflags" != "X"; then
  	 PERL_CFLAGS="$perlcppflags"
         fi
*** ../vim-6.2.157/src/version.c Mon Dec 29 20:21:49 2003
--- src/version.c Mon Dec 29 20:25:14 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     158,
   /**/

--
A fool learns from his mistakes, a wise man from someone elses.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.159
Problem:    When using expression folding and 'foldopen' is "undo" an undo
	     command doesn't always open the fold.
Solution:   Save and restore the KeyTyped variable when evaluating 'foldexpr'.
	     (Taro Muraoka)
Files:     src/fold.c


*** ../vim-6.2.158/src/fold.c Tue Sep  2 22:25:25 2003
--- src/fold.c Tue Dec 16 09:47:43 2003
***************
*** 2842,2847 ****
--- 2842,2848 ----
       int  n;
       int  c;
       linenr_T lnum = flp->lnum + flp->off;
+     int  save_keytyped;

       win = curwin;
       curwin = flp->wp;
***************
*** 2854,2860 ****
--- 2855,2866 ----
       if (lnum <= 1)
  	 flp->lvl = 0;

+     /* KeyTyped may be reset to 0 when calling a function which invokes
+      * do_cmdline().  To make 'foldopen' work correctly restore KeyTyped. */
+     save_keytyped = KeyTyped;
       n = eval_foldexpr(flp->wp->w_p_fde, &c);
+     KeyTyped = save_keytyped;
+
       switch (c)
       {
  	 /* "a1", "a2", .. : add to the fold level */
*** ../vim-6.2.158/src/version.c Mon Dec 29 20:27:03 2003
--- src/version.c Mon Dec 29 20:29:37 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     159,
   /**/

--
I AM THANKFUL...
...for all the complaining I hear about the government
because it means we have freedom of speech.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.160
Problem:    When 'virtualedit' is "all" and 'selection is "exclusive",
	     selecting a double-width character below a single-width character
	     may cause a crash.
Solution:   Avoid overflow on unsigned integer decrement. (Taro Muraoka)
Files:     src/normal.c


*** ../vim-6.2.159/src/normal.c Sun Nov  9 20:35:08 2003
--- src/normal.c Tue Dec 16 10:06:16 2003
***************
*** 1510,1516 ****
  			 oap->start_vcol = start;
  		     if (end > oap->end_vcol)
  		     {
! 		 if (*p_sel == 'e' && start - 1 >= oap->end_vcol)
  			     oap->end_vcol = start - 1;
  			 else
  			     oap->end_vcol = end;
--- 1510,1517 ----
  			 oap->start_vcol = start;
  		     if (end > oap->end_vcol)
  		     {
! 		 if (*p_sel == 'e' && start >= 1
! 					 && start - 1 >= oap->end_vcol)
  			     oap->end_vcol = start - 1;
  			 else
  			     oap->end_vcol = end;
*** ../vim-6.2.159/src/version.c Mon Dec 29 20:30:12 2003
--- src/version.c Mon Dec 29 20:32:24 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     160,
   /**/

--
I AM THANKFUL...
...for the piles of laundry and ironing because it means I
have plenty of clothes to wear.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.161 (extra)
Problem:    VMS: Missing header file.  Reading input busy loops.
Solution:   Include termdef.h.  Avoid the use of a wait function in
	     vms_read().  (Frank Ries)
Files:     src/os_unix.h, src/os_vms.c


*** ../vim-6.2.160/src/os_unix.h Mon Jan 20 21:14:13 2003
--- src/os_unix.h Mon Nov 10 10:53:44 2003
***************
*** 218,223 ****
--- 218,224 ----
   #include <tt2def.h>
   #include <jpidef.h>
   #include <rms.h>
+ #include <trmdef.h>
   #include <string.h>
   #include <starlet.h>
   #include <socket.h>
*** ../vim-6.2.160/src/os_vms.c Wed Oct 29 14:40:27 2003
--- src/os_vms.c Tue Dec 23 14:30:31 2003
***************
*** 53,62 ****
   static short iochan; 	 /* TTY I/O channel */
   static short iosb[4];  /* IO status block */

! int vms_match_num = 0;
! int vms_match_alloced = 0;
! int vms_match_free = 0;
! char_u **vms_fmatch = NULL;
   static char *Fspec_Rms; 	       /* rms file spec, passed implicitly between
routines */


--- 53,61 ----
   static short iochan; 	 /* TTY I/O channel */
   static short iosb[4];  /* IO status block */

! static int vms_match_num = 0;
! static int vms_match_free = 0;
! static char_u **vms_fmatch = NULL;
   static char *Fspec_Rms; 	       /* rms file spec, passed implicitly between
routines */


***************
*** 145,151 ****
  	 return;
   }

! static TT_MODE
   get_tty(void)
   {

--- 144,150 ----
  	 return;
   }

!     static TT_MODE
   get_tty(void)
   {

***************
*** 299,322 ****
       int
   vms_read(char *inbuf, size_t nbytes)
   {
!     int     status, function, len;
!     float   wait = 0.05;
!     TT_MODE tt_mode;

       /* whatever happened earlier we need an iochan here */
       if (!iochan)
!        tt_mode = get_tty();

!     function = (IO$_READLBLK | IO$M_NOECHO | IO$M_TIMED | IO$M_ESCAPE);
       memset(inbuf, 0, nbytes);

       while (1)
       {
!  status = sys$qiow(0,iochan,function,&iosb,0,0,inbuf,nbytes-1,0,0,0,0);
  	 len = strlen(inbuf);
  	 if (len > 0)
  	     break;
-  lib$wait(&wait);
       }
       return len;
   }
--- 298,327 ----
       int
   vms_read(char *inbuf, size_t nbytes)
   {
!     int  status, function, len;
!     TT_MODE tt_mode;
!     ITEM itmlst[2];
!     static long trm_mask[8] = {-1, -1, -1, -1, -1, -1, -1, -1};

       /* whatever happened earlier we need an iochan here */
       if (!iochan)
!  tt_mode = get_tty();
!
!     vul_item(&itmlst[0], 0, TRM$_MODIFIERS,
! 	    (char *)(TRM$M_TM_ESCAPE | TRM$M_TM_NOECHO | TRM$M_TM_NOEDIT |
! 	       TRM$M_TM_NOFILTR | TRM$M_TM_NORECALL | TRM$M_TM_TRMNOECHO), 0);
!     vul_item(&itmlst[1], sizeof(trm_mask), TRM$_TERM, (char *)&trm_mask, 0);

!     function = (IO$_READLBLK | IO$M_EXTEND);
       memset(inbuf, 0, nbytes);

       while (1)
       {
!  status = sys$qiow(0, iochan, function, &iosb, 0, 0, inbuf, nbytes - 1,
! 					       0, 0, &itmlst, sizeof(itmlst));
  	 len = strlen(inbuf);
  	 if (len > 0)
  	     break;
       }
       return len;
   }
***************
*** 328,338 ****
    * Returns:  1 - continue finding matches
    *      0 - stop trying to find any further mathces
    */
! static int
   vms_wproc(char *name, int val)
   {
       int i;
       int nlen;

       if (val != DECC$K_FILE) /* Directories and foreing non VMS files are not
counting  */
  	 return 1;
--- 333,344 ----
    * Returns:  1 - continue finding matches
    *      0 - stop trying to find any further mathces
    */
!     static int
   vms_wproc(char *name, int val)
   {
       int i;
       int nlen;
+     static int vms_match_alloced = 0;

       if (val != DECC$K_FILE) /* Directories and foreing non VMS files are not
counting  */
  	 return 1;
*** ../vim-6.2.160/src/version.c Mon Dec 29 20:32:43 2003
--- src/version.c Mon Dec 29 20:34:56 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     161,
   /**/

--
From "know your smileys":
  [:-) Frankenstein's monster

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.162
Problem:    ":redraw" doesn't always display the text that includes the cursor
	     position, e.g. after ":call cursor(1, 0)". (Eugene Minkovskii)
Solution:   Call update_topline() before redrawing.
Files:     src/ex_docmd.c


*** ../vim-6.2.161/src/ex_docmd.c Wed Oct 29 14:37:09 2003
--- src/ex_docmd.c Tue Dec 16 13:51:40 2003
***************
*** 7116,7121 ****
--- 7116,7122 ----

       RedrawingDisabled = 0;
       p_lz = FALSE;
+     update_topline();
       update_screen(eap->forceit ? CLEAR :
   #ifdef FEAT_VISUAL
  	     VIsual_active ? INVERTED :
*** ../vim-6.2.161/src/version.c Mon Dec 29 20:36:56 2003
--- src/version.c Mon Dec 29 20:38:47 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     162,
   /**/

--
From "know your smileys":
  :-E Has major dental problems

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.163
Problem:    "make install" may also copy AAPDIR directories.
Solution:   Delete AAPDIR directories, just like CVS directories.
Files:     src/Makefile


*** ../vim-6.2.162/src/Makefile Sun Nov  2 15:37:11 2003
--- src/Makefile Wed Dec 24 14:28:14 2003
***************
*** 1724,1730 ****
  	 chmod $(FILEMOD) `find $(DEST_MACRO) -type f -print`
  	 chmod $(SCRIPTMOD) $(DEST_MACRO)/less.sh
   # When using CVS some CVS directories might have been copied.
!  cvs=`find $(DEST_MACRO) -name CVS -print`; \
  	       if test -n "$$cvs"; then \
  		  rm -rf $$cvs; \
  	       fi
--- 1727,1733 ----
  	 chmod $(FILEMOD) `find $(DEST_MACRO) -type f -print`
  	 chmod $(SCRIPTMOD) $(DEST_MACRO)/less.sh
   # When using CVS some CVS directories might have been copied.
!  cvs=`find $(DEST_MACRO) -name CVS -or -name AAPDIR -print`; \
  	       if test -n "$$cvs"; then \
  		  rm -rf $$cvs; \
  	       fi
***************
*** 1751,1757 ****
   # install the runtime tools
  	 $(INSTALL_DATA_R) $(TOOLSSOURCE)/* $(DEST_TOOLS)
   # When using CVS some CVS directories might have been copied.
!  cvs=`find $(DEST_TOOLS) -name CVS -print`; \
  	       if test -n "$$cvs"; then \
  		  rm -rf $$cvs; \
  	       fi
--- 1754,1760 ----
   # install the runtime tools
  	 $(INSTALL_DATA_R) $(TOOLSSOURCE)/* $(DEST_TOOLS)
   # When using CVS some CVS directories might have been copied.
!  cvs=`find $(DEST_TOOLS) -name CVS -or -name AAPDIR -print`; \
  	       if test -n "$$cvs"; then \
  		  rm -rf $$cvs; \
  	       fi
*** ../vim-6.2.162/src/version.c Mon Dec 29 20:39:18 2003
--- src/version.c Mon Dec 29 20:41:33 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     163,
   /**/

--
From "know your smileys":
  :-| :-|   Deja' vu!

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.164 (after 6.2.144)
Problem:    When "g:html_use_css" is set the HTML header generated by the
	     2html script is still wrong.
Solution:   Search for a string instead of jumping to a fixed line number.
	     Go to the start of the line before inserting the header.
	     (Jess Thrysoee)
Files:     runtime/syntax/2html.vim


*** ../vim-6.2.163/runtime/syntax/2html.vim Sun Nov  2 17:50:31 2003
--- runtime/syntax/2html.vim Thu Nov 13 17:01:05 2003
***************
*** 1,6 ****
   " Vim syntax support file
   " Maintainer: Bram Moolenaar <Bram@...>
! " Last Change: 2003 Nov 02
   "        (modified by David Ne\v{c}as (Yeti) <yeti@...>)

   " Transform a file into HTML, using the current syntax highlighting.
--- 1,6 ----
   " Vim syntax support file
   " Maintainer: Bram Moolenaar <Bram@...>
! " Last Change: 2003 Nov 13
   "        (modified by David Ne\v{c}as (Yeti) <yeti@...>)

   " Transform a file into HTML, using the current syntax highlighting.
***************
*** 290,296 ****

   " Now, when we finally know which, we define the colors and styles
   if exists("html_use_css")
!   8
   endif

   " Find out the background and foreground color.
--- 290,296 ----

   " Now, when we finally know which, we define the colors and styles
   if exists("html_use_css")
!   1;/<style type="text/+1
   endif

   " Find out the background and foreground color.
***************
*** 351,357 ****
       endif
     else
       execute '%s+<span class="' . s:id_name . '">\([^<]*\)</span>+\1+g'
!     8
     endif
   endwhile

--- 351,359 ----
       endif
     else
       execute '%s+<span class="' . s:id_name . '">\([^<]*\)</span>+\1+g'
!     if exists("html_use_css")
!       1;/<style type="text/+1
!     endif
     endif
   endwhile

***************
*** 360,366 ****

   " The DTD
   if exists("html_use_css")
!   exe "normal! ggi<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\"
\"http://www.w3.org/TR/html4/strict.dtd\">\n\e"
   endif

   " Cleanup
--- 362,368 ----

   " The DTD
   if exists("html_use_css")
!   exe "normal! gg0i<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\"
\"http://www.w3.org/TR/html4/strict.dtd\">\n\e"
   endif

   " Cleanup
*** ../vim-6.2.163/src/version.c Mon Dec 29 20:42:51 2003
--- src/version.c Mon Dec 29 20:46:55 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     164,
   /**/

--
From "know your smileys":
  :-| :-|   Deja' vu!

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.165
Problem:    The configure checks hang when using autoconf 2.57.
Solution:   Invoke AC_PROGRAM_EGREP to set $EGREP. (Aron Griffis)
Files:     src/auto/configure, src/configure.in


*** ../vim-6.2.164/src/auto/configure Mon Dec 29 20:27:03 2003
--- src/auto/configure Wed Dec 24 14:10:23 2003
***************
*** 943,950 ****
     ac_cv_prog_CPP="$CPP"
   fi
   echo "$ac_t""$CPP" 1>&6
!  echo $ac_n "checking for POSIXized ISC""... $ac_c" 1>&6
! echo "configure:944: checking for POSIXized ISC" >&5
   if test -d /etc/conf/kconfig.d &&
     grep _POSIX_VERSION /usr/include/sys/unistd.h >/dev/null 2>&1
   then
--- 943,960 ----
     ac_cv_prog_CPP="$CPP"
   fi
   echo "$ac_t""$CPP" 1>&6
!  cat > conftest.$ac_ext <<EOF
! #line 948 "configure"
! #include "confdefs.h"
!
! EOF
! if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
!   egrep "" >/dev/null 2>&1; then
!   :
! fi
! rm -f conftest*
!  echo $ac_n "checking for POSIXized ISC""... $ac_c" 1>&6
! echo "configure:958: checking for POSIXized ISC" >&5
   if test -d /etc/conf/kconfig.d &&
     grep _POSIX_VERSION /usr/include/sys/unistd.h >/dev/null 2>&1
   then
*** ../vim-6.2.164/src/configure.in Mon Dec 29 20:27:03 2003
--- src/configure.in Wed Dec 24 14:09:32 2003
***************
*** 13,18 ****
--- 13,19 ----
   dnl Checks for programs.
   AC_PROG_CC dnl required by almost everything
   AC_PROG_CPP dnl required by header file checks
+ AC_PROGRAM_EGREP dnl required by AC_EGREP_CPP
   AC_ISC_POSIX dnl required by AC_C_CROSS
   AC_PROG_AWK dnl required for "make html" in ../doc

*** ../vim-6.2.164/src/version.c Mon Dec 29 20:49:00 2003
--- src/version.c Mon Dec 29 20:51:56 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     165,
   /**/

--
From "know your smileys":
  :.-( Crying

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.166
Problem:    When $GZIP contains "-N" editing compressed files doesn't work
	     properly.
Solution:   Add "-n" to "gzip -d" to avoid restoring the file name. (Oyvind
	     Holm)
Files:     runtime/plugin/gzip.vim


*** ../vim-6.2.165/runtime/plugin/gzip.vim Sun Apr  6 17:30:34 2003
--- runtime/plugin/gzip.vim Mon Dec 22 16:14:42 2003
***************
*** 1,6 ****
   " Vim plugin for editing compressed files.
   " Maintainer: Bram Moolenaar <Bram@...>
! " Last Change: 2003 Apr 06

   " Exit quickly when:
   " - this plugin was already loaded
--- 1,6 ----
   " Vim plugin for editing compressed files.
   " Maintainer: Bram Moolenaar <Bram@...>
! " Last Change: 2003 Dec 22

   " Exit quickly when:
   " - this plugin was already loaded
***************
*** 19,31 ****
     " set binary mode before reading the file
     " use "gzip -d", gunzip isn't always available
     autocmd BufReadPre,FileReadPre *.gz,*.bz2,*.Z setlocal bin
!   autocmd BufReadPost,FileReadPost *.gz  call s:read("gzip -d")
     autocmd BufReadPost,FileReadPost *.bz2 call s:read("bzip2 -d")
     autocmd BufReadPost,FileReadPost *.Z   call s:read("uncompress")
     autocmd BufWritePost,FileWritePost *.gz  call s:write("gzip")
     autocmd BufWritePost,FileWritePost *.bz2 call s:write("bzip2")
     autocmd BufWritePost,FileWritePost *.Z   call s:write("compress -f")
!   autocmd FileAppendPre 	 *.gz  call s:appre("gzip -d")
     autocmd FileAppendPre 	 *.bz2 call s:appre("bzip2 -d")
     autocmd FileAppendPre 	 *.Z   call s:appre("uncompress")
     autocmd FileAppendPost  *.gz  call s:write("gzip")
--- 19,31 ----
     " set binary mode before reading the file
     " use "gzip -d", gunzip isn't always available
     autocmd BufReadPre,FileReadPre *.gz,*.bz2,*.Z setlocal bin
!   autocmd BufReadPost,FileReadPost *.gz  call s:read("gzip -dn")
     autocmd BufReadPost,FileReadPost *.bz2 call s:read("bzip2 -d")
     autocmd BufReadPost,FileReadPost *.Z   call s:read("uncompress")
     autocmd BufWritePost,FileWritePost *.gz  call s:write("gzip")
     autocmd BufWritePost,FileWritePost *.bz2 call s:write("bzip2")
     autocmd BufWritePost,FileWritePost *.Z   call s:write("compress -f")
!   autocmd FileAppendPre 	 *.gz  call s:appre("gzip -dn")
     autocmd FileAppendPre 	 *.bz2 call s:appre("bzip2 -d")
     autocmd FileAppendPre 	 *.Z   call s:appre("uncompress")
     autocmd FileAppendPost  *.gz  call s:write("gzip")
***************
*** 69,75 ****
     let tmpe = tmp . "." . expand("<afile>:e")
     " write the just read lines to a temp file "'[,']w tmp.gz"
     execute "silent '[,']w " . tmpe
!   " uncompress the temp file: call system("gzip -d tmp.gz")
     call system(a:cmd . " " . tmpe)
     " delete the compressed lines; remember the line number
     let l = line("'[") - 1
--- 69,75 ----
     let tmpe = tmp . "." . expand("<afile>:e")
     " write the just read lines to a temp file "'[,']w tmp.gz"
     execute "silent '[,']w " . tmpe
!   " uncompress the temp file: call system("gzip -dn tmp.gz")
     call system(a:cmd . " " . tmpe)
     " delete the compressed lines; remember the line number
     let l = line("'[") - 1
*** ../vim-6.2.165/src/version.c Mon Dec 29 21:00:25 2003
--- src/version.c Mon Dec 29 21:04:18 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     166,
   /**/

--
From "know your smileys":
  C=}>;*{)) Drunk, devilish chef with a toupee in an updraft,
	    a mustache, and a double chin

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.167
Problem:    The Python interface leaks memory when assigning lines to a
	     buffer. (Sergey Khorev)
Solution:   Do not copy the line when calling ml_replace().
Files:     src/if_python.c


*** ../vim-6.2.166/src/if_python.c Wed Nov 12 20:56:23 2003
--- src/if_python.c Tue Dec 23 10:26:13 2003
***************
*** 2241,2256 ****
  	 if (save == NULL)
  	     return FAIL;

!  /* We do not need to free save, as we pass responsibility for
! 	 * it to vim, via the final parameter of ml_replace().
! 	 */
  	 PyErr_Clear();
  	 curbuf = buf;

  	 if (u_savesub((linenr_T)n) == FAIL)
  	     PyErr_SetVim(_("cannot save undo information"));
!  else if (ml_replace((linenr_T)n, (char_u *)save, TRUE) == FAIL)
  	     PyErr_SetVim(_("cannot replace line"));
  	 else
  	     changed_bytes((linenr_T)n, 0);

--- 2246,2265 ----
  	 if (save == NULL)
  	     return FAIL;

!  /* We do not need to free "save" if ml_replace() consumes it. */
  	 PyErr_Clear();
  	 curbuf = buf;

  	 if (u_savesub((linenr_T)n) == FAIL)
+  {
  	     PyErr_SetVim(_("cannot save undo information"));
! 	    vim_free(save);
!  }
!  else if (ml_replace((linenr_T)n, (char_u *)save, FALSE) == FAIL)
!  {
  	     PyErr_SetVim(_("cannot replace line"));
+ 	    vim_free(save);
+  }
  	 else
  	     changed_bytes((linenr_T)n, 0);

***************
*** 2390,2402 ****
  	 if (!PyErr_Occurred())
  	 {
  	     for (i = 0; i < old_len && i < new_len; ++i)
! 	 if (ml_replace((linenr_T)(lo+i), (char_u *)array[i], TRUE)
  								       == FAIL)
  		 {
  		     PyErr_SetVim(_("cannot replace line"));
  		     break;
  		 }
  	 }

  	 /* Now we may need to insert the remaining new old_len. If we do, we
  	  * must free the strings as we finish with them (we can't pass the
--- 2399,2413 ----
  	 if (!PyErr_Occurred())
  	 {
  	     for (i = 0; i < old_len && i < new_len; ++i)
! 	 if (ml_replace((linenr_T)(lo+i), (char_u *)array[i], FALSE)
  								       == FAIL)
  		 {
  		     PyErr_SetVim(_("cannot replace line"));
  		     break;
  		 }
  	 }
+  else
+ 	    i = 0;

  	 /* Now we may need to insert the remaining new old_len. If we do, we
  	  * must free the strings as we finish with them (we can't pass the
*** ../vim-6.2.166/src/version.c Mon Dec 29 21:04:38 2003
--- src/version.c Mon Dec 29 21:06:33 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     167,
   /**/

--
From "know your smileys":
  |-( Contact lenses, but has lost them

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.168
Problem:    Python interface: There is no way to get the indices from a range
	     object.
Solution:   Add the "start" and "end" attributes. (Maurice S. Barnum)
Files:     src/if_python.c, runtime/doc/if_pyth.txt


*** ../vim-6.2.167/src/if_python.c Mon Dec 29 21:07:26 2003
--- src/if_python.c Tue Dec 23 10:26:13 2003
***************
*** 1476,1482 ****
       static PyObject *
   RangeGetattr(PyObject *self, char *name)
   {
!     return Py_FindMethod(RangeMethods, self, name);
   }

       static PyObject *
--- 1476,1487 ----
       static PyObject *
   RangeGetattr(PyObject *self, char *name)
   {
!     if (strcmp(name, "start") == 0)
!  return Py_BuildValue("i",((RangeObject *)(self))->start - 1);
!     else if (strcmp(name, "end") == 0)
!  return Py_BuildValue("i",((RangeObject *)(self))->end - 1);
!     else
!  return Py_FindMethod(RangeMethods, self, name);
   }

       static PyObject *
*** ../vim-6.2.167/runtime/doc/if_pyth.txt Sun Jun  1 12:20:33 2003
--- runtime/doc/if_pyth.txt Mon Dec 29 10:03:38 2003
***************
*** 1,4 ****
! *if_pyth.txt*   For Vim version 6.2.  Last change: 2002 Mar 11


  		   VIM REFERENCE MANUAL    by Paul Moore
--- 1,4 ----
! *if_pyth.txt*   For Vim version 6.2.  Last change: 2003 Dec 29


  		   VIM REFERENCE MANUAL    by Paul Moore
***************
*** 242,250 ****
   can, of course, change as a result of slice assignments, line deletions, or
   the range.append() method).

! Unlike buffers, ranges do not have a "name" attribute, nor do they have mark()
! or range() methods. They do have an append() method, however, which adds
! line(s) to the end of the range.

   ==============================================================================
   5. Window objects 			 *python-window*
--- 252,271 ----
   can, of course, change as a result of slice assignments, line deletions, or
   the range.append() method).

! The range object attributes are:
!  r.start  Index of first line into the buffer
!  r.end  Index of last line into the buffer
!
! The range object methods are:
!  r.append(str) Append a line to the range
!  r.append(list) Append a list of lines to the range
! 		 Note that the option of supplying a list of strings to
! 		 the append method differs from the equivalent method
! 		 for Python's built-in list objects.
!
! Example (assume r is the current range):
!  # Send all lines in a range to the default printer
!  vim.command("%d,%dhardcopy!" % (r.start+1,r.end+1))

   ==============================================================================
   5. Window objects 			 *python-window*
*** ../vim-6.2.167/src/version.c Mon Dec 29 21:07:26 2003
--- src/version.c Mon Dec 29 21:10:20 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     168,
   /**/

--
From "know your smileys":
  <|-) Chinese
  <|-( Chinese and doesn't like these kind of jokes

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.169
Problem:    The prototype for _Xmblen() appears in a recent XFree86 header
	     file, causing a warning for our prototype. (Hisashi T Fujinaka)
Solution:   Move the prototype to an osdef file, so that it's filtered out.
Files:     src/mbyte.c, src/osdef2.h.in


*** ../vim-6.2.168/src/mbyte.c Sun Nov  9 20:20:26 2003
--- src/mbyte.c Tue Dec 23 16:03:30 2003
***************
*** 543,549 ****
   # else
  	     char buf[MB_MAXBYTES];
   # ifdef X_LOCALE
- 	    extern int _Xmblen __ARGS((char *, size_t));
   #  ifndef mblen
   #   define mblen _Xmblen
   #  endif
--- 547,552 ----
*** ../vim-6.2.168/src/osdef2.h.in Sat Dec 15 22:24:12 2001
--- src/osdef2.h.in Wed Dec 24 10:26:00 2003
***************
*** 79,81 ****
--- 79,87 ----
   #else
   extern char *mktemp __ARGS((char *));
   #endif
+
+ #ifdef ISC
+ extern int _Xmblen __ARGS((char const *, size_t));
+ #else
+ extern int _Xmblen __ARGS((char *, size_t));
+ #endif
*** ../vim-6.2.168/src/version.c Mon Dec 29 21:14:00 2003
--- src/version.c Mon Dec 29 21:16:30 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     169,
   /**/

--
From "know your smileys":
  :-* A big kiss!

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Patch 6.2.170
Problem:    When using Sun WorkShop the current directory isn't changed to
	     where the file is.
Solution:   Set the 'autochdir' option when using WorkShop.  And avoid using
	     the basename when 'autochdir' is not set.
Files:     src/gui_x11.c, src/ex_cmds.c


*** ../vim-6.2.169/src/gui_x11.c Sun Jul 27 14:16:53 2003
--- src/gui_x11.c Wed Dec 24 14:25:10 2003
***************
*** 1223,1228 ****
--- 1223,1229 ----
  	     if (strcmp("-ws", argv[arg]) == 0)
  	 {
  	     usingSunWorkShop++;
+ 	    p_acd = TRUE;
  	     gui.dofork = FALSE; /* don't fork() when starting GUI */
  	     mch_memmove(&argv[arg], &argv[arg + 1],
  					     (--*argc - arg) * sizeof(char *));
*** ../vim-6.2.169/src/ex_cmds.c Sun Nov  9 20:23:26 2003
--- src/ex_cmds.c Wed Dec 24 14:31:16 2003
***************
*** 2615,2621 ****
  		 ffname = free_fname;
  	     other_file = otherfile(ffname);
   #ifdef FEAT_SUN_WORKSHOP
! 	    if (usingSunWorkShop && (cp = vim_strrchr(sfname, '/')) != NULL)
  		 sfname = ++cp;
   #endif
  	 }
--- 2615,2622 ----
  		 ffname = free_fname;
  	     other_file = otherfile(ffname);
   #ifdef FEAT_SUN_WORKSHOP
! 	    if (usingSunWorkShop && p_acd
! 				   && (cp = vim_strrchr(sfname, '/')) != NULL)
  		 sfname = ++cp;
   #endif
  	 }
***************
*** 3122,3128 ****
  				      && vim_chdirfile(curbuf->b_ffname) == OK)
  	 shorten_fnames(TRUE);

!     if (gui.in_use && curbuf->b_fname != NULL)
       {
   # ifdef FEAT_SUN_WORKSHOP
  	 if (usingSunWorkShop)
--- 3123,3129 ----
  				      && vim_chdirfile(curbuf->b_ffname) == OK)
  	 shorten_fnames(TRUE);

!     if (gui.in_use && curbuf->b_ffname != NULL)
       {
   # ifdef FEAT_SUN_WORKSHOP
  	 if (usingSunWorkShop)
*** ../vim-6.2.169/src/version.c Mon Dec 29 21:17:44 2003
--- src/version.c Mon Dec 29 21:20:47 2003
***************
*** 639,640 ****
--- 639,642 ----
   {   /* Add new patch number below this line */
+ /**/
+     170,
   /**/

--
hundred-and-one symptoms of being an internet addict:
92. It takes you two hours to check all 14 of your mailboxes.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Attached is ldif.vim, a syntax file for the Lightweight Directory
Interchange Format.  It's my first stab at Vim syntax highlighting, so
comments are welcome.  Lines necessary in filetype.vim:

" LDAP LDIF
au BufNewFile,BufRead *.ldif 	 setf ldif

-Zak

" Vim syntax file
" Language: LDAP LDIF
" Maintainer: Zak Johnson <zakj@...>
" Last Change: 2003-12-29

if version < 600
   syntax clear
elseif exists("b:current_syntax")
   finish
endif

syn sync linebreaks=2

syn match ldifAttribute /^[^ #][^:]*/ contains=ldifOption display
syn match ldifOption /;[^:]\+/ contained contains=ldifPunctuation display
syn match ldifPunctuation /;/ contained display

syn region ldifStringValue matchgroup=ldifPunctuation start=/: /  end=/\_$/
skip=/\n /
syn region ldifBase64Value matchgroup=ldifPunctuation start=/:: / end=/\_$/
skip=/\n /
syn region ldifFileValue   matchgroup=ldifPunctuation start=/:< / end=/\_$/
skip=/\n /

syn region ldifComment start=/^#/ end=/\_$/ skip=/\n /

if version >= 508 || !exists("did_xdefaults_syntax_inits")
   if version < 508
     let did_xdefaults_syntax_inits = 1
     command -nargs=+ HiLink hi link <args>
   else
     command -nargs=+ HiLink hi def link <args>
   endif

   HiLink ldifAttribute  Type
   HiLink ldifOption  Identifier
   HiLink ldifPunctuation Normal
   HiLink ldifStringValue String
   HiLink ldifBase64Value Special
   HiLink ldifFileValue  Special
   HiLink ldifComment  Comment

   delcommand HiLink
endif

let b:current_syntax = "ldif"

Hi there,

I don't know if this is the right place to post, but I have a suggestion for GUI
improvement: Instead of listing open buffers in the buffers menu, it would be
more effective to be able to select between them using (GUI) tabs. (Just like in
Mozilla or Ultraedit)

I wonder if anyone would be interested in implementing this, or if I would have
to do it myself eventually? (I don't know how to at the moment...)

Regards,
Johan

* Johan Kotlinski wrote:
> I don't know if this is the right place to post, but I have a
> suggestion for GUI improvement: Instead of listing open buffers in
> the buffers menu, it would be more effective to be able to select
> between them using (GUI) tabs. (Just like in Mozilla or Ultraedit)

http://vim.sourceforge.net/scripts/script.php?script_id=765

This is for gtk1 and vim 6.1, I don't know about plans for gtk2 and
vim 6.2.

Norbert

On Mon, 2003-12-29 at 21:17, Norbert Tretkowski wrote:
> * Johan Kotlinski wrote:
> >
> > I don't know if this is the right place to post, but I have a
> > suggestion for GUI improvement: Instead of listing open buffers in
> > the buffers menu, it would be more effective to be able to select
> > between them using (GUI) tabs. (Just like in Mozilla or Ultraedit)
>
> http://vim.sourceforge.net/scripts/script.php?script_id=765
>
> This is for gtk1 and vim 6.1, I don't know about plans for gtk2
> and vim 6.2.

AAAAUUUUUGH!!!!

This URL has been dead for ages, and it is *such* a shame that the
patch wasn't posted. I've tried several times to track it down,
anybody around here by chance have a copy?


--
Steve Hall  [ digitect@... ]

Replyed From: lizl <lizl@...>

> * Johan Kotlinski wrote:
> > I don't know if this is the right place to post, but I have a
> > suggestion for GUI improvement: Instead of listing open buffers in
> > the buffers menu, it would be more effective to be able to select
> > between them using (GUI) tabs. (Just like in Mozilla or Ultraedit)
>
> http://vim.sourceforge.net/scripts/script.php?script_id=765
>
> This is for gtk1 and vim 6.1, I don't know about plans for gtk2 and
> vim 6.2.
>
> Norbert
>


I think use bufexplorer.vim and winmanager.vim can do it better,you can download
it from vim sctript
ÑïÖݵçÐÅ¿í´øÍø

Johan Kotlinski wrote:

> I don't know if this is the right place to post, but I have a
> suggestion for GUI improvement: Instead of listing open buffers in the
> buffers menu, it would be more effective to be able to select between
> them using (GUI) tabs. (Just like in Mozilla or Ultraedit)
>
> I wonder if anyone would be interested in implementing this, or if I
> would have to do it myself eventually? (I don't know how to at the
> moment...)

The idea has existed for a while.  It needs to be implemented in the
most popular GUI versions before I'll include it.  That might be a
problem for Motif, I don't think there is a tab-panel widget for it.

Perhaps someone can also make a version for console Vim? :-)

--
hundred-and-one symptoms of being an internet addict:
98. The Alta Vista administrators ask you what sites are missing
     in their index files.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

Dnia Tuesday 30 of December 2003 02:33, Johan Kotlinski napisa³:
> Hi there,
>
> I don't know if this is the right place to post, but I have a suggestion
> for GUI improvement: Instead of listing open buffers in the buffers menu,
> it would be more effective to be able to select between them using (GUI)
> tabs. (Just like in Mozilla or Ultraedit)

You can tear off menu and place it somewhere. It is much easier to use
than tabs, especially with many files.

m.
--
LaTeX + Vim = http://vim-latex.sourceforge.net/
Vim-list(s) Users Map: (last change 12 Dec)
  http://skawina.eu.org/mikolaj/vimlist
Are You There?

On Tue, Dec 30, 2003 at 02:33:47AM +0100, Johan Kotlinski wrote:
> Hi there,
>
> I don't know if this is the right place to post, but I
> have a suggestion for GUI improvement: Instead of listing
> open buffers in the buffers menu, it would be more
> effective to be able to select between them using (GUI)
> tabs. (Just like in Mozilla or Ultraedit)

Its not tabs, but in my opinion its far better.

I have the following lines in my .vimrc file:

----------------------------------
set winminheight=0
set winminwidth=0

map <C-J> <C-W>j<C-W>_
map <C-K> <C-W>k<C-W>_
map <C-H> <C-W>h<C-W><BAR>
map <C-L> <C-W>l<C-W><BAR>
----------------------------------

Then, whenever I open a new file I use:
     :sp <filename>
or
     :vsp <filename>

What this does, it it sets the minimum size of a split
window to 0 rows/columns.  I then split the window using :sp
and :vsp to open files (horizontal and vertical splits
respectively).  Once I have windows open, ^J and ^K will
move up and down through the windows, maximizing each to the
full height of the screen when you move to it.  ^H and ^L do
the same but moving left and right through vertical splits.

Horizontal splits allow you to see the filenames in the
status bar (if you show that in your status bar).  I use
this setup by having sets of files open in each vertical
split.  For instance, one vertical column of files might
have my C code and header files for project A, the next for
project B, etc.

For me at least, this is FAR better than tabs.  No using the
silly mouse, large numbers of files can be logically
grouped, and large numbers of files don't fill the entire
window with useless tabs.  I use this setup with up to 60
files.

--David

Hi there!

Thanks for all the helpful answers :)

Eventually I found what I was looking for, a script named minibufexpl.vim that
works really well. It's not as ergonomical as a proper GUI solution, but it at
least works the same.

Thanks to all the people who suggested alternative solutions aswell. As I don't
like to use the mouse, I think I agree with David's idea on how to navigate
multiple buffers, that the best option is to map something like ^J and ^K to go
to the next or previous buffer. I mostly want the tabs as a quick way to see
which buffers are open, and which keypresses I should use to get to a certain
buffer. It's a very effective memory aid!

I agree it might not be very useful if you have 60+ files open, but I can't see
any reason to why I would want to edit that many files at once anyway...

Regards,
Johan

Hi there!

Thanks for all the helpful answers :)

Eventually I found what I was looking for, a script named minibufexpl.vim that
works really well. It's not as ergonomical as a proper GUI solution, but it at
least works the same.

Thanks to all the people who suggested alternative solutions aswell. As I don't
like to use the mouse, I think I agree with David's idea on how to navigate
multiple buffers, that the best option is to map something like ^J and ^K to go
to the next or previous buffer. I mostly want the tabs as a quick way to see
which buffers are open, and which keypresses I should use to get to a certain
buffer. It's a very effective memory aid!

I agree it might not be very useful if you have 60+ files open, but I can't see
any reason to why I would want to edit that many files at once anyway...

Regards,
Johan

>-----Original Message-----
>From: David Morris [mailto:lists@...]
>Sent: Tuesday, December 30, 2003 11:21 AM
>To: vim-dev@...
>Subject: Re: idea for GUI improvement (file tabs)
>
>[snip] ... whenever I open a new file I use:
>    :sp <filename>
>or
>    :vsp <filename>
>
>[snip]
>Horizontal splits allow you to see the filenames in the
>status bar (if you show that in your status bar).  I use
>this setup by having sets of files open in each vertical
>split.  For instance, one vertical column of files might
>have my C code and header files for project A, the next for
>project B, etc.
>
>For me at least, this is FAR better than tabs.  No using the
>silly mouse, large numbers of files can be logically
>grouped, and large numbers of files don't fill the entire
>window with useless tabs.  I use this setup with up to 60
>files.
>
>--David

I like this idea; might have to start using it myself.

I use sessions to group files by project (programming task, that is), but I
think it might be nice to keep each program and its subordinate subroutines
[each one is in a separate file <sigh\>] in a separate vertical split ... so
thanks for sharing. :)