Dnia wtorek, 25 lipca 2006 02:14, Eric Van Dewoestine napisał:
1. We are in /home/mikolaj::
echo findifile(b, 1;)
1/b
You are giving findfile() a relative path to search, so it is
returning a relative result.
Result is the same regardless to path in second argument.
Dnia wtorek, 25 lipca 2006 07:11, A.J.Mechelynck napisał:
I don't see any inconsistency. According to the help, findfile() is
Just like |finddir()|, but find a file instead of a directory. and
finddir() has: When the found directory is below the current directory
a relative path is returned.
On 7/25/06, Mikolaj Machowski [EMAIL PROTECTED] wrote:
Dnia wtorek, 25 lipca 2006 02:14, Eric Van Dewoestine napisał:
1. We are in /home/mikolaj::
echo findifile(b, 1;)
1/b
You are giving findfile() a relative path to search, so it is
returning a relative result.
Benji Fisher wrote:
On Fri, Jul 21, 2006 at 03:31:15PM -0500, mwoehlke wrote:
Is this possible? It just occurred to me that it would be great if there
was a VIM-related program that would 'cat' in color using VIM's
highlighting rules. Is this something that VIM could be made to do via
I noticed recently that vim does not always set 'filetype' to mail
when I edit mutt temporary files, e.g., postponed messages. I
traced the problem to mutt's use of mktemp() with the pattern
muttXX. I don't know about other OSs, but mktemp() on SunOS
5.8 replaces those Xs with characters
On 7/26/06, mwoehlke [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
I noticed recently that vim does not always set 'filetype' to mail
when I edit mutt temporary files, e.g., postponed messages. I
traced the problem to mutt's use of mktemp() with the pattern
muttXX. I don't know about
Yakov Lerner wrote:
On 7/26/06, mwoehlke [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
I noticed recently that vim does not always set 'filetype' to mail
when I edit mutt temporary files, e.g., postponed messages. I
traced the problem to mutt's use of mktemp() with the pattern
muttXX.
On 7/25/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 7/23/06, Nikolai Weibull [EMAIL PROTECTED] wrote:
On 7/23/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 7/23/06, Nikolai Weibull [EMAIL PROTECTED] wrote:
When output from for example :echon comes within 12 columns of the
right hand
Dnia wtorek, 25 lipca 2006 16:50, Eric Van Dewoestine napisał:
So, the results are still consistent with the documented behavior.
But not internally consistent. But OK - it is documented behaviour.
Regarding ';', the docs imply that it forces a search upwards, but
should probably state that
Hello Vim Developers,
I was timing the startup process by stepping though what I
think Gvim does (on Win XP Pro with 7.0.42).
gvim -u NONE -N
That starts up without _vimrc or _gvimrc or plugins and sets
nocp.
:so $vim\_vimrc
worked fine.
:so $vim\_gvimrc
also worked fine.
Bill McCarthy wrote:
Hello Vim Developers,
I was timing the startup process by stepping though what I
think Gvim does (on Win XP Pro with 7.0.42).
gvim -u NONE -N
That starts up without _vimrc or _gvimrc or plugins and sets
nocp.
:so $vim\_vimrc
worked fine.
:so $vim\_gvimrc
11 matches
Mail list logo
