From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 13133@debbugs.gnu.org
Subject: bug#13133: 24.2.90; scroll-conservatively is too coarse a setting
Date: Tue, 11 Dec 2012 09:09:59 +0200 [thread overview]
Message-ID: <83pq2h9i9k.fsf@gnu.org> (raw)
In-Reply-To: <50C6954F.5020104@yandex.ru>
> Date: Tue, 11 Dec 2012 06:07:11 +0400
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: 13133@debbugs.gnu.org
>
> On 10.12.2012 12:52, Eli Zaretskii wrote:
> >> Date: Mon, 10 Dec 2012 12:28:58 +0400
> >> From: Dmitry Gutov <dgutov@yandex.ru>
> >> CC: 13133@debbugs.gnu.org
> >>
> >> Like I mentioned, I don't want C-M-e/C-M-a to recenter. Why do you think
> >> it's TRT?
> >
> > Because you generally want to see the entire definition of the API,
> > not just the opening brace or paren.
>
> Not sure if I understand you here. For example, if I'm in an Elisp
> function, I can press C-M-a to go to its beginning, and the whole
> definition (including arglist and docstring) will be visible. If the
> value of scroll-conservatively is small, though, the function body may
> be cut in half.
> Or do you specifically mean non-lisp languages where the docstring is
> above the function definition?
Yes, the latter.
> >> As far as I'm concerned, recentering might be fine when we go to the end
> >> of a small function (it will fit on the screen anyway), but a larger
> >> function, which might have fit on the full screen, will be cut in half.
> >
> > IMO, C-M-e/C-M-a is not for observing the whole function. You may be
> > looking for a separate feature, or maybe a modification of an existing
> > feature.
>
> I don't think you can reasonably decide what they are for.
I didn't decide anything, I just gave you my interpretation. That's
what "IMO" is for.
> > Can you cook up a test case? I'd like to see why this happens. (If
> > showing this requires injection of specific amount of text into the
> > compilation buffer, you could use 'cat' or some similar program to do
> > so, instead of actually running a compiler.)
>
> Here's one:
Thanks, I'll take a look.
prev parent reply other threads:[~2012-12-11 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 3:29 bug#13133: 24.2.90; scroll-conservatively is too coarse a setting Dmitry Gutov
2012-12-10 6:30 ` Eli Zaretskii
2012-12-10 6:46 ` Dmitry Gutov
2012-12-10 7:08 ` Eli Zaretskii
2012-12-10 8:28 ` Dmitry Gutov
2012-12-10 8:52 ` Eli Zaretskii
2012-12-11 2:07 ` Dmitry Gutov
2012-12-11 7:09 ` Eli Zaretskii [this message]
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=83pq2h9i9k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13133@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.