unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8180@debbugs.gnu.org
Subject: bug#8180: 24.0.50; verbose, confusing y-or-n-p prompts in `find-file-no-select'
Date: Thu, 28 Apr 2016 12:14:49 +0200	[thread overview]
Message-ID: <87bn4uqbty.fsf@gnus.org> (raw)
In-Reply-To: <435FEA4267C54CB2B558397723E571FE@us.oracle.com> (Drew Adams's message of "Sat, 5 Mar 2011 07:16:35 -0800")

"Drew Adams" <drew.adams@oracle.com> writes:

> There are several `y-or-n-p' prompts in `find-file-no-select' that are
> very long (e.g. 6 lines!) and confusing.  Some other (alternative)
> user interaction should be found for this.  Either just a short prompt
> or, if it is important to convey some background info, then also pop
> up an informative window for that.  But do not try to provide such
> info in the prompt.

[...]

> "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.

`find-file-no-select' doesn't exist, and `find-file-noselect' isn't a
command...  Are you referring to `find-file-literally'?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2016-04-28 10: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 [this message]
2016-04-28 13:41   ` Drew Adams
2016-05-01 17:59 ` Lars Ingebrigtsen
2016-05-01 18:14   ` 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=87bn4uqbty.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=8180@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).