unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problem binding mouse-1 to Info-mouse-follow-nearest-node
Date: Mon, 11 Apr 2011 17:53:31 +0200	[thread overview]
Message-ID: <4DA323FB.8010302@gmx.at> (raw)
In-Reply-To: <83zknwrgds.fsf@gnu.org>

 >> Could you reproduce the behavior I described on your machine?
 >
 > I couldn't try that where I wrote the previous message, but I can
 > now.  Yes, I see it.  And no, it wasn't introduced after the lex-bind
 > merge, because I see it in revision 103755 (I happen to have a binary
 > for that revision in one of my branches).

For some reason I must have missed it all the time.

 > The immediate problem which triggers the error is that deactivate-mark
 > is called after Info-mouse-follow-nearest-node already changed the
 > node displayed in the *info* buffer, which involves narrowing the
 > buffer to a different range of character positions, and that causes
 > the region to reference the portion of the buffer outside the current
 > restriction.

We could simply try doing

(buffer-substring-no-properties
  (max (region-beginning) (point-min))
  (min (region-end) (point-max)))

in `deactivate-mark'.  But I have no idea how the region should be
defined when it's not entirely within the accessible portion of a
buffer.

martin



  reply	other threads:[~2011-04-11 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  9:35 Problem binding mouse-1 to Info-mouse-follow-nearest-node martin rudalics
2011-04-11  9:46 ` Eli Zaretskii
2011-04-11 12:36   ` martin rudalics
2011-04-11 13:44     ` Juanma Barranquero
2011-04-11 14:50     ` Eli Zaretskii
2011-04-11 15:53       ` martin rudalics [this message]
2011-04-11 16:59         ` Eli Zaretskii

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=4DA323FB.8010302@gmx.at \
    --to=rudalics@gmx.at \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).