Bill McCarthy wrote:
On Sun 23-Sep-07 8:34pm -0600, Dasn wrote:
I've posted on vim_use some days before:
$ vim -c q 'foo ~ foo'
$ vim -c normal '0
E20: Mark not set
Filename contains '~' character which is around with path separators
(i.e. ' ' and ',') has such problem.
And the patch:
check this out buddies. kool website for:
* hacking and anti hacking tricks
* anti hackng tricks.
* registry tweaks
* orkut tricks
* small virus
* computer tricks
and loads of different tricks...
www.realm-of-tricks.blogspot.com
www.registrydecoded.blogspot.com
Bill McCarthy wrote:
On Sun 23-Sep-07 8:34pm -0600, Dasn wrote:
I've posted on vim_use some days before:
$ vim -c q 'foo ~ foo'
$ vim -c normal '0
E20: Mark not set
Filename contains '~' character which is around with path separators
(i.e. ' ' and ',') has such problem.
And
Patch 7.1.117
Problem:Can't check wether Vim was compiled with Gnome. (Tony Mechelynck)
Solution: Add gui_gnome to the has() list.
Files: src/eval.c
*** ../vim-7.1.116/src/eval.c Mon Sep 17 22:19:43 2007
--- src/eval.c Sun Sep 16 19:24:49 2007
***
*** 10879,10884
Suresh Govindachar wrote:
Here's what MicroSoft is up to for console/terminal:
http://www.powershell.com/plus/
Weird that that thing seems to still have only 16 colors!
It is possible to try out PowerShell (a shell, not a
console/terminal) today. Commands in PowerShell do
On Tue 25-Sep-07 5:46am -0600, Bram Moolenaar wrote:
Bill McCarthy wrote:
On Sun 23-Sep-07 8:34pm -0600, Dasn wrote:
I've posted on vim_use some days before:
$ vim -c q 'foo ~ foo'
$ vim -c normal '0
E20: Mark not set
Filename contains '~' character which is around with path
Bram Moolenaar wrote:
Patch 7.1.120
Problem:Can't properly check memory leaks while running tests.
Solution: Add an argument to garbagecollect(). Delete functions and
variables in the test scripts.
Files: runtime/doc/eval.txt, src/eval.c, src/globals.h, src/main.c,
No responses to this bug report... It didn't slip through the cracks,
did it?
In a nutshell: there's apparently a race condition in the TermResponse
autocmd. It fires for normal vim, fires only some of the time with
vimdiff.
Thanks,
Aron
--~--~-~--~~~---~--~~
Bram Moolenaar wrote:
Charles Campbell wrote:
Hello!
I don't seem to have test63.in or test63.ok for some reason. test62.in,
test62.ok, test64.in, and test64.ok are there...
test63 was added in patch 7.1.040.
Hmm -- the vim I've got has a --version with the following initial
Ben Schmidt wrote:
Maybe expand it only if the file name starts with tilde + path separator?
(IIRC, ~user is not expanded on Windows).
Though it could be handy if it were in a few circumstances.
Don't know how easy or otherwise it would be to implement it, though.
The only thing that
Aron Griffis wrote:
No responses to this bug report... It didn't slip through the cracks,
did it?
In a nutshell: there's apparently a race condition in the TermResponse
autocmd. It fires for normal vim, fires only some of the time with
vimdiff.
I almost forgot about this. I'm making a
Patch 7.1.122
Problem:Mac: building Vim.app fails. Using wrong architecture.
Solution: Use line continuation for the gui_bundle dependency. Detect the
system architecture with uname -a.
Files: src/main.aap
*** ../vim-7.1.121/src/main.aap Thu May 10 18:48:19 2007
---
The only thing that requires a little care (IIUC) is to make sure that if the
tilde is followed by a backslash, the latter is a true backslash and not an
escaper backslash for something else than a backslash: in ~\foo, ~ means
$HOME while in ~\ foo it doesn't, and the filename is ~ foo.
13 matches
Mail list logo
