all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark Mynsted <mmynsted_news@gbronline.com>
Subject: Re: After cvs, emacs does not encode file correctly as dos
Date: 16 Sep 2002 08:07:50 -0500	[thread overview]
Message-ID: <m21y7unkux.fsf@mmynsted.corp.vha.com> (raw)
In-Reply-To: vafr8g2gdje.fsf@lucy.cs.uni-dortmund.de

>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

 Kai> Mark Mynsted <mmynsted_news@gbronline.com> writes:
 >> I have a file called notes.txt.  It has DOS style line endings etc.
 >> It is stored under linux.  When I view it from Emacs all was well,
 >> i.e. Emacs correctly identified it as a DOS file and used the dos
 >> encoding when visiting the file.  (I need the file to have the dos
 >> line endings, etc.)  I next started to manage the file using CVS.  Now
 >> the only way I can get Emacs to visit the file and display the line
 >> endings, etc, correctly is to:
 >> 
 >> C-x <RET>c dos<RET>C-x C-f ~/doc/notes.txt 

 Kai> What happens when you visit it normally, without C-x RET c?

The file is filled with ^M characters.  If I query the current coding
system, via M-x describe-current-coding-system  I get:

  - -- undecided-unix

 Kai> Note that CVS might frob line endings.

Is that what is happening?  Is there something I can do?

-- 
-MM
I rarely read email from this address          /"\
because of spam.                               \ /     ASCII Ribbon Campaign
I MAY see it if you put #NOTSPAM#               X      Against HTML Mail
in the subject line.                           / \

  reply	other threads:[~2002-09-16 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 13:41 After cvs, emacs does not encode file correctly as dos Mark Mynsted
2002-09-10 13:49 ` Kai Großjohann
2002-09-16 13:07   ` Mark Mynsted [this message]
2002-09-16 13:54     ` Kai Großjohann
2002-09-17 12:44       ` Mark Mynsted
2002-09-17 13:17         ` Stefan Monnier <foo@acm.com>
2002-09-18 12:46           ` Mark Mynsted

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=m21y7unkux.fsf@mmynsted.corp.vha.com \
    --to=mmynsted_news@gbronline.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.