On Tue, 5 Sep 2006, Peter Hodge wrote:
> Hello Jorge,
>
> The problem is solved if you change this line:
>
> 768 sub reloadlist{
>
> to this:
>
> 768 sub reloadlist {
>
> It looks as though it is a bug in the perl syntax file. You should send the
> maintainer an email with your perl code
On Tue, 5 Sep 2006, A.J.Mechelynck wrote:
>
> The gentoo package managing system need not be aware of your own-compiled Vim,
> any more that my SuSE package managing system is aware of my Vim 7.0.83 (e.g.,
> it won't list it if I do "rpm -qa |grep vim").
>
But I suppose I would need to recompile
Hello Luis,
* On Thu, Aug 31, 2006 at 02:31:18PM -0300, Luis A. Florit <[EMAIL PROTECTED]>
wrote:
> I use Vim and Quickfix to compile C++ programs. I have set
>
> let &makeprg='g++ -o %< %'
>
> as the compiler. My problem is that while compiling, vim goes to
> the console, distracti
--- "A.J.Mechelynck" <[EMAIL PROTECTED]> wrote:
>
> It doesn't. After pasting into an empty buffer via the clipboard,
> block-deleting the column of numbers (from the left margin up to, but
> not including, the s in "sub" at top and the last } at bottom) and
> setting 'filetype' to perl, I see
Hello Jorge,
The problem is solved if you change this line:
768 sub reloadlist{
to this:
768 sub reloadlist {
It looks as though it is a bug in the perl syntax file. You should send the
maintainer an email with your perl code snippet, and he should be able to fix
it. It probably never ev
Jorge Almeida wrote:
On Mon, 4 Sep 2006, A.J.Mechelynck wrote:
I don't know about gentoo, but packaged distributions are always several steps
behind the "real world". The 66 patches between 7.0.17 and 7.0.83 don't make
the latter "bleeding-edge" and the former "stable"; rather, they make the
lat
On Mon, 4 Sep 2006, A.J.Mechelynck wrote:
>
> I don't know about gentoo, but packaged distributions are always several steps
> behind the "real world". The 66 patches between 7.0.17 and 7.0.83 don't make
> the latter "bleeding-edge" and the former "stable"; rather, they make the
> latter "up-to-da
Silent1 wrote:
[...]
Lastly when you get the list of suggestions, what are the different
keys you can press to cancel the drop down (I've been pressing escape
but then I'm out of insert mode and the suggestion i was on has been
filled in my code). I remember vim's help had the list of keys but i
Jorge Almeida wrote:
On Mon, 4 Sep 2006, A.J.Mechelynck wrote:
I already downgraded to 6.4. Vim is just not a package I can afford to
do without...
Of course I hope to be able to upgrade someday.
There are several things you can do, independently of each other:
- Upgrade to 7.0.083
Not a good
Hi all,
with vim7's omni-completion how do you call/get functions/variables
relating to a specific class?
$object = new HTML_QuickForm();
$object->
And then after you type -> how do i call for completions only relating
to the HTML_QuickForm class? I've tried the patch for ctags for PHP5
but my r
On Mon, 4 Sep 2006, A.J.Mechelynck wrote:
>
I already downgraded to 6.4. Vim is just not a package I can afford to
do without...
Of course I hope to be able to upgrade someday.
> There are several things you can do, independently of each other:
>
> - Upgrade to 7.0.083
Not a good option for me.
Jorge Almeida wrote:
I've upgraded to vim-7.0.17. I don't know which version I had before,
probably 6.4. I run linux (gentoo).
After upgrading, syntax for perl seems to have gone to the trash.
Colours appear chaotic and pressing 'o' in normal mode opens a new line
but without the proper identatio
On Mon, 4 Sep 2006, Mikolaj Machowski wrote:
>
> For syntax: you probably have some personalized syntax files which
> clash with default Vim7 ones. Changes required with spell checking could
> cause that effect. Check your .vim directory (and .vimrc file) and
> remove/comment all your definitions
Dnia poniedziałek, 4 września 2006 16:44, Jorge Almeida napisał:
> I've upgraded to vim-7.0.17. I don't know which version I had before,
> probably 6.4. I run linux (gentoo).
> After upgrading, syntax for perl seems to have gone to the trash.
> Colours appear chaotic and pressing 'o' in normal mode
I've upgraded to vim-7.0.17. I don't know which version I had before,
probably 6.4. I run linux (gentoo).
After upgrading, syntax for perl seems to have gone to the trash.
Colours appear chaotic and pressing 'o' in normal mode opens a new line
but without the proper identation. How can such a thing
On 9/4/06, Jochen Baier <[EMAIL PROTECTED]> wrote:
Hi,
with scrolloff=999 the cursor is in the middle of the
window, but not on the top or end of a file (or small file).
Is it possible to have it always in the middle of the window
? maybe with adding '~' above and below of the text.
At end of
Just tried your new version lookupfile plugin, it can now works in
case-insensitive mode!
Thanks everybody!
Eddy
2006/9/3, Hari Krishna Dara <[EMAIL PROTECTED]>:
On Sat, 2 Sep 2006 at 10:25pm, Hari Krishna Dara wrote:
>
> On Fri, 1 Sep 2006 at 11:19pm, Eddy Zhao wrote:
>
> > Sorry, forget to
Hi,
with scrolloff=999 the cursor is in the middle of the
window, but not on the top or end of a file (or small file).
Is it possible to have it always in the middle of the window
? maybe with adding '~' above and below of the text.
thanks for hints,
jochen
Hello,
Post from comp.editors:
--
From: "Sascha T." <[EMAIL PROTECTED]>
Newsgroups: comp.editors
Subject: Re: The vim and emacs wars
Date: 3 Sep 2006 16:21:41 -0700
I've been using Emacs eversince - for something like ten years, I
19 matches
Mail list logo
