Re: Unix/DOS text mode?

Re: Unix/DOS text mode?

[Joshua]

    I think I'm being a bit dense on this issue for which I apologize.  What
option needs to be set to have the Cygwin-packaged vim autodetect
binary/text files and edit/save accordingly?  My .vimrc is a binary file,
BTW.  Thanks and BCNU//jle

From: Corinna Vinschen <cygwin at cygwin dot com>
To: cygwin at cygwin dot com
Date: Tue, 20 Nov 2001 16:29:20 +0100
Subject: Re: Unix/DOS text mode?
References: <000b01c171d5$8a3b4f40$2ae61718@bdfrd1.tx.home.com>

----------------------------------------------------------------------------
----

On Tue, Nov 20, 2001 at 09:10:48AM -0600, Joshua wrote:
>     Corinna,
>
>     Thanks for the enlightenment.  Regarding your statement, 'These files
> must be in binary mode on Cygwin regardless of the bin/textmode of the
> underlying mount point.', what files are you referring to?  I would
> understand if the Cygwin files, ie config files in /etc need to be binary,
> but are you saying that Cygwin needs to deal with all files (like
> /cygwin/c/autoexec.bat) in a binary mode?  Or could the vim packaged with
> Cygwin be set to autodetect the binary/text type?  My understanding of how
> vim/gvim worked was that it would detect the binary/text type and preserve
> the type when you edit save the file.  BCNU//jle

It does recognize bin/text, just not for script files as .vimrc.
These must be binmode (LF, not CRLF lineending).

Corinna

> From: Corinna Vinschen <cygwin at cygwin dot com>
> To: cygwin at cygwin dot com
> Date: Tue, 20 Nov 2001 10:28:25 +0100
> Subject: Re: Unix/DOS text mode?
> References: <000f01c17193$e7b4c6c0$2ae61718@bdfrd1.tx.home.com>
>
> --------------------------------------------------------------------------
--
> ----
>
> On Tue, Nov 20, 2001 at 01:20:59AM -0600, Joshua wrote:
> >     Hmm, I've noticed this difference between the PC version of vim/gvim
> > versus the vim that comes with cygwin.  Using the PC version, vim/gvim
> seems
> > to be able to tell whether you're opening a unix file or a PC file and
> > display/edit appropriately.
> >
> >     I tried copying my _vimrc from my PC installation to .vimrc in my
home
> > directory, but that doesn't do the trick.  I figured it was either a
> switch
> > in vimrc or something to do with the mounts themselves.  BCNU//jle
>
> The Cygwin vim has the same ability to recognize Unix/DOS files
> as the Windows native version.  After a discussion with Bram Moolenaar
> he decided not to add that recognition to the vim script files
> as .vimrc.  These files must be in binary mode on Cygwin regardless
> of the bin/textmode of the underlying mount point.
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin@cygwin.com
> Red Hat, Inc.
>
> --
>
>
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua wrote:
>     I think I'm being a bit dense on this issue for which I apologize.  What
> option needs to be set to have the Cygwin-packaged vim autodetect
> binary/text files and edit/save accordingly?  My .vimrc is a binary file,
> BTW.  Thanks and BCNU//jle

Nothing.  It should work automagically.  Which it does on my system.
I've just tested it explicitely since your postings made me nervous.

However, the unix/dos file recognition works based on examining only
the first line, AFAIK, so if the first line has only a LF instead of
an CRLF for some reason, vim treats the file as unixy.  Then you see
the ^M beginning with line 2.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Bjoern Kahl AG Resy]

 Hallo !

On Wed, 21 Nov 2001, Corinna Vinschen wrote:

On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua wrote:
> >     I think I'm being a bit dense on this issue for which I apologize.  What
> > option needs to be set to have the Cygwin-packaged vim autodetect
> > binary/text files and edit/save accordingly?  My .vimrc is a binary file,

> Nothing.  It should work automagically.  Which it does on my system.
> I've just tested it explicitely since your postings made me nervous.

 Hmm. At least for the version I installed last friday (using
 "install now" (aka setup) on the cygwin site) did *not* work.
 I have had to copy "/usr/share/vimv/im60/vimrc_example" as
 ".vimrc" to my $HOME and add the line "set fileformats=unix,dos"
 under the line "set nocompatible".

> However, the unix/dos file recognition works based on examining only
> the first line, AFAIK, so if the first line has only a LF instead of
> an CRLF for some reason, vim treats the file as unixy.  Then you see
> the ^M beginning with line 2.

 My english is somewhat limited, but as I understand the "options.txt"
 in vim doc-folder, vim reads the whole file dicides on how many <CR>,
 <CR><NL> and >NL> it found. (However, that chapter in the docs is not
 really clear to me).


 Bjoern

-- 
+---------------------------------------------------------------------+
| Dipl.-Phys. Bjoern Kahl +++ AG Embedded Systems and Robotics (RESY) |
| Informatics Faculty +++ Building 48 +++ University of Kaiserslautern|
| phone: +49-631-205-2654 +++ www: http://resy.informatik.uni-kl.de   |
+---------------------------------------------------------------------+



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Corinna Vinschen]

On Wed, Nov 21, 2001 at 10:43:29AM +0100, Bjoern Kahl AG Resy wrote:
> 
>  Hallo !
> 
> On Wed, 21 Nov 2001, Corinna Vinschen wrote:
> 
> On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua wrote:
> > >     I think I'm being a bit dense on this issue for which I apologize.  What
> > > option needs to be set to have the Cygwin-packaged vim autodetect
> > > binary/text files and edit/save accordingly?  My .vimrc is a binary file,
> 
> > Nothing.  It should work automagically.  Which it does on my system.
> > I've just tested it explicitely since your postings made me nervous.
> 
>  Hmm. At least for the version I installed last friday (using
>  "install now" (aka setup) on the cygwin site) did *not* work.
>  I have had to copy "/usr/share/vimv/im60/vimrc_example" as
>  ".vimrc" to my $HOME and add the line "set fileformats=unix,dos"
>  under the line "set nocompatible".

