all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dmitry.kurochkin@gmail.com, 9034@debbugs.gnu.org
Subject: bug#9034: point adjustment (with invisible text) moves to the next line
Date: Thu, 26 Aug 2021 18:33:29 +0200	[thread overview]
Message-ID: <871r6gyxly.fsf@gnus.org> (raw)
In-Reply-To: <8335qwtdia.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Aug 2021 18:46:37 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Just doing `M-: 4 RET' will result in this code adjusting point in
>> the buffer.  Doing, for instance, `M-x foo RET' (where `foo' does
>> nothing) does not result in this point movement.
>> 
>> So is `M-:' doing some weird thing in the original buffer to trigger
>> this oddity?
>
> Doing M-: in what part of the recipe?

Eval this:

  (progn (switch-to-buffer "test")
         (insert "aline1\nbline2\ncline3\n")
         (put-text-property 7 14 'invisible t) ; region [\nbline2]
         (goto-char (point-min)))

Then

C-e
M-: 4 RET

This will move point to the start of the next line about half the time.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-08-26 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 13:04 bug#9034: point adjustment after `end-of-visual-line' moves to the next line Dmitry Kurochkin
2011-07-11  4:16 ` Stefan Monnier
2011-07-11  8:27   ` Dmitry Kurochkin
2021-08-25 16:32 ` bug#9034: point adjustment (with invisible text) " Lars Ingebrigtsen
2021-08-25 16:43   ` Eli Zaretskii
2021-08-26 13:48     ` Lars Ingebrigtsen
2021-08-26 15:46       ` Eli Zaretskii
2021-08-26 16:33         ` Lars Ingebrigtsen [this message]
2021-08-26 16:48           ` Eli Zaretskii
2021-08-26 17:05             ` Lars Ingebrigtsen
2021-08-26 17:13               ` 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

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

  git send-email \
    --in-reply-to=871r6gyxly.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=9034@debbugs.gnu.org \
    --cc=dmitry.kurochkin@gmail.com \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.