all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: gsstark@mit.edu, emacs-devel@gnu.org
Subject: Re: filling inside minibuffer behaves poorly
Date: Sat, 04 Nov 2006 01:37:01 -0500	[thread overview]
Message-ID: <E1GgF9J-0003Lc-Ap@fencepost.gnu.org> (raw)
In-Reply-To: <87zmb9bci3.fsf@stark.xeocode.com> (message from Gregory Stark on 02 Nov 2006 19:27:32 -0500)

    I understand your concern and I'm sure I'm in a pretty small minority with
    this problem. But the more I think about it I can't think of any situation
    where you wouldn't want this behaviour. After all minibuffer prompts are for
    inputing text that's going _somewhere_ and the prompt isn't going to be going
    with it.

That seems like a good argument, except for one thing: in most cases
the text isn't going anywhere that you'd care about filling, so the
main purpose of filling would be to make it look nice in the
minibuffer.  And it looks nicer in the minibuffer the old way.

The appearance of the text in the minibuffer is clearly secondary to
its appearance in real use.  So if both issues arose equally often,
I'd say that the latter wins.  But what if the latter issue only
arises in a few commands, and the former can arise for all commands?
Maybe then the existing code is better.

I am not sure how to judge this, and I wonder what others think.

  reply	other threads:[~2006-11-04  6:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ejsoxlu4.fsf@enterprisedb.com>
2006-11-02 21:47 ` filling inside minibuffer behaves poorly Richard Stallman
2006-11-03  0:27   ` Gregory Stark
2006-11-04  6:37     ` Richard Stallman [this message]
2006-11-04  7:37       ` Mathias Dahl
2006-11-04 18:12       ` John S. Yates, Jr.
2006-11-05 19:22         ` Richard Stallman

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=E1GgF9J-0003Lc-Ap@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gsstark@mit.edu \
    /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.