unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: colon in the mode-line
Date: Wed, 29 Nov 2006 21:01:17 +0200	[thread overview]
Message-ID: <uirgyaxhe.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0611290855o44ee8acrf271188e806fdad9@mail.gmail.com> (lekktu@gmail.com)

> Date: Wed, 29 Nov 2006 17:55:29 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> 
> >From man/mule.texi:
> 
>   The mode line indicates whether multibyte character support is enabled
>   in the current buffer.  If it is, there are two or more characters (most
>   often two dashes) before the colon near the beginning of the mode line.
>   When multibyte characters are not enabled, nothing precedes the colon
>   except a single dash.
> 
> Which colon?

>From man/screen.texi:

      The colon after @var{cs} changes to another string in some cases.
    Emacs uses newline characters to separate lines in the buffer.  Some
    files use different conventions for separating lines: either
    carriage-return linefeed (the MS-DOS convention) or just
    carriage-return (the Macintosh convention).  If the buffer's file uses
    carriage-return linefeed, the colon changes to either a backslash
    (@samp{\}) or @samp{(DOS)}, depending on the operating system.  If the
    file uses just carriage-return, the colon indicator changes to either
    a forward slash (@samp{/}) or @samp{(Mac)}.  On some systems, Emacs
    displays @samp{(Unix)} instead of the colon for files that use newline
    as the line separator.

  reply	other threads:[~2006-11-29 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 16:55 colon in the mode-line Juanma Barranquero
2006-11-29 19:01 ` Eli Zaretskii [this message]
2006-11-29 23:05   ` Juanma Barranquero
2006-11-30  4:21     ` Eli Zaretskii
2006-12-01 13:23     ` Eli Zaretskii
2006-12-01 15:12       ` Juanma Barranquero

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=uirgyaxhe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

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

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).