unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: schwab@linux-m68k.org
Cc: 13277-done@debbugs.gnu.org
Subject: bug#13277: 24.2.91; -nw display bug with overlay-arrow
Date: Thu, 27 Dec 2012 19:32:33 +0200	[thread overview]
Message-ID: <83sj6rmmdq.fsf@gnu.org> (raw)
In-Reply-To: <83fw2unedh.fsf@gnu.org>

> Date: Tue, 25 Dec 2012 21:03:22 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 13277@debbugs.gnu.org
> 
> > From: Andreas Schwab <schwab@linux-m68k.org>
> > Date: Tue, 25 Dec 2012 19:13:44 +0100
> > 
> > This is a regression from emacs 23, already present in 24.1:
> > 
> > $ cat bug.el
> > (set (make-local-variable 'overlay-arrow-string) "=>")
> > (set (make-local-variable 'overlay-arrow-position) (point-marker))
> > ;;(setq truncate-lines t)
> > (insert-char ?- (window-width))
> > (goto-char (point-min))
> > $ emacs -nw -l ./bug.el
> > 
> > The cursor is placed at the right margin.  Either moving forward two
> > characters or deleting one character (so that the line fits in the
> > window) puts the cursor after the arrow, where it belongs.
> 
> It's a consequence of the bidirectional display, under which we can no
> longer assume that, if point is at position P, and that position is
> not visible, the cursor should be put on the first visible glyph whose
> position is >= P.  (In this case, the first 2 characters are obscured
> by the overlay arrow, and don't appear on the line.)

Should be fixed in revision 111082 on the emacs-24 branch.  (The fix
is a simple one-liner, and is so obviously correct that it can only
cause problems if it exposes another bug, so I think it's appropriate
for the branch.)





      reply	other threads:[~2012-12-27 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-25 18:13 bug#13277: 24.2.91; -nw display bug with overlay-arrow Andreas Schwab
2012-12-25 19:03 ` Eli Zaretskii
2012-12-27 17:32   ` Eli Zaretskii [this message]

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=83sj6rmmdq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13277-done@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).