unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 33076@debbugs.gnu.org
Subject: bug#33076: 26; `read-only-mode' messages
Date: Thu, 20 Aug 2020 17:49:00 +0200	[thread overview]
Message-ID: <878se9s4gj.fsf@gnus.org> (raw)
In-Reply-To: <87zhlm2dwf.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Wed, 10 Jul 2019 15:54:40 +0200")

> This is output by the define-minor-mode machinery:
>
>            (if (called-interactively-p 'any)
>                (progn
>                  ,(if (and globalp (not variable))
>                       `(customize-mark-as-set ',mode))
>                  ;; Avoid overwriting a message shown by the body,
>                  ;; but do overwrite previous messages.
>                  (unless (and (current-message)
>                               (not (equal ,last-message
>                                           (current-message))))
>                    (let ((local ,(if globalp "" " in current buffer")))
> 		     (message ,(format "%s %%sabled%%s" pretty-name)
> 			      (if ,getter "en" "dis") local)))))
>
> So it looks easy enough to change, but it's a change that would affect
> all minor mode.  Do we want all interactive minor modes to message the
> buffer names?  I don't know what I think of it myself.
>
> Perhaps mainly because some buffer names are so long that this would
> increase the echo area sometimes, which is slightly annoying.

After thinking about this for a year, I've come to the conclusion that
this would be more annoying than informative, so I'm closing this as a
"wontfix".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2020-08-20 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 17:04 bug#33076: 26; `read-only-mode' messages Drew Adams
2019-07-10 13:54 ` Lars Ingebrigtsen
2019-07-10 14:36   ` Drew Adams
2020-08-20 15:49   ` Lars Ingebrigtsen [this message]

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=878se9s4gj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=33076@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).