all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: nitish chandra <nitishchandrachinta@gmail.com>
Cc: 25599@debbugs.gnu.org
Subject: bug#25599: Why edit markers after insert?
Date: Wed, 08 Mar 2017 18:39:23 +0100	[thread overview]
Message-ID: <8737en1xdg.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAK88tCHfvhcJ=0=+cYW5WOkWGPNiZOX6AZZ5XBoGTGeyLojeLQ@mail.gmail.com> (nitish chandra's message of "Wed, 8 Mar 2017 21:44:59 +0530")

On Mär 08 2017, nitish chandra <nitishchandrachinta@gmail.com> wrote:

> In primitive-undo in simple.el, aroud line 2550 (in master) we adjust the
> markers after the insertion.
>
> (dolist (adj valid-marker-adjustments)
>                (set-marker (car adj)
>                            (- (car adj) (cdr adj))))
>
> Why is this needed? Won't insert take care of adjusting the markers?

Only marker originally pointing inside the deleted region were recorded
here, and this is to make sure they regain their previous position after
the reinsertion.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





  reply	other threads:[~2017-03-08 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 14:18 bug#25599: 26.0.50; "Marker does not point anywhere" error signaled by primitive-undo near an overlay with an auto-removal insert-in-front-hooks value Dmitry Gutov
2017-03-08 16:14 ` bug#25599: Why edit markers after insert? nitish chandra
2017-03-08 17:39   ` Andreas Schwab [this message]
2017-03-08 18:08     ` nitish chandra
2017-03-08 18:17       ` nitish chandra
2017-03-09 19:39         ` nitish chandra
2017-05-14  1:12           ` Dmitry Gutov
2017-06-11 18:10             ` npostavs
2017-06-17  1:06               ` Dmitry Gutov

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=8737en1xdg.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=25599@debbugs.gnu.org \
    --cc=nitishchandrachinta@gmail.com \
    /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.