Interesting.  I have no such option set explicitely.  When opening
vi and then call `:set fileformats', the output is

  fileformats=unix,dos

And this is the default setting on Unix systems.  Cygwin is treated as
a Unix system by vim.

> > However, the unix/dos file recognition works based on examining only
> > the first line, AFAIK, so if the first line has only a LF instead of
> > an CRLF for some reason, vim treats the file as unixy.  Then you see
> > the ^M beginning with line 2.
> 
>  My english is somewhat limited, but as I understand the "options.txt"
>  in vim doc-folder, vim reads the whole file dicides on how many <CR>,
>  <CR><NL> and >NL> it found. (However, that chapter in the docs is not
>  really clear to me).

You're right.  It examines the whole file but the notes are clear:

- If _all_ lines end in CRLF, it's treated as dos file.
- If _one_ line is found with only a LF, unix is preferred over dos.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

SSH & Editing in a Basic Shell, etc

[Peter M Boyd]

I am having difficulty trying to use CYGWIN SSH to
connect from Windows NT Client to Windows NT Server
and run only a SHELL environment and NOT a Windows GUI
environment. Any shell will do if it can support my
further requirements, which are to be able:

(1)	to page or browse through text files

(2) to use an edit program to edit text files (and
support the CTRL& functions that the editor
may need)

(3)	to interrupt a long running function

(4)	to run programs that can be run from DOS CMD.EXE


I have the latest (as of 15 Nov 2001) CYQWIN & CYGWIN
SSH installed.

I have been advised to use the ‘bash’ shell and would
be happy to use something else if known to satisfy the
above.

Connection is working fine; (4) is working fine

I canÂ’t get anything to work for (1) to (3).

Can you suggest what can be used to achieve these.

I have already had quite a lot of advice that is
either imprecise or that the advisors havenÂ’t tried
for themselves.

I’ve recently tried ‘vim’ for (1) and (2), but ‘vim’
just “hangs” when invoked.

‘vim’ works fine in a local shell shell environment

My current SSH environments is:

----------------------

BASH=/bin/bash
BASH_VERSINFO=([0]="2" [1]="05" [2]="0" [3]="8"
[4]="release" [5]="i686-pc-cygwin")
BASH_VERSION=$'2.05.0(8)-release'
COLUMNS=80
COMPUTERNAME=NOADP_NT
COMSPEC=$'C:\\WINNT\\system32\\cmd.exe'
CYGWIN=$'binmode ntsec tty'
DIRSTACK=()
EUID=513
GROUPS=()
HISTFILE=/cygdrive/d/temp/.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/cygdrive/d/temp
HOMEDRIVE=d:
HOMEPATH=$'\\temp'
HOSTNAME=NOADP_NT
HOSTTYPE=i686
IFS=$' \t\n'
INCLUDE=$'C:\\Program Files\\Mts\\Include'
LIB=$'C:\\Program Files\\Mts\\Lib'
LINES=60
LOGNAME=ratest
MACHTYPE=i686-pc-cygwin
MAIL=/var/spool/mail/ratest
MAILCHECK=60
MAKE_MODE=unix
NTRESKIT=$'C:\\Program Files\\rksupport'
NUMBER_OF_PROCESSORS=1
OLDPWD=/cygdrive/d/temp
OPTERR=1
OPTIND=1
OS=Windows_NT
OS2LIBPATH=$'C:\\WINNT\\system32\\os2\\dll;'
OSTYPE=cygwin
PATH=$'/usr/local/bin:/usr/bin:/bin:/usr/local/bin:/cygdrive/c/WINNT/system32:/cygdrive/c/WINNT:/cygdrive/c/Win32App/PVCS/DIMENS~1/5.0/PROG:/cygdrive/c/Win32App/PVCS/DIMENS~1/ORANT/BIN:/cygdrive/c/orawinnt/BIN:.:/cygdrive/c/WINNT/System32/WBEM:/cygdrive/c/Program
Files/Mts:/cygdrive/c/Program Files/rksupport:/bin'
PATHEXT=$'.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PIPESTATUS=([0]="0")
PPID=306
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=$'x86 Family 6 Model 5 Stepping
2, GenuineIntel'
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0502
PS1=$'\\[\\033]0;\\w\\007\n\\033[32m\\]\\u@\\h
\\[\\033[33m\\w\\033[0m\\]\n$ '
PS2=$'> '
PS4=$'+ '
PWD=/cygdrive/d/temp
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:histexpand:monitor:history:interactive-comments:emacs
SHLVL=1
SSH_CLIENT=$'127.0.0.1 2934 22'
SSH_TTY=/dev/tty1
SYSTEMDRIVE=C:
SYSTEMROOT=$'C:\\WINNT'
TERM=cygwin
TZ=GMTST0GMTDT-1,M3.5.0/2,M10.5.0/3
UID=513
USER=ratest
USERPROFILE=$'C:\\WINNT\\Profiles\\ratest'
WINDIR=$'C:\\WINNT'
_=pwd
i=$'/etc/profile.d/*.sh'

--------------


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

SSH & Editing in a Basic Shell, etc

[Peter M Boyd]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3414 bytes --]

I am having difficulty trying to use CYGWIN SSH to
connect from Windows NT Client to Windows NT Server
and run only a SHELL environment and NOT a Windows GUI
environment. Any shell will do if it can support my
further requirements, which are to be able:

(1)	to page or browse through text files

(2) to use an edit program to edit text files (and
support the CTRL& functions that the editor
may need)

(3)	to interrupt a long running function

(4)	to run programs that can be run from DOS CMD.EXE


I have the latest (as of 15 Nov 2001) CYQWIN & CYGWIN
SSH installed.

I have been advised to use the ‘bash’ shell and would
be happy to use something else if known to satisfy the
above.

Connection is working fine; (4) is working fine

I canÂ’t get anything to work for (1) to (3).

Can you suggest what can be used to achieve these.

I have already had quite a lot of advice that is
either imprecise or that the advisors havenÂ’t tried
for themselves.

I’ve recently tried ‘vim’ for (1) and (2), but ‘vim’
just “hangs” when invoked.

‘vim’ works fine in a local shell shell environment

My current SSH environments is:

----------------------

BASH=/bin/bash
BASH_VERSINFO=([0]="2" [1]="05" [2]="0" [3]="8"
[4]="release" [5]="i686-pc-cygwin")
BASH_VERSION=$'2.05.0(8)-release'
COLUMNS=80
COMPUTERNAME=NOADP_NT
COMSPEC=$'C:\\WINNT\\system32\\cmd.exe'
CYGWIN=$'binmode ntsec tty'
DIRSTACK=()
EUID=513
GROUPS=()
HISTFILE=/cygdrive/d/temp/.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/cygdrive/d/temp
HOMEDRIVE=d:
HOMEPATH=$'\\temp'
HOSTNAME=NOADP_NT
HOSTTYPE=i686
IFS=$' \t\n'
INCLUDE=$'C:\\Program Files\\Mts\\Include'
LIB=$'C:\\Program Files\\Mts\\Lib'
LINES=60
LOGNAME=ratest
MACHTYPE=i686-pc-cygwin
MAIL=/var/spool/mail/ratest
MAILCHECK=60
MAKE_MODE=unix
NTRESKIT=$'C:\\Program Files\\rksupport'
NUMBER_OF_PROCESSORS=1
OLDPWD=/cygdrive/d/temp
OPTERR=1
OPTIND=1
OS=Windows_NT
OS2LIBPATH=$'C:\\WINNT\\system32\\os2\\dll;'
OSTYPE=cygwin
PATH=$'/usr/local/bin:/usr/bin:/bin:/usr/local/bin:/cygdrive/c/WINNT/system32:/cygdrive/c/WINNT:/cygdrive/c/Win32App/PVCS/DIMENS~1/5.0/PROG:/cygdrive/c/Win32App/PVCS/DIMENS~1/ORANT/BIN:/cygdrive/c/orawinnt/BIN:.:/cygdrive/c/WINNT/System32/WBEM:/cygdrive/c/Program
Files/Mts:/cygdrive/c/Program Files/rksupport:/bin'
PATHEXT=$'.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PIPESTATUS=([0]="0")
PPID=306
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=$'x86 Family 6 Model 5 Stepping
2, GenuineIntel'
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0502
PS1=$'\\[\\033]0;\\w\\007\n\\033[32m\\]\\u@\\h
\\[\\033[33m\\w\\033[0m\\]\n$ '
PS2=$'> '
PS4=$'+ '
PWD=/cygdrive/d/temp
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:histexpand:monitor:history:interactive-comments:emacs
SHLVL=1
SSH_CLIENT=$'127.0.0.1 2934 22'
SSH_TTY=/dev/tty1
SYSTEMDRIVE=C:
SYSTEMROOT=$'C:\\WINNT'
TERM=cygwin
TZ=GMTST0GMTDT-1,M3.5.0/2,M10.5.0/3
UID=513
USER=ratest
USERPROFILE=$'C:\\WINNT\\Profiles\\ratest'
WINDIR=$'C:\\WINNT'
_=pwd
i=$'/etc/profile.d/*.sh'

--------------


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Corinna Vinschen]

On Wed, Nov 21, 2001 at 10:43:29AM +0100, Bjoern Kahl AG Resy wrote:
> 
>  Hallo !
> 
> On Wed, 21 Nov 2001, Corinna Vinschen wrote:
> 
> On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua wrote:
> > >     I think I'm being a bit dense on this issue for which I apologize.  What
> > > option needs to be set to have the Cygwin-packaged vim autodetect
> > > binary/text files and edit/save accordingly?  My .vimrc is a binary file,
> 
> > Nothing.  It should work automagically.  Which it does on my system.
> > I've just tested it explicitely since your postings made me nervous.
> 
>  Hmm. At least for the version I installed last friday (using
>  "install now" (aka setup) on the cygwin site) did *not* work.
>  I have had to copy "/usr/share/vimv/im60/vimrc_example" as
>  ".vimrc" to my $HOME and add the line "set fileformats=unix,dos"
>  under the line "set nocompatible".

Interesting.  I have no such option set explicitely.  When opening
vi and then call `:set fileformats', the output is

  fileformats=unix,dos

