unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: `font-lock-add-keywords' works... sometimes
Date: Tue, 19 Mar 2019 23:22:14 +0100	[thread overview]
Message-ID: <87wokuqzc9.fsf@web.de> (raw)
In-Reply-To: <86ef72kdtb.fsf@zoho.eu> (Emanuel Berg's message of "Tue, 19 Mar 2019 17:51:28 +0100")

Emanuel Berg <moasenwood@zoho.eu> writes:

> Still, it can be interesting to understand why my identical code works
> for Message mode, but not for Text mode?

I tried to figure it out, but after reading the code, I got the
impression that it is intended to work.

> BTW what is the proper "notation" for an Emacs major mode? Personally,
> I'm all ascii with lowercase and dashes, I even do that with my file
> system, e.g. ~/tools/torque-wrench or ~/fighters/juan-manuel-marquez,
> so I'd like to denote them (the major modes) for ex "message-mode" and
> "text-mode". But in the help (.e.g., `C-h M' when I type this) it is
> "Message mode", not message-mode, so I suppose I'm technically
> incorrect.

I guess both are ok and no one cares.  Most people seem to prefer the
lowercase version.  C-h M just tries to be cool.

Some background: we have `major-mode', which is bound to a symbol naming
the mode, and the pretty version `mode-name' which specifies a string
(most of the time) to be displayed in the mode-line.  See the macro
`define-derived-mode' for example, where you specify both kinds of
names.


Michael.



  reply	other threads:[~2019-03-19 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  7:26 `font-lock-add-keywords' works... sometimes Emanuel Berg
2019-03-19 14:42 ` Michael Heerdegen
2019-03-19 16:51   ` Emanuel Berg
2019-03-19 22:22     ` Michael Heerdegen [this message]
2019-03-19 23:37       ` Emanuel Berg
2019-03-20  6:22       ` Eli Zaretskii
2019-03-21 14:25         ` Emanuel Berg
2019-03-19 16:44 ` Stefan Monnier
2019-03-19 17:04   ` Emanuel Berg
2019-03-19 22:09   ` Michael Heerdegen

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=87wokuqzc9.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@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.
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).