Tyru Exe wrote:
> Hi list.
>
> I tested this code on vim73.
> :echo "\" =~# "\"=> 0
>
> Is this right behavior?
Yes, using "\" as a regexp will give unpredictable behavior.
It's not a valid pattern.
--
Back up my hard drive? I can't find the reverse switch!
/// Bram Moolenaar -- b...@
Dominique Pelle wrote:
> ryo7000 skribis:
>
> > Hi
> >
> > gVim crashes when operating as follows.
> >
> > gvim -u NONE -U NONE --noplugin --nofork -c "set guifont=Sans\ 10" -
> > c vnew
> >
> > qa
> > :tabnew
> > :q
> > q
> > 1...@a
> >
> > The cause of the crash is as follows.
> >
> > *
Tyru Exe wrote:
> Hi list.
>
> Place these scripts in ~/.vim
> - autoload/mylib.vim
> - autoload/mylib2.vim
>
>
> --- autoload/mylib.vim ---
>
> function! mylib#func()
> echo 'mylib#func()'
> echo exists('*mylib2#func')
> endfunction
>
>
> --- autoload/mylib2.vim ---
>
> function!
I have exactly the same problem under vim 7.2.436 with ruby files.
When I have syntax on and foldmethod=syntax then when I'm typing some
characters in class body, somewhere at the top of the class, it's
really slow.
When I changed foldmethod to indent it started to work smoothly.
On May 27, 7:08 a
Thank you for a more appropriate patch.
> Please use this patch and try it out:
I tried this patch, Segfault did not occur at all.
Regards,
ryo7000
On 7月11日, 午後9:16, Bram Moolenaar wrote:
> Dominique Pelle wrote:
> > ryo7000 skribis:
>
> > > Hi
>
> > > gVim crashes when operating as follows.
>
This appears to happen more often these days: I send a message to a user
and some blacklist system blocks my message. I have no control over
what my ISP does, these services simply block my message without a way
for me to fix this.
Please, don't use these blacklist services, they are very annoyi
Hi tyru,
I've run into this while adding integration between two plug-ins I was
developing. When you control both plug-ins you can add a dummy function
which the other plug-in can try to call (where catch /E117/ means the
plug-in isn't installed) or you can just use the g:loaded_plugin
conven
Hi again tyru,
In case you didn't know / haven't found it yet, you can use the stridx()
function instead: stridx("foo \ bar", "\") >= 0 evaluates to
true.
- Peter Odding
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replyin
On 11/07/10 16:04, Bram Moolenaar wrote:
This appears to happen more often these days: I send a message to a user
and some blacklist system blocks my message. I have no control over
what my ISP does, these services simply block my message without a way
for me to fix this.
Please, don't use the
Tony Mechelynck wrote:
> On 11/07/10 16:04, Bram Moolenaar wrote:
> >
> > This appears to happen more often these days: I send a message to a user
> > and some blacklist system blocks my message. I have no control over
> > what my ISP does, these services simply block my message without a way
>
Jjgod Jiang wrote (a long time ago):
> Running vim under Mac OS X terminal do not support copy to/from
> system clipboard currently, this patch add this feature. To have
> this feature in mainstream, we receive the following benifits:
>
> 1. We can copy from/to system clipboard without running
I see.
Thanks Bram, Peter.
On Jul 11, 9:16 pm, Bram Moolenaar wrote:
> Tyru Exe wrote:
> > Hi list.
>
> > I tested this code on vim73.
> > :echo "\" =~# "\" => 0
>
> > Is this right behavior?
>
> Yes, using "\" as a regexp will give unpredictable behavior.
> It's not a valid pattern.
>
> --
>
> Bram
> This works as intended. Autoload scripts are only loaded when used.
> Not when you check if something defined in it exists.
This is expected behavior?
hmm, but checking this at command-line, exists() returns 1.
:echo exists('*mylib#func')
and seeing :scriptnames, autoload/mylib.vim h
On Jul 10, 3:57 pm, Bram Moolenaar wrote:
> [copying to vim-dev, Mattias's mail server blocks my messages]
Oops, seems my server doesn't like your hosting provider. Just added
an exception, so that should work better next time.
> I found that a few files were left behind after unpacking, I added
From: Benjamin R. Haskell
I often find myself trying to figure out what function performs a certain
function. Particularly for list- and dictionary-functions, I consistently
found myself unable to get back to the 'List manipulation' and 'Dictionary
manipulation' subsections of *function-list*.
I don't know about anyone else, but I just use the built-in spam and
message routing facilities within Thunderbird. The message routing
stuff I use to direct any/all vim related activities to the vim folder
and spam just gets put into the junk folder where I review everything.
I am a member
Benjamin R. Haskell wrote:
> I often find myself trying to figure out what function performs a certain
> function. Particularly for list- and dictionary-functions, I consistently
> found myself unable to get back to the 'List manipulation' and 'Dictionary
> manipulation' subsections of *function
Mattias Winther wrote:
> On Jul 10, 3:57 pm, Bram Moolenaar wrote:
> > [copying to vim-dev, Mattias's mail server blocks my messages]
>
> Oops, seems my server doesn't like your hosting provider. Just added
> an exception, so that should work better next time.
Thanks. But you might want to re
Hi,
I've improved the patch for handling JavaScript code indenting through
cindent. Now it is able to handle anonymous functions inside
parentheses etc. correctly. The diff from the latest changeset is
attached. This reverts the change made to 'cin_iscase' (addition of
argument 'strict'). Now the
On Sun, 11 Jul 2010, tyru wrote:
> > Bram
> > This works as intended. Autoload scripts are only loaded when used.
> > Not when you check if something defined in it exists.
>
> This is expected behavior?
> hmm, but checking this at command-line, exists() returns 1.
> :echo exists('*mylib#func
Hari Kumar wrote:
> I've improved the patch for handling JavaScript code indenting through
> cindent. Now it is able to handle anonymous functions inside
> parentheses etc. correctly. The diff from the latest changeset is
> attached. This reverts the change made to 'cin_iscase' (addition of
> arg
On 11 July 2010 16:45, Bram Moolenaar wrote:
>
> Jjgod Jiang wrote (a long time ago):
>
>> Running vim under Mac OS X terminal do not support copy to/from
>> system clipboard currently, this patch add this feature. To have
>> this feature in mainstream, we receive the following benifits:
>>
>> 1. W
ryo7000 wrote:
>> Please use this patch and try it out:
>
> I tried this patch, Segfault did not occur at all.
Patch also works for me: no more crash, no more valgrind error.
-- Dominique
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
Christian -
I included your patch to produce a side-by-side diff with :TOhtml.
It looks nice!
I changed it a bit, so that it also works when producing CSS.
And quit the buffers for the individual html files.
And add a variable to disable this behavior and produce just one
HTML file for the curre
Jjgod Jiang wrote (a long time ago):
> >> Running vim under Mac OS X terminal do not support copy to/from
> >> system clipboard currently, this patch add this feature. To have
> >> this feature in mainstream, we receive the following benifits:
> >>
> >> 1. We can copy from/to system clipboard wit
Benjamin R. Haskell wrote:
> On Sun, 11 Jul 2010, tyru wrote:
>
> > > Bram
> > > This works as intended. Autoload scripts are only loaded when used.
> > > Not when you check if something defined in it exists.
> >
> > This is expected behavior?
> > hmm, but checking this at command-line, exists
Bram Moolenaar wrote:
> Christian -
>
> I included your patch to produce a side-by-side diff with :TOhtml.
> It looks nice!
>
> I changed it a bit, so that it also works when producing CSS.
> And quit the buffers for the individual html files.
> And add a variable to disable this behavior and prod
Mac terminal vim version 7.2.444
Linux terminal version 7.2.330
:set formatlistpat
returns:
formatlistpat=^\s*\d\+[\]:.)}\t ]\s*
Doing the following results in an error
:set formatlistpat=^\s*\d\+[\]:.)}\t ]\s*
E518: Unknown option: ]\s*
I know this is the default...
When I tried to customize
On Sun, 11 Jul 2010, Bee wrote:
> Mac terminal vim version 7.2.444
> Linux terminal version 7.2.330
>
> :set formatlistpat
> returns:
> formatlistpat=^\s*\d\+[\]:.)}\t ]\s*
>
> Doing the following results in an error
>
> :set formatlistpat=^\s*\d\+[\]:.)}\t ]\s*
>
> E518: Unknown option: ]\s*
On Jul 11, 9:33 pm, "Benjamin R. Haskell" wrote:
> On Sun, 11 Jul 2010, Bee wrote:
> > Mac terminal vim version 7.2.444
> > Linux terminal version 7.2.330
>
> > :set formatlistpat
> > returns:
> > formatlistpat=^\s*\d\+[\]:.)}\t ]\s*
>
> > Doing the following results in an error
>
> > :set formatl
On Jul 11, 2:20 pm, Bram Moolenaar wrote:
> Jjgod Jiang wrote (a long time ago):
> > >> Running vim under Mac OS X terminal do not support copy to/from
> > >> system clipboard currently, this patch add this feature. To have
> > >> this feature in mainstream, we receive the following benifits:
>
>
On Jul 11, 5:10 pm, Dominique Pellé wrote:
> Bram Moolenaar wrote:
> > Christian -
>
> > I included your patch to produce a side-by-side diff with :TOhtml.
> > It looks nice!
>
>
> I see one problem. In my ~/.vimrc, I have this:
>
> let html_use_css=1
> let html_use_xhtml=1
> let html_dyn
32 matches
Mail list logo
