From: nitish chandra <nitishchandrachinta@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 25599@debbugs.gnu.org
Subject: bug#25599: Why edit markers after insert?
Date: Wed, 8 Mar 2017 23:47:49 +0530 [thread overview]
Message-ID: <CAK88tCGhZuwUdzjw-V7F91VARKpy8+G+SQOYQkcrUysF-6Ba2w@mail.gmail.com> (raw)
In-Reply-To: <CAK88tCFOjwEQ3xJ7ZagEd0w643s5YTK_1PV1Mdb18CrT1HOuQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
Sorry, the above process threw some warnings. I didn't notice them before:
Warning (emacs): Encountered (#<marker at 1 in *scratch*> . -14) entry in
undo list with no matching (TEXT . POS) entry
On 8 March 2017 at 23:38, nitish chandra <nitishchandrachinta@gmail.com>
wrote:
>
> 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.
>>
>
> I removed this part of the code to see what changes.
>
> 1. I put a marker in a line
> 2. Deleted the line
> 3. Undo-ed the delete
>
> The marker is still in the proper place. So markers in the deleted string
> do seem to regain their position properly.
>
[-- Attachment #2: Type: text/html, Size: 1460 bytes --]
next prev parent reply other threads:[~2017-03-08 18:17 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
2017-03-08 18:08 ` nitish chandra
2017-03-08 18:17 ` nitish chandra [this message]
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=CAK88tCGhZuwUdzjw-V7F91VARKpy8+G+SQOYQkcrUysF-6Ba2w@mail.gmail.com \
--to=nitishchandrachinta@gmail.com \
--cc=25599@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 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.