From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18340@debbugs.gnu.org
Subject: bug#18340: 24.4.50; Bad UI for `find-file-literally'
Date: Wed, 04 May 2016 17:47:26 +0300 [thread overview]
Message-ID: <83futxkhhd.fsf@gnu.org> (raw)
In-Reply-To: <877ffazlhj.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 04 May 2016 02:59:36 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 04 May 2016 02:59:36 +0200
> Cc: 18340@debbugs.gnu.org
>
> Drew Adams <drew.adams@oracle.com> writes:
>
> > Summary: Don't show a multi-line message for prompting `y-or-n-p'
> > in the echo area and expect users to see it.
> >
> > The UI for `find-file-literally' depends on `resize-mini-windows' being
> > non-nil. Not a good idea. To see how bad it can be, set
> > `resize-mini-windows' to nil, then visit a file, then try to visit it
> > using `M-x find-file-literally'. You see only this line in the echo
> > area, which is not even a question:
> >
> > The file foo.el is already visited normally.
>
> We should perhaps consider obsoleting `resize-mini-windows'. Emacs has
> many prompts now that don't make sense in a single line.
Those prompts should bind resize-mini-windows non-nil.
I don't understand the rest of the bug report, but the specific part
about find-file-literally will be definitely fixed by that.
next prev parent reply other threads:[~2016-05-04 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:37 bug#18340: 24.4.50; Bad UI for `find-file-literally' Drew Adams
2016-05-04 0:59 ` Lars Ingebrigtsen
2016-05-04 14:47 ` Eli Zaretskii [this message]
2021-10-10 22:30 ` Stefan Kangas
2021-10-11 1:06 ` bug#18340: [External] : " Drew Adams
2021-10-11 11:57 ` Eli Zaretskii
2021-10-11 6:17 ` Juri Linkov
2021-10-11 11:41 ` Stefan Kangas
[not found] <<9fd1f4c3-a944-4305-9eb5-9f3a877d1b8b@default>
[not found] ` <<877ffazlhj.fsf@gnus.org>
[not found] ` <<83futxkhhd.fsf@gnu.org>
2016-05-04 15:05 ` Drew Adams
2016-05-04 15:23 ` Eli Zaretskii
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=83futxkhhd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18340@debbugs.gnu.org \
--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).