From: James D <nospam@please.no>
Subject: Re: mode-line in emacs
Date: Wed, 28 May 2003 00:48:17 -0300 [thread overview]
Message-ID: <bb1bi402ubn@enews4.newsguy.com> (raw)
In-Reply-To: vfhe7gxpz7.fsf@rpc71.cs.man.ac.uk
Phillip Lord wrote:
>>>>>> "James" == James D <nospam@please.no> writes:
>
> James> Can someone explain what those end-of-line (dos, unix, mac,
> James> undecided) annotations in emacs mode-line mean? Let me put it
> James> more clearly: I know LF is the separation of lines convention
> James> for unix, CR for mac and CRLF for dos (CR=carriage return,
> James> LF=line feed) but still it is not obvious to me what exactly
> James> they mean and how they affect my files. I am writing a little
> James> book using LaTeX and some of my files are marked dos, others
> James> unix. Is the final output influenced by these options? Are
> James> they really options? How can I change them? Please educate
> James> me. Thanks James D
>
>
> They reflect the current status of the file. They are not shown in the
> line endings are the default for the system (so unix does not show on
> a emacs running under unix, dos does not show on windows).
>
> So if some of your files show "unix" and some show "dos" you are
> presumably using a mac?
Pardon me, I should have been more precise. I am using linux --when I say
some of my files show "unix" I actually mean ":", some of them may have
been created in a windows machine, though.
- - -
> You probably want to find out why this is happening. Emacs will
> generally cope, but having inconsistent file endings can cause havoc
> with some applications.
>
> Phil
I followed the instructions by Kai Großjohann (thank you Kai) and now all my
files have the unix line-endings. I think I understand a little better now,
Thank you guys.
James D
next prev parent reply other threads:[~2003-05-28 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 16:59 mode-line in emacs James D
2003-05-27 17:24 ` Phillip Lord
2003-05-28 3:48 ` James D [this message]
2003-05-27 18:45 ` Kai Großjohann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb1bi402ubn@enews4.newsguy.com \
--to=nospam@please.no \
/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).