From: Juri Linkov <juri@jurta.org>
To: rms@gnu.org
Cc: bug-gnu-emacs@gnu.org, amicitas@gmail.com
Subject: Re: I-search: Clicking in minibuf during I-search fails.
Date: Sat, 27 Oct 2007 01:43:48 +0300 [thread overview]
Message-ID: <87fxzxwlaq.fsf@jurta.org> (raw)
In-Reply-To: <E1IkybC-0004bF-Cg@fencepost.gnu.org> (Richard Stallman's message of "Thu\, 25 Oct 2007 05\:01\:54 -0400")
> The beginning of the minibuffer is the wrong position to put point,
> because the prompt is read-only, and to start editing the user needs to
> move point to the editable area. The right position is where the mouse
> was clicked,
>
> Ok, now I understand you. Indeed, that is the right position.
>
> So why does the event have the wrong position in it?
I guess this is because clicking mouse button with the code
(let ((cursor-in-echo-area t))
(read-event))
always returns an event where the buffer position is 1.
PS: I already suggested trying an alternative solution that gets rid of
using `read-event', and binds C-w to a new command in the minibuffer
for editing the search string.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2007-10-26 22:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 3:16 I-search: Clicking in minibuf during I-search fails amicitas
2007-10-10 13:55 ` Drew Adams
2007-10-10 21:03 ` Richard Stallman
[not found] ` <mailman.1937.1192050272.18990.bug-gnu-emacs@gnu.org>
2007-10-10 21:51 ` amicitas
2007-10-10 23:44 ` Juri Linkov
2007-10-12 2:46 ` Richard Stallman
2007-10-28 14:51 ` Juri Linkov
[not found] ` <mailman.1940.1192060132.18990.bug-gnu-emacs@gnu.org>
2007-10-14 23:34 ` amicitas
2007-10-19 23:52 ` Juri Linkov
2007-10-21 7:26 ` Richard Stallman
2007-10-22 0:35 ` Juri Linkov
2007-10-23 7:12 ` Richard Stallman
2007-10-23 23:52 ` Juri Linkov
2007-10-24 8:33 ` Richard Stallman
2007-10-24 21:28 ` Juri Linkov
2007-10-25 9:01 ` Richard Stallman
2007-10-26 22:43 ` Juri Linkov [this message]
2007-10-27 13:58 ` 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=87fxzxwlaq.fsf@jurta.org \
--to=juri@jurta.org \
--cc=amicitas@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=rms@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 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.