And this is the default setting on Unix systems.  Cygwin is treated as
a Unix system by vim.

> > However, the unix/dos file recognition works based on examining only
> > the first line, AFAIK, so if the first line has only a LF instead of
> > an CRLF for some reason, vim treats the file as unixy.  Then you see
> > the ^M beginning with line 2.
> 
>  My english is somewhat limited, but as I understand the "options.txt"
>  in vim doc-folder, vim reads the whole file dicides on how many <CR>,
>  <CR><NL> and >NL> it found. (However, that chapter in the docs is not
>  really clear to me).

You're right.  It examines the whole file but the notes are clear:

- If _all_ lines end in CRLF, it's treated as dos file.
- If _one_ line is found with only a LF, unix is preferred over dos.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Bjoern Kahl AG Resy]

 Hallo !

On Wed, 21 Nov 2001, Corinna Vinschen wrote:

On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua wrote:
> >     I think I'm being a bit dense on this issue for which I apologize.  What
> > option needs to be set to have the Cygwin-packaged vim autodetect
> > binary/text files and edit/save accordingly?  My .vimrc is a binary file,

> Nothing.  It should work automagically.  Which it does on my system.
> I've just tested it explicitely since your postings made me nervous.

 Hmm. At least for the version I installed last friday (using
 "install now" (aka setup) on the cygwin site) did *not* work.
 I have had to copy "/usr/share/vimv/im60/vimrc_example" as
 ".vimrc" to my $HOME and add the line "set fileformats=unix,dos"
 under the line "set nocompatible".

> However, the unix/dos file recognition works based on examining only
> the first line, AFAIK, so if the first line has only a LF instead of
> an CRLF for some reason, vim treats the file as unixy.  Then you see
> the ^M beginning with line 2.

 My english is somewhat limited, but as I understand the "options.txt"
 in vim doc-folder, vim reads the whole file dicides on how many <CR>,
 <CR><NL> and >NL> it found. (However, that chapter in the docs is not
 really clear to me).


 Bjoern

-- 
+---------------------------------------------------------------------+
| Dipl.-Phys. Bjoern Kahl +++ AG Embedded Systems and Robotics (RESY) |
| Informatics Faculty +++ Building 48 +++ University of Kaiserslautern|
| phone: +49-631-205-2654 +++ www: http://resy.informatik.uni-kl.de   |
+---------------------------------------------------------------------+



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[AGalick]

Thanks, this worked, but I never needed a .vimrc before and
my .viminfo history/recall is only loaded if I explicitly type :rv.
I (and my boss) were fed up with me squirrelling
with it, so I shelled out $79 for a cygwin 1.0 CD at
ccpcomputersupplies.com.  They're the only place
I could find with a stable release for sale.  Either
I'm paying for being a sorry excuse of a 'puter geek,
or I'm getting a good deal to avoid being a guinea pig.

Albert



                                                                                                              
                    "Larry Hall                                                                               
                    (RFK                 To:     AGalick@attotech.com, cygwin@cygwin.com                      
                    Partners,            cc:                                                                  
                    Inc)"                Subject:     Re: Unix/DOS text mode?                                 
                    <lhall@rfk.co                                                                             
                    m>                                                                                        
                                                                                                              
                    11/19/01                                                                                  
                    04:34 PM                                                                                  
                                                                                                              
                                                                                                              



