colon in the mode-line

colon in the mode-line

[Juanma Barranquero]

>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?

                    /L/e/k/t/u

Re: colon in the mode-line

[Eli Zaretskii]

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

Re: colon in the mode-line

[Juanma Barranquero]

On 11/29/06, Eli Zaretskii <eliz@gnu.org> wrote:


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

That's entirely my point: the description of multibyte character
support confusingly refers to a colon that some users won't ever see.
It would be better to simply refer to the first (or leftmost,
whatever) chars of the mode line, instead of them being "before the
colon".

                    /L/e/k/t/u

Re: colon in the mode-line

[Eli Zaretskii]

> Date: Thu, 30 Nov 2006 00:05:35 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: emacs-devel@gnu.org
> 
> That's entirely my point: the description of multibyte character
> support confusingly refers to a colon that some users won't ever see.

Patches welcome; or I will fix it myself when I have time.

Re: colon in the mode-line

[Eli Zaretskii]

> Date: Thu, 30 Nov 2006 00:05:35 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: emacs-devel@gnu.org
> 
> > 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.
> 
> That's entirely my point: the description of multibyte character
> support confusingly refers to a colon that some users won't ever see.
> It would be better to simply refer to the first (or leftmost,
> whatever) chars of the mode line, instead of them being "before the
> colon".

I fixed this.

Re: colon in the mode-line

[Juanma Barranquero]

On 12/1/06, Eli Zaretskii <eliz@gnu.org> wrote:

> I fixed this.

Thanks.

                    /L/e/k/t/u