From: Drew Adams <drew.adams@oracle.com>
To: 18340@debbugs.gnu.org
Subject: bug#18340: 24.4.50; Bad UI for `find-file-literally'
Date: Wed, 27 Aug 2014 14:37:45 -0700 (PDT) [thread overview]
Message-ID: <9fd1f4c3-a944-4305-9eb5-9f3a877d1b8b@default> (raw)
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.
Huh? A user who sees that has no clue as to what is going on.
Beyond this design being incredibly ill-advised in general, it breaks
the use of a standalone minibuffer frame, for which
`resize-mini-windows' has no effect. In my code, for example, I do this,
where `'1on1-fit-minibuffer-frame' resizes the minibuffer frame to fit
its current contents:
(add-hook 'post-command-hook '1on1-fit-minibuffer-frame)
That of course has no effect during `read-key', which is what is used by
`y-or-n-p' (which is used by `find-file-literally').
`1on1-fit-minibuffer-frame' is also a command that increases the
minibuffer frame height by a line when it is repeated. It is bound
in the minibuffer to `C-o'. But of course that is ineffective for
something like `y-or-n-p', which does not use the minibuffer.
Please reimplement the multiple-line message and associated y-or-n
question for `find-file-literally', so that the message part is visible
somewhere outside of the echo area. Pop up a separate window for it,
show it in a tooltip, or show it any number of other reasonable ways.
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-08-15 on LEG570
Bzr revision: 117706 rgm@gnu.org-20140815043406-p5hbu97cbm7pulcn
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2014-08-27 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:37 Drew Adams [this message]
2016-05-04 0:59 ` bug#18340: 24.4.50; Bad UI for `find-file-literally' Lars Ingebrigtsen
2016-05-04 14:47 ` Eli Zaretskii
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=9fd1f4c3-a944-4305-9eb5-9f3a877d1b8b@default \
--to=drew.adams@oracle.com \
--cc=18340@debbugs.gnu.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).