Linda W wrote:
> 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
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
On 26/07/06, Linda W <[EMAIL PROTECTED]> wrote:
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 |
Thank you both for the reply. But when I type ^V010 or ^Vx0a it enters
<00> instead of <0a> (LF). Does anyone know why?
Trent Gamblin wrote:
Thank you both for the reply. But when I type ^V010 or ^Vx0a it enters
<00> instead of <0a> (LF). Does anyone know why?
That is documented under ":help i_CTRL-V_digit", which we both
mentioned. Nulls are represented by linefeeds internally. To enter a
linefeed, break t
Dear All,
Thank you very much for all your responses. I am sorry. My file is a
little different now. It is like following:
1 data_34.dat pre= -7872.11914060 post= -7812.80517600 diff= 59.31396460
2 data_5.dat pre= -7986.76147466 post= -7926.94091800 diff= 59.82055666
3 data_16.dat pre=
On Wed, 2006-07-26 at 15:24 +0200, A.J.Mechelynck wrote:
> That is documented under ":help i_CTRL-V_digit", which we both
> mentioned. Nulls are represented by linefeeds internally. To enter a
> linefeed, break the line.
Sorry, should have read that first. Thanks again!
:%s/\<[a-z]\+\>//gI
another option is to include \C in the regular expression itself:
:%s/\C\<[a-z]\+\>//g
One should be careful about this, as the help states:
:help /\C
Note that 'ignorecase', "\c" and "\C" are not
used for the character classes.
And wh
On Wed, 2006-07-26 at 09:27 +, Xiaoshen Li wrote:
> Dear All,
> Thank you very much for all your responses. I am sorry. My file is a
> little different now. It is like following:
>
> 1 data_34.dat pre= -7872.11914060 post= -7812.80517600 diff= 59.31396460
> 2 data_5.dat pre= -7986.761474
Hi,
Tim Chase wrote:
> > > :%s/\<[a-z]\+\>//gI
> > another option is to include \C in the regular expression itself:
> >
> > :%s/\C\<[a-z]\+\>//g
>
> One should be careful about this, as the help states:
>
> :help /\C
>
>
> Note that 'ignorecase', "\c" and "\C" are not
> use
Xiaoshen Li wrote:
Dear All,
Thank you very much for all your responses. I am sorry. My file is a
little different now. It is like following:
1 data_34.dat pre= -7872.11914060 post= -7812.80517600 diff= 59.31396460
2 data_5.dat pre= -7986.76147466 post= -7926.94091800 diff= 59.82055666
Careful, Tim: UTF-8 is unsuited to binary editing, because you
can't enter a byte >127 by itself in UTF-8.
True enough. I tend not to use UTF-8, so I defer to your far
greater experience/knowledge on the matter.
For doing binary editing in vim (a rare occurance, when I'm not
just using a prope
Tim Chase wrote:
Careful, Tim: UTF-8 is unsuited to binary editing, because you
can't enter a byte >127 by itself in UTF-8.
True enough. I tend not to use UTF-8, so I defer to your far
greater experience/knowledge on the matter.
For doing binary editing in vim (a rare occurance, when I'm not
On Wed, 26 Jul 2006, Xiaoshen Li apparently wrote:
> Thank you very much for all your responses. I am sorry. My file is a
> little different now. It is like following:
> 1 data_34.dat pre= -7872.11914060 post= -7812.80517600 diff= 59.31396460
> 2 data_5.dat pre= -7986.76147466 post= -7926.940
I know you lose some generality with this solution...
:%s/.*\(data_\d*\.dat\).*/\1
but it looks a little easier on the eyes. Any cons
to doing it this way?
On Wed, 26 Jul 2006, Alan G Isaac wrote:
> On Wed, 26 Jul 2006, Xiaoshen Li apparently wrote:
> > Thank you very much for all your response
>> :[EMAIL PROTECTED](\S\+\)[EMAIL PROTECTED]
On Wed, 26 Jul 2006, (MDT) [EMAIL PROTECTED] apparently wrote:
> I know you lose some generality with this solution...
> :%s/.*\(data_\d*\.dat\).*/\1
> but it looks a little easier on the eyes. Any cons
> to doing it this way?
One extra charact
On Wed, 2006-07-26 at 09:04 -0500, Tim Chase wrote:
> For doing binary editing in vim (a rare occurance, when I'm not
> just using a proper hex-editor), I tend to use the xxd that comes
> with the windows version (and is usually available on most Linux
> systems I've used) for transforming into an
Currently I have a couple functions defined that when I do \rc for
example it checks my Perl code. When I run this it opens up a DOS window
to show me the "ok" or "error" message.
How do I get that to show up in the bottom of my window (is that the
command area?).
:Robert
On 7/26/06, Robert Hicks <[EMAIL PROTECTED]> wrote:
Currently I have a couple functions defined that when I do \rc for
example it checks my Perl code. When I run this it opens up a DOS window
to show me the "ok" or "error" message.
How do I get that to show up in the bottom of my window (is that
Yakov Lerner wrote:
On 7/26/06, Robert Hicks <[EMAIL PROTECTED]> wrote:
Currently I have a couple functions defined that when I do \rc for
example it checks my Perl code. When I run this it opens up a DOS window
to show me the "ok" or "error" message.
How do I get that to show up in the bottom
I tried using 'cdpath' on Windows and it seems to be broken, but I
don't know for sure since I've never used it before. From the
Command Prompt I execute
gvim -N -u NONE
Then within gvim,
:set cdpath?
cdpath=,,
:pwd
C:\Documents and Settings\garyjohn
:cd Desktop
Is there a way Vim, when it displays an error and gives me a line number
for me to click on that line number and Vim takes me there?
:Robert
On 7/26/06, Trent Gamblin <[EMAIL PROTECTED]> wrote:
On Wed, 2006-07-26 at 09:04 -0500, Tim Chase wrote:
> For doing binary editing in vim (a rare occurance, when I'm not
> just using a proper hex-editor), I tend to use the xxd that comes
> with the windows version (and is usually available on mo
On 7/26/06, Gary Johnson <[EMAIL PROTECTED]> wrote:
I tried using 'cdpath' on Windows and it seems to be broken, but I
don't know for sure since I've never used it before. From the
Command Prompt I execute
gvim -N -u NONE
Then within gvim,
:set cdpath?
cdpath=,,
:pwd
C:\
On Wed, 2006-07-26 at 21:53 +0300, Yakov Lerner wrote:
> If you add '-p' option to 'xxd' (see man xxd), like this:
> au BufReadPost *.bin if &bin | %!xxd -p
> then you different hex format (without offsets) where
> you can easily add and remove bytes. The
> downside of 'xxd -p' format is,
On Wed 26-Jul-06 1:10am -0600, Linda W wrote:
> 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.
That's the default handling - treat as text.
You
On 2006-07-26, Cory Echols <[EMAIL PROTECTED]> wrote:
> On 7/26/06, Gary Johnson <[EMAIL PROTECTED]> wrote:
> > I tried using 'cdpath' on Windows and it seems to be broken, but I
> > don't know for sure since I've never used it before. From the
> > Command Prompt I execute
> >
> > gvim -N -u N
Hello Vim List,
I just tried out Chip's AsNeeded script. After installing
the VBA, I copied everything from \vim\vimfiles\plugin\
(except scripts, like netrwPlugin, which also exist in
$vimruntime\plugin) to \vim\vimfiles\AsNeeded\.
I then tried it out on one of the same author's scripts:
:
Hello,
I run vim on Solaris, Linux and Cygwin (actually I use only the win32
native version of vim, generally the one compiled by Tony).
And I have one set of scripts for all systems.
* On Tue, Jul 25, 2006 at 12:14:43AM -0700, Gary Johnson <[EMAIL PROTECTED]>
wrote:
> To that end, I have done
Hello,
I could not find a way to avoid the error.
$ cat .vimrc
set nocp
nmap ,nc :let @x='0ct*abcd f;i)+'
$ LANG= vim -u .vimrc -U NONE --noplugin
If I typed ',nc', then I've got error message.
E115: Missing quote: '0ct*^Iabcd
E15: Invalid expression: '0ct*^Iabcd
Press ENTER or type command to
Luc Hermitte wrote:
Hello,
I run vim on Solaris, Linux and Cygwin (actually I use only the win32
native version of vim, generally the one compiled by Tony).
[...]
I'm not distributing them anymore at the moment. My latest Vim for
Windows was a v7.0aa ALPHA, now outdated. Please fall back on
SungHyun Nam wrote:
Hello,
I could not find a way to avoid the error.
$ cat .vimrc
set nocp
nmap ,nc :let @x='0ct*abcd f;i)+'
$ LANG= vim -u .vimrc -U NONE --noplugin
If I typed ',nc', then I've got error message.
E115: Missing quote: '0ct*^Iabcd
E15: Invalid expression: '0ct*^Iabcd
Press EN
Hi All,
I want to match all the words in a file which are not keywords.
In a verilog code, I want to match all the signal names execpt for
the keywords.
/\w\+ finds all the words.
But How do I make vim understand, not to pick up any keyword.
Best Regards,
Shankar
On Tue, Jul 25, 2006 at 11:14:09AM -0400, Charles E Campbell Jr wrote:
> Hello!
>
> I was trying :breakadd file 484 */visincr.vim and got
>
> Breakpoint in "/home/cec/.vim/autoload/visincr.vim" line 484
> Entering Debug mode. Type "cont" to continue.
> /home/cec/.vim/autoload/visincr.vim
> line
On Tue, Jul 25, 2006 at 12:36:44AM +0400, Pavel Volkovitskiy wrote:
> Hello!
>
> I have to sort python's list quite often, so i want to make a script to
> do that
>
> for example i have:
>a = [
> 'aaa' , 'XXX', '','dsgrg', 'sdgsfdg', 'gfdgffg',
> 'dfgfdgw:swf', 'sdfsdg', 'sdf
On Tue, 25 Jul 2006 at 11:14am, Charles E Campbell Jr wrote:
> Hello!
>
> I was trying :breakadd file 484 */visincr.vim and got
>
> Breakpoint in "/home/cec/.vim/autoload/visincr.vim" line 484
> Entering Debug mode. Type "cont" to continue.
> /home/cec/.vim/autoload/visincr.vim
> line 638: fun!
36 matches
Mail list logo
