unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Filipp Gunbin <fgunbin@fastmail.fm>, swe20144@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: editing, searching minibuffer content  [was: Feeling lost without tabs]
Date: Tue, 3 Nov 2015 08:25:06 -0800 (PST)	[thread overview]
Message-ID: <3b508437-559c-4653-aa80-185c788bb83b@default> (raw)
In-Reply-To: <m2wptzksba.fsf@fastmail.fm>

> When I started using Emacs I didn't know that I can use isearch in
> minibuffer.  When I found that possibility, things became simpler.  I
> frequently think that things like that probably should be mentioned in
> manual / tutorial somewhere near the beginning...

Yes.  It is not as well known as it could be that you can generally
edit the contents of the minibuffer.  And that includes Isearch.

There are only a few keys that have other than their usual meanings
in the minibuffer keymaps.

Unfortunately some of those few keys are commonly used for editing,
and some of them are even normally self-inserting.  They could be
(and except for `RET' _should_ be, IMO) just self-inserting in the
minibuffer also: `?', `SPC', `C-j' (newline).

(After a few decades Emacs finally allowed `SPC' to self-insert,
but only for file-name completion.)

Add to this the fact that some people use Ido or similar, which
reduces normal editing of minibuffer content even further, and
it is little wonder that many users do not realize that the
minibuffer is an editable buffer - a place where you can edit
text in many of the usual ways.



  reply	other threads:[~2015-11-03 16:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5726.1405828965.1147.help-gnu-emacs@gnu.org>
2014-07-20 14:19 ` Feeling lost without tabs Dan Espen
2014-07-20 18:11   ` Bob Proulx
2014-07-20 18:34   ` Emanuel Berg
     [not found]   ` <mailman.5777.1405879906.1147.help-gnu-emacs@gnu.org>
2014-07-20 21:44     ` Emanuel Berg
2014-07-21 17:02       ` Bob Proulx
2014-07-20 23:52     ` Dan Espen
2014-07-21 22:54       ` Emanuel Berg
2014-07-21 23:33         ` Bob Proulx
2014-07-22  2:44         ` Dan Espen
2014-07-22 21:23           ` Emanuel Berg
     [not found]         ` <mailman.5833.1405985639.1147.help-gnu-emacs@gnu.org>
2014-07-22 22:02           ` Emanuel Berg
2014-08-04  1:20             ` OT: User Interfaces (was: Feeling lost without tabs) Bob Proulx
     [not found]             ` <mailman.6530.1407115234.1147.help-gnu-emacs@gnu.org>
2014-08-04 22:10               ` Emanuel Berg
2014-07-20 18:28 ` Feeling lost without tabs Emanuel Berg
2015-11-03 14:07 ` swe20144
2015-11-03 14:21   ` Dan Espen
2015-11-03 15:22   ` Yuri Khan
2015-11-03 15:46     ` Dirk-Jan C. Binnema
2015-11-03 17:31       ` Michael Heerdegen
2015-11-03 17:47         ` Charles Philip Chan
2015-11-03 21:24           ` Michael Heerdegen
2015-11-03 15:37   ` Filipp Gunbin
2015-11-03 16:25     ` Drew Adams [this message]
2015-11-03 15:53   ` Aziz Yemloul
2015-11-03 15:56   ` Charles Philip Chan
2015-11-03 20:07   ` Bob Proulx
2015-11-03 23:48   ` Kendall Shaw

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=3b508437-559c-4653-aa80-185c788bb83b@default \
    --to=drew.adams@oracle.com \
    --cc=fgunbin@fastmail.fm \
    --cc=help-gnu-emacs@gnu.org \
    --cc=swe20144@gmail.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.
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).