At 04:00 PM 11/19/2001, AGalick@attotech.com wrote:
>After an upgrade, I seem to have lost all sanity in vi(m).
>I used to see .txt files the same with notepad or vi, but
>now in vi every line ends with a blue ^M.  I've played
>with mount -[t|b] and tried [un and re]installing vim but I'm
>stumped.  The thing is, it seems to have also disabled all
>the nice search string history/recall (I guess because .viminfo
>also shows those damned ^M's).  What have I done
>or what has cygwin done?  I guess other stuff got upgraded,
>too, but I don't know what.


Try setting "fileformat=dos" in your .vimrc file if you always want
your files to be treated as a DOS text file.  See the help in vim for
more info.





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX






--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[AGalick]

Thanks, this worked, but I never needed a .vimrc before and
my .viminfo history/recall is only loaded if I explicitly type :rv.
I (and my boss) were fed up with me squirrelling
with it, so I shelled out $79 for a cygwin 1.0 CD at
ccpcomputersupplies.com.  They're the only place
I could find with a stable release for sale.  Either
I'm paying for being a sorry excuse of a 'puter geek,
or I'm getting a good deal to avoid being a guinea pig.

Albert



                                                                                                              
                    "Larry Hall                                                                               
                    (RFK                 To:     AGalick@attotech.com, cygwin@cygwin.com                      
                    Partners,            cc:                                                                  
                    Inc)"                Subject:     Re: Unix/DOS text mode?                                 
                    <lhall@rfk.co                                                                             
                    m>                                                                                        
                                                                                                              
                    11/19/01                                                                                  
                    04:34 PM                                                                                  
                                                                                                              
                                                                                                              



At 04:00 PM 11/19/2001, AGalick@attotech.com wrote:
>After an upgrade, I seem to have lost all sanity in vi(m).
>I used to see .txt files the same with notepad or vi, but
>now in vi every line ends with a blue ^M.  I've played
>with mount -[t|b] and tried [un and re]installing vim but I'm
>stumped.  The thing is, it seems to have also disabled all
>the nice search string history/recall (I guess because .viminfo
>also shows those damned ^M's).  What have I done
>or what has cygwin done?  I guess other stuff got upgraded,
>too, but I don't know what.


Try setting "fileformat=dos" in your .vimrc file if you always want
your files to be treated as a DOS text file.  See the help in vim for
more info.





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX






--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Joshua]

Corinna et al,

Strangely enough, my vim does *not* start up with the
fileformats=dos,unix option either.  However, adding
that switch to .vimrc does the trick.  I wonder where
your installation is getting that option set at? 
BCNU//jle

From: Corinna Vinschen <cygwin at cygwin dot com> 
To: cygwin <cygwin at cygwin dot com> 
Date: Wed, 21 Nov 2001 11:16:43 +0100 
Subject: Re: Unix/DOS text mode? 
References:
<20011121102822.E21630@cygbert.vinschen.de>
<Pine.GSO.4.40.0111211032100.1160-100000@domino.informatik.uni-kl.de>


--------------------------------------------------------------------------------

On Wed, Nov 21, 2001 at 10:43:29AM +0100, Bjoern Kahl
AG Resy wrote:
> 
>  Hallo !
> 
> On Wed, 21 Nov 2001, Corinna Vinschen wrote:
> 
> On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua
wrote:
> > >     I think I'm being a bit dense on this issue
for which I apologize.  What
> > > option needs to be set to have the
Cygwin-packaged vim autodetect
> > > binary/text files and edit/save accordingly?  My
.vimrc is a binary file,
> 
> > Nothing.  It should work automagically.  Which it
does on my system.
> > I've just tested it explicitely since your
postings made me nervous.
> 
>  Hmm. At least for the version I installed last
friday (using
>  "install now" (aka setup) on the cygwin site) did
*not* work.
>  I have had to copy
"/usr/share/vimv/im60/vimrc_example" as
>  ".vimrc" to my $HOME and add the line "set
fileformats=unix,dos"
>  under the line "set nocompatible".

Interesting.  I have no such option set explicitely. 
When opening
vi and then call `:set fileformats', the output is

  fileformats=unix,dos

And this is the default setting on Unix systems. 
Cygwin is treated as
a Unix system by vim.

> > However, the unix/dos file recognition works based
on examining only
> > the first line, AFAIK, so if the first line has
only a LF instead of
> > an CRLF for some reason, vim treats the file as
unixy.  Then you see
> > the ^M beginning with line 2.
> 
>  My english is somewhat limited, but as I understand
the "options.txt"
>  in vim doc-folder, vim reads the whole file dicides
on how many <CR>,
>  <CR><NL> and >NL> it found. (However, that chapter
in the docs is not
>  really clear to me).

You're right.  It examines the whole file but the
notes are clear:

- If _all_ lines end in CRLF, it's treated as dos
file.
- If _one_ line is found with only a LF, unix is
preferred over dos.

Corinna

-- 
Corinna Vinschen                  Please, send mails
regarding Cygwin to
Cygwin Developer                               
mailto:cygwin@cygwin.com
Red Hat, Inc.



=====


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

The default value of "fileformats" depends on whether the "compatible" 
option is set.
If it is, then fileformats="", so file format autodetection is disabled.
If it isn't, then fileformats="unix,dos".
(This is for the UNIX version (including Cygwin).  The Windoze native 
version uses "dos,unix" in both cases.)

If a .vimrc exists, even if it is empty, "nocompatible" will be set, 
otherwise "compatible" will be set.

So, a default installation of vim on Cygwin will not enable file format 
detection.

(Source: ":help compatible".)

HTH,

  - Michael

At 20:07 22-11-2001, Joshua wrote:
>Corinna et al,
>
>Strangely enough, my vim does *not* start up with the
>fileformats=dos,unix option either.  However, adding
>that switch to .vimrc does the trick.  I wonder where
>your installation is getting that option set at?
>BCNU//jle
>
>From: Corinna Vinschen <cygwin at cygwin dot com>
>To: cygwin <cygwin at cygwin dot com>
>Date: Wed, 21 Nov 2001 11:16:43 +0100
>Subject: Re: Unix/DOS text mode?
>References:
><20011121102822.E21630@cygbert.vinschen.de>
><Pine.GSO.4.40.0111211032100.1160-100000@domino.informatik.uni-kl.de>
>
>
>--------------------------------------------------------------------------------
>
>On Wed, Nov 21, 2001 at 10:43:29AM +0100, Bjoern Kahl
>AG Resy wrote:
> >
> >  Hallo !
> >
> > On Wed, 21 Nov 2001, Corinna Vinschen wrote:
> >
> > On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua
>wrote:
> > > >     I think I'm being a bit dense on this issue
>for which I apologize.  What
> > > > option needs to be set to have the
>Cygwin-packaged vim autodetect
> > > > binary/text files and edit/save accordingly?  My
>.vimrc is a binary file,
> >
> > > Nothing.  It should work automagically.  Which it
>does on my system.
> > > I've just tested it explicitely since your
>postings made me nervous.
> >
> >  Hmm. At least for the version I installed last
>friday (using
> >  "install now" (aka setup) on the cygwin site) did
>*not* work.
> >  I have had to copy
>"/usr/share/vimv/im60/vimrc_example" as
> >  ".vimrc" to my $HOME and add the line "set
>fileformats=unix,dos"
> >  under the line "set nocompatible".
>
>Interesting.  I have no such option set explicitely.
>When opening
>vi and then call `:set fileformats', the output is
>
>   fileformats=unix,dos
>
>And this is the default setting on Unix systems.
>Cygwin is treated as
>a Unix system by vim.
>
> > > However, the unix/dos file recognition works based
>on examining only
> > > the first line, AFAIK, so if the first line has
>only a LF instead of
> > > an CRLF for some reason, vim treats the file as
>unixy.  Then you see
> > > the ^M beginning with line 2.
> >
> >  My english is somewhat limited, but as I understand
>the "options.txt"
> >  in vim doc-folder, vim reads the whole file dicides
>on how many <CR>,
> >  <CR><NL> and >NL> it found. (However, that chapter
>in the docs is not
> >  really clear to me).
>
>You're right.  It examines the whole file but the
>notes are clear:
>
>- If _all_ lines end in CRLF, it's treated as dos
>file.
>- If _one_ line is found with only a LF, unix is
>preferred over dos.
>
>Corinna
>
>--
>Corinna Vinschen                  Please, send mails
>regarding Cygwin to
>Cygwin Developer
>mailto:cygwin@cygwin.com
>Red Hat, Inc.
>
>
>
>=====
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
>http://geocities.yahoo.com/ps/info1
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/


-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

At 23:05 22-11-2001, I wrote:
>The default value of "fileformats" depends on whether the "compatible" 
>option is set.
>If it is, then fileformats="", so file format autodetection is disabled.
>If it isn't, then fileformats="unix,dos".
>(This is for the UNIX version (including Cygwin).  The Windoze native 
>version uses "dos,unix" in both cases.)
>
>If a .vimrc exists, even if it is empty, "nocompatible" will be set, 
>otherwise "compatible" will be set.
>
>So, a default installation of vim on Cygwin will not enable file format 
>detection.
>
>(Source: ":help compatible".)

Here's a patch that changes the default fileformats in vi-compatible mode 
to "unix,dos", for Cygwin.
I'll also attach it, since I'm using Eudora (with format=flowed), which may 
screw up indentation.

If Corinna likes the patch, I'll also send it to the vim-dev list.  (It may 
be a while before it becomes "official", though, since Bram is on a 
well-deserved vacation.)

  - Michael

-------------------------8<-------------------------
--- ORIG/option.h       Thu Nov 22 23:10:21 2001
+++ option.h    Thu Nov 22 23:19:03 2001
@@ -67,7 +67,11 @@
  # else
  #  define DFLT_FF      "unix"
  #  define DFLT_FFS_VIM "unix,dos"
-#  define DFLT_FFS_VI  ""
+#  if defined(__CYGWIN__) || defined(__CYGWIN32__)
+#   define DFLT_FFS_VI "unix,dos"      /* Cygwin always needs file 
detection */
+#  else
+#   define DFLT_FFS_VI ""
+#  endif
  #  define DFLT_TEXTAUTO        FALSE
  # endif
  #endif
------------------------->8-------------------------

