From: "Stephan Stahl" <stahl@eos.franken.de>
Cc: stahl@eos.franken.de, emacs-devel@gnu.org, rms@gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: M-x compile should tell its status (a little bit better)..
Date: Wed, 14 Jul 2004 08:55:08 +0200 (CEST) [thread overview]
Message-ID: <46068.217.194.34.123.1089788108.squirrel@wwws.franken.de> (raw)
In-Reply-To: <x54qobcts9.fsf@lola.goethe.zz>
Hi David.
David Kastrup said:
> Richard Stallman <rms@gnu.org> writes:
>
>> This would do no harm, but mode-name is always supposed to be a string.
>
> Oooh. I am moping because in AUCTeX, I was thinking of having a few
> "flags" attached to the mode-name, so that I can have a mode-name
> something like
>
> '((TeX-use-pdftex "PDF") TeX-base-mode-name (TeX-source-specials "^"))
>
> where the actual name is automatically composed from a few `lighters'
> that would look pretty foolish anywhere else.
>
> So may be I need to hand-construct mode-name after all.
I have seen that cc-mode has something similar. (c-toggle-hungry-state and
c-toggle-auto-state). It adds /h or /a or /ah to the mode name if they are
activated. It does so by adding
(c-auto-hungry-string c-auto-hungry-string)
to minor-mode-alist. I think AUCTeX could do the same?
Well actually the docs to cc-mode are not 100% correct. It says:
The state of the minor modes is always reflected in the minor mode
list on the modeline of the CC Mode buffer. When auto-newline mode is
enabled, you will see `C/a' on the mode line(1). When hungry delete
mode is enabled you will see `C/h' and if both modes were enabled, you'd
see `C/ah'.
I do however NOT see 'C/ah' in the mode line but 'C Outl o^o/ah'. cc-mode
should maybe append (c-auto-hungry-string c-auto-hungry-string) to the
front of minor-mode-alist? Then it would look like the docs say..
Stephan
--
Stephan Stahl
next prev parent reply other threads:[~2004-07-14 6:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 6:15 M-x compile should tell its status (a little bit better) Stephan Stahl
2004-04-22 17:40 ` Richard Stallman
2004-04-22 18:54 ` Stephan Stahl
2004-04-24 14:27 ` Richard Stallman
2004-04-23 18:01 ` Kevin Rodgers
2004-04-23 21:48 ` Stephan Stahl
2004-04-27 16:43 ` Kevin Rodgers
2004-04-29 18:13 ` Stephan Stahl
2004-04-29 19:44 ` Stefan Monnier
2004-07-11 1:43 ` Stephan Stahl
[not found] ` <E1Bjnft-0008Qk-JH@fencepost.gnu.org>
[not found] ` <61133.217.194.34.123.1089623439. squirrel@wwws.franken.de>
[not found] ` <61133.217.194.34.123.1089623439.squirrel@wwws.franken.de>
2004-07-12 16:16 ` Stephan Stahl
2004-07-12 17:20 ` Stefan Monnier
2004-07-14 0:18 ` Richard Stallman
2004-07-14 0:32 ` David Kastrup
2004-07-14 6:55 ` Stephan Stahl [this message]
2004-07-14 8:44 ` David Kastrup
2004-07-14 9:38 ` Stephan Stahl
2004-07-14 13:23 ` Kim F. Storm
2004-07-15 13:17 ` Richard Stallman
2004-07-14 14:08 ` Stefan
2004-07-15 13:17 ` Richard Stallman
2004-04-25 18:09 ` Richard Stallman
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=46068.217.194.34.123.1089788108.squirrel@wwws.franken.de \
--to=stahl@eos.franken.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).