On 14/01/09 07:16, Yasuhiro MATSUMOTO wrote:
> Oops. sorry.
>
> However, the problem happen with the script as your said. :-)
>
> Thanks.
"E486: Pattern not found" means that there was no match. Are you sure
you ran that script while the current file contained one or more 。
characters? When
2009/1/14 Tony Mechelynck :
> On 14/01/09 07:16, Yasuhiro MATSUMOTO wrote:
>> Oops. sorry.
>>
>> However, the problem happen with the script as your said. :-)
>>
>> Thanks.
>
> "E486: Pattern not found" means that there was no match. Are you sure
> you ran that script while the current file c
On 14/01/09 03:03, Yasuhiro MATSUMOTO wrote:
> Hi all.
>
> It seems that quoting arguments of shebang command depend on shellslash.
> but on windows, cmd.exe or command.com can't treat single quote.
>
> --- test.vimrc ---
> set nocompatible
> set shellslash
> --
>
cmd.exe and
On 14/01/09 09:54, Dominique Pelle wrote:
> 2009/1/14 Tony Mechelynck:
>
>> On 14/01/09 07:16, Yasuhiro MATSUMOTO wrote:
>>> Oops. sorry.
>>>
>>> However, the problem happen with the script as your said. :-)
>>>
>>> Thanks.
>> "E486: Pattern not found" means that there was no match. Are you s
On Wed, Jan 14, 2009 at 5:55 PM, Tony Mechelynck
wrote:
>
> On 14/01/09 03:03, Yasuhiro MATSUMOTO wrote:
>> Hi all.
>>
>> It seems that quoting arguments of shebang command depend on shellslash.
>> but on windows, cmd.exe or command.com can't treat single quote.
>>
>> --- test.vimrc ---
>> set no
Bram, please check third patch from me. :-)
see below as descriptions.
http://groups.google.co.jp/group/vim_dev/browse_thread/thread/e9945dbdd6ab388f?hl=ja#455ac73ba4bb0e47
- Yasuhiro Matsumoto
On Wed, Jan 14, 2009 at 6:00 PM, Tony Mechelynck
wrote:
>
> On 14/01/09 09:54, Dominique Pelle wrot
On Wed, Jan 14, 2009 at 6:51 PM, Yasuhiro MATSUMOTO wrote:
> On Wed, Jan 14, 2009 at 5:55 PM, Tony Mechelynck
> wrote:
>>
>> On 14/01/09 03:03, Yasuhiro MATSUMOTO wrote:
>>> Hi all.
>>>
>>> It seems that quoting arguments of shebang command depend on shellslash.
>>> but on windows, cmd.exe or co
On Jan 14, 2:55 am, Tony Mechelynck wrote:
> cmd.exe and command.com also can't handle the forward slash as a path
> separator
I don't know about command.com, but cmd.exe certainly CAN handle
forward slash perfectly fine. Some things don't work, notably tab-
completion of path names and the "c
On 14/01/09 16:41, Ben Fritz wrote:
>
>
> On Jan 14, 2:55 am, Tony Mechelynck wrote:
>
>> cmd.exe and command.com also can't handle the forward slash as a path
>> separator
>
> I don't know about command.com, but cmd.exe certainly CAN handle
> forward slash perfectly fine. Some things don't work,
this will apply to a finite subset of subscribers
* you must have bash
* you must have python
* your python must have BeautifulSoup
* you must want a slick way to get the latest netrw
and i know there are already scripts to update wide swaths
of plugins, but i had such fun writin
Nick is looking for a new perl.vim maintainer as described below but his
original message didn't make it to the vim-dev list for some reason
(even though it was CCed). I've forwarded it to make sure it gets the
exposure he was looking for.
- Forwarded message from Nick Hibma -
From: Ni
* Charles Campbell [090113 11:42]:
>
> Marvin Renich wrote:
> > Sorry to jump in so late, and after you have a solution, but wouldn't
> > putting @NoSpell in the proper places in syntax/netrw.vim be a better
> > solution? How often do you really want spell checking on a directory
> > listing? We
Yasuhiro Matsumoto wrote:
> On Wed, Jan 14, 2009 at 6:51 PM, Yasuhiro MATSUMOTO
> wrote:
> > On Wed, Jan 14, 2009 at 5:55 PM, Tony Mechelynck
> > wrote:
> >>
> >> On 14/01/09 03:03, Yasuhiro MATSUMOTO wrote:
> >>> Hi all.
> >>>
> >>> It seems that quoting arguments of shebang command depend o
Yasuhiro Matsumoto wrote:
> Bram, please check third patch from me. :-)
>
> see below as descriptions.
>
> http://groups.google.co.jp/group/vim_dev/browse_thread/thread/e9945dbdd6ab388f?hl=ja#455ac73ba4bb0e47
Thanks, I'll add it to the todo list.
--
Engineers understand that their appearanc
Dominique Pelle wrote:
> When the argument of the commands :diffget or :diffput
> results in the same buffer as the current buffer, the command
> corrupts the content of the current buffer.
>
> Steps to reproduce:
>
> 1/ create 2 sample files
>
> $ echo foo > file1
> $ echo bar > file2
>
> 2
Hello *,
thanks for all the feedback, this was actually rather helpful. Thanks
especially to Charles for the explanation of why this happens. Since
I don't have admin rights on the machine(s) in question and thus
can't uninstall any old netrw versions, I've settled on the
`...@nospell` op
On 14/01/09 22:13, Bram Moolenaar wrote:
>
> Yasuhiro Matsumoto wrote:
>
>> On Wed, Jan 14, 2009 at 6:51 PM, Yasuhiro MATSUMOTO
>> wrote:
>>> On Wed, Jan 14, 2009 at 5:55 PM, Tony Mechelynck
>>> wrote:
On 14/01/09 03:03, Yasuhiro MATSUMOTO wrote:
> Hi all.
>
> It seems that qu
Yes thats all. thanks
On 1/15/09, Tony Mechelynck wrote:
> On 14/01/09 22:13, Bram Moolenaar wrote:
>>
>> Yasuhiro Matsumoto wrote:
>>
>>> On Wed, Jan 14, 2009 at 6:51 PM, Yasuhiro MATSUMOTO
>>> wrote:
On Wed, Jan 14, 2009 at 5:55 PM, Tony Mechelynck
wrote:
> On 14/01/09 03:03, Y
Hi all.
Starting vim with arguments '*.rb' is very slow. It cause vim search
ruby path from system call in 'ftplugin/ruby.vim'.
'ftplugin/perl.vim' check perlpath as global variable with
exists('perlpath'). I use poor spec machine, and I wrote followingin
my vimrc to ignore search .
let g:perlp
On Wed, 14 Jan 2009 12:54:32 -0500
James Vega wrote:
> Nick is looking for a new perl.vim maintainer as described below but
> his original message didn't make it to the vim-dev list for some
> reason (even though it was CCed). I've forwarded it to make sure it
> gets the exposure he was looking
20 matches
Mail list logo