-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

[-- Attachment #1: Type: text/plain, Size: 170 bytes --]

At 23:30 22-11-2001, Michael Schaap wrote:
>I'll also attach it, since I'm using Eudora (with format=flowed), which 
>may screw up indentation.

Uh oh...

Here it is. :-)

[-- Attachment #2: ff_patch --]
[-- Type: application/octet-stream, Size: 417 bytes --]

--- ORIG/option.h	Thu Nov 22 23:10:21 2001
+++ option.h	Thu Nov 22 23:19:03 2001
@@ -67,7 +67,11 @@
 # else
 #  define DFLT_FF	"unix"
 #  define DFLT_FFS_VIM	"unix,dos"
-#  define DFLT_FFS_VI	""
+#  if defined(__CYGWIN__) || defined(__CYGWIN32__)
+#   define DFLT_FFS_VI	"unix,dos"	/* Cygwin always needs file detection */
+#  else
+#   define DFLT_FFS_VI	""
+#  endif
 #  define DFLT_TEXTAUTO	FALSE
 # endif
 #endif

[-- Attachment #3: Type: text/plain, Size: 210 bytes --]


-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 

[-- Attachment #4: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

[-- Attachment #1: Type: text/plain, Size: 427 bytes --]

At 23:30 22-11-2001, Michael Schaap wrote:
>I'll also attach it, since I'm using Eudora (with format=flowed), which 
>may screw up indentation.

Uh oh...

Here it is. :-)
Attachment:
ff_patch
Description: Binary data

-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 

[-- Attachment #2: ff_patch --]
[-- Type: text/x-diff, Size: 417 bytes --]

--- ORIG/option.h	Thu Nov 22 23:10:21 2001
+++ option.h	Thu Nov 22 23:19:03 2001
@@ -67,7 +67,11 @@
 # else
 #  define DFLT_FF	"unix"
 #  define DFLT_FFS_VIM	"unix,dos"
-#  define DFLT_FFS_VI	""
+#  if defined(__CYGWIN__) || defined(__CYGWIN32__)
+#   define DFLT_FFS_VI	"unix,dos"	/* Cygwin always needs file detection */
+#  else
+#   define DFLT_FFS_VI	""
+#  endif
 #  define DFLT_TEXTAUTO	FALSE
 # endif
 #endif

Re: Unix/DOS text mode?

[Corinna Vinschen]

On Thu, Nov 22, 2001 at 11:30:11PM +0100, Michael Schaap wrote:
> At 23:05 22-11-2001, I wrote:
> >The default value of "fileformats" depends on whether the "compatible" 
> >option is set.
> >If it is, then fileformats="", so file format autodetection is disabled.
> >If it isn't, then fileformats="unix,dos".
> >(This is for the UNIX version (including Cygwin).  The Windoze native 
> >version uses "dos,unix" in both cases.)
> >
> >If a .vimrc exists, even if it is empty, "nocompatible" will be set, 
> >otherwise "compatible" will be set.
> >
> >So, a default installation of vim on Cygwin will not enable file format 
> >detection.
> >
> >(Source: ":help compatible".)
> 
> Here's a patch that changes the default fileformats in vi-compatible mode 
> to "unix,dos", for Cygwin.
> I'll also attach it, since I'm using Eudora (with format=flowed), which may 
> screw up indentation.
> 
> If Corinna likes the patch, I'll also send it to the vim-dev list.  (It may 
> be a while before it becomes "official", though, since Bram is on a 
> well-deserved vacation.)

I'm all with it but please drop the usage of __CYGWIN32__.  It's
depricated.  I will send a patch to vim-dev which drops all other
__CYGWIN32__ in favour of __CYGWIN later.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

At 23:43 22-11-2001, you wrote:
>I'm all with it but please drop the usage of __CYGWIN32__.  It's
>depricated.  I will send a patch to vim-dev which drops all other
>__CYGWIN32__ in favour of __CYGWIN later.

Okay.  I saw three different Cygwin checks in the header files, so I 
decided to go with the safest one.

Here's a new patch.

  - Michael

-------------------------8<-------------------------
--- ORIG/option.h       Thu Nov 22 23:10:21 2001
+++ option.h    Thu Nov 22 23:49:07 2001
@@ -67,7 +67,11 @@
  # else
  #  define DFLT_FF      "unix"
  #  define DFLT_FFS_VIM "unix,dos"
-#  define DFLT_FFS_VI  ""
+#  ifdef __CYGWIN__
+#   define DFLT_FFS_VI "unix,dos"      /* Cygwin always needs file 
detection */
+#  else
+#   define DFLT_FFS_VI ""
+#  endif
  #  define DFLT_TEXTAUTO        FALSE
  # endif
  #endif
------------------------->8-------------------------

[-- Attachment #2: ff_patch --]
[-- Type: application/octet-stream, Size: 386 bytes --]

--- ORIG/option.h	Thu Nov 22 23:10:21 2001
+++ option.h	Thu Nov 22 23:49:07 2001
@@ -67,7 +67,11 @@
 # else
 #  define DFLT_FF	"unix"
 #  define DFLT_FFS_VIM	"unix,dos"
-#  define DFLT_FFS_VI	""
+#  ifdef __CYGWIN__
+#   define DFLT_FFS_VI	"unix,dos"	/* Cygwin always needs file detection */
+#  else
+#   define DFLT_FFS_VI	""
+#  endif
 #  define DFLT_TEXTAUTO	FALSE
 # endif
 #endif

[-- Attachment #3: Type: text/plain, Size: 210 bytes --]


-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 

[-- Attachment #4: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

At 23:43 22-11-2001, you wrote:
>I'm all with it but please drop the usage of __CYGWIN32__.  It's
>depricated.  I will send a patch to vim-dev which drops all other
>__CYGWIN32__ in favour of __CYGWIN later.

Okay.  I saw three different Cygwin checks in the header files, so I 
decided to go with the safest one.

Here's a new patch.

  - Michael

-------------------------8<-------------------------
--- ORIG/option.h       Thu Nov 22 23:10:21 2001
+++ option.h    Thu Nov 22 23:49:07 2001
@@ -67,7 +67,11 @@
  # else
  #  define DFLT_FF      "unix"
  #  define DFLT_FFS_VIM "unix,dos"
-#  define DFLT_FFS_VI  ""
+#  ifdef __CYGWIN__
+#   define DFLT_FFS_VI "unix,dos"      /* Cygwin always needs file 
detection */
+#  else
+#   define DFLT_FFS_VI ""
+#  endif
  #  define DFLT_TEXTAUTO        FALSE
  # endif
  #endif
------------------------->8-------------------------
Attachment:
ff_patch
Description: Binary data

-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 

[-- Attachment #2: ff_patch --]
[-- Type: text/x-diff, Size: 386 bytes --]

--- ORIG/option.h	Thu Nov 22 23:10:21 2001
+++ option.h	Thu Nov 22 23:49:07 2001
@@ -67,7 +67,11 @@
 # else
 #  define DFLT_FF	"unix"
 #  define DFLT_FFS_VIM	"unix,dos"
-#  define DFLT_FFS_VI	""
+#  ifdef __CYGWIN__
+#   define DFLT_FFS_VI	"unix,dos"	/* Cygwin always needs file detection */
+#  else
+#   define DFLT_FFS_VI	""
+#  endif
 #  define DFLT_TEXTAUTO	FALSE
 # endif
 #endif

Re: Unix/DOS text mode?

[Corinna Vinschen]

On Thu, Nov 22, 2001 at 11:30:11PM +0100, Michael Schaap wrote:
> At 23:05 22-11-2001, I wrote:
> >The default value of "fileformats" depends on whether the "compatible" 
> >option is set.
> >If it is, then fileformats="", so file format autodetection is disabled.
> >If it isn't, then fileformats="unix,dos".
> >(This is for the UNIX version (including Cygwin).  The Windoze native 
> >version uses "dos,unix" in both cases.)
> >
> >If a .vimrc exists, even if it is empty, "nocompatible" will be set, 
> >otherwise "compatible" will be set.
> >
> >So, a default installation of vim on Cygwin will not enable file format 
> >detection.
> >
> >(Source: ":help compatible".)
> 
> Here's a patch that changes the default fileformats in vi-compatible mode 
> to "unix,dos", for Cygwin.
> I'll also attach it, since I'm using Eudora (with format=flowed), which may 
> screw up indentation.
> 
> If Corinna likes the patch, I'll also send it to the vim-dev list.  (It may 
> be a while before it becomes "official", though, since Bram is on a 
> well-deserved vacation.)

I'm all with it but please drop the usage of __CYGWIN32__.  It's
depricated.  I will send a patch to vim-dev which drops all other
__CYGWIN32__ in favour of __CYGWIN later.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

At 23:05 22-11-2001, I wrote:
>The default value of "fileformats" depends on whether the "compatible" 
>option is set.
>If it is, then fileformats="", so file format autodetection is disabled.
>If it isn't, then fileformats="unix,dos".
>(This is for the UNIX version (including Cygwin).  The Windoze native 
>version uses "dos,unix" in both cases.)
>
>If a .vimrc exists, even if it is empty, "nocompatible" will be set, 
>otherwise "compatible" will be set.
>
>So, a default installation of vim on Cygwin will not enable file format 
>detection.
>
>(Source: ":help compatible".)

Here's a patch that changes the default fileformats in vi-compatible mode 
to "unix,dos", for Cygwin.
I'll also attach it, since I'm using Eudora (with format=flowed), which may 
screw up indentation.

If Corinna likes the patch, I'll also send it to the vim-dev list.  (It may 
be a while before it becomes "official", though, since Bram is on a 
well-deserved vacation.)

  - Michael

-------------------------8<-------------------------
--- ORIG/option.h       Thu Nov 22 23:10:21 2001
+++ option.h    Thu Nov 22 23:19:03 2001
@@ -67,7 +67,11 @@
  # else
  #  define DFLT_FF      "unix"
  #  define DFLT_FFS_VIM "unix,dos"
-#  define DFLT_FFS_VI  ""
+#  if defined(__CYGWIN__) || defined(__CYGWIN32__)
+#   define DFLT_FFS_VI "unix,dos"      /* Cygwin always needs file 
detection */
+#  else
+#   define DFLT_FFS_VI ""
+#  endif
  #  define DFLT_TEXTAUTO        FALSE
  # endif
  #endif
------------------------->8-------------------------

-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Michael Schaap]

The default value of "fileformats" depends on whether the "compatible" 
option is set.
If it is, then fileformats="", so file format autodetection is disabled.
If it isn't, then fileformats="unix,dos".
(This is for the UNIX version (including Cygwin).  The Windoze native 
version uses "dos,unix" in both cases.)

If a .vimrc exists, even if it is empty, "nocompatible" will be set, 
otherwise "compatible" will be set.

So, a default installation of vim on Cygwin will not enable file format 
detection.

(Source: ":help compatible".)

HTH,

  - Michael

At 20:07 22-11-2001, Joshua wrote:
>Corinna et al,
>
>Strangely enough, my vim does *not* start up with the
>fileformats=dos,unix option either.  However, adding
>that switch to .vimrc does the trick.  I wonder where
>your installation is getting that option set at?
>BCNU//jle
>
>From: Corinna Vinschen <cygwin at cygwin dot com>
>To: cygwin <cygwin at cygwin dot com>
>Date: Wed, 21 Nov 2001 11:16:43 +0100
>Subject: Re: Unix/DOS text mode?
>References:
>< 20011121102822.E21630@cygbert.vinschen.de >
>< Pine.GSO.4.40.0111211032100.1160-100000@domino.informatik.uni-kl.de >
>
>
>--------------------------------------------------------------------------------
>
>On Wed, Nov 21, 2001 at 10:43:29AM +0100, Bjoern Kahl
>AG Resy wrote:
> >
> >  Hallo !
> >
> > On Wed, 21 Nov 2001, Corinna Vinschen wrote:
> >
> > On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua
>wrote:
> > > >     I think I'm being a bit dense on this issue
>for which I apologize.  What
> > > > option needs to be set to have the
>Cygwin-packaged vim autodetect
> > > > binary/text files and edit/save accordingly?  My
>.vimrc is a binary file,
> >
> > > Nothing.  It should work automagically.  Which it
>does on my system.
> > > I've just tested it explicitely since your
>postings made me nervous.
> >
> >  Hmm. At least for the version I installed last
>friday (using
> >  "install now" (aka setup) on the cygwin site) did
>*not* work.
> >  I have had to copy
>"/usr/share/vimv/im60/vimrc_example" as
> >  ".vimrc" to my $HOME and add the line "set
>fileformats=unix,dos"
> >  under the line "set nocompatible".
>
>Interesting.  I have no such option set explicitely.
>When opening
>vi and then call `:set fileformats', the output is
>
>   fileformats=unix,dos
>
>And this is the default setting on Unix systems.
>Cygwin is treated as
>a Unix system by vim.
>
> > > However, the unix/dos file recognition works based
>on examining only
> > > the first line, AFAIK, so if the first line has
>only a LF instead of
> > > an CRLF for some reason, vim treats the file as
>unixy.  Then you see
> > > the ^M beginning with line 2.
> >
> >  My english is somewhat limited, but as I understand
>the "options.txt"
> >  in vim doc-folder, vim reads the whole file dicides
>on how many <CR>,
> >  <CR><NL> and >NL> it found. (However, that chapter
>in the docs is not
> >  really clear to me).
>
>You're right.  It examines the whole file but the
>notes are clear:
>
>- If _all_ lines end in CRLF, it's treated as dos
>file.
>- If _one_ line is found with only a LF, unix is
>preferred over dos.
>
>Corinna
>
>--
>Corinna Vinschen                  Please, send mails
>regarding Cygwin to
>Cygwin Developer
> mailto:cygwin@cygwin.com
>Red Hat, Inc.
>
>
>
>=====
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
> http://geocities.yahoo.com/ps/info1
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/


-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Joshua]

Corinna et al,

Strangely enough, my vim does *not* start up with the
fileformats=dos,unix option either.  However, adding
that switch to .vimrc does the trick.  I wonder where
your installation is getting that option set at? 
BCNU//jle

From: Corinna Vinschen <cygwin at cygwin dot com> 
To: cygwin <cygwin at cygwin dot com> 
Date: Wed, 21 Nov 2001 11:16:43 +0100 
Subject: Re: Unix/DOS text mode? 
References:
< 20011121102822.E21630@cygbert.vinschen.de >
< Pine.GSO.4.40.0111211032100.1160-100000@domino.informatik.uni-kl.de >


--------------------------------------------------------------------------------

On Wed, Nov 21, 2001 at 10:43:29AM +0100, Bjoern Kahl
AG Resy wrote:
> 
>  Hallo !
> 
> On Wed, 21 Nov 2001, Corinna Vinschen wrote:
> 
> On Tue, Nov 20, 2001 at 07:54:47PM -0600, Joshua
wrote:
> > >     I think I'm being a bit dense on this issue
for which I apologize.  What
> > > option needs to be set to have the
Cygwin-packaged vim autodetect
> > > binary/text files and edit/save accordingly?  My
.vimrc is a binary file,
> 
> > Nothing.  It should work automagically.  Which it
does on my system.
> > I've just tested it explicitely since your
postings made me nervous.
> 
>  Hmm. At least for the version I installed last
friday (using
>  "install now" (aka setup) on the cygwin site) did
*not* work.
>  I have had to copy
"/usr/share/vimv/im60/vimrc_example" as
>  ".vimrc" to my $HOME and add the line "set
fileformats=unix,dos"
>  under the line "set nocompatible".

Interesting.  I have no such option set explicitely. 
When opening
vi and then call `:set fileformats', the output is

  fileformats=unix,dos

And this is the default setting on Unix systems. 
Cygwin is treated as
a Unix system by vim.

> > However, the unix/dos file recognition works based
on examining only
> > the first line, AFAIK, so if the first line has
only a LF instead of
> > an CRLF for some reason, vim treats the file as
unixy.  Then you see
> > the ^M beginning with line 2.
> 
>  My english is somewhat limited, but as I understand
the "options.txt"
>  in vim doc-folder, vim reads the whole file dicides
on how many <CR>,
>  <CR><NL> and >NL> it found. (However, that chapter
in the docs is not
>  really clear to me).

You're right.  It examines the whole file but the
notes are clear:

- If _all_ lines end in CRLF, it's treated as dos
file.
- If _one_ line is found with only a LF, unix is
preferred over dos.

Corinna

-- 
Corinna Vinschen                  Please, send mails
regarding Cygwin to
Cygwin Developer                               
mailto:cygwin@cygwin.com
Red Hat, Inc.



=====


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Joshua]

    Corinna,

    Thanks for the enlightenment.  Regarding your statement, 'These files
must be in binary mode on Cygwin regardless of the bin/textmode of the
underlying mount point.', what files are you referring to?  I would
understand if the Cygwin files, ie config files in /etc need to be binary,
but are you saying that Cygwin needs to deal with all files (like
/cygwin/c/autoexec.bat) in a binary mode?  Or could the vim packaged with
Cygwin be set to autodetect the binary/text type?  My understanding of how
vim/gvim worked was that it would detect the binary/text type and preserve
the type when you edit save the file.  BCNU//jle


From: Corinna Vinschen <cygwin at cygwin dot com>
To: cygwin at cygwin dot com
Date: Tue, 20 Nov 2001 10:28:25 +0100
Subject: Re: Unix/DOS text mode?
References: <000f01c17193$e7b4c6c0$2ae61718@bdfrd1.tx.home.com>

----------------------------------------------------------------------------
----

On Tue, Nov 20, 2001 at 01:20:59AM -0600, Joshua wrote:
>     Hmm, I've noticed this difference between the PC version of vim/gvim
> versus the vim that comes with cygwin.  Using the PC version, vim/gvim
seems
> to be able to tell whether you're opening a unix file or a PC file and
> display/edit appropriately.
>
>     I tried copying my _vimrc from my PC installation to .vimrc in my home
> directory, but that doesn't do the trick.  I figured it was either a
switch
> in vimrc or something to do with the mounts themselves.  BCNU//jle

The Cygwin vim has the same ability to recognize Unix/DOS files
as the Windows native version.  After a discussion with Bram Moolenaar
he decided not to add that recognition to the vim script files
as .vimrc.  These files must be in binary mode on Cygwin regardless
of the bin/textmode of the underlying mount point.

Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Peter Buckley]

 > After a discussion with Bram Moolenaar
 > he decided not to add that recognition to the vim script files
 > as .vimrc.  These files must be in binary mode on Cygwin regardless
 > of the bin/textmode of the underlying mount point.


Looks to me like "these files must be in binary mode" are "the vim 
script files, )such) as .vimrc."

