From: "Joshua" <jle@post.com>
To: <cygwin@cygwin.com>
Subject: Re: Unix/DOS text mode?
Date: Mon, 12 Nov 2001 10:38:00 -0000 [thread overview]
Message-ID: <000f01c17193$e7b4c6c0$2ae61718@bdfrd1.tx.home.com> (raw)
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/
next reply other threads:[~2001-11-20 7:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 10:38 Joshua [this message]
2001-11-12 13:38 ` Corinna Vinschen
2001-11-13 4:38 ` vipin aravind
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 6:05 AGalick
2001-11-29 11:20 ` AGalick
2001-11-15 2:55 Joshua
2001-11-15 3:19 ` Michael Schaap
2001-11-15 3:46 ` Michael Schaap
2001-11-15 3:47 ` Michael Schaap
2001-11-22 14:33 ` Michael Schaap
2001-11-15 3:50 ` Corinna Vinschen
2001-11-15 3:53 ` Michael Schaap
2001-11-22 14:52 ` Michael Schaap
2001-11-22 14:45 ` Corinna Vinschen
2001-11-22 14:30 ` Michael Schaap
2001-11-22 14:05 ` Michael Schaap
2001-11-22 11:07 ` Joshua
2001-11-13 12:13 Joshua
2001-11-14 1:10 ` Corinna Vinschen
2001-11-14 4:35 ` Bjoern Kahl AG Resy
2001-11-14 5:50 ` Corinna Vinschen
2001-11-21 2:17 ` Corinna Vinschen
2001-11-21 1:43 ` Bjoern Kahl AG Resy
2001-11-13 6:34 Joshua
2001-11-13 6:40 ` Peter Buckley
2001-11-13 6:59 ` Corinna Vinschen
2001-11-12 3:14 AGalick
2001-11-12 5:42 ` Larry Hall (RFK Partners, Inc)
2001-11-12 13:47 ` vipin aravind
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000f01c17193$e7b4c6c0$2ae61718@bdfrd1.tx.home.com' \
--to=jle@post.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).