unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: `vertical-motion', `goto-line' set point to invisible text
Date: Sat, 09 Jul 2011 17:13:21 +0400	[thread overview]
Message-ID: <87fwmf38cu.fsf@gmail.com> (raw)
In-Reply-To: <E1Qe0V5-0000eI-0n@fencepost.gnu.org>

On Tue, 05 Jul 2011 03:56:55 -0400, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
> > Cc: emacs-devel@gnu.org
> > Date: Tue, 05 Jul 2011 07:52:09 +0400
> > 
> >   (progn (switch-to-buffer "test")
> >          (insert "aline1\nbline2\ncline3\n")
> >          (put-text-property 7 14 'invisible t)
> >          (goto-char (point-min)))
> > 
> > Now if you run M-: (progn (end-of-visual-line) (point)), it moves to
> > point 14, which is end of line 2 as expected.  But then emacs adjusts
> > the point and moves it to beginning of line3, C-x = says point is 15.
> 
> Interestingly, the first time you do this, there's no adjustment from
> 14 to 15.  Sounds like some snafu with the last point position?
> 
> I can confirm that this happens because point adjustment: setting
> global-disable-point-adjustment to non-nil eliminates the problem:
> point stays at position 14.
> 
> Also, C-e behaves correctly no matter what.  So it's something
> specific to end-of-visual-line or vertical-motion.
> 
> Perhaps stepping through adjust_point_for_property with a debugger
> will show what's wrong.

I have opened a bug report #9034 [1] for this issue.  Hopefully it would
get some attention.  Seems it should not be too hard to investigate
investigate the problem for somebody how understands the code well
enough.

Please provide additional details for the bug report if I missed
anything.

Regards,
  Dmitry

[1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9034



      reply	other threads:[~2011-07-09 13:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03  2:59 `vertical-motion', `goto-line' set point to invisible text Dmitry Kurochkin
2011-07-03  6:55 ` Eli Zaretskii
2011-07-03  7:31   ` Dmitry Kurochkin
2011-07-03 13:33     ` Eli Zaretskii
2011-07-04  2:08       ` Dmitry Kurochkin
2011-07-03 14:50 ` Stefan Monnier
2011-07-03 15:14   ` Eli Zaretskii
2011-07-04 14:01     ` Stefan Monnier
2011-07-04 15:14       ` Eli Zaretskii
2011-07-04 18:10         ` Stefan Monnier
2011-07-04 20:06           ` Eli Zaretskii
2011-07-04 20:06           ` Eli Zaretskii
2011-07-05  2:22           ` Dmitry Kurochkin
2011-07-05  2:55             ` Eli Zaretskii
2011-07-05  3:52             ` Dmitry Kurochkin
2011-07-05  7:56               ` Eli Zaretskii
2011-07-09 13:13                 ` Dmitry Kurochkin [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=87fwmf38cu.fsf@gmail.com \
    --to=dmitry.kurochkin@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).