I'd like to before :sourc'ing a file to execute
one of my scripts (always the same).
I though the autocmd 'SourcePre' event will
help nut I can't get it work the way I'd needed it:
As a first test I did:
:au SourcePre *.vim let g:sfile=afile
then amatch (I know sfile will not
work
Try expanding it.
au SourcePre *.vim echomsg afile= . expand(afile)
au SourcePre *.vim let g:sfile = afile
On 5/26/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
I'd like to before :sourc'ing a file to execute
one of my scripts (always the same).
I though the autocmd 'SourcePre' event will
help
On 5/26/06, Eric Arnold [EMAIL PROTECTED] wrote:
Try expanding it.
au SourcePre *.vim echomsg afile= . expand(afile)
au SourcePre *.vim let @a = afile
au SourcePre *.vim let @a = expand(afile )
On 5/26/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
I'd like to before :sourc'ing a file to
-Original Message-
From: Eric Arnold [mailto:[EMAIL PROTECTED]
Sent: 26 May 2006 16:07
To: Zdenek Sekera
Cc: vim-dev@vim.org
Subject: Re: source, runtime and all that
On 5/26/06, Eric Arnold [EMAIL PROTECTED] wrote:
Try expanding it.
au SourcePre *.vim echomsg afile= .
Zdenek Sekera wrote:
I also thought 'runtime' is somehow equivalent
to :source, except it is smart enough
to use 'runtimepath'. Using the same test above
(':runtime test.vim') I found this does *not*
fire up the autocmd while :source does.
Is this intentional or can it be considered a bug?
I got my balloon function to do WEB lookups of word under mouse,
on wiki/google/dictionary via python.
However for couple of issues I am stuck with (any help appreciated):
1. The gvim freezes (cursor stop blinking for 3 seconds) while
python is doing web lookups. Can I run this lookup as a
On 5/26/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
-Original Message-
From: Charles E Campbell Jr [mailto:[EMAIL PROTECTED]
Sent: 26 May 2006 16:19
To: Zdenek Sekera
Cc: vim-dev@vim.org
Subject: Re: source, runtime and all that
Zdenek Sekera wrote:
I also thought 'runtime' is
On 5/25/06, William O'Higgins Witteman [EMAIL PROTECTED] wrote:
On Thu, May 25, 2006 at 03:13:45PM -0400, James Vega wrote:
Aha! You have spotted the problem. I have both vim-perl and vim-python
installed, and even though they have the same priority, the system is
defaulting to vim.python.
On Fri, May 26, 2006 at 11:52:42AM +0200, Meino Christian Cramer wrote:
Please ignore...
If you're going to send test messages at least put in something amusing
or interesting for people to read. Something like the following (a
fortune that turned up a few days ago; anyone who's used Oracle --
Hi all,
The problem I'm having is I'll open all folds in a buffer, switch
buffers, go back to the original and all folds are closed again. Is
there a way to stop this? ie Vim remembers the 'fold state' of the
buffer when I return to it? So if folds were open when I left they'll
be open when I
Dnia piątek, 26 maja 2006 03:28, David Purton napisał:
Any suggestions? It kind of looks like a bug, but maybe I'm missing
something obvious.
Maybe you have some custom highlighting definitions for HTML? Remove
them and check once more.
m.
On Fri, May 26, 2006 at 07:42:11AM -0500, Tim Chase wrote:
(c)h1Headline/h1
My cursor is denoted by (c). How can I most quickly jump to the start
of the Headline word?
Pressing w or e isn't any good, I still have to press at least three
times. Not nice, almost as bad as cursor keys.
:help motion.txt
and then you will be on your way to joining the ranks of vim experts.
Some of us are just rank ;)
But yes, Vim's multitude of ways for jumping around a document
quickly are one of the hallmarks of why folks who learn it well
seldom leave for another editor.
-tim
Mark Woodward wrote:
Hi all,
The problem I'm having is I'll open all folds in a buffer, switch
buffers, go back to the original and all folds are closed again. Is
there a way to stop this? ie Vim remembers the 'fold state' of the
buffer when I return to it? So if folds were open when I left
Hi All:
I apologize for breaking the thread. I just share dc's problem about
syntax highlighting in html and build-in spellchecker: when I edit a
html file spell checking doesn't work, but as soon as I do
syntax off
the spell check works again! Any idea how to remedy it? I compiled vim 7
from
Hi all:
I love the new spell check features. I usually write in English, which
is why I set my spellchecker to en-us. However I sometimes write in
Chinese, which AFAIK has no vim spell checker. So every time I write
something it will underline it. Of course I can manually write
:set nospell
to
(I missed part of this thread, so sorry if this has already been mentioned).
Have you checked for mode lines at the top or bottom of the files
which set fold options? If there aren't any which might be confusing
you, you could consider adding your own mode lines to have the folding
appropriate
I'm getting the same behavior under the same conditions on both WinXP
and Linux (Ubuntu 5.10), with standard installations of Vim 7 (i.e.,
without compile-time or command-line modifications, or modifications
to .*vimrc's). I've delved a bit deeper (though unsystematically and
unscientifically)
Consider this: I'm editing the HTML:
(c)h1Headline/h1
My cursor is denoted by (c). How can I most quickly jump to the start
of the Headline word?
Pressing w or e isn't any good, I still have to press at least three
times. Not nice, almost as bad as cursor keys.
Dunno how arbitrary your input
Jiang Qian wrote:
Hi All:
I apologize for breaking the thread. I just share dc's problem about
syntax highlighting in html and build-in spellchecker: when I edit a
html file spell checking doesn't work, but as soon as I do
syntax off
the spell check works again! Any idea how to remedy it? I
Hi,
Need help, after so many time I still can't fix this.
http://permalink.gmane.org/gmane.editors.vim/22144
The problem is that any ! command returns, for example !!dir returns (after a
couple seconds):
E485: Can't read file x.tmp
If I do :!dir a console opens and says:
Jiang Qian wrote:
Hi all:
I love the new spell check features. I usually write in English, which
is why I set my spellchecker to en-us. However I sometimes write in
Chinese, which AFAIK has no vim spell checker. So every time I write
something it will underline it. Of course I can manually
Oops. I inadvertently added a real signature delimiter. I meant:
Jiang Qian wrote:
Hi all:
I love the new spell check features. I usually write in English, which
is why I set my spellchecker to en-us. However I sometimes write in
Chinese, which AFAIK has no vim spell checker. So every time I
Thanks! I'm working on a deadline today but will see if I can integrate
this and make things work on Monday.
Max
-Original Message-
From: Eric Arnold [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 5:57 AM
To: Max Dyckhoff
Cc: vim@vim.org
Subject: Re: Working directory
On Fri, 26 May 2006, Tim Chase wrote:
[snip]
I've also had times where, while I regularly use the fH varient of matters
to go forward to the first character in the tag, sometimes I get stung, as in
[c] lilook here!/li
(with the cursor on [c]). Using fl (eff ell) in attempt to jump to the
Then again, some might argue that Vim is about thinking before
making a calculated move..
Vim...the chess of editors :)
Vim is an artistic blend of the two. Basic stuff becomes second
nature so that it just comes flying out of the fingers. The more
complex stuff takes a moment of thought
Gerald Lai wrote:
[...]
Then again, some might argue that Vim is about thinking before making a
calculated move..
--
Gerald
IMHO, Vim is about both editing files any way you might think of (and
possibly thinking before you do it), and having (or possibly letting you
make) simple keystrokes
Jansen of Lorkeers, Richard wrote:
I have a general question concerning installation of VIM on a OpenVMS
systems. Who has experience with the installation of the software?
Its been a long time since I've used VMS. So I have no recent
experience in the installing vim under OpenVMS. Once
Does anybody know how to get gvim to really print the expression
result from --remote-expr to stdout, as it says in the docs. I always
get an error popup with the results (although the expression wasn't
a failure, the error popup just seems to be the default).
Eric Arnold wrote:
Does anybody know how to get gvim to really print the expression
result from --remote-expr to stdout, as it says in the docs. I always
get an error popup with the results (although the expression wasn't
a failure, the error popup just seems to be the default).
Use vim (the
On Fri, 26 May 2006, Juan Lanus wrote:
[snip]
The problem is that any ! command returns, for example !!dir returns (after a
couple seconds):
E485: Can't read file x.tmp
If I do :!dir a console opens and says:
C:\WINNT\system32\CMD.EXE /c dir
shell returned -1
Hit any key to close
On 5/26/06, Gerald Lai [EMAIL PROTECTED] wrote:
My first assessment would be to check if
C:\WINNT\system32\CMD.EXE
does exist. Does it?
Yes it does. I'm not at that PC now, but I assume it's there because I
can open DOS windows with the usual shortcut that points to
If you have a file in _mixed_ language (part of the file in English
and another part in Chinese), then I don't know if (or how) Vim can
spell-check only the English paragraphs. It might be as simple as
excluding anything in the Chinese part of the Unicode range from
spell-checking
On Fri, 26 May 2006 07:58:22 -0600
Eric Arnold [EMAIL PROTECTED] wrote:
(I missed part of this thread, so sorry if this has already been
mentioned).
Have you checked for mode lines at the top or bottom of the files
which set fold options? If there aren't any which might be confusing
you,
On Fri, 26 May 2006, Juan Lanus wrote:
On 5/26/06, Gerald Lai [EMAIL PROTECTED] wrote:
My first assessment would be to check if
C:\WINNT\system32\CMD.EXE
does exist. Does it?
Yes it does. I'm not at that PC now, but I assume it's there because I
can open DOS windows with the usual shortcut
Juan Lanus wrote:
... when I use the :! syntax a DOS window
containing the error shows.
Issue the : !dir and in the resulting DOS window,
issue the path command. The output will be what this
_particular_ dos window has for the path environment
variable.
Then directly open a
You could check:
if bufnr($) == 1 !bufloaded(1)
this seems to be the case when it's first sourcing .vimrc, anyway.
On 5/26/06, Hari Krishna Dara [EMAIL PROTECTED] wrote:
One of my plugins was using the VimEnter autocommand to initialize some
of the values. The autocommand is added while
OS: Windows2000
VIM version: GVIM 7.0 from www.vim.org
I used ':vimgrep/pattern/j %' to search for a pattern
in current buffer and listed the matches in the quickfix
window. Then I double-clicked the left button of the mouse
on the items in the quickfix window to jump to the
corresponding
38 matches
Mail list logo
