unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 18340@debbugs.gnu.org, larsi@gnus.org
Subject: bug#18340: 24.4.50; Bad UI for `find-file-literally'
Date: Wed, 04 May 2016 18:23:51 +0300	[thread overview]
Message-ID: <83y47pj188.fsf@gnu.org> (raw)
In-Reply-To: <79aed96d-c930-4bd0-9c88-94900191071a@default> (message from Drew Adams on Wed, 4 May 2016 08:05:04 -0700 (PDT))

> Date: Wed, 4 May 2016 08:05:04 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 18340@debbugs.gnu.org
> 
> > > 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, 
> 
> What don't you understand about it?

I understood nothing beyond the example with resize-mini-windows and a
normal frame which has a minibuffer.

> > but the specific part about find-file-literally will be
> > definitely fixed by that.
> 
> I don't think so.  `resize-mini-windows' will do nothing for a
> standalone minibuffer.

Please show a recipe, as I didn't understand the problem.  Repeating
what you said the first time doesn't help.

> Again: "Don't show a multi-line message for prompting `y-or-n-p' in
> the echo area and expect users to see it."

Please let us judge what would be the best solution for problems.

> It is NOT a good idea to depend on `resize-mini-windows' showing
> all of a multi-line message.

You contradict yourself: above you said that the value of
resize-mini-windows doesn't necessarily help.

> If the code _really_ needs to interact with the user using a
> multi-line message, then `y-or-n-p' is the _wrong_ way to ask
> the question.  If users need to read multiple lines then hitting
> a single key to choose is probably not appropriate.

I don't think I agree.  I see no reason to treat single-line and
multi-line prompts differently, not without a good reason.  The fact
that there's more than one line doesn't cut it.

> This should be rethought, IMO.  If the prompt cannot reasonably
> be a single line then some other interaction should be used.
> Do not just look for a way to force minibuffer-window resizing.

Once again, please don't dictate solutions for problems.





  reply	other threads:[~2016-05-04 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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     ` bug#18340: 24.4.50; Bad UI for `find-file-literally' Drew Adams
2016-05-04 15:23       ` Eli Zaretskii [this message]
2014-08-27 21:37 Drew Adams
2016-05-04  0:59 ` Lars Ingebrigtsen
2016-05-04 14:47   ` Eli Zaretskii
2021-10-10 22:30 ` Stefan Kangas
2021-10-11  6:17   ` Juri Linkov
2021-10-11 11:41     ` Stefan Kangas

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=83y47pj188.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18340@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --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).