From: Dmitry Gutov <dgutov@yandex.ru>
To: martin rudalics <rudalics@gmx.at>, Juri Linkov <juri@linkov.net>
Cc: 35887@debbugs.gnu.org, npostavs@gmail.com, Bob Proulx <bob@proulx.com>
Subject: bug#35887: 26.1; global-eldoc-mode minibuffer noise is very annoying
Date: Tue, 4 Jun 2019 16:30:35 +0300 [thread overview]
Message-ID: <1f8fc8bc-5858-c95e-f876-4020f9f43593@yandex.ru> (raw)
In-Reply-To: <2f351f60-2fbd-3ea5-1f4d-24aec7871bf3@gmx.at>
On 04.06.2019 11:21, martin rudalics wrote:
> Would you consider an application like Firefox operational if
> you launch it for the first time in your live, spin your mouse-wheel
> to find out whether there's something below the part you see on your
> screen and get a bell ringing and the information that you are at the
> end of a thing called "buffer"? Or that after selecting some text
> with the mouse you just have "Mark set"?
It almost feels like the general approach for a long time has been to
compensate the general "clunkiness" (or at least peculiarity) of some UI
corners with extra verbosity.
It's like the program is saying "it's okay if we're doing unusual
things, but we'll tell you everything we're doing along the way".
I don't find it jarring myself, but we could probably do better.
next prev parent reply other threads:[~2019-06-04 13:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 19:51 bug#35887: 26.1; global-eldoc-mode minibuffer noise is very annoying Bob Proulx
2019-05-24 20:47 ` npostavs
2019-05-24 21:35 ` Bob Proulx
2019-05-24 22:38 ` Dmitry Gutov
2019-05-24 23:24 ` Bob Proulx
2019-05-25 2:21 ` Noam Postavsky
2019-05-25 6:19 ` Eli Zaretskii
2019-05-26 11:51 ` Basil L. Contovounesios
2019-05-25 8:00 ` martin rudalics
2019-05-27 20:30 ` Juri Linkov
2019-05-27 22:31 ` Drew Adams
2019-05-28 15:54 ` Basil L. Contovounesios
2019-06-04 8:21 ` martin rudalics
2019-06-04 13:30 ` Dmitry Gutov [this message]
2019-06-05 21:06 ` Juri Linkov
2019-05-27 3:23 ` Drew Adams
2020-08-16 10:16 ` Stefan Kangas
2020-08-16 14:32 ` Drew Adams
2020-08-16 16:12 ` Kévin Le Gouguec
2020-08-16 14:39 ` Eli Zaretskii
2020-10-01 12:27 ` Stefan Kangas
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=1f8fc8bc-5858-c95e-f876-4020f9f43593@yandex.ru \
--to=dgutov@yandex.ru \
--cc=35887@debbugs.gnu.org \
--cc=bob@proulx.com \
--cc=juri@linkov.net \
--cc=npostavs@gmail.com \
--cc=rudalics@gmx.at \
/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).