unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: CC Mode 5.31.3
Date: Sat, 25 Feb 2006 11:37:01 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1060225102936.397A-100000@acm.acm> (raw)
In-Reply-To: <87slq8xyqv.fsf-monnier+gmane.emacs.devel@gnu.org>

Hi, Stefan!

On Fri, 24 Feb 2006, Stefan Monnier wrote:

>> The issues with the Mode Name, and minor mode flags in the mode line are
>> still unresolved.  On typing M-x smerge-mode, C Mode's flags (the "/la"
>> of "C/la") now stay with the major mode, but this is done by setting
>> mode-name to "C/la", a stop-gap solution at best.  This is ugly, and I
>> don't find it an acceptable solution..

>Could you remind me why you don't use mode-line-process?

Ignorance, mainly.  :-)  It sounds like a great idea, though.

mode-line-process appears to work fine for Emacs 2[012], but not for
XEmacs, where it is displayed to the right of the minor modes.

This variable is defined by the info it displays, not by its position in
the mode line.  It would have been nice to have the variable
`mode-right-of-name' (and even `mode-left-of-name').  It is a pity that
it is now too late to add these variables into the standard
mode-line-format and the Elisp manual.

Is there any guarantee that a buffer.c won't invoke any process (whatever
that might mean) that would overwrite mode-line-process?

>        Stefan

-- 
Alan.

       reply	other threads:[~2006-02-25 11:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87slq8xyqv.fsf-monnier+gmane.emacs.devel@gnu.org>
2006-02-25 11:37 ` Alan Mackenzie [this message]
2006-02-26 15:36   ` CC Mode 5.31.3 Stefan Monnier
2006-02-24 18:13 Alan Mackenzie
2006-02-24 18:51 ` Sean O'Rourke
2006-02-24 22:04   ` Alan Mackenzie
2006-02-26 12:10 ` Richard Stallman
2006-02-26 17:19   ` Alan Mackenzie
2006-02-27 19:01     ` Richard Stallman
2006-02-26 20:39   ` Alan Mackenzie
2006-02-27  9:07     ` Kim F. Storm
2006-02-27 15:10       ` Alan Mackenzie
2006-02-27 23:46       ` Richard Stallman
2006-02-27 14:31     ` Stefan Monnier
2006-02-27 23:47       ` Richard Stallman
2006-02-27 19:02     ` Richard Stallman
2006-02-26 12:46 ` Vivek Dasmohapatra

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=Pine.LNX.3.96.1060225102936.397A-100000@acm.acm \
    --to=acm@muc.de \
    --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).