unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: gnu-emacs-help@gnu.org
Subject: Re: Weird capitalisation in "<mode-name> enabled in current buffer"
Date: Wed, 31 Aug 2022 18:20:04 +0200	[thread overview]
Message-ID: <87sflcl70r.fsf@gmx.net> (raw)
In-Reply-To: <87a67k63r4.fsf@fastmail.fm> (Joost Kremers's message of "Wed, 31 Aug 2022 13:34:12 +0200")

[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]

On Wed, 31 Aug 2022 13:34:12 +0200 Joost Kremers <joostkremers@fastmail.fm> wrote:

> Hi list,
>
> I "wrote" a teeny-tiny minor mode `dedicated-mode` inspired by the same-name
> mode available on Melpa. It's basically just a single line:
>
> ```
> (define-minor-mode dedicated-mode
>   "Minor mode to dedicate a window to its buffer."
>   :init-value nil :lighter " D" :global nil
>   (set-window-dedicated-p nil dedicated-mode))
> ```
>
> Now, never mind that this shouldn't be a minor mode at all, since it should be
> linked to the window, not the buffer. What's strange is that when I activate
> this mode, the message in the echo area reads:
>
> DeDicateD moDe enabled in current buffer
>
> Note the capital Ds in the words "DeDicateD moDe". Same thing happens when I
> deactivate the mode.
>
> Funny thing is, if I change the :lighter in the mode definition to lower case
> "d", the capitalisation does not happen.
>
> So, what should I file this under? Bug or joke? :D

It's due to the last line in easy-mmode-pretty-mode-name:

      ;; Replace any (case-insensitive) matches for LIGHTER in NAME
      ;; with a literal LIGHTER.  E.g., if NAME is "Iimage mode" and
      ;; LIGHTER is " iImag", then this will produce "iImage mode".
      ;; (LIGHTER normally comes from the mode-line string passed to
      ;; define-minor-mode, and normally includes at least one leading
      ;; space.)
      (replace-regexp-in-string (regexp-quote lighter) lighter name t t))))

The patch below fixes your use case but breaks the case mentioned in the
above comment.  A fix handling both cases might be tricky.

Steve Berman


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: easy-mmode patch --]
[-- Type: text/x-patch, Size: 675 bytes --]

diff --git a/lisp/emacs-lisp/easy-mmode.el b/lisp/emacs-lisp/easy-mmode.el
index c3a4e9fc7a..e70946921e 100644
--- a/lisp/emacs-lisp/easy-mmode.el
+++ b/lisp/emacs-lisp/easy-mmode.el
@@ -79,7 +79,8 @@ easy-mmode-pretty-mode-name
       ;; (LIGHTER normally comes from the mode-line string passed to
       ;; define-minor-mode, and normally includes at least one leading
       ;; space.)
-      (replace-regexp-in-string (regexp-quote lighter) lighter name t t))))
+      ;; (replace-regexp-in-string (regexp-quote lighter) lighter name t t)
+      name)))

 (defconst easy-mmode--arg-docstring
   "This is a %sminor mode.  If called interactively, toggle the

  reply	other threads:[~2022-08-31 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 11:34 Weird capitalisation in "<mode-name> enabled in current buffer" Joost Kremers
2022-08-31 16:20 ` Stephen Berman [this message]
2022-08-31 21:42   ` Joost Kremers

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=87sflcl70r.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=gnu-emacs-help@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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).