HTH,
Peter

Joshua wrote:

>     Corinna,
> 
>     Thanks for the enlightenment.  Regarding your statement, 'These files
> must be in binary mode on Cygwin regardless of the bin/textmode of the
> underlying mount point.', what files are you referring to?  I would
> understand if the Cygwin files, ie config files in /etc need to be binary,
> but are you saying that Cygwin needs to deal with all files (like
> /cygwin/c/autoexec.bat) in a binary mode?  Or could the vim packaged with
> Cygwin be set to autodetect the binary/text type?  My understanding of how
> vim/gvim worked was that it would detect the binary/text type and preserve
> the type when you edit save the file.  BCNU//jle
> 
> 
> From: Corinna Vinschen <cygwin at cygwin dot com>
> To: cygwin at cygwin dot com
> Date: Tue, 20 Nov 2001 10:28:25 +0100
> Subject: Re: Unix/DOS text mode?
> References: <000f01c17193$e7b4c6c0$2ae61718@bdfrd1.tx.home.com>
> 
> ----------------------------------------------------------------------------
> ----
> 
> On Tue, Nov 20, 2001 at 01:20:59AM -0600, Joshua wrote:
> 
>>    Hmm, I've noticed this difference between the PC version of vim/gvim
>>versus the vim that comes with cygwin.  Using the PC version, vim/gvim
>>
> seems
> 
>>to be able to tell whether you're opening a unix file or a PC file and
>>display/edit appropriately.
>>
>>    I tried copying my _vimrc from my PC installation to .vimrc in my home
>>directory, but that doesn't do the trick.  I figured it was either a
>>
> switch
> 
>>in vimrc or something to do with the mounts themselves.  BCNU//jle
>>
> 
> The Cygwin vim has the same ability to recognize Unix/DOS files
> as the Windows native version.  After a discussion with Bram Moolenaar
> he decided not to add that recognition to the vim script files
> as .vimrc.  These files must be in binary mode on Cygwin regardless
> of the bin/textmode of the underlying mount point.
> 
> Corinna
> 
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin@cygwin.com
> Red Hat, Inc.
> 
> --
> 
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 


