From: Richard Stallman <rms@gnu.org>
Cc: help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: isearch doesn't seem to set mark where search began
Date: Sun, 03 Oct 2004 10:32:09 -0400 [thread overview]
Message-ID: <E1CE7PF-0002jk-AK@fencepost.gnu.org> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBKEIECGAA.drew.adams@oracle.com>
Exiting the search with C-g means it does not move.
That should not set the mark. I don't want that to change.
You say the problem arises because of a customization.
If you can suggest a clean patch that won't change the normal
behavior but improves matters with your customization, I won't object
to that.
next prev parent reply other threads:[~2004-10-03 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-02 16:34 isearch doesn't seem to set mark where search began Drew Adams
2004-10-02 20:15 ` Juri Linkov
2004-10-04 15:19 ` Richard Stallman
2004-10-03 14:32 ` Richard Stallman [this message]
2004-10-03 17:35 ` Drew Adams
2004-10-04 15:20 ` 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
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=E1CE7PF-0002jk-AK@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--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.
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).