unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: 23079@debbugs.gnu.org
Cc: jonas@bernoul.li
Subject: bug#23079: 25.0.92; Movement commands leave cursor in invisible line
Date: Mon, 21 Mar 2016 21:26:10 +0100	[thread overview]
Message-ID: <87fuvj7f31.fsf@web.de> (raw)
In-Reply-To: <87oaa77fev.fsf@web.de> (Michael Heerdegen's message of "Mon, 21 Mar 2016 21:19:04 +0100")

Hi,

I forgot to CC Jonas who cares about the bug in Magit.


Michael Heerdegen <michael_heerdegen@web.de> writes:

> Hello,
>
> I try to give a recipe resembling a bug in Magit concerning hidden lines
> and cursor movement.  In some buffer (emacs -Q) do
>
>
>   (insert "111" "\n222\n"
>           (propertize "333\n444\n\n" 'invisible t)
>           "555\n666\n")
>
> and move around with C-n, C-p.  Then the cursor will appear over the
> first "5" but point is actually located inside the invisible area.  This
> is the cause of our trouble.
>
> (setq line-move-visual t) helps, but setting (setq goal-column 0) makes
> it appear again.
>
> For reference, this is the original report in Magit (including
> screenshots):
>
>   https://github.com/magit/magit/issues/2592
>
>
> Thanks,
>
> Michael.
>
>
>
> In GNU Emacs 25.0.92.11 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
>  of 2016-03-21 built on drachen
> Repository revision: 76ef52267cf887e3e1aa6d25b3b16dd0601dd459
> Windowing system distributor 'The X.Org Foundation', version 11.0.11802000
> System Description:	Debian GNU/Linux testing (stretch)
>
> Configured features:
> XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND DBUS GSETTINGS NOTIFY
> LIBXML2 FREETYPE XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11





  reply	other threads:[~2016-03-21 20:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 20:19 bug#23079: 25.0.92; Movement commands leave cursor in invisible line Michael Heerdegen
2016-03-21 20:26 ` Michael Heerdegen [this message]
2016-03-21 21:11 ` Stefan Monnier
2016-03-21 22:29   ` Michael Heerdegen
2016-03-22  1:27     ` Stefan Monnier
2016-03-22 16:02       ` Michael Heerdegen
2016-03-22 16:16         ` Stefan Monnier
2016-03-22 16:48           ` Michael Heerdegen
2016-03-23  1:59             ` Stefan Monnier
2016-03-23  3:41               ` Eli Zaretskii
2016-03-23 11:23                 ` Stefan Monnier
2016-03-23 15:12                   ` Michael Heerdegen
2016-03-24  2:07                     ` Michael Heerdegen
2016-03-24 21:32                       ` Michael Heerdegen
2016-03-24 22:01                         ` Stefan Monnier
2016-03-25 11:42                           ` Jonas Bernoulli
2016-03-25 13:53                             ` Eli Zaretskii
2016-03-26 10:21                               ` Jonas Bernoulli
2016-03-21 22:54   ` Michael Heerdegen
2020-08-15  4:22   ` Stefan Kangas
2020-10-01 12:26     ` Stefan Kangas

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=87fuvj7f31.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=23079@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    /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).