From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 12253@debbugs.gnu.org
Subject: bug#12253: Restore window start position
Date: Fri, 24 Aug 2012 11:45:20 +0200 [thread overview]
Message-ID: <50374D30.7090401@gmx.at> (raw)
In-Reply-To: <877gsp9sl2.fsf@mail.jurta.org>
> Usually Info widens the Info buffer, moves point using `goto-char' and
> finally narrows the buffer to the current node. There is no way to use
> `set-window-point' in this workflow. Other places (that move point
> after narrowing) could use the same function `goto-char' for consistency.
Conceptually, `goto-char' and `set-window-point' are idempotent with the
current buffer in the selected window. Now *info* synchronizes
navigation in all windows showing *info*. But if I split an *info*
window showing the (narrowed) beginning of *info* and do
(set-window-point (window-in-direction 'below) (point-max))
with the upper window selected, the lower window shows the (narrowed)
end of *info* and
(with-selected-window (window-in-direction 'below)
(goto-char (point-max)))
does the same. So I still miss you.
martin
next prev parent reply other threads:[~2012-08-24 9:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 22:17 bug#12253: Restore window start position Juri Linkov
2012-08-22 7:08 ` martin rudalics
2012-08-22 23:38 ` Juri Linkov
2012-08-23 8:48 ` martin rudalics
2012-08-23 22:00 ` Juri Linkov
2012-08-24 9:45 ` martin rudalics [this message]
2012-08-25 0:29 ` Juri Linkov
2012-08-25 13:40 ` martin rudalics
2012-08-25 19:29 ` Juri Linkov
2012-08-28 8:53 ` Juri Linkov
2013-01-16 16:57 ` Drew Adams
2013-01-18 22:42 ` Drew Adams
2013-01-19 10:17 ` Juri Linkov
2013-01-19 15:03 ` Drew Adams
2013-03-29 16:56 ` Drew Adams
2021-05-11 14:33 ` Drew Adams
2021-05-11 17:53 ` Juri Linkov
2021-05-11 18:46 ` bug#12253: [External] : " Drew Adams
2021-05-11 19:29 ` Juri Linkov
2021-05-11 20:18 ` Drew Adams
2021-05-12 8:47 ` martin rudalics
2024-01-10 11:31 ` Stefan Kangas
2024-01-10 17:16 ` Juri Linkov
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=50374D30.7090401@gmx.at \
--to=rudalics@gmx.at \
--cc=12253@debbugs.gnu.org \
--cc=juri@jurta.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.