unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Dmitry Gutov <dgutov@yandex.ru>
Cc: pinkanon pinkanon <pinkanon.pinkanon@yandex.ru>, 34939@debbugs.gnu.org
Subject: bug#34939: Some minibuffer behaviour is annoying
Date: Wed, 29 May 2019 15:26:15 -0700 (PDT)	[thread overview]
Message-ID: <0501caa5-0196-45fd-8bc6-8dbb176622ce@default> (raw)
In-Reply-To: <877ea96i6t.fsf@mail.linkov.net>

> Here is a complete 1-to-1 rewrite of the C function ‘print_error_message’
> in Lisp that now can be used for more user-friendly displaying error messages
                   ^^^^^^^^^^^
> in the minibuffer

I haven't been following this thread.  But it looks
like this will use `minibuffer-message' for errors
raised during minibuffer input, and block `message',
except for logging.  Is that right?

If not, just what does this change represent?

If so, please do not do this.  We should continue to
use `message' by default - have normal error messaging,
whether the minibuffer is active or not - there's no
substitute for `message' in this context.

If a particular user wants to add this function to
`minibuffer-setup-hook' she can do so, but it should
not be the default behavior.

Your "can be used" is appropriate for a user choice.
It's not appropriate for changing the default behavior.





  reply	other threads:[~2019-05-29 22:26 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 19:13 bug#34939: Some minibuffer behaviour is annoying pinkanon pinkanon
2019-03-22 16:57 ` Dmitry Gutov
2019-03-23  2:32   ` Richard Stallman
2019-03-23  9:46     ` Dmitry Gutov
2019-03-23  9:50       ` Eli Zaretskii
2019-03-23 11:24         ` Dmitry Gutov
2019-03-23 12:18           ` pinkanon pinkanon
     [not found]       ` <<83o961q5rr.fsf@gnu.org>
2019-03-23 15:51         ` Drew Adams
2019-03-31 19:50           ` Juri Linkov
2019-03-31 19:49 ` Juri Linkov
2019-03-31 20:29   ` Juri Linkov
2019-04-01 13:08     ` Dmitry Gutov
2019-04-01 20:31       ` Juri Linkov
2019-04-01 21:53         ` Dmitry Gutov
2019-04-03 20:50           ` Juri Linkov
2019-05-19 20:16       ` Juri Linkov
2019-04-01 10:10   ` pinkanon pinkanon
2019-04-01 20:25     ` Juri Linkov
2019-04-02 18:25       ` pinkanon pinkanon
2019-04-01 13:03   ` Dmitry Gutov
2019-04-01 20:29     ` Juri Linkov
2019-04-07 20:43       ` Juri Linkov
2019-04-07 23:09         ` Dmitry Gutov
2019-04-08 19:47           ` Juri Linkov
2019-04-08 22:00             ` Drew Adams
2019-04-08 23:06               ` Dmitry Gutov
2019-04-08 23:32                 ` Drew Adams
2019-04-08 23:37                   ` Dmitry Gutov
2019-04-08 23:59                     ` Drew Adams
2019-04-09  0:11                       ` Dmitry Gutov
2019-04-09 18:26                         ` Drew Adams
2019-05-24 22:49   ` Dmitry Gutov
2019-05-27 20:15     ` Juri Linkov
2019-05-27 20:58       ` Dmitry Gutov
2019-05-29 21:53         ` Juri Linkov
2019-05-29 22:26           ` Drew Adams [this message]
2019-05-30 19:50             ` Juri Linkov
2019-05-30 21:00               ` Drew Adams
2019-05-30 21:35                 ` Juri Linkov
2019-06-03 20:27           ` Juri Linkov
2019-06-04 15:15             ` Dmitry Gutov

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=0501caa5-0196-45fd-8bc6-8dbb176622ce@default \
    --to=drew.adams@oracle.com \
    --cc=34939@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=juri@linkov.net \
    --cc=pinkanon.pinkanon@yandex.ru \
    /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).