unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
To: Austin Clements <amdragon@mit.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] Save and restore point explicitly in `notmuch-wash-toggle-invisible-action'.
Date: Wed, 25 May 2011 03:00:43 +0400	[thread overview]
Message-ID: <87y61vpuuc.fsf@gmail.com> (raw)
In-Reply-To: <BANLkTi=_PszwPDRbRxVpVhkT=YRAi5dGDQ@mail.gmail.com>

On Tue, 24 May 2011 18:43:41 -0400, Austin Clements <amdragon@mit.edu> wrote:
> On Tue, May 24, 2011 at 6:16 PM, Dmitry Kurochkin
> <dmitry.kurochkin@gmail.com> wrote:
> > When a user clicks the button, the cursor is somewhere inside the old
> > label.  If we save the point as a marker, after step 3 it would end up
> > at the position where the old label was.  If the new label is inserted
> > before the old one, that means after the new label.  So the cursor jumps
> > from inside the button to the position after the button.  Since the new
> > button is placed at the same position where the old one was, restoring
> > the point to the same offset it was at the beginning works as we need.
> 
> Saving point this way is a bit dangerous, though.  For example, if
> you're near the end of the buffer and shorten the label, attempting to
> restore the point could result in an error (or, a more benign example:
> the cursor could wind up outside the label so pressing RET repeatedly
> won't toggle it).
> 
> Unfortunately, I don't know of a clean solution to this, but I think I
> would rather the cursor move, but stay within the label (probably
> moving to the beginning), than have problems like the above.

Good point.  I will send an amended patch that moved to min(old-pos,
new-button-end - 1).  This leaves the cursor in place when possible and
avoids problems with out-of-bounds position (assuming the label is not
empty).

Regards,
  Dmitry

  parent reply	other threads:[~2011-05-24 23:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-22 18:57 [PATCH 1/3] Use different labels for wash buttons when text is visible or hidden Dmitry Kurochkin
2011-05-22 18:57 ` [PATCH 2/3] test: fix expected output for emacs tests after the wash button label changes Dmitry Kurochkin
2011-05-22 18:57 ` [PATCH 3/3] test: add test for hiding/showing signature in notmuch-show view Dmitry Kurochkin
2011-05-23 15:29 ` [PATCH] Save and restore point explicitly in `notmuch-wash-toggle-invisible-action' Dmitry Kurochkin
2011-05-24 20:20   ` Carl Worth
2011-05-24 20:43     ` Dmitry Kurochkin
2011-05-24 22:01       ` Carl Worth
2011-05-24 22:16         ` Dmitry Kurochkin
2011-05-24 22:22           ` Carl Worth
2011-05-24 22:43           ` Austin Clements
2011-05-24 22:57             ` Carl Worth
2011-05-24 23:00             ` Dmitry Kurochkin [this message]
2011-05-24 23:02               ` Dmitry Kurochkin
2011-05-24 23:20             ` Carl Worth
2011-05-24 23:27               ` Dmitry Kurochkin
2011-05-24 23:36                 ` Carl Worth

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y61vpuuc.fsf@gmail.com \
    --to=dmitry.kurochkin@gmail.com \
    --cc=amdragon@mit.edu \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).