Loading ...
Sorry, an error occurred while loading the content.

vim patchs - why not a big-patch?

Expand Messages
  • Ryan J M
    I have been a vimmer for years, but it was my first time to build it from src, because I found that my CENTOS vim got some problems on cscope co-operations.
    Message 1 of 20 , Jul 18, 2009
    • 0 Attachment
      I have been a vimmer for years, but it was my first time to build it
      from src, because I found that my CENTOS vim got some problems on
      cscope co-operations.
      Following README file lcoated at
      ftp://ftp.vim.org/pub/vim/patches/7.2/README, I got a little pain when
      patching. please take a look at logs at the bottom.

      why don't vim provide a whole big patch for 001-latest one?
      Fix me if I missed anything, thanks.


      =====

      root@xxx ~/vim72/vim72 > patch -p0 < ../patchs/7.2.001-100
      patching file src/pty.c
      patching file src/version.c
      patching file src/menu.c
      patching file src/version.c
      patching file src/spell.c
      patching file src/version.c
      patching file src/version.c
      patching file src/if_cscope.c
      patching file src/if_cscope.h
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file runtime/scripts.vim
      patching file src/version.c
      patching file runtime/doc/os_vms.txt
      can't find file to patch at input line 743
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.006/src/os_vms_conf.h Thu May 10 19:26:17 2007
      |--- src/os_vms_conf.h Sat Aug 16 05:09:17 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      can't find file to patch at input line 756
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.006/src/Make_vms.mms Mon Oct 29 22:38:54 2007
      |--- src/Make_vms.mms Sat Aug 16 05:17:41 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      2 out of 2 hunks ignored
      can't find file to patch at input line 792
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.006/src/testdir/Make_vms.mms Wed Jun 25 00:34:23 2008
      |--- src/testdir/Make_vms.mms Tue Aug 19 06:28:07 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      7 out of 7 hunks ignored
      patching file src/testdir/test30.in
      patching file src/testdir/test54.in
      patching file src/version.c
      patching file src/buffer.c
      patching file src/version.c
      patching file src/if_perl.xs
      patching file src/version.c
      patching file src/mbyte.c
      patching file src/misc2.c
      patching file src/normal.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file src/ex_cmds2.c
      patching file src/version.c
      patching file src/ui.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file src/testdir/Makefile
      patching file src/version.c
      patching file src/ex_getln.c
      patching file src/version.c
      patching file src/ui.c
      patching file src/version.c
      patching file src/ex_cmds.c
      patching file src/version.c
      patching file src/ex_cmds.h
      patching file src/ex_docmd.c
      patching file src/version.c
      patching file src/main.c
      patching file src/version.c
      patching file src/ex_docmd.c
      patching file src/fileio.c
      patching file src/globals.h
      patching file src/version.c
      patching file Filelist
      patching file src/testdir/Make_ming.mak
      patching file src/version.c
      patching file src/screen.c
      patching file src/version.c
      patching file src/option.c
      patching file src/version.c
      patching file src/normal.c
      patching file src/version.c
      patching file src/normal.c
      patching file src/version.c
      patching file src/ex_cmds.h
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file src/ex_docmd.c
      patching file src/version.c
      patching file src/ex_cmds.h
      patching file src/version.c
      patching file runtime/doc/cmdline.txt
      patching file runtime/doc/eval.txt
      patching file runtime/doc/starting.txt
      patching file runtime/doc/usr_21.txt
      patching file src/eval.c
      patching file src/ex_cmds.c
      patching file src/ex_cmds.h
      patching file src/ex_docmd.c
      patching file src/feature.h
      patching file src/fileio.c

      patching file src/main.c
      patching file src/mark.c
      patching file src/misc1.c
      patching file src/proto/eval.pro
      patching file src/proto/ex_cmds.pro
      patching file src/proto/mark.pro
      patching file src/option.c
      patching file src/structs.h
      patching file src/vim.h
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file src/fileio.c
      patching file src/testdir/test42.ok
      patching file src/version.c
      patching file src/buffer.c
      patching file src/version.c
      patching file src/gui_x11.c
      patching file src/mbyte.c
      patching file src/misc2.c
      patching file src/os_unix.c
      patching file src/version.c
      can't find file to patch at input line 4715
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |--
      |You can tune a file system, but you can't tuna fish
      | -- man tunefs
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.036 (extra)
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.036 (extra)
      |Problem: Mismatches between alloc/malloc, free/vim_free,
      | realloc/vim_realloc.
      |Solution: Use the right function. (Dominique Pelle)
      |Files: src/gui_riscos.c, src/gui_w48.c, src/mbyte.c, src/os_vms.c,
      | src/os_w32exe.c, src/os_win16.c
      |
      |
      |*** ../vim-7.2.035/src/gui_riscos.c Thu May 10 19:33:26 2007
      |--- src/gui_riscos.c Wed Nov 12 11:47:54 2008
      --------------------------
      File to patch: Skip this patch? [y]
      Skipping patch.
      2 out of 2 hunks ignored
      can't find file to patch at input line 4751
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.035/src/gui_w48.c Thu Jul 24 20:50:23 2008
      |--- src/gui_w48.c Wed Nov 12 11:37:41 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      4 out of 4 hunks ignored
      can't find file to patch at input line 4832
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.035/src/os_vms.c Wed Aug 6 18:38:52 2008
      |--- src/os_vms.c Wed Nov 12 11:42:12 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      4 out of 4 hunks ignored
      can't find file to patch at input line 4916
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.035/src/os_w32exe.c Fri Jul 1 00:06:20 2005
      |--- src/os_w32exe.c Wed Nov 12 11:45:43 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      can't find file to patch at input line 4936
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.035/src/os_win16.c Wed Jun 25 00:49:34 2008
      |--- src/os_win16.c Wed Nov 12 11:45:53 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      patching file src/version.c
      patching file src/os_unix.c
      patching file src/version.c
      patching file src/if_xcmdsrv.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file src/fileio.c
      patching file src/version.c
      patching file src/buffer.c
      patching file src/ex_cmds.c
      patching file src/ex_cmds2.c

      patching file src/ex_docmd.c
      patching file src/ex_getln.c
      can't find file to patch at input line 5672
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.040/src/if_sniff.c Sat Aug 9 19:41:16 2008
      |--- src/if_sniff.c Wed Nov 12 17:48:46 2008
      --------------------------
      File to patch: Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      patching file src/main.c
      patching file src/netbeans.c
      patching file src/normal.c
      patching file src/popupmnu.c
      patching file src/proto/buffer.pro
      patching file src/proto/ex_cmds.pro
      patching file src/quickfix.c

      patching file src/window.c
      patching file src/version.c
      patching file src/buffer.c
      patching file src/move.c
      patching file src/structs.h
      patching file src/version.c
      patching file src/vim.h
      patching file src/version.c
      patching file src/auto/configure
      patching file src/configure.in
      patching file src/eval.c
      patching file src/version.c
      patching file src/if_python.c
      patching file src/version.c
      patching file src/mbyte.c
      patching file src/version.c
      patching file src/main.c
      patching file src/vim.h
      patching file src/version.c
      patching file src/eval.c

      patching file src/normal.c
      patching file src/proto/eval.pro
      patching file src/version.c
      can't find file to patch at input line 6743
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |--
      |Microsoft's definition of a boolean: TRUE, FALSE, MAYBE
      |"Embrace and extend"...?
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.049 (extra)
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.049 (extra)
      |Problem: Win32: the clipboard doesn't support UTF-16.
      |Solution: Change UCS-2 support to UTF-16 support. (Jia Yanwei)
      |Files: src/gui_w32.c, src/gui_w48.c, src/mbyte.c, src/misc1.c,
      | src/os_mswin.c, src/os_win32.c, src/proto/os_mswin.pro
      |
      |
      |*** ../vim-7.2.048/src/gui_w32.c Tue Jun 24 23:46:14 2008
      |--- src/gui_w32.c Thu Nov 20 16:47:10 2008
      --------------------------
      File to patch: Skip this patch? [y] Skipping patch.
      5 out of 5 hunks ignored
      can't find file to patch at input line 6830
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.048/src/gui_w48.c Wed Nov 12 13:35:31 2008
      |--- src/gui_w48.c Thu Nov 20 16:42:32 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      11 out of 11 hunks ignored
      patching file src/mbyte.c
      patching file src/misc1.c
      can't find file to patch at input line 7147
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.048/src/os_mswin.c Sat Aug 9 19:37:30 2008
      |--- src/os_mswin.c Thu Nov 20 17:05:10 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      19 out of 19 hunks ignored
      can't find file to patch at input line 7605
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.048/src/os_win32.c Thu Jul 24 20:50:30 2008
      |--- src/os_win32.c Thu Nov 20 16:44:33 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      15 out of 15 hunks ignored
      can't find file to patch at input line 7868
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.048/src/proto/os_mswin.pro Sat May 5 19:07:50 2007
      |--- src/proto/os_mswin.pro Thu Nov 20 16:41:00 2008
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      patching file src/version.c
      patching file src/spell.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/ex_getln.c
      patching file src/proto/ex_getln.pro
      patching file runtime/doc/eval.txt
      patching file runtime/doc/options.txt
      patching file src/version.c
      patching file runtime/doc/eval.txt
      patching file src/eval.c
      patching file src/version.c
      patching file src/workshop.c
      patching file src/version.c
      patching file src/getchar.c
      patching file src/version.c
      patching file src/diff.c

      patching file src/eval.c
      patching file src/ex_cmds.c
      patching file src/ex_docmd.c
      patching file src/fileio.c
      patching file src/fold.c
      patching file src/globals.h
      patching file src/gui.c
      patching file src/gui_at_sb.c
      patching file src/gui_gtk_x11.c
      patching file src/gui_xmdlg.c
      patching file src/gui_xmebw.c
      patching file src/main.c
      patching file src/mbyte.c
      patching file src/message.c

      patching file src/netbeans.c
      patching file src/option.c
      patching file src/os_unix.c
      patching file src/spell.c
      patching file src/ui.c
      patching file src/window.c
      patching file src/version.c
      patching file src/spell.c
      patching file src/version.c
      patching file src/spell.c
      patching file src/version.c
      patching file src/version.c
      patching file src/version.c
      patching file src/diff.c
      patching file src/version.c

      patching file runtime/doc/spell.txt
      patching file src/spell.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file src/buffer.c
      patching file src/version.c
      patching file src/if_perl.xs
      patching file src/version.c
      patching file src/ops.c
      patching file src/version.c
      patching file src/gui.c
      patching file src/version.c
      patching file runtime/doc/eval.txt
      patching file src/eval.c
      patching file src/version.c
      patching file src/ex_docmd.c
      patching file src/version.c
      patching file src/tag.c

      patching file src/version.c
      patching file src/spell.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      can't find file to patch at input line 12865
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |--
      |Close your shells, or I'll kill -9 you
      |Tomorrow I'll quota you
      |Remember the disks'll always be full
      |And then while I'm away
      |I'll write ~ everyday
      |And I'll send-pr all my buggings to you.
      | [ CVS log "Beatles style" for FreeBSD ports/INDEX, Satoshi Asami ]
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.071
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.071 (extra)
      |Problem: Win32: Handling netbeans events while Vim is busy updating the
      | screen may cause a crash.
      |Solution: Like with GTK, only handle netbeans messages in the main loop.
      | (Xavier de Gaye)
      |Files: src/gui_w48.c, src/netbeans.c
      |
      |
      |*** ../vim-7.2.070/src/gui_w48.c Thu Nov 20 17:09:09 2008
      |--- src/gui_w48.c Thu Dec 11 23:47:18 2008
      --------------------------
      File to patch: Skip this patch? [y] Skipping patch.
      1 out of 1 hunk ignored
      patching file src/netbeans.c
      patching file src/version.c
      can't find file to patch at input line 12945
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |--
      |No children may attend school with their breath smelling of "wild onions."
      | [real standing law in West Virginia, United States of America]
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.072 (extra)
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.072 (extra)
      |Problem: Compiler warning in Sniff code.
      |Solution: Use return value of pipe(). (Dominique Pelle)
      |Files: src/if_sniff.c
      |
      |NOTE: Patch was adjusted to avoid problems with CVS interference.
      |
      |*** ../vim-7.2.071/src/if_sniff.c Sat Nov 15 14:11:10 2008
      |--- src/if_sniff.c Sat Dec 6 14:01:57 2008
      --------------------------
      File to patch: Skip this patch? [y] Skipping patch.
      1 out of 1 hunk ignored
      patching file src/version.c
      patching file src/misc2.c
      patching file src/option.c
      patching file src/proto/misc2.pro
      patching file src/version.c
      can't find file to patch at input line 13136
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |
      |--
      |ARTHUR: If you do not open these doors, we will take this castle by force ...
      | [A bucket of slops land on ARTHUR. He tries to retain his dignity.]
      | "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.074 (extra)
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.074 (extra, after 7.2.073)
      |Problem: ":set <xHome>" has the same output as ":set <Home>". (Matt
      | Wozniski)
      |Solution: Don't translate "x" keys to its alternative for ":set".
      |Files: src/gui_mac.c
      |
      |
      |*** ../vim-7.2.073/src/gui_mac.c Sat Aug 9 19:37:28 2008
      |--- src/gui_mac.c Sun Dec 14 12:28:26 2008
      --------------------------
      File to patch: Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      patching file src/version.c
      patching file src/version.c
      patching file src/version.c
      patching file src/fileio.c
      patching file src/version.c
      patching file src/fileio.c
      patching file src/version.c
      patching file src/fold.c
      patching file src/version.c
      patching file runtime/doc/netbeans.txt
      patching file src/buffer.c
      patching file src/globals.h
      patching file src/netbeans.c
      patching file src/proto/netbeans.pro
      patching file src/version.c
      patching file src/edit.c
      patching file src/version.c
      patching file src/message.c
      patching file src/version.c
      patching file src/ex_cmds.c
      patching file src/version.c
      patching file src/tag.c
      patching file src/version.c
      patching file src/if_python.c
      patching file src/version.c
      patching file src/term.c
      patching file src/version.c
      patching file src/diff.c
      patching file src/version.c
      patching file src/misc2.c
      patching file src/version.c
      can't find file to patch at input line 14760
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |--
      |hundred-and-one symptoms of being an internet addict:
      |21. Your dog has its own home page.
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.088 (extra)
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.088 (extra)
      |Problem: OpenClipboard() may fail when another application is using the
      | clipboard.
      |Solution: Retry OpenClipboard() a few times. (Jianrong Yu)
      |Files: src/os_mswin.c
      |
      |
      |*** ../vim-7.2.087/src/os_mswin.c Thu Nov 20 17:09:09 2008
      |--- src/os_mswin.c Thu Jan 22 18:38:12 2009
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      3 out of 3 hunks ignored
      patching file src/version.c
      can't find file to patch at input line 14858
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |--
      |hundred-and-one symptoms of being an internet addict:
      |22. You've already visited all the links at Yahoo and you're halfway through
      | Lycos.
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.089 (extra)
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.089 (extra)
      |Problem: Win32: crash when using Ultramon buttons.
      |Solution: Don't use a WM_OLE message of zero size. (Ray Megal)
      |Files: src/if_ole.cpp, src/gui_w48.c
      |
      |
      |*** ../vim-7.2.088/src/if_ole.cpp Sun Mar 16 14:53:11 2008
      |--- src/if_ole.cpp Mon Jan 19 21:16:33 2009
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      can't find file to patch at input line 14885
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.088/src/gui_w48.c Wed Dec 24 12:20:10 2008
      |--- src/gui_w48.c Mon Jan 19 21:19:30 2009
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      1 out of 1 hunk ignored
      patching file src/version.c
      patching file src/ex_docmd.c
      patching file src/version.c
      patching file src/if_cscope.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      can't find file to patch at input line 15308
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |
      |
      |--
      |Now it is such a bizarrely improbable coincidence that anything as
      |mind-bogglingly useful as the Babel fish could have evolved purely by chance
      |that some thinkers have chosen to see it as a final and clinching proof of the
      |NON-existence of God.
      |The argument goes something like this: 'I refuse to prove that I exist,' says
      |God, 'for proof denies faith, and without faith I am nothing.'
      |'But,' says Man, 'the Babel fish is a dead giveaway, isn't it? It could not
      |have evolved by chance. It proves you exist, and so therefore, by your own
      |arguments, you don't. QED.'
      |'Oh dear,' says God, 'I hadn't thought of that,' and promptly vanishes in a
      |puff of logic.
      |'Oh, that was easy,' says Man, and for an encore goes on to prove that black
      |is white and gets himself killed on the next pedestrian crossing.
      | -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
      |
      | /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      |/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      |\\\ download, build and distribute -- http://www.A-A-P.org ///
      | \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
      |To: vim-dev@...
      |Subject: Patch 7.2.093 (extra)
      |Fcc: outbox
      |From: Bram Moolenaar <Bram@...>
      |Mime-Version: 1.0
      |Content-Type: text/plain; charset=ISO-8859-1
      |Content-Transfer-Encoding: 8bit
      |------------
      |
      |Patch 7.2.093 (extra)
      |Problem: Win32: inputdialog() and find/replace dialogs can't handle
      | multi-byte text.
      |Solution: Use the wide version of dialog functions when available. (Yanwei
      | Jia)
      |Files: src/gui_w32.c, src/gui_w48.c
      |
      |
      |*** ../vim-7.2.092/src/gui_w32.c Thu Nov 20 17:09:09 2008
      |--- src/gui_w32.c Wed Jan 28 21:15:29 2009
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      2 out of 2 hunks ignored
      can't find file to patch at input line 15368
      Perhaps you used the wrong -p or --strip option?
      The text leading up to this was:
      --------------------------
      |*** ../vim-7.2.092/src/gui_w48.c Wed Jan 28 14:17:21 2009
      |--- src/gui_w48.c Wed Jan 28 21:10:26 2009
      --------------------------
      File to patch:
      Skip this patch? [y]
      Skipping patch.
      5 out of 5 hunks ignored
      patching file src/version.c
      patching file src/edit.c
      patching file src/version.c
      patching file src/normal.c
      patching file src/version.c
      patching file src/ex_cmds.c
      patching file src/version.c
      patching file src/os_unix.c
      patching file src/version.c
      patching file src/eval.c
      patching file src/version.c
      patching file src/option.c
      patching file src/version.c
      patching file src/ex_cmds2.c
      patching file src/version.c
      root@xxx ~/vim72/vim72 >


      --
      FIXME if it is wrong.

      --~--~---------~--~----~------------~-------~--~----~
      You received this message from the "vim_use" maillist.
      For more information, visit http://www.vim.org/maillist.php
      -~----------~----~----~----~------~----~------~--~---
    • Raúl Núñez de Arenas Coronado
      Saluton Ryan :) ... Probably your problem is that your vim72 sources doesn t include the extra files? If you are going to use all the patches published by
      Message 2 of 20 , Jul 18, 2009
      • 0 Attachment
        Saluton Ryan :)

        Ryan J M <s...@...> dixit:
        > I have been a vimmer for years, but it was my first time to build it
        > from src, because I found that my CENTOS vim got some problems on
        > cscope co-operations.
        > Following README file lcoated at
        > ftp://ftp.vim.org/pub/vim/patches/7.2/README, I got a little pain when
        > patching. please take a look at logs at the bottom.

        Probably your problem is that your vim72 sources doesn't include the
        "extra" files? If you are going to use all the patches published by Bram
        you need to have the pristine sources and the extra sources. This is a
        blind shot because I haven't had time to read your problem. I've patched
        my Vim to 228 (by now...) without any problem, and I do it automatically
        using a little shell script.

        > why don't vim provide a whole big patch for 001-latest one?

        Bram already provides 001-100, 100-200, etc. Providing 001-latest would
        be a bit of a problem due to the following reasons:

        - Bram would have to work a bit more each time he writes a patch. He is
        not paid for his work on Vim, and even if he is, this is additional
        and unneeded work. Instead of uploading the new patches, he would have
        to make sure to update the 001-latest tarball (or whatever) with each
        patch. I wouldn't do it, for sure. And I prefer Bram working in Vim
        rather than doing administrative tasks.

        - People like me, who automates the process, can now download only the
        new files (new patches, etc.) using wget instead of downloading a big
        tarball each time. This would be slower and less comfortable. For a
        start, I can tell if new patches have been published just by looking
        at the directory listing at ftp.vim.org (although I don't do it, I'm
        subscribed to vim_dev instead).

        - Some other very intelligent reason that I can't think about right now
        because I'm not clever enough ;)

        For me, saving time for Bram is enough.

        > patching file runtime/doc/os_vms.txt
        > can't find file to patch at input line 743
        > Perhaps you used the wrong -p or --strip option?

        Don't know the rest of the problems, this one is caused by not having
        the "extra" sources. You have only the UNIX sources, download the file
        "vim-7.2-extra.tar.gz" and the patches should apply cleanly. I usually
        download "vim-7.2-lang.tar.gz" too, just in case. Having the full
        sources is better if you patch frequently: you don't have to cherrypick
        the patches, then.

        --
        Raúl "DervishD" Núñez de Arenas Coronado
        Linux Registered User 88736 | http://www.dervishd.net
        It's my PC and I'll cry if I want to... RAmen!

        --~--~---------~--~----~------------~-------~--~----~
        You received this message from the "vim_use" maillist.
        For more information, visit http://www.vim.org/maillist.php
        -~----------~----~----~----~------~----~------~--~---
      • Tony Mechelynck
        ... This question, like all questions about compiling Vim, belongs on the vim_dev list where I m trying to redirect it. Because it would take needlessly much
        Message 3 of 20 , Jul 18, 2009
        • 0 Attachment
          On 18/07/09 14:47, Ryan J M wrote:
          >
          > I have been a vimmer for years, but it was my first time to build it
          > from src, because I found that my CENTOS vim got some problems on
          > cscope co-operations.
          > Following README file lcoated at
          > ftp://ftp.vim.org/pub/vim/patches/7.2/README, I got a little pain when
          > patching. please take a look at logs at the bottom.
          >
          > why don't vim provide a whole big patch for 001-latest one?
          > Fix me if I missed anything, thanks.
          >

          This question, like all questions about compiling Vim, belongs on the
          vim_dev list where I'm trying to redirect it.

          Because it would take needlessly much time to produce and space to keep
          on the disk as many big 001-xxx patches as there are individual patches.

          What Bram does is produce recapitulative patches now and then, usually
          for every round hundred. Indeed, under
          ftp://ftp.vim.org/pub/vim/patches/7.2/ there are the following files:

          README
          the "table of contents"
          MD5
          MD5SUMS
          I'm not sure, but I believe these two are related
          with "checksumming" the patches
          7.2.001 to 7.2.234
          234 individual patches
          7.2.001-100.gz
          7.2.101-200.gz
          two compressed recapitulative patches

          so you only need to apply two big patches plus 34 small ones; then
          _keep_ your patched sources so the next time you won't have to apply
          that many of them.

          Anyway, if you could apply just one 7.2.001-234.gz patch rather than two
          recapitulative ones plus 34 individual ones, I think you would get the
          same "patching errors", because apparently they stem from the fact that
          you didn't download the extra archive. The result is that every change
          to an "extra" source gives a "file not found" error in the patcher.

          That's exactly why, on my Unix HowTo page
          http://users.skynet.be/antoine.mechelynck/vim/compunix.htm , I recommend
          to download _all three_ archives (unix, extra and lang) even if you're
          on Unix (and so probably won't need the "extra" sources) and even if you
          don't want multilingual features. If you have the full sources from all
          three archives, all patches should apply cleanly. Then (depending on
          your configuration) modules that you don't need will be neither compiled
          nor linked anyway.


          Best regards,
          Tony.
          --
          Your home electrical system is basically a bunch of wires that
          bring electricity into your home and take if back out before it has a
          chance to kill you. This is called a "circuit". The most common home
          electrical problem is when the circuit is broken by a "circuit
          breaker"; this causes the electricity to back up in one of the wires
          until it bursts out of an outlet in the form of sparks, which can
          damage your carpet. The best way to avoid broken circuits is to change
          your fuses regularly.
          Another common problem is that the lights flicker. This
          sometimes means that your electrical system is inadequate, but more
          often it means that your home is possessed by demons, in which case
          you'll need to get a caulking gun and some caulking. If you're not
          sure whether your house is possessed, see "The Amityville Horror", a
          fine documentary film based on an actual book. Or call in a licensed
          electrician, who is trained to spot the signs of demonic possession,
          such as blood coming down the stairs, enormous cats on the dinette
          table, etc.
          -- Dave Barry, "The Taming of the Screw"

          --~--~---------~--~----~------------~-------~--~----~
          You received this message from the "vim_use" maillist.
          For more information, visit http://www.vim.org/maillist.php
          -~----------~----~----~----~------~----~------~--~---
        • Markus Heidelberg
          ... Why does Vim provide patches at all? For convenience you can use a repository for updating your Vim sources, for example one of these:
          Message 4 of 20 , Jul 18, 2009
          • 0 Attachment
            Ryan J M, 18.07.2009:
            >
            > why don't vim provide a whole big patch for 001-latest one?

            Why does Vim provide patches at all?

            For convenience you can use a repository for updating your Vim sources,
            for example one of these:
            http://repo.or.cz/w/vim_extended.git
            http://repo.or.cz/w/vim_mainline.git

            Markus


            --~--~---------~--~----~------------~-------~--~----~
            You received this message from the "vim_use" maillist.
            For more information, visit http://www.vim.org/maillist.php
            -~----------~----~----~----~------~----~------~--~---
          • bill lam
            ... git already got a very good support for branch, so that can the vim_extended made as a branch in vim_mainline? -- regards,
            Message 5 of 20 , Jul 18, 2009
            • 0 Attachment
              On Sat, 18 Jul 2009, Markus Heidelberg wrote:
              >
              > Ryan J M, 18.07.2009:
              > >
              > > why don't vim provide a whole big patch for 001-latest one?
              >
              > Why does Vim provide patches at all?
              >
              > For convenience you can use a repository for updating your Vim sources,
              > for example one of these:
              > http://repo.or.cz/w/vim_extended.git
              > http://repo.or.cz/w/vim_mainline.git

              git already got a very good support for branch, so that can the
              vim_extended made as a branch in vim_mainline?

              --
              regards,
              ====================================================
              GPG key 1024D/4434BAB3 2008-08-24
              gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

              --~--~---------~--~----~------------~-------~--~----~
              You received this message from the "vim_use" maillist.
              For more information, visit http://www.vim.org/maillist.php
              -~----------~----~----~----~------~----~------~--~---
            • bill lam
              ... It is rather strange that Bram does not push his version control repository for public read access, or that he never use any version control system
              Message 6 of 20 , Jul 18, 2009
              • 0 Attachment
                On Sat, 18 Jul 2009, Raúl Núñez de Arenas Coronado wrote:
                > Bram already provides 001-100, 100-200, etc. Providing 001-latest would
                > be a bit of a problem due to the following reasons:

                It is rather strange that Bram does not push his version control
                repository for public read access, or that he never use any version
                control system (cvs/svn/git/hg/...) for maintaining vim source file?

                --
                regards,
                ====================================================
                GPG key 1024D/4434BAB3 2008-08-24
                gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

                --~--~---------~--~----~------------~-------~--~----~
                You received this message from the "vim_use" maillist.
                For more information, visit http://www.vim.org/maillist.php
                -~----------~----~----~----~------~----~------~--~---
              • Markus Heidelberg
                ... The reason why I created two repositories is that vim_mainline should eventually get tags for released versions and branches for each stable line. At least
                Message 7 of 20 , Jul 18, 2009
                • 0 Attachment
                  bill lam, 19.07.2009:
                  >
                  > On Sat, 18 Jul 2009, Markus Heidelberg wrote:
                  > > http://repo.or.cz/w/vim_extended.git
                  > > http://repo.or.cz/w/vim_mainline.git
                  >
                  > git already got a very good support for branch, so that can the
                  > vim_extended made as a branch in vim_mainline?

                  The reason why I created two repositories is that vim_mainline should
                  eventually get tags for released versions and branches for each stable
                  line. At least these branches would be irrelevant for vim_extended and
                  would only add clutter.

                  The branches vim, vim-runtime and vim-messages in vim_extended are not
                  necessary as well. Maybe they could be removed and only be available in
                  vim_mainline. You can always get them by looking at the second parent
                  commit of the appropriate merge commit in the vim-with-runtime branch,
                  _if_ you need them.

                  Markus



                  --~--~---------~--~----~------------~-------~--~----~
                  You received this message from the "vim_use" maillist.
                  For more information, visit http://www.vim.org/maillist.php
                  -~----------~----~----~----~------~----~------~--~---
                • bill lam
                  Hi Markus, Thank you for explanation, and for the great job for setting up a git mirror to vim source! -- regards,
                  Message 8 of 20 , Jul 18, 2009
                  • 0 Attachment
                    Hi Markus,

                    Thank you for explanation, and for the great job for setting up a git
                    mirror to vim source!

                    --
                    regards,
                    ====================================================
                    GPG key 1024D/4434BAB3 2008-08-24
                    gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

                    --~--~---------~--~----~------------~-------~--~----~
                    You received this message from the "vim_use" maillist.
                    For more information, visit http://www.vim.org/maillist.php
                    -~----------~----~----~----~------~----~------~--~---
                  • Marc Weber
                    ... Doesn t git solve all these problems in the nicest way possible? All those patches can be added as top-git branches. If you miss a piece you can add it
                    Message 9 of 20 , Jul 18, 2009
                    • 0 Attachment
                      Excerpts from Raúl Núñez de Arenas Coronado's message of Sat Jul 18 19:35:19 +0200 2009:
                      > For me, saving time for Bram is enough.
                      Doesn't git solve all these problems in the nicest way possible?
                      All those patches can be added as top-git branches. If you miss a piece
                      you can add it later and update the following patches automatically.
                      Updating is as much work as doing git pull.

                      By the way have a look at this git repo: It may already contain most of
                      those patches. git://repo.or.cz/vim_mainline.git

                      I think raw patches are nice. But I personally prefer git much more.
                      (You can still use git to export those patches automatically). One
                      implementation I like is top-git.

                      And it would be best for vim if git was the "main" repo because working
                      on local patches is very easy if you learned how to do it once (My
                      experience. Yours may differ)

                      And it's not only about Bram's time. It's a about everyone's time trying
                      playing around with the code and new features.

                      If you like I can write down a short introduction to top-git showing why
                      it's a great collaborative tool to keep patches (and their merges) up to
                      date.

                      Marc Weber

                      --~--~---------~--~----~------------~-------~--~----~
                      You received this message from the "vim_use" maillist.
                      For more information, visit http://www.vim.org/maillist.php
                      -~----------~----~----~----~------~----~------~--~---
                    • Raúl Núñez de Arenas Coronado
                      Saluton Marc :) ... Not at all unless Bram puts time explaining which revisions are inter-patches (so, probably unstable and you shouldn t try to build Vim
                      Message 10 of 20 , Jul 19, 2009
                      • 0 Attachment
                        Saluton Marc :)

                        Marc Weber <m...@...> dixit:
                        > Excerpts from Raúl Núñez de Arenas Coronado's message of Sat Jul 18 19:35:19 +0200 2009:
                        >> For me, saving time for Bram is enough.
                        > Doesn't git solve all these problems in the nicest way possible?

                        Not at all unless Bram puts time explaining which revisions are
                        "inter-patches" (so, probably unstable and you shouldn't try to build
                        Vim from them) and which revisions are not.

                        In the end, he should maintain two public branches: one for unstable
                        code, another for stable code. Right now he has probably his revision
                        control private and publishes only code that can be considered stable.

                        I do more or less the same with my projects. I have Bazaar branches for
                        all of them containing the current development code, and from time to
                        time I publish stable versions. I don't want nor like to maintain a
                        stable branch and do merges from the unstable branch. Way too much work
                        for me. If anyone wants to play with the code, he can branch from my
                        repositories, no problem. But I don't release new versions or patches
                        from a Bazaar branch. My view.

                        > And it's not only about Bram's time. It's a about everyone's time trying
                        > playing around with the code and new features.

                        Then ask Bram to publish his repositories.

                        > If you like I can write down a short introduction to top-git showing
                        > why it's a great collaborative tool to keep patches (and their merges)
                        > up to date.

                        Thanks, but no thanks. I'm very happy with Bazaar, and I don't decide
                        about Vim sources, repositories and whatnot. You have to ask Bram, not
                        me. I was just explaining why I think Bram doesn't publish a tarball
                        containing patches from 001 to latest. I wasn't even discussing revision
                        control systems ;)

                        --
                        Raúl "DervishD" Núñez de Arenas Coronado
                        Linux Registered User 88736 | http://www.dervishd.net
                        It's my PC and I'll cry if I want to... RAmen!

                        --~--~---------~--~----~------------~-------~--~----~
                        You received this message from the "vim_use" maillist.
                        For more information, visit http://www.vim.org/maillist.php
                        -~----------~----~----~----~------~----~------~--~---
                      • Ryan J M
                        ... Thanks, when adding extra and lang packages, vim72 was updated to latest patch cleanly. ... I guess there might be a simple shell script could make all
                        Message 11 of 20 , Jul 19, 2009
                        • 0 Attachment
                          2009/7/19 Raúl Núñez de Arenas Coronado <raulnac@...>:

                          > Probably your problem is that your vim72 sources doesn't include the
                          > "extra" files? If you are going to use all the patches published by Bram
                          > you need to have the pristine sources and the extra sources. This is a
                          > blind shot because I haven't had time to read your problem. I've patched
                          > my Vim to 228 (by now...) without any problem, and I do it automatically
                          > using a little shell script.


                          Thanks, when adding "extra" and "lang" packages, vim72 was updated to
                          latest patch cleanly.


                          >
                          > For me, saving time for Bram is enough.
                          >

                          I guess there might be a simple shell script could make all of us happy :)

                          ====
                          #!/bin/sh

                          #prepare
                          mkdir -p vim-7.2-latest
                          cd vim-7.2-latest
                          tar xfz $path_src/vim-7.2.tar.bz2
                          tar xfz $path_src/vim-7.2-extra.tar.gz
                          tar xfz $path_src/vim-7.2-lang.tar.gz

                          #patch
                          for i in $(seq 1 1 2000)
                          do
                          if [ -f $path_patch/7.2.$i ]
                          then
                          echo "Patching $path_patch/7.2.$i..."
                          patch -p0 < $path_patch/7.2.$i
                          else
                          # no more patches, quit patching...
                          echo "[ done ]"
                          break
                          fi
                          done

                          cd ..
                          tar cfz vim-72-latest.tgz vim-72-latest
                          ====

                          Sorry for the ugly(wrong) script, haven't wrote for long time...


                          --
                          FIXME if it is wrong.

                          --~--~---------~--~----~------------~-------~--~----~
                          You received this message from the "vim_use" maillist.
                          For more information, visit http://www.vim.org/maillist.php
                          -~----------~----~----~----~------~----~------~--~---
                        • Ryan J M
                          On Sun, Jul 19, 2009 at 5:32 AM, Markus ... There might be two reasons that I thought git repo is inconvenience 1) not all vimmers have git installed on their
                          Message 12 of 20 , Jul 19, 2009
                          • 0 Attachment
                            On Sun, Jul 19, 2009 at 5:32 AM, Markus
                            Heidelberg<markus.heidelberg@...> wrote:
                            >
                            > For convenience you can use a repository for updating your Vim sources,
                            > for example one of these:
                            > http://repo.or.cz/w/vim_extended.git
                            > http://repo.or.cz/w/vim_mainline.git
                            >

                            There might be two reasons that I thought git repo is inconvenience
                            1) not all vimmers have git installed on their boxes.
                            2) comparing to gzip-ed or bzip-ed files, it might take more time to
                            download via git.

                            Just my personal view, :)



                            --
                            FIXME if it is wrong.

                            --~--~---------~--~----~------------~-------~--~----~
                            You received this message from the "vim_use" maillist.
                            For more information, visit http://www.vim.org/maillist.php
                            -~----------~----~----~----~------~----~------~--~---
                          • Marc Weber
                            Hi Markus! It s nice to see that you respond that fast! Would you mind me collecting all major vim patches which maybe will never be merged into mainline? I d
                            Message 13 of 20 , Jul 19, 2009
                            • 0 Attachment
                              Hi Markus!

                              It's nice to see that you respond that fast!
                              Would you mind me collecting all major vim patches which maybe will
                              never be merged into mainline?
                              I'd like to create top-git branches for them maybe pushing them to your
                              repo?
                              The vim wiki could be used to explain which branch adds which features
                              and how stable a branch is.

                              The idea is to make patch writers responsible to keep their patches
                              upstream. Most of the time they do so anyway. If they don't you can
                              clearly see which work has to be to update a patch.

                              vim-dev list: Do you think it's ok to add a pointer on vim.org download
                              page telling about this "vim-experimental-maybe-next" wiki page?

                              My goal is that trying out a new feature is as easy as:
                              git clone ...
                              git checkout branch
                              ./configure --enable-...
                              make

                              This is important to get more testers so that features become more
                              stable.

                              Of course I don't want to force anyone using git if they prefer bazaar.
                              I found one use case some month ago I couldn't do in bazaar such as
                              finding a patch adding a line or such. It was in bazaar unstable that
                              time. I didn't find a task I couldn't do with git. That's why I most
                              familiar with it today.

                              Marc Weber

                              --~--~---------~--~----~------------~-------~--~----~
                              You received this message from the "vim_use" maillist.
                              For more information, visit http://www.vim.org/maillist.php
                              -~----------~----~----~----~------~----~------~--~---
                            • Marc Weber
                              ... Ryan, thank you for your interest! 1) You can export to patches easily. Hosting sites such as github.com do create compressed archives (.zip and .tar.gz or
                              Message 14 of 20 , Jul 19, 2009
                              • 0 Attachment
                                Excerpts from Ryan J M's message of Sun Jul 19 16:45:16 +0200 2009:
                                > There might be two reasons that I thought git repo is inconvenience
                                > 1) not all vimmers have git installed on their boxes.
                                > 2) comparing to gzip-ed or bzip-ed files, it might take more time to
                                > download via git.

                                Ryan, thank you for your interest!

                                1) You can export to patches easily. Hosting sites such as github.com do
                                create compressed archives (.zip and .tar.gz or such) on the fly.
                                Basically it's as much work as running
                                $ git show $REV > patch
                                2) using git you can fetch the latest rev only by using
                                git clone --depth 1 $git_source
                                as git compresses data it won't take that much longer.

                                benefits: You can use git pull to get newest patches.
                                compare this to:
                                - open browser to go to www.vim.org -> downloads -> ..
                                - run patch -p1
                                (still no easy way to distribute your changes other people can follow!)
                                To distribute your changes just pick an mirror and do git push.

                                git has more benefits: You can automate sending patches to mailinglists,
                                you can create RSS feeds etc.

                                I don't want to branch Vim at this point in time. All I want is making
                                it easy to distribute ideas and extensions so that they can be explored
                                and tested. Whether such extensions will be integrated into mainline vim
                                or not is another topic.

                                Marc Weber

                                --~--~---------~--~----~------------~-------~--~----~
                                You received this message from the "vim_use" maillist.
                                For more information, visit http://www.vim.org/maillist.php
                                -~----------~----~----~----~------~----~------~--~---
                              • pansz
                                ... Do you really think so? I don t. Many FOSS users may think against your argument. You can change the compile arguments when compiling and disable/enable
                                Message 15 of 20 , Jul 19, 2009
                                • 0 Attachment
                                  Tony Mechelynck 写道:
                                  >
                                  > This question, like all questions about compiling Vim, belongs on the
                                  > vim_dev list where I'm trying to redirect it.
                                  >

                                  Do you really think so? I don't. Many FOSS users may think against your
                                  argument.

                                  You can change the compile arguments when compiling and disable/enable
                                  features you want. This is called "customization", it is something like
                                  changing menu options, not "development" at all.

                                  i.e. I don't do any development on vim, I'm a pure user of vim, but I
                                  definitely need to compile vim. So the vim-use mail list should include
                                  those who want to compile vim without changing any source code.

                                  For patches, I think if the OP only want the latest, he can use vim svn,
                                  it always contains a stable revision (i.e. no inter-patch revisions) and
                                  it is reasonably new.


                                  --~--~---------~--~----~------------~-------~--~----~
                                  You received this message from the "vim_use" maillist.
                                  For more information, visit http://www.vim.org/maillist.php
                                  -~----------~----~----~----~------~----~------~--~---
                                • Matt Wozniski
                                  ... *shrug*, I once tried to move a question on compiling from vim-dev to vim-use and was admonished by Bram for it. So, at the very least, Bram sides with
                                  Message 16 of 20 , Jul 19, 2009
                                  • 0 Attachment
                                    On Sun, Jul 19, 2009 at 9:22 PM, pansz wrote:
                                    >
                                    > Tony Mechelynck 写道:
                                    >>
                                    >> This question, like all questions about compiling Vim, belongs on the
                                    >> vim_dev list where I'm trying to redirect it.
                                    >>
                                    >
                                    > Do you really think so? I don't.

                                    *shrug*, I once tried to move a question on compiling from vim-dev to
                                    vim-use and was admonished by Bram for it. So, at the very least,
                                    Bram sides with Tony, even if you and I may find it unintuitive. :-)
                                    Really, compiling software is somewhere in-between using it and
                                    developing it. Most users never need to compile, though, and all
                                    developers will, so vim-dev is probably the better place to get the
                                    more targeted audience.

                                    ~Matt

                                    --~--~---------~--~----~------------~-------~--~----~
                                    You received this message from the "vim_use" maillist.
                                    For more information, visit http://www.vim.org/maillist.php
                                    -~----------~----~----~----~------~----~------~--~---
                                  • Markus Heidelberg
                                    Hi, ... Heh, not always :) I was pretty busy the last days. ... That would be nice. I ve always appreciated some help with this, but lost interest in looking
                                    Message 17 of 20 , Aug 1, 2009
                                    • 0 Attachment
                                      Hi,

                                      Marc Weber, 19.07.2009:
                                      > It's nice to see that you respond that fast!

                                      Heh, not always :)
                                      I was pretty busy the last days.

                                      > Would you mind me collecting all major vim patches which maybe will
                                      > never be merged into mainline?

                                      That would be nice. I've always appreciated some help with this, but
                                      lost interest in looking at more patches myself.

                                      > I'd like to create top-git branches for them

                                      I've never used topgit or another tool on top of git.
                                      What's the benefit? Why not just ordinary git branches? This would also
                                      add another dependency for users, wouldn't it?

                                      > maybe pushing them to your repo?

                                      Sure.

                                      > The vim wiki could be used to explain which branch adds which features
                                      > and how stable a branch is.

                                      Currently there is a online description for each branch, but further
                                      information could go into a wiki page or something to not overload the
                                      repo page.
                                      I guess you already know about
                                      http://groups.google.com/group/vim_dev/web/vim-patches

                                      > The idea is to make patch writers responsible to keep their patches
                                      > upstream.

                                      That was my initial idea back then, that the patch authors could have
                                      some kind of upstream, where they can send their patches to and
                                      everybody could find them.

                                      > vim-dev list: Do you think it's ok to add a pointer on vim.org download
                                      > page telling about this "vim-experimental-maybe-next" wiki page?

                                      I have no objections to it.
                                      I planned to ask for a link to the vim_mainline/vim_extended
                                      repositories. But I planned to do it after the rewrite, which hasn't
                                      been done yet and may not be done in the near future.

                                      > My goal is that trying out a new feature is as easy as:
                                      > git clone ...
                                      > git checkout branch
                                      > ./configure --enable-...
                                      > make

                                      It already is as easy.

                                      > Of course I don't want to force anyone using git if they prefer bazaar.

                                      Or another system or none at all. At least at the gitweb page of
                                      vim_extended there are links for downloading raw patch files. But for
                                      enjoying the advantages, of course it is the best to just use git with
                                      this git repo.

                                      Markus


                                      --~--~---------~--~----~------------~-------~--~----~
                                      You received this message from the "vim_use" maillist.
                                      For more information, visit http://www.vim.org/maillist.php
                                      -~----------~----~----~----~------~----~------~--~---
                                    • Markus Heidelberg
                                      ... These reasons have nothing to do with inconvenience. Markus --~--~---------~--~----~------------~-------~--~----~ You received this message from the
                                      Message 18 of 20 , Aug 1, 2009
                                      • 0 Attachment
                                        Ryan J M, 19.07.2009:
                                        > There might be two reasons that I thought git repo is inconvenience
                                        > 1) not all vimmers have git installed on their boxes.
                                        > 2) comparing to gzip-ed or bzip-ed files, it might take more time to
                                        > download via git.

                                        These reasons have nothing to do with inconvenience.

                                        Markus


                                        --~--~---------~--~----~------------~-------~--~----~
                                        You received this message from the "vim_use" maillist.
                                        For more information, visit http://www.vim.org/maillist.php
                                        -~----------~----~----~----~------~----~------~--~---
                                      • Markus Heidelberg
                                        ... Regardless of where compile questions belong to (and I think it s absolutely OK in vim-use), moving them to vim-dev will not work. Since the vim lists a
                                        Message 19 of 20 , Aug 1, 2009
                                        • 0 Attachment
                                          Matt Wozniski, 20.07.2009:
                                          >
                                          > On Sun, Jul 19, 2009 at 9:22 PM, pansz wrote:
                                          > >
                                          > > Tony Mechelynck 写道:
                                          > >>
                                          > >> This question, like all questions about compiling Vim, belongs on the
                                          > >> vim_dev list where I'm trying to redirect it.
                                          > >>
                                          > >
                                          > > Do you really think so? I don't.
                                          >
                                          > *shrug*, I once tried to move a question on compiling from vim-dev to
                                          > vim-use and was admonished by Bram for it. So, at the very least,
                                          > Bram sides with Tony, even if you and I may find it unintuitive. :-)

                                          Regardless of where compile questions belong to (and I think it's
                                          absolutely OK in vim-use), moving them to vim-dev will not work.
                                          Since the vim lists a subscriber-only and you don't know it the person
                                          is subscibed to both, you force him to subscribe to it to continue
                                          discussing his questions. But it's more probably that the questions will
                                          be forked and discussed in two ways on the two mailing lists.

                                          Markus


                                          --~--~---------~--~----~------------~-------~--~----~
                                          You received this message from the "vim_use" maillist.
                                          For more information, visit http://www.vim.org/maillist.php
                                          -~----------~----~----~----~------~----~------~--~---
                                        • Marc Weber
                                          ... top-git branches are ordinary branches with additional info attached such as .top-msg (info about this branch) and .top-deps (information on which
                                          Message 20 of 20 , Aug 13, 2009
                                          • 0 Attachment
                                            Excerpts from Markus Heidelberg's message of Sat Aug 01 19:07:29 +0200 2009:
                                            > I've never used topgit or another tool on top of git.
                                            > What's the benefit? Why not just ordinary git branches? This would also
                                            > add another dependency for users, wouldn't it?
                                            top-git branches are "ordinary" branches with additional info attached
                                            such as .top-msg (info about this branch) and .top-deps (information on
                                            which branches this branch is based)

                                            The benefits are:
                                            * top-git let's you track hierarchies of branches. You can use dotty to
                                            visualize dependencies
                                            * top-git let's you export patch series easily
                                            * top-git let's you merge your branch and its dependencies with upstream
                                            easily by invoking "tg update".

                                            Of course this all can be done manually as well. In the end it doesn't
                                            matter. Having all in one git repo would be a huge step IMHO.

                                            Marc Weber

                                            --~--~---------~--~----~------------~-------~--~----~
                                            You received this message from the "vim_use" maillist.
                                            For more information, visit http://www.vim.org/maillist.php
                                            -~----------~----~----~----~------~----~------~--~---
                                          Your message has been successfully submitted and would be delivered to recipients shortly.