From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 8180@debbugs.gnu.org
Subject: bug#8180: 24.0.50; verbose, confusing y-or-n-p prompts in `find-file-no-select'
Date: Sun, 01 May 2016 21:14:42 +0300 [thread overview]
Message-ID: <83k2jdmyr1.fsf@gnu.org> (raw)
In-Reply-To: <87lh3tzml6.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 01 May 2016 19:59:01 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 01 May 2016 19:59:01 +0200
> Cc: 8180@debbugs.gnu.org
>
> > "The file maybe-a-very-long-file-name.jpg is already visited literally,
> > meaning no coding system decoding, format conversion, or local variables.
> > You have asked to visit it normally,
> > but Emacs can only visit a file in one way at a time.
> >
> > Do you want to revisit the file normally now? (y or n) "
> >
> > That is _ridiculously_ long and confusing. It is horribly user
> > unfriendly. `find-file-noselect' is now filled to the gills with such
> > gobbledygook prompts, each more twisted and verbose than the next.
>
> I don't think it's gobbledygook. You only get a prompt like that if
> you've previously visited a file literally, and then you probably know
> what that is, because just about the only way to get such a buffer is by
> using the `M-x find-file-literally' command.
The prompt used to be just
"Save file and revisit non-literally? "
but it was enhanced (by Richard, no less), to make it more explicit
and clear.
> So I don't see anything to fix here. Closing.
I agree.
prev parent reply other threads:[~2016-05-01 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 15:16 bug#8180: 24.0.50; verbose, confusing y-or-n-p prompts in `find-file-no-select' Drew Adams
2011-03-06 0:12 ` Chong Yidong
2016-04-28 10:14 ` Lars Ingebrigtsen
2016-04-28 13:41 ` Drew Adams
2016-05-01 17:59 ` Lars Ingebrigtsen
2016-05-01 18:14 ` Eli Zaretskii [this message]
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=83k2jdmyr1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8180@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 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.