Re: Vim-7.4 no longer recognizes some mail files by file name

On Tue, Jul 30, 2013 at 12:05 PM, Manuel Ortega wrote: > On Mon, Jul 29, 2013 at 8:36 PM, Gary Johnson wrote: > >> >> This should be detected by both of the following patterns in >> $VIMRUNTIME/filetype.vim: >> >> mutt[[:alnum:]_-]\{6\} >> mutt[[:alnum:]._-]\{6\} >> >> Both of those patte

Re: strikethrough text in gvim

On Mi, 24 Jul 2013, Jeroen Budts wrote: > I have a feature request for gvim, I'm not sure if I should ask it > here or on the dev list? > Would it be possible to add support for strikethrough text in Gvim? > Since gvim can already display bold, italic, underline and undercurl > text I guess it can

Re: Vim slow after big count insert

Hi Mike! On So, 21 Jul 2013, Mike Williams wrote: > On 20/07/2013 10:13, LCD 47 wrote: > > I believe this can be fixed with a counter that means something > >along the lines of: "this line is longer than &tw, and it has no > >breaking point for the first X characters". Then X would be update

Re: Vim-7.4 no longer recognizes some mail files by file name

On Mon, Jul 29, 2013 at 8:36 PM, Gary Johnson wrote: > I just noticed this today with 7.4b but the behavior is the same > with 7.4a.9. It works correctly with 7.3.882. > > The problem is that when I open a temporary file created by mutt > with the name /tmp/muttV1LGjR, the latest versions of vim

Re: [patch] :perldo doesn't work on 32-bit Windows

Hi Bram, 2013/07/30 Tue 5:15:49 UTC+9 Bram Moolenaar wrote: > OK. Is _USE_32BIT_TIME_T only used by Perl or does it affect the whole > of Vim? It affects the whole of Vim. So we have to consider other if_*s. I confirmed that if_python/python3/ruby worked fine with or without _USE_32BIT_TIME_T. I

Re: BUG: Yank of "exclusive" selection set via marks is off-by-one at first

Christian Brabandt wrote: > On Fr, 26 Jul 2013, Ingo Karkat wrote: > > > Hello Vim developers, > > > > Patch 7.3.590 allows to set the visual selection directly via the marks > > '< and '>. I've found a problem with :set selection=exclusive (while > > developing a custom mapping): When the firs

Re: Vim-7.4 no longer recognizes some mail files by file name

Gary Johnson wrote: > I just noticed this today with 7.4b but the behavior is the same > with 7.4a.9. It works correctly with 7.3.882. > > The problem is that when I open a temporary file created by mutt > with the name /tmp/muttV1LGjR, the latest versions of vim do not > recognize this as a fi

[Patch] Escape file names when reading files in Zip container

Hello, I'm editing OOXML files pretty often with vim and the zip plugin. However those have a [Content_Types.xml] file inside the zip that can't be opened. You'll find attached a simple patch against trunk to fix that problem by just escaping the name of the file to open in the unzip command. Th

[Patch] can't open [Content_Types.xml] files in OOXML files

Hello, I'm using the zip plugin to open OOXML and ODF files pretty often and OOXML files are containing a file named [Content_Types.xml]. There is a bug in the zip.vim that prevents those files to be opened. You'll find attached a simple patch against trunk fixing that bug by just escaping the

Re: [patch] Should we use vimLoadLib() in if_tcl.c?

Hi, 2013/07/29 Mon 21:53:51 UTC+9 Ken Takata wrote: > I think vimLoadLib() is used because of security reason, > but LoadLibraryEx() is used directly in if_tcl.c. > Should we use vimLoadLib() in if_tcl.c? > > --- a/src/if_tcl.c > +++ b/src/if_tcl.c > @@ -195,7 +195,7 @@ > > if (hTclLib) >

Re: With vim 7.4a and 7.4b I get default compatible mode even with a vimrc file

On Monday, 29 July 2013 11:16:49 UTC+2, anst wrote: > On windows 7 64-bit I get this behaviour both in gvim and vim. > The options I have in the vimrc file are read, so this seems like a bug. > > Regards > Andreas Stabel As I stated in my first post the vimrc file is read so it is not a problem