From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73743@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#73743: Auto-save dialog needs extra RET
Date: Thu, 17 Oct 2024 22:29:59 -0400 [thread overview]
Message-ID: <E1t1ckZ-0005g8-F5@fencepost.gnu.org> (raw)
In-Reply-To: <868quor4hg.fsf@gnu.org> (message from Eli Zaretskii on Wed, 16 Oct 2024 08:39:23 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > > > I notice on the dialog of emacs -nw, after lots of ^G's
> > > > Auto-save? (y or n) y
> > > > Auto-save done
> >
> > That much is normal, but
> >
> > > > [Then nothing happens, and we need to hit RET to see the next question:]
> >
> > the failure to move on to the next question seems like a bug.
> > Why is it waiting for the user to type RET?
> It doesn't. It calls read_stdin, which reads 1 byte.
We may be miscommunicating.
After "Auto-save done", it should ask the next question, right?
Why does it instead try to read a character at that point
before asking another question?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-10-18 2:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 7:09 bug#73743: Auto-save dialog needs extra RET Dan Jacobson
2024-10-11 9:16 ` Eli Zaretskii
2024-10-16 3:02 ` Richard Stallman
2024-10-16 5:39 ` Eli Zaretskii
2024-10-18 2:29 ` Richard Stallman [this message]
2024-10-18 6:11 ` Eli Zaretskii
2024-10-25 21:37 ` Dan Jacobson
2024-10-26 6:50 ` Eli Zaretskii
2024-10-26 8:22 ` Dan Jacobson
2024-10-28 4:54 ` Richard Stallman
2024-10-28 4:54 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1t1ckZ-0005g8-F5@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=73743@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.