Hi all,
On Thu, 2007-03-15 at 09:41 -0500, Brian Neal wrote:
Hi -
I just downloaded the non-Cream pre-built Vim for Windows (version
7.0.215). The go up command (-) in the Netrw plugin no longer seems
to work. Neither the - command or putting the cursor over the ../ and
hitting return does
Hi,
I'm using vim7.0 on CentOS 4.3.
In my .vimrc, I add a colorscheme command:
colorscheme desert
When I source my session file, I found all the highlight groups defined in
plugins are cleared. Then I turn on verbose and sourced the session file
again, and found that vim firstly find desert
Let me rephrase my question:
Is it possible to display the omni-completion menu in normal mode, eg
from a function called in normal mode?
I don't want to set omnifunc or completefunc for this.
Regards,
Thomas.
RE: Java syntax folding question
I didn't find the syntax scripts worked well for me with java, so I use this
instead.
zz collapses to function definitions
za completely unfolds a function
Set folding stuff
:set fmr={,}
:set fdm=marker
:map silent zz :set foldlevel=1^M1G
:map silent za :set
From: Mark Woodward markonlinux internode on.net, Fri, March 16, 2007 5:50 am
On Thu, 2007-03-15 at 09:41 -0500, Brian Neal wrote:
I just downloaded the non-Cream pre-built Vim for Windows (version
7.0.215). The go up command (-) in the Netrw plugin no longer
seems to work. Neither the -
What is the latest version of netrw? I am have version v108k. I am getting an
error of undefined tfile variable. Can someone help me with this?
TIA
Michael D. Phillips - A computer science enthusiast
I do not hate Windows, I just like the alternatives better.
Linux is my primary choice.
Hi,
When opening a file, is there a way to tell vim which name to use for
the swapfile?
I'm writing a little vim config file to edit a CMS' content in a DB.
Each page has a parts named 'body', which the script makes available
through
:Radiant edit pages/Home Page/body
or, for another page:
Hello,
I wrote a plugin that displays some information in the commandline using
the echon command when entering a buffer. This works fine, unless a
buffer is entered for the second time and the 'set hidden' option is
enabled - in this case vim overwrites the command line with info like:
Brian Neal wrote:
I just downloaded the non-Cream pre-built Vim for Windows (version
7.0.215). The go up command (-) in the Netrw plugin no longer seems
to work. Neither the - command or putting the cursor over the ../ and
hitting return does anything anymore. Any ideas? Thanks.
Please try
From: Charles E Campbell Jr, Fri, March 16, 2007 12:17 pm
Please try netrw v108l which I just put on my website:
http://mysite.verizon.net/astronaut/vim/index.html#NETRW
Unfortunately these appear distributed in vimball format only.
It is unrealistic to expect users to fire off a home-brewed
Isn't a vimball just another archive? It seems, according to the
vimball help file that it's just a bunch of inert files. It doesn't
really run anything... Maybe I am wrong, though.
-fREW
On 3/16/07, Steve Hall [EMAIL PROTECTED] wrote:
From: Charles E Campbell Jr, Fri, March 16, 2007 12:17
On 3/16/07, John north [EMAIL PROTECTED] wrote:
RE: Java syntax folding question
I didn't find the syntax scripts worked well for me with java, so I use this
instead.
zz collapses to function definitions
za completely unfolds a function
Set folding stuff
:set fmr={,}
:set fdm=marker
:map
Thomas wrote:
Let me rephrase my question:
Is it possible to display the omni-completion menu in normal mode, eg
from a function called in normal mode?
I don't want to set omnifunc or completefunc for this.
No, the omni-completion menu only works in Insert mode.
Using the popup menu
John Wiersba wrote:
Thanks, Tony, for your reply.
My pleasure. I did see this present post of yours on the list; the reason I
didn't answer is I had nothing significant to contribute.
As far as I can tell everything is set up to give case-sensitive
globbing. Bash does case-sensitive
Hi,
Can somebody let me know how to show the current value of path?
Thanks,
Peng
On 16-Mar-2007 20:59, A.J.Mechelynck wrote:
As far as I can tell everything is set up to give case-sensitive
globbing. Bash does case-sensitive globbing at the command line and
in a simple script
#!/bin/bash
echo file*
Do you believe vim is shelling out to do globbing under cygwin,
Steve Hall wrote:
From: Charles E Campbell Jr, Fri, March 16, 2007 12:17 pm
Please try netrw v108l which I just put on my website:
http://mysite.verizon.net/astronaut/vim/index.html#NETRW
Unfortunately these appear distributed in vimball format only.
It is unrealistic to expect users to fire
* Peng Yu [2007.03.16 16:30]:
Can somebody let me know how to show the current
value of path?
:set path?
--
JR
Peng Yu wrote the following on 03/16/2007 01:16 PM:
Hi,
Can somebody let me know how to show the current value of path?
Thanks,
Peng
Inside or outside of vim? Unix/Linux or Windows? Programatically in
vim or just as a command?
Try:
:!echo $PATH
inside vim on the command line on
Raphael Bauduin wrote:
Hi,
When opening a file, is there a way to tell vim which name to use for
the swapfile?
I'm writing a little vim config file to edit a CMS' content in a DB.
Each page has a parts named 'body', which the script makes available
through
:Radiant edit pages/Home Page/body
Found this amusing: a while back, for some open web survey of
cast your vote for your favorite software, I submitted Vim.
There was a mandatory field for the company that produced it,
so I put in Bram's name.
Well, a year or so later, somehow that combination of my name and
Bram as a business
On 2007-03-16, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Here is how to avoid modifying system files: Since there is a test at the
start of the netrw scripts to avoid double sourcing, you can test them by
unvimballing them under $VIM/vimfiles, $HOME/vimfiles or $HOME/.vim,
without removing
On 2007-03-16, Richard England [EMAIL PROTECTED] wrote:
Peng Yu wrote the following on 03/16/2007 01:16 PM:
Hi,
Can somebody let me know how to show the current value of path?
Thanks,
Peng
Inside or outside of vim? Unix/Linux or Windows? Programatically in
vim or just as a
Peng Yu wrote:
Hi,
Can somebody let me know how to show the current value of path?
Thanks,
Peng
Which path? There are two of them, and they have nothing in common beside
the name.
There is a PATH environment variable, used by the shell to search for
executables, which can be shown as
Michael,
Thanks for your reply. You're right -- disabling the CASE_INSENSITIVE_FILENAME
compile-time option changes this behavior. However, I disagree that case
insensitivity is the correct behavior. Cygwin is perfectly capable of
supporting case-sensitive globbing behavior and unix tools,
On Fri, 2007-03-16 at 21:33 +0100, A.J.Mechelynck wrote:
Steve Hall wrote:
Unfortunately these appear distributed in vimball format only.
The vimball format is actually a text format.
No, vimball is an amalgamation of text files, but it is NOT intended
to be edited in situ like a text
Gary Johnson wrote:
On 2007-03-16, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Here is how to avoid modifying system files: Since there is a test at the
start of the netrw scripts to avoid double sourcing, you can test them by
unvimballing them under $VIM/vimfiles, $HOME/vimfiles or $HOME/.vim,
On Fri, 2007-03-16 at 13:26 -0500, fREW wrote:
Isn't a vimball just another archive? It seems, according to the
vimball help file that it's just a bunch of inert files. It doesn't
really run anything... Maybe I am wrong, though.
When you use :source filename, Vim executes the code in
Steve Hall wrote:
On Fri, 2007-03-16 at 21:33 +0100, A.J.Mechelynck wrote:
Steve Hall wrote:
Unfortunately these appear distributed in vimball format only.
The vimball format is actually a text format.
No, vimball is an amalgamation of text files, but it is NOT intended
to be edited in situ
Steve Hall wrote:
On Fri, 2007-03-16 at 13:26 -0500, fREW wrote:
Isn't a vimball just another archive? It seems, according to the
vimball help file that it's just a bunch of inert files. It doesn't
really run anything... Maybe I am wrong, though.
When you use :source filename, Vim executes
Tim Chase wrote:
Found this amusing: a while back, for some open web survey of
cast your vote for your favorite software, I submitted Vim.
There was a mandatory field for the company that produced it,
so I put in Bram's name.
Well, a year or so later, somehow that combination of my name and
On 16-Mar-2007 23:13, John Wiersba wrote:
Thanks for your reply. You're right -- disabling the CASE_INSENSITIVE_FILENAME
compile-time option changes this behavior. However, I disagree that case
insensitivity is the correct behavior. Cygwin is perfectly capable of
supporting case-sensitive
On Sat, 2007-03-17 at 00:03 +0100, A.J.Mechelynck wrote:
Sure. But you don't _have_ to source it. Since 15 June 2006, you can
use instead
:UseVimball /temp
Tony, you convinced me to try again. But I feel vindicated, again I
experienced the same kind of issues I always seem to have.
Steve Hall wrote:
On Sat, 2007-03-17 at 00:03 +0100, A.J.Mechelynck wrote:
Sure. But you don't _have_ to source it. Since 15 June 2006, you can
use instead
:UseVimball /temp
Tony, you convinced me to try again. But I feel vindicated, again I
experienced the same kind of issues I
Hi,
A multithreaded matcher might be useful to vim but do we have a
need for
fuzzy matching ?
vim doesn't use threads at the moment, and Bram seems to be reluctant
to include threads for various reasons.
Bye,
Nico
On 3/16/07, Asiri Rathnayake [EMAIL PROTECTED] wrote:
On Fri, 2007-03-16 at 10:44 +0100, Nicolas Weber wrote:
A multithreaded matcher might be useful to vim but do we have a
need for
fuzzy matching ?
vim doesn't use threads at the moment, and Bram seems to be reluctant
to include
On Fri, 2007-03-16 at 12:03 +0100, Nikolai Weibull wrote:
On 3/16/07, Asiri Rathnayake [EMAIL PROTECTED] wrote:
On Fri, 2007-03-16 at 10:44 +0100, Nicolas Weber wrote:
A multithreaded matcher might be useful to vim but do we have a
need for
fuzzy matching ?
vim doesn't use
On Friday 16 March 2007 01:54, A.J.Mechelynck wrote:
Josh wrote:
any ideas about why support was dropped for kvim.
My guess is: no one at kde wanted to go on doing it.
Maybe they ran into too
many snags and didn't think it was worth it.
The KVim development team found some
Hello!
During compilation of Vim 7.0 under AIX (5.1 or 5.2) I get the next error:
message.c, line 4180.1: 1506-191 (E) The character # is not a valid C
source character.
message.c, line 4180.2: 1506-046 (S) Syntax error.
message.c, line 4182.1: 1506-191 (E) The character # is not a valid C
My problem with the quoteplus register is solved. The
reason was, that the xorg-X11-devel-package wasn`t
installed and therefore no xterm_clipboard ...
possible.
My be, that I installed this package (and
neccessaries) on my former system suse 10.1 earlier is
other reasons, and therefore not had
Nikolai Weibull wrote:
On 3/15/07, Asiri Rathnayake [EMAIL PROTECTED] wrote:
Hi all,
I went through the above idea presented for google summer of code 2007
and found it interesting. In my opinion, incorporating Thompson NFA into
regexp from the ground up is pretty cool. I also went
On 3/16/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
I actually wrote a simplification of his library, removing the
approximate matching stuff, as part of my master's, which is well
documented. I still haven't had time to put up the PDF, though.
Interesting.
I did confirm that this behavior has changed between vim 6.4 and vim 7.0 (under
cygwin) by rebuilding vim 6.4 from source. In vim 6.4, :e file* is
case-sensitive; in vim 7.0 it is not. I will file a bug report if I can't find
a switch to turn this back to the vim 6.4 behavior.
-
Oleg Goodyckov wrote:
During compilation of Vim 7.0 under AIX (5.1 or 5.2) I get the next error:
message.c, line 4180.1: 1506-191 (E) The character # is not a valid C
source character.
message.c, line 4180.2: 1506-046 (S) Syntax error.
message.c, line 4182.1: 1506-191 (E) The character #
On Fri, 2007-03-16 at 14:08 +0100, Martin Stubenschrott wrote:
On Thu, Mar 15, 2007 at 11:28:45PM +0530, Asiri Rathnayake wrote:
Hi all,
I went through the above idea presented for google summer of code 2007
and found it interesting. In my opinion, incorporating Thompson NFA into
45 matches
Mail list logo
