From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>, Kevin Foley <kevin@kevinjfoley.me>
Cc: 44202@debbugs.gnu.org
Subject: bug#44202: [PATCH] Add variable to control confirmation of help-mode-revert-buffer
Date: Tue, 17 Nov 2020 05:04:29 -0800 [thread overview]
Message-ID: <CADwFkmnkBez=4yXmgiFJ7bF4eXTs6x5xjZ5KhUmSHGZAbDjCEg@mail.gmail.com> (raw)
In-Reply-To: <87lffsruwg.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> So I've just removed the prompting in *Help* unconditionally on the
> trunk now.
I like this change. But I have now run into the scenario where I type
`g' to see the new value of a variable (where I expected a change) and
nothing seemed to happen. The problem, of course, was that the value of
the variable did not change as I expected.
For me, this is fine, but I think this risks being confusing to
beginners. And now I'm starting to think that perhaps this is why the
prompt was added in the first place.
So I wonder if it would perhaps make sense to show a message when the
buffer is reverted? That way the user will get at least some feedback.
next prev parent reply other threads:[~2020-11-17 13:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 20:25 bug#44202: [PATCH] Add variable to control confirmation of help-mode-revert-buffer Kevin Foley
2020-10-24 23:40 ` Drew Adams
2020-10-25 0:01 ` Stefan Kangas
2020-10-25 13:39 ` Kevin Foley
2020-10-25 13:50 ` Lars Ingebrigtsen
2020-10-25 14:47 ` Kevin Foley
2020-10-25 16:50 ` Lars Ingebrigtsen
2020-10-25 18:42 ` Stefan Kangas
2020-10-25 20:08 ` Kevin Foley
2020-10-26 10:22 ` Lars Ingebrigtsen
2020-10-26 14:59 ` Stefan Kangas
2020-10-26 22:05 ` Kevin Foley
2020-10-27 7:27 ` Lars Ingebrigtsen
2020-11-17 13:04 ` Stefan Kangas [this message]
2020-11-24 5:26 ` Lars Ingebrigtsen
2020-11-24 15:57 ` Stefan Kangas
2020-11-25 7:01 ` Lars Ingebrigtsen
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='CADwFkmnkBez=4yXmgiFJ7bF4eXTs6x5xjZ5KhUmSHGZAbDjCEg@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=44202@debbugs.gnu.org \
--cc=kevin@kevinjfoley.me \
--cc=larsi@gnus.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.
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).