From: Dmitry Gutov <dgutov@yandex.ru>
To: Andreas Schwab <schwab@suse.de>
Cc: Paul Pogonyshev <pogonyshev@gmail.com>, 15322@debbugs.gnu.org
Subject: bug#15322: VC log buffer scrolls itself
Date: Sun, 03 May 2015 06:38:37 +0300 [thread overview]
Message-ID: <86y4l649fm.fsf@yandex.ru> (raw)
In-Reply-To: <mvm4n875a09.fsf@hawking.suse.de> (Andreas Schwab's message of "Thu, 24 Oct 2013 10:49:26 +0200")
Andreas Schwab <schwab@suse.de> writes:
> IMHO scrolling should only happen if point is still at BOB.
While this makes sense, and would help with fixing bug#20470 without
re-introducing the main pain point of this one, we don't have any easy
access to the "current" value of point, neither from
`vc-print-log-internal' (which is called before any output is shown),
nor from within the goto-location-func lambda it passes
`vc-log-internal-common', because the latter is called from
`vc--process-sentinel', after point is temporarily moved to
(process-mark p).
next prev parent reply other threads:[~2015-05-03 3:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 13:24 bug#15322: VC log buffer scrolls itself Paul Pogonyshev
2013-09-10 15:57 ` Eli Zaretskii
2013-09-10 16:04 ` Glenn Morris
2013-09-10 18:05 ` Glenn Morris
2013-09-10 18:30 ` Eli Zaretskii
2013-09-11 6:58 ` Paul Pogonyshev
2013-09-11 13:28 ` Eli Zaretskii
2013-09-12 6:26 ` Glenn Morris
2013-09-12 7:25 ` Paul Pogonyshev
2013-09-12 15:57 ` Glenn Morris
2013-09-12 19:09 ` Stefan Monnier
2013-09-12 19:30 ` Glenn Morris
2013-09-26 7:17 ` Paul Pogonyshev
2013-10-24 8:39 ` Paul Pogonyshev
2013-10-24 8:49 ` Andreas Schwab
2013-10-24 14:24 ` Stefan Monnier
2014-08-02 16:04 ` Paul Pogonyshev
2015-05-03 3:38 ` Dmitry Gutov [this message]
2014-11-19 21:19 ` Richard Copley
2014-11-19 21:57 ` Richard Copley
2015-05-03 3:32 ` Dmitry Gutov
2015-05-03 14:34 ` Eli Zaretskii
2015-05-03 15:58 ` Dmitry Gutov
2015-05-03 16:32 ` Eli Zaretskii
2015-05-03 18:33 ` 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
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=86y4l649fm.fsf@yandex.ru \
--to=dgutov@yandex.ru \
--cc=15322@debbugs.gnu.org \
--cc=pogonyshev@gmail.com \
--cc=schwab@suse.de \
/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).