-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 09:10:48AM -0600, Joshua wrote:
>     Corinna,
> 
>     Thanks for the enlightenment.  Regarding your statement, 'These files
> must be in binary mode on Cygwin regardless of the bin/textmode of the
> underlying mount point.', what files are you referring to?  I would
> understand if the Cygwin files, ie config files in /etc need to be binary,
> but are you saying that Cygwin needs to deal with all files (like
> /cygwin/c/autoexec.bat) in a binary mode?  Or could the vim packaged with
> Cygwin be set to autodetect the binary/text type?  My understanding of how
> vim/gvim worked was that it would detect the binary/text type and preserve
> the type when you edit save the file.  BCNU//jle

It does recognize bin/text, just not for script files as .vimrc.
These must be binmode (LF, not CRLF lineending).

Corinna

> From: Corinna Vinschen <cygwin at cygwin dot com>
> To: cygwin at cygwin dot com
> Date: Tue, 20 Nov 2001 10:28:25 +0100
> Subject: Re: Unix/DOS text mode?
> References: <000f01c17193$e7b4c6c0$2ae61718@bdfrd1.tx.home.com>
> 
> ----------------------------------------------------------------------------
> ----
> 
> On Tue, Nov 20, 2001 at 01:20:59AM -0600, Joshua wrote:
> >     Hmm, I've noticed this difference between the PC version of vim/gvim
> > versus the vim that comes with cygwin.  Using the PC version, vim/gvim
> seems
> > to be able to tell whether you're opening a unix file or a PC file and
> > display/edit appropriately.
> >
> >     I tried copying my _vimrc from my PC installation to .vimrc in my home
> > directory, but that doesn't do the trick.  I figured it was either a
> switch
> > in vimrc or something to do with the mounts themselves.  BCNU//jle
> 
> The Cygwin vim has the same ability to recognize Unix/DOS files
> as the Windows native version.  After a discussion with Bram Moolenaar
> he decided not to add that recognition to the vim script files
> as .vimrc.  These files must be in binary mode on Cygwin regardless
> of the bin/textmode of the underlying mount point.
> 
> Corinna
> 
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin@cygwin.com
> Red Hat, Inc.
> 
> --
> 
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Joshua]

    Hmm, I've noticed this difference between the PC version of vim/gvim
