unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: monnier@iro.umontreal.ca
Cc: 17777@debbugs.gnu.org
Subject: bug#17777: [Emacs-diffs] emacs-24 r117241: Fix bug #17777 with	keyboard macros and visual-order cursor movement.
Date: Mon, 16 Jun 2014 22:40:35 +0300	[thread overview]
Message-ID: <83d2e8ve18.fsf@gnu.org> (raw)
In-Reply-To: <83sin6up76.fsf@gnu.org>

> Date: Sun, 15 Jun 2014 19:12:29 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 17777@debbugs.gnu.org
> 
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Cc: 17777@debbugs.gnu.org
> > Date: Sun, 15 Jun 2014 00:14:06 -0400
> > 
> > >> >    if (w->window_end_valid
> > >> > +      && NILP (Vexecuting_kbd_macro)
> > >> >        && !windows_or_buffers_changed
> > >> >        && b
> > >> >        && !b->clip_changed
> > >> NILP (Vexecuting_kbd_macro) seems like a workaround.
> > > It isn't.
> > >> Why can't the glyph matrix be used in this case?
> > > Because cursor position is not up-to-date in that case.
> > >> I means which part of the glyph matrix is wrong in the OP's recipe
> > >> (since this makes no change to the buffer)?
> > > The cursor position.
> > 
> > But that can occur even without executing kbd macros, no?
> 
> Not sure what you mean by that.

I think I know now what you meant, and I found a better solution for
the problem (r117250 on the emacs-24 branch).  I hope you will like
it.





  reply	other threads:[~2014-06-16 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1WvlrC-0007Ya-Lc@vcs.savannah.gnu.org>
2014-06-14 21:06 ` bug#17777: [Emacs-diffs] emacs-24 r117241: Fix bug #17777 with keyboard macros and visual-order cursor movement Stefan Monnier
2014-06-15  2:47   ` Eli Zaretskii
2014-06-15  4:14     ` Stefan Monnier
2014-06-15 16:12       ` Eli Zaretskii
2014-06-16 19:40         ` Eli Zaretskii [this message]
2014-06-16 21:50           ` Stefan Monnier
2014-06-16 21:28         ` Stefan Monnier
2014-06-17  2:46           ` 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=83d2e8ve18.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17777@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).