From: Juri Linkov <juri@jurta.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 33532@debbugs.gnu.org, Markus Triska <triska@metalevel.at>
Subject: bug#33532: 26.1; set-window-configuration does not restore display start
Date: Tue, 04 Dec 2018 23:47:09 +0200 [thread overview]
Message-ID: <87k1kp9e4y.fsf@mail.linkov.net> (raw)
In-Reply-To: <5C063BCA.3090301@gmx.at> (martin rudalics's message of "Tue, 04 Dec 2018 09:33:14 +0100")
> 'auto-revert-tail-mode' already has
>
> (when buffer-file-name
> (setq eob (eobp))
> (walk-windows
> (lambda (window)
> (and (eq (window-buffer window) buffer)
> (= (window-point window) (point-max))
> (push window eoblist)))
> 'no-mini t))
>
> plus
>
> (when buffer-file-name
> (when eob (goto-char (point-max)))
> (dolist (window eoblist)
> (set-window-point window (point-max)))))
>
> without changing the markers' point insertion types. We can easily
> extend that to handle a window's previous buffers' points.
Again, no support for window configurations and non-writable window
states. But maybe it's possible to access all buffer's windows,
even windows in window configurations/states, and changes their
window points, including previous buffers' points in window
configurations/states.
BTW, I understand why reverting a dired buffer moves its point-marker to
the beginning of the buffer in the selected window window restored from
a window configuration. But I don't understand why point-marker is
moved to the end of the dired buffer in non-selected window restored
from a window configuration.
next prev parent reply other threads:[~2018-12-04 21:47 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
2018-12-04 21:44 ` Juri Linkov
2018-12-04 8:33 ` martin rudalics
2018-12-04 21:47 ` Juri Linkov [this message]
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
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=87k1kp9e4y.fsf@mail.linkov.net \
--to=juri@jurta.org \
--cc=33532@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--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 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).