versus the vim that comes with cygwin.  Using the PC version, vim/gvim seems
to be able to tell whether you're opening a unix file or a PC file and
display/edit appropriately.

    I tried copying my _vimrc from my PC installation to .vimrc in my home
directory, but that doesn't do the trick.  I figured it was either a switch
in vimrc or something to do with the mounts themselves.  BCNU//jle

From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
To: AGalick at attotech dot com, cygwin at cygwin dot com
Date: Mon, 19 Nov 2001 16:34:25 -0500
Subject: Re: Unix/DOS text mode?

----------------------------------------------------------------------------
----

At 04:00 PM 11/19/2001, AGalick@attotech.com wrote:
>After an upgrade, I seem to have lost all sanity in vi(m).
>I used to see .txt files the same with notepad or vi, but
>now in vi every line ends with a blue ^M.  I've played
>with mount -[t|b] and tried [un and re]installing vim but I'm
>stumped.  The thing is, it seems to have also disabled all
>the nice search string history/recall (I guess because .viminfo
>also shows those damned ^M's).  What have I done
>or what has cygwin done?  I guess other stuff got upgraded,
>too, but I don't know what.


Try setting "fileformat=dos" in your .vimrc file if you always want
your files to be treated as a DOS text file.  See the help in vim for
more info.





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 01:20:59AM -0600, Joshua wrote:
>     Hmm, I've noticed this difference between the PC version of vim/gvim
> versus the vim that comes with cygwin.  Using the PC version, vim/gvim seems
> to be able to tell whether you're opening a unix file or a PC file and
> display/edit appropriately.
> 
>     I tried copying my _vimrc from my PC installation to .vimrc in my home
> directory, but that doesn't do the trick.  I figured it was either a switch
> in vimrc or something to do with the mounts themselves.  BCNU//jle

The Cygwin vim has the same ability to recognize Unix/DOS files
as the Windows native version.  After a discussion with Bram Moolenaar
he decided not to add that recognition to the vim script files
as .vimrc.  These files must be in binary mode on Cygwin regardless
of the bin/textmode of the underlying mount point.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[vipin aravind]

[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]

what is  the operating  system  you are on?
vipin
----- Original Message -----
From: "Joshua" <jle@post.com>
To: <cygwin@cygwin.com>
Sent: Tuesday, November 20, 2001 12:50 PM
Subject: Re: Unix/DOS text mode?


>     Hmm, I've noticed this difference between the PC version of vim/gvim
> versus the vim that comes with cygwin.  Using the PC version, vim/gvim
seems
> to be able to tell whether you're opening a unix file or a PC file and
> display/edit appropriately.
>
>     I tried copying my _vimrc from my PC installation to .vimrc in my home
> directory, but that doesn't do the trick.  I figured it was either a
switch
> in vimrc or something to do with the mounts themselves.  BCNU//jle
>
> From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
> To: AGalick at attotech dot com, cygwin at cygwin dot com
> Date: Mon, 19 Nov 2001 16:34:25 -0500
> Subject: Re: Unix/DOS text mode?
>
> --------------------------------------------------------------------------
--
> ----
>
> At 04:00 PM 11/19/2001, AGalick@attotech.com wrote:
> >After an upgrade, I seem to have lost all sanity in vi(m).
> >I used to see .txt files the same with notepad or vi, but
> >now in vi every line ends with a blue ^M.  I've played
> >with mount -[t|b] and tried [un and re]installing vim but I'm
> >stumped.  The thing is, it seems to have also disabled all
> >the nice search string history/recall (I guess because .viminfo
> >also shows those damned ^M's).  What have I done
> >or what has cygwin done?  I guess other stuff got upgraded,
> >too, but I don't know what.
>
>
> Try setting "fileformat=dos" in your .vimrc file if you always want
> your files to be treated as a DOS text file.  See the help in vim for
> more info.
>
>
>
>
>
> Larry Hall                              lhall@rfk.com
> RFK Partners, Inc.                      http://www.rfk.com
> 838 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX
>
>
>
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


[-- Attachment #2: InterScan_Disclaimer.txt --]
[-- Type: text/plain, Size: 856 bytes --]

-------------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------


[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Unix/DOS text mode?

[AGalick]

After an upgrade, I seem to have lost all sanity in vi(m).
I used to see .txt files the same with notepad or vi, but
now in vi every line ends with a blue ^M.  I've played
with mount -[t|b] and tried [un and re]installing vim but I'm
stumped.  The thing is, it seems to have also disabled all
the nice search string history/recall (I guess because .viminfo
also shows those damned ^M's).  What have I done
or what has cygwin done?  I guess other stuff got upgraded,
too, but I don't know what.

Thanks,
Albert Galick


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[Larry Hall (RFK Partners, Inc)]

At 04:00 PM 11/19/2001, AGalick@attotech.com wrote:
>After an upgrade, I seem to have lost all sanity in vi(m).
>I used to see .txt files the same with notepad or vi, but
>now in vi every line ends with a blue ^M.  I've played
>with mount -[t|b] and tried [un and re]installing vim but I'm
>stumped.  The thing is, it seems to have also disabled all
>the nice search string history/recall (I guess because .viminfo
>also shows those damned ^M's).  What have I done
>or what has cygwin done?  I guess other stuff got upgraded,
>too, but I don't know what.


Try setting "fileformat=dos" in your .vimrc file if you always want
your files to be treated as a DOS text file.  See the help in vim for
more info.





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Unix/DOS text mode?

[vipin aravind]

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

you need  set  fileformat=dos.
you  may  try removing  the ctrl-m's  like  this  too  for a session
:%s/^M//g    where  ^  is   produced  by typing  ctrl-v.
vipin
----- Original Message ----- 
From: <AGalick@attotech.com>
To: <cygwin@cygwin.com>
Sent: Tuesday, November 20, 2001 2:30 AM
Subject: Unix/DOS text mode?


> After an upgrade, I seem to have lost all sanity in vi(m).
> I used to see .txt files the same with notepad or vi, but
> now in vi every line ends with a blue ^M.  I've played
> with mount -[t|b] and tried [un and re]installing vim but I'm
> stumped.  The thing is, it seems to have also disabled all
> the nice search string history/recall (I guess because .viminfo
> also shows those damned ^M's).  What have I done
> or what has cygwin done?  I guess other stuff got upgraded,
> too, but I don't know what.
> 
> Thanks,
> Albert Galick
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 


[-- Attachment #2: InterScan_Disclaimer.txt --]
[-- Type: text/plain, Size: 856 bytes --]

-------------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------


[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/