unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Peter Dyballa <Peter_Dyballa@Web.DE>,
	Bostjan Vilfan <bjvilfan@gmail.com>
Cc: Emacs Help <help-gnu-emacs@gnu.org>
Subject: RE: automatic selection during search
Date: Wed, 25 Sep 2013 08:22:12 -0700 (PDT)	[thread overview]
Message-ID: <9de72fc9-c6e9-4715-8e01-a72e47e00e07@default> (raw)
In-Reply-To: <AEC938A1-80DA-405A-BF2A-3234E93472FE@Web.DE>

> > Does anyone know how to avoid this unwanted selection?
> 
> Don't press C-SPACE or C-@ or C-INSERT before pressing C-s!

And if you are not hitting such a key before using `C-s', then it's
likely that something in your init file (~/.emacs) is causing this.
It should not happen if you start Emacs without your init file:
`emacs -Q'.

If there is no such problem with `emacs -Q' then bisect your init file
recursively until you locate the culprit code: comment out half of it,
then 1/4, then 1/8,... until you narrow it down.  You can use command
`comment-region' to comment and uncomment (with `C-u') the region.
(I bind it to `C-;'.)



  reply	other threads:[~2013-09-25 15:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  6:38 automatic selection during search Bostjan Vilfan
2013-09-25 14:52 ` Peter Dyballa
2013-09-25 15:22   ` Drew Adams [this message]
2013-09-26  3:51   ` Yuri Khan
2013-09-26  8:38     ` Peter Dyballa
2013-09-26  9:08       ` Tassilo Horn
     [not found]       ` <mailman.2906.1380186548.10748.help-gnu-emacs@gnu.org>
2013-09-26 14:46         ` Barry Margolin
     [not found]           ` <mailman.2924.1380210221.10748.help-gnu-emacs@gnu.org>
2013-09-26 17:17             ` Barry Margolin
     [not found]               ` <mailman.2941.1380216751.10748.help-gnu-emacs@gnu.org>
2013-09-26 18:53                 ` Barry Margolin
     [not found]             ` <<barmar-B00378.13172226092013@news.eternal-september.org>
2013-09-26 17:32               ` Drew Adams
2013-09-26 18:44           ` Peter Dyballa
     [not found]         ` <<barmar-A2B1E2.10465526092013@news.eternal-september.org>
2013-09-26 15:43           ` Drew Adams
2013-09-26 16:01             ` Yuri Khan
2013-09-26 17:27               ` Stefan Monnier
     [not found]   ` <mailman.2894.1380167482.10748.help-gnu-emacs@gnu.org>
2013-09-30 19:59     ` Kai Grossjohann
2013-09-30 20:05       ` Barry Margolin
2013-10-01  3:56         ` Yuri Khan
2013-10-01 12:47           ` Stefan Monnier
2013-09-25 15:40 ` Eli Zaretskii
     [not found] ` <mailman.2858.1380123666.10748.help-gnu-emacs@gnu.org>
2013-09-25 15:51   ` Barry Margolin
     [not found] <<CAAm34zryY6rrua7nQGHXAgHvofjTkOob9Eet9t9LcJ=Xw2bZ5A@mail.gmail.com>
     [not found] ` <<83a9j0hptk.fsf@gnu.org>
2013-09-25 16:25   ` Drew Adams
     [not found] <mailman.2845.1380113901.10748.help-gnu-emacs@gnu.org>
2013-09-27  6:26 ` bjvilfan
2013-09-27 15:20   ` Drew Adams

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=9de72fc9-c6e9-4715-8e01-a72e47e00e07@default \
    --to=drew.adams@oracle.com \
    --cc=Peter_Dyballa@Web.DE \
    --cc=bjvilfan@gmail.com \
    --cc=help-gnu-emacs@gnu.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.
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).