unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Avoiding moving point into minibuffer prompt area
Date: Tue, 16 Aug 2005 07:23:19 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICKEMACLAA.drew.adams@oracle.com> (raw)
In-Reply-To: <200508160510.j7G5A7I06387@raven.dms.auburn.edu>

       One possible compromise, assuming there is a useful use case
       for copying prompt text, would be to permit copying it with the
mouse,
       but still inhibit moving the cursor into the prompt by command
       or keyboard.  Would that be good enough?

    That would force one to use the mouse and assumes that one has a mouse
    available.

Yes, of course. To "Would that be enough?", I guess your answer is "No".

       I note too that, by design, commands like `C-a' do not move
       into the prompt.

    That is because of field properties.  To see this, do C-x C-f,
    move into the prompt (sorry) and to C-u x =

That's the how, not the why. My point was that it is designed purposely to
prevent C-a from moving point to that beginning of the minibuffer (and a
good thing, too).

  reply	other threads:[~2005-08-16 14:23 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  1:29 Avoiding moving point into minibuffer prompt area Lennart Borgman
2005-08-16  1:53 ` Luc Teirlinck
2005-08-16  4:07   ` Drew Adams
2005-08-16  5:10     ` Luc Teirlinck
2005-08-16 14:23       ` Drew Adams [this message]
2005-08-16 14:49         ` Luc Teirlinck
2005-08-16  5:15     ` Luc Teirlinck
2005-08-16  4:13 ` Luc Teirlinck
2005-08-16  4:51   ` Drew Adams
2005-08-16 16:34     ` David Reitter
2005-08-16 17:57       ` Luc Teirlinck
2005-08-16 18:27         ` Lennart Borgman
2005-08-16 19:12           ` Luc Teirlinck
2005-08-16 21:54             ` Lennart Borgman
2005-08-16 22:09               ` Luc Teirlinck
2005-08-16 22:29                 ` Lennart Borgman
2005-08-17  3:05             ` Drew Adams
2005-08-17  3:53               ` Luc Teirlinck
2005-08-17  3:59               ` Luc Teirlinck
2005-08-17 15:52               ` Richard M. Stallman
2005-08-18  5:44                 ` Drew Adams
2005-08-16 21:34         ` David Reitter
2005-08-16 19:52     ` Randal L. Schwartz
2005-08-17  3:07       ` Drew Adams
2005-08-17  3:13         ` Randal L. Schwartz
2005-08-17  3:17           ` Drew Adams
2005-08-16 20:43     ` Richard M. Stallman
2005-08-16  9:04   ` Lennart Borgman
2005-08-16  9:59     ` Juri Linkov
2005-08-16 10:49       ` Lennart Borgman
2005-08-16 11:27         ` Juri Linkov
2005-08-16 11:46           ` Lennart Borgman
2005-08-16 20:43         ` Richard M. Stallman
2005-08-16 22:15           ` Lennart Borgman
2005-08-17 15:51             ` Richard M. Stallman
2005-08-17 16:12               ` Lennart Borgman
2005-08-18 21:15                 ` Richard M. Stallman
2005-08-18 22:46                   ` Lennart Borgman
2005-08-19 23:07                     ` Richard M. Stallman
2005-08-19 23:55                       ` Lennart Borgman
2005-08-22  5:01                         ` Richard M. Stallman
2005-08-22  5:02                         ` Richard M. Stallman
2005-08-16 20:43       ` Richard M. Stallman
2005-08-16 13:57     ` Luc Teirlinck
2005-08-16 14:15       ` Lennart Borgman
2005-08-16 18:29 ` Richard M. Stallman
2005-08-17  9:01   ` Emilio Lopes
2005-08-17 11:14     ` Lennart Borgman

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=DNEMKBNJBGPAOPIJOOICKEMACLAA.drew.adams@oracle.com \
    --to=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).