On Tue, 2 Jan 2007, A.J.Mechelynck wrote:
see my HowTo page for Unix/Linux:
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
See also
: help if_perl.txt
: help if_cscop.txt
Configuring with --enable-perlinterp will (if it succeeds) build a Vim
executable with +perl
could be catched by the parent script readwithvim.
Any idea?
--
Jorge Almeida
On Wed, 6 Sep 2006, Yakov Lerner wrote:
Are you on Windows ?
No way!
On unix/linux, it's dubious you would lose
viminfo contents (that' where cursor positions come from)
when upgrading vim. I upgrade vim often, and I never lose
cursor positions (linux).
Well, I did more than once, but I
On Wed, 6 Sep 2006, Yakov Lerner wrote:
This is probably what's causing you problems, *not* the vim
updates. There is no way that vim update would overwrite the
~/.viminfo file.
You're right. I'll use session files, rather than change the viminfo
limit.
Thank you.
Jorge
On Thu, 7 Sep 2006, A.J.Mechelynck wrote:
To do something when closing down, place it in an autocommand for the VimLeave
autocommand (as above). To do it during startup, place it in your vimrc. To do
it at the cery end of startup, put it in an autocommand dor the VimEnter
autocommand. And
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 vim
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 snippet,
On Tue, 5 Sep 2006, Peter Hodge wrote:
Well, there was a bug in the older syntax file I used (the one from 2005), but
the newer syntax file I downloaded is fine. If you don't want to put the new
syntax file in your home directory (~/.vim/syntax/perl.vim), you can also put
it in
On Tue, 5 Sep 2006, A.J.Mechelynck wrote:
Jorge Almeida wrote:
On Tue, 5 Sep 2006, Peter Hodge wrote:
Best regards,
Tony.
Thanks again for your help.
Regards,
Jorge
such a thing happen?
This doesn't seem vim anymore.
What can I do?
--
Jorge Almeida
for perl files. Later you can
reintroduce them carefully.
No, no personalized syntax files for perl. Only a few mappings, which
still work...
Google shows there are other people affected, but no solution...
Thanks.
--
Jorge Almeida
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.
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-date and the
stdin...
What version of Vim are you using?
:version
VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Nov 16 2005 01:53:08)
(...)
OS is linux (gentoo), terminal is Konsole (from KDE), shell is bash.
--
Jorge Almeida
On Tue, 13 Jun 2006, John Love-Jensen wrote:
Hi Jorge,
Vim does its job, and after quitting vim I get:
Actually, you are getting the Vim: Reading from stdin... first, and then Vim
does it's job.
When Vim quits, it restores the screen (available in some termcaps), which
includes the prior
15 matches
Mail list logo