>
> And here's my fix for this malfeature, which is so obviously one of
> the many, many bugs in Vi that has sadly stuck around far too long:
>
Nikolai,
It is a matter of preference, not a malfeature. It would take months of
retraining for me to adapt if the cursor was 'fixed' so that it does
Hi Thore,
I've never tried folding like this before, and unfortunately I don't have time
to try out this 'optimized' version, but it may work faster for you (I've just
replaced the regex matches with stridx and rearranged the code flow):
set foldexpr=GetFoldLevel()
function! GetFoldLevel()
Hi Thore,
You can probably get away with foldmethod=expr in large files by de-activating
it in Insert mode. I.e., add this to your after/ftplugin/php.vim:
augroup FastFold
autocmd!
autocmd InsertEnter * if &ft == 'php' | setlocal foldmethod=manual | endif
autocmd Insertleave * if &ft ==
Hello all,
I just want to throw this idea out there as a potential solution to the
problems I am having with the PHP syntax. It would be helpful to be able to
name sequential 'nextgroups' for regions and matches, so that the syntax will
highlight an area using certain groups in specific order. I.
Hi Weiguang,
This might help you:
:match IncSearch /\%V\+/
Highlight the area you're interested in with CTRL-V and it remains highlighted
while you edit.
See ':help /\%V' for more information.
regards,
Peter
Send instant messages to your online friends http://au.messenger.yahoo.com
100 levels works for me on OS X.
regards,
Peter
--- "A.J.Mechelynck" <[EMAIL PROTECTED]> wrote:
> Under ":help starstar-wildcard" it is said that the ** wildcard goes up
> to 100 levels deep.
>
> Under ":help starstar" it is said that it goes up to 30 levels deep by
> default, but that any
Hi Srinath,
> For now, I am just going to set noignorecase to get around this, but
> it would be nice if this were fixed. On another note, I would like an
> option which only ignores case when searching. When doing completion,
> I have taken the trouble of typing "Graph" with a capital G, so I
> d
Hello scott,
The 'filetype=' message is what happens when you use ':set filetype=' and don't
specify any filetype.
If you have 'cindent' turned on, Vim will add an indent after a line ending in
a comma (,) and your sample sentence does. Use ':set cindent?' to check if it
is turned on.
regards,
Hi Scott,
>
> excuse me
>
> this transcends ridiculous
>
> i am editing text, and i have gone around the bend to tell vim
> that i am doing so
>
Apparently you can just make a file like this:
~/.vim/ftdetect/txt.vim:
au BufRead,BufNewFile *.txt set filetype=txt
All done. See ':help ne
Sep 13 14:35:14 2006
--- vim70/src/edit.cWed Sep 13 14:26:45 2006
***
*** 3019,3024
--- 3019,3031
p = line + curwin->w_cursor.col;
mb_ptr_back(line, p);
+ /*
+ * PETER HODGE - if completeopt contains 'stop', then stop
+ * insert c
--- Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
> Peter Hodge wrote:
>
> > Backspacing or typing while the Vim 7 Insert completion popup window
> > is running is very difficult when the completion list is long or comes
> > from many sources. Because the po
>
> 1. The second title above is misleading. Bram uses "(after patch nnn)"
> when a patch _depends_ on another, i.e., requires patch nnn to have been
> applied previously, usually because the later patch fixes a bug
> introduced by the earlier one. For instance, official patch 7.0.057 is
> lab
Hello Yakov,
If I recall correctly, didn't you write the shell script which automatically
patches and installs Vim 7? If so, why not expand on it to allow (optionally)
installing unofficial patches from vim.org as well? Maybe a
'--with-patch=' argument would work?
regards,
Peter
--- Yakov Le
Just my 2c worth, is it a display problem that goes away when you press CTRL+L?
regards,
Peter
--- jinxjinx <[EMAIL PROTECTED]> wrote:
>
> :verbose set makeprg? makeef? autowrite? autowriteall?
> makeprg=make
> makeef=
> noautowrite
> noautowriteall
>
> :verbose setlocal filetype?
>filety
--- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> On 10/3/06, Marc Weber <[EMAIL PROTECTED]> wrote:
> > > parsed, it's just executed line-by-line. What /would/ make sense is
> > > to cache the compiled regexes so that regexes used in a loop won't
> > > have to be compiled as often. That's a fair
> Argh. This is exactly why all the hacks one has to employ never
> really quite make it. There's always some base you haven't covered,
> some point you can't reach.
>
> Seriously, if people want to f**k up their session, let them. No one
> who isn't prepared to get burned is going to override
--- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> On 10/4/06, Peter Hodge <[EMAIL PROTECTED]> wrote:
> >
> > --- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> >
> > > > Great idea,
> > > > Nikolei!
> > >^- gaa
>
> Seeing as you've identified the location and apparent fix, why not you?
>
Because I don't want to maintain my own set of patches, that would be more
tiring than using upper-case commands.
On Yahoo!7
M
Hello,
I have discovered that it is possible for a syntax region to overlap a syntax
keyword, even though the region is not contained in the keyword. Take the
following code example and apply the syntax commands below:
TEST CODE:
(is_array($foo))
( is_array($foo) )
SYNTAX COMMANDS:
--- Ilya Bobir <[EMAIL PROTECTED]> wrote:
> Peter Hodge wrote:
> > Hello,
> >
> > I have discovered that it is possible for a syntax region to overlap a
> syntax
> > keyword, even though the region is not contained in the keyword. Take the
> > f
> BTW, using
>
> gvim -u NONE -U NONE
>
> is both redundant (in the case of -U NONE), dangerous (since
> default settings may truncate your viminfo on exit), and put
> you in vi compatible mode. Better is:
>
> gvim -u NONE -i NONE -N
>
I wouldn't think the -i option is necessary, beca
>
> I can reproduce the problem. Indeed looks like a bug. Removing
> "containedin=NOTHING" solves it, while it should not change anything.
>
Sorry for finding a bug while you are so busy. But I am addicted to syntax
highlighting, it's such a wonderful feature.
regards,
Peter
> --
> hundre
Hello,
I've seen it mentioned on this list before, there is already a way to integrate
Vim into Eclipse. Search the mailing list archives for 'Eclipse' (sorry I
don't have time to find it for you).
regards,
Peter
--- Martin Krischik <[EMAIL PROTECTED]> wrote:
> Hello
>
> At the end of the Vi
Hello,
Do you intend to make Elastic Tabs available in a console vim as well?
regards,
Peter
--- Nick Gravgaard <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am the creator of a mechanism called elastic tabstops (see
> nickgravgaard.com/elastictabstops/). Right now, my plan is to try and
> imple
> I don't think so - just the GTK version. One of the advantages of the
> elastic tabstop system is that proportional fonts can be used without
> breaking vertical alignment, and obviously this advantage is invalid
> in a monospaced console.
I'm not fussed about proportional fonts, I'm interested
--- Nick Gravgaard <[EMAIL PROTECTED]> wrote:
> On 20/10/06, Peter Hodge <[EMAIL PROTECTED]> wrote:
> > > I don't think so - just the GTK version. One of the advantages of the
> > > elastic tabstop system is that proportional fonts can be used without
I think it is because you may have a copy of the plugin in $VIMRUNTIME as well
as in your .vim folder. In this way, your .vim copy is sourced first (well,
according to 'rtp'), sets the g:plugin_name variable and when the $VIMRUNTIME
plugins are sourced, and it sees the variable and prevents loadin
--- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> I figured that it was easier to add items to a cluster using
> containedin= for a syntax definition I'm writing, but it seems that
> one can't do it that way. Is there a reason for this, or is it an
> oversight? Can we add this to the todo? I've
--- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> On 10/25/06, Peter Hodge <[EMAIL PROTECTED]> wrote:
>
> > --- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
>
> > > I figured that it was easier to add items to a cluster using
> > > containedin
--- Nick Gravgaard <[EMAIL PROTECTED]> wrote:
> Hi Zdenek,
>
> On 30/10/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> >
> > Hi, Nick,
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Nick Gravgaard
> > > Sent: 19 October 2006 13:42
--- ÐикÑоѬ ÐaожђÑ&аѬов <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm working on a syntax file for .edc files. The problem before me is
> that I want to use a different syntax file for a "script" part. I've
> created the syntax file for the script syntax, and I've read how yto use
> "s
--- ÐикÑÐ¾Ñ ÐожÑÑ
аÑов <[EMAIL PROTECTED]> wrote:
> Ð ÑÑ, 2006-11-01 в 10:53 +1100, Peter Hodge напиÑа:
> > --- ÃøúÃþì ÃaþöÃÃ&ðìþò
> <[EMAIL PROTECTED]> wrote:
> >
> > > Hello,
> > >
wrote:
> Ð ÑÑ, 2006-11-01 в 23:26 +1100, Peter Hodge напиÑа:
> > --- ÃâøúÃâþÃ⬠ÚþöÃÆÃâ¦Ã°Ãâ¬Ã¾Ã²
> <[EMAIL PROTECTED]> wrote:
> >
> > > Ãâ ÃÃâ¬, 2006-11-01 ò 10:53 +1100, Peter Hodge
> ýðÿøÃÃ
Hello,
I agree, it would be great if the popup-menu could be optimized. One of the
best features of Vim is that is fast enough to keep up with my keystrokes (many
editors will begin to 'lag' when given commands too rapidly, and I have to stop
and wait for them). I often have to slacken my pace w
I would find this feature very useful as well.
+1
regards,
Peter
--- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> I'm a firm believer in the nextgroup directive for defining syntaxes.
> It allows you to define grammars, which I really enjoy doing.
> However, one problem is that many languages a
Hello Yakov,
Couldn't you hook into the FileChangedShell autocmd event and merge the changes
into your buffer from there? You can also handle the swap file message with
SwapExists event.
regards,
Peter
--- Yakov Lerner <[EMAIL PROTECTED]> wrote:
> Hello Bram,
> Is it possible to add this item
--- Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> On 4/23/07, Yakov Lerner <[EMAIL PROTECTED]> wrote:
> > wish: allow a: in the function definition line:
> > function foo(a:line1, a:line2)
> > This is currently not allowed. But it seems logical to allow it.
>
> Why should it be? Extra typi
--- "Larson, David" <[EMAIL PROTECTED]> wrote:
> I often need to replace parameter text and usually try to remember the
> text object that selects the "inner parameter", only to come up short
> since that type isn't defined. It seems natural to have a "parameter"
> text object, where it would act
38 matches
Mail list logo
