all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: 33532@debbugs.gnu.org, triska@metalevel.at
Subject: bug#33532: 26.1; set-window-configuration does not restore display start
Date: Tue, 04 Dec 2018 08:41:26 +0200	[thread overview]
Message-ID: <83d0qhaj55.fsf@gnu.org> (raw)
In-Reply-To: <87a7lmqkry.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 04 Dec 2018 00:59:29 +0200)

> From: Juri Linkov <juri@jurta.org>
> Cc: Markus Triska <triska@metalevel.at>,  Eli Zaretskii <eliz@gnu.org>,  33532@debbugs.gnu.org
> Date: Tue, 04 Dec 2018 00:59:29 +0200
> 
> What do you think about implementing the same behavior for
> markers like it's implemented by 'comint-move-point-for-output'?
> I.e. the same way as 'comint-move-point-for-output' moves point
> to the end of the output, after erasing the buffer markers could
> move their positions towards their previous valid position until
> there is enough reverted text that they reach the old position.
> 
> This is straightforward to implement.

Is it?  Then perhaps I don't understand what "this" is, because
support for keeping the markers' positions is implemented on the C
level, and every insertion/deletion primitive runs the low-level code
which implements that.  I wouldn't call changes in that area
"straightforward" at all.

Please also keep in mind that markers are the basis for other
important features, like overlays and conversion of character to byte
positions and vice versa.  We need to consider the implications on all
those features.





  reply	other threads:[~2018-12-04  6:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 22:11 bug#33532: 26.1; set-window-configuration does not restore display start Markus Triska
2018-11-28  6:41 ` Eli Zaretskii
2018-11-28 17:13   ` Markus Triska
2018-11-28 17:41     ` Eli Zaretskii
2018-11-28 17:58       ` Markus Triska
2018-11-28 18:29         ` Eli Zaretskii
2018-11-29  8:31     ` martin rudalics
2018-11-29 18:09       ` Markus Triska
2018-11-29 19:11         ` martin rudalics
2018-11-30 16:58           ` Markus Triska
2018-11-30 17:47             ` martin rudalics
2018-12-01 22:52               ` Juri Linkov
2018-12-02  8:34                 ` martin rudalics
2018-12-03  0:52                   ` Juri Linkov
2018-12-03  7:45                     ` martin rudalics
2018-12-03 22:59                       ` Juri Linkov
2018-12-04  6:41                         ` Eli Zaretskii [this message]
2018-12-04 21:44                           ` Juri Linkov
2018-12-04  8:33                         ` martin rudalics
2018-12-04 21:47                           ` Juri Linkov
2018-12-05  9:16                             ` martin rudalics
2018-12-06  0:09                               ` Juri Linkov
2018-12-06  9:09                                 ` martin rudalics
2018-12-06 23:38                                   ` Juri Linkov
2018-12-25 21:49                               ` Juri Linkov
2018-11-30 19:20             ` 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=83d0qhaj55.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33532@debbugs.gnu.org \
    --cc=juri@jurta.org \
    --cc=triska@metalevel.at \
    /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.