Yakov Lerner wrote:
What are these dozens of bounce emails from [EMAIL PROTECTED] ?
Is it just me ? I got suddenly not one but 18 of them, and it's not
first time.
Yakov
Not seeing any here, but they could have been filtered out by my
spam daemon. Ever since spammers started cont
Yakov Lerner wrote:
Wrong list ?
Yakov
Oops...sorry;
Must need higher octane coffee...(or sleep)...
sigh,
linda
The manpages for "my" bash's (3.1.11 on Linux and 3.1.17 on cygwin/i686),
under Parameter Expansion, has:
${!prefix*}
[EMAIL PROTECTED]
Expands to the names of variables whose names begin with prefix,
separated by the first character of the IFS special variable.
---
From t
A.J.Mechelynck wrote:
Linda W wrote:
Is there some other option to tell Vim not to use the DOS/Windows
Shell options to non-DOS/Win shells? :-)
I searched ...
see
:help 'shell'
:help 'shellcmdflag'
:help 'shellpipe'
:help 'shellquot
I changed my COMSPEC on win32 to C:\bin\bash.exe.
In vi, when I use the "!" to execute a command on Windows,
like "ls", it tried to execute it with:
C:\bin\bash /c ls
where ^^--- is an argument to the DOS/Windows Shell, but doesn't
work for for bash.
Is there some other option to tell V
I couldn't figure out what flag to use to turn on the "very magic"
flag by default. Could someone maybe tell me where I should have
looked to find it? :-)
Thanks,
Linda
A.J.Mechelynck wrote:
For a single file:
:e ++ff=dos foobar.txt
:setlocal ff=unix
:w
For all *.txt files in the current directory:
:set fileformats=dos
:args *.txt
:set nomore
:argdo setl ff=unix | w
:set more " assuming this is your preferred setting
Seems to be a bug in the "diff.exe" program included
in the VIMRUNTIME dir in the Win32-GUI distribution.
It compares files with CRLF endings as "identical" with
the same text & "LF" endings.
Note -- I'm not using any of the "ignore white space", or ignore
CR's at the end of the line.
I was try
A.J.Mechelynck wrote:
As has been repeatedly said this past week, this requires a viminfo
setting and an autocommand.
Maybe as has not been said. I have all that.
The autocommand is defined near line 70 of $VIMRUNTIME/vimrc_example.vim
so if you source the latter, you should hav
A.J.Mechelynck wrote:
As has been repeatedly said this past week, this requires a viminfo
setting and an autocommand.
Has it been said that it didn't require these in the past? I.e. --
has this requirement changed since 64?
The autocommand is defined near line 70 of $VIMRUNTIME/v
A.J.Mechelynck wrote:
when I edit a file, then exit, then re-edit, I'm no longer placed
back at the same location
Is this a bug, or did some value not get properly updated when
we were upgraded to vim7 from vim6? I.e. do I need to change
some setting?
As has been repeatedly said this past wee
Am running under cygwin, where they've updated to vim7.
One of the first problems I'm noticing is that when I edit a file,
then exit, then re-edit, I'm no longer placed back at the location
I was at when I had previously exited.
Is this a bug, or did some value not get properly updated when
we w
I note that Yahoo is blocking (traffic overflow given as reason) the VIM
announcement. Given Yahoo's track record with human rights, maybe it's
time to think about moving the group to another host, like Google?
Sorry, I really don't like yahoo's track record in this area, and I can't
think they'
13 matches
Mail list logo
