From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44503@debbugs.gnu.org, winkler@gnu.org
Subject: bug#44503: 27.1; image-scroll-up and image-scroll-down
Date: Thu, 10 Jun 2021 18:33:43 +0300 [thread overview]
Message-ID: <83r1h9bup4.fsf@gnu.org> (raw)
In-Reply-To: <87wnr1ah9c.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 10 Jun 2021 17:09:19 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 44503@debbugs.gnu.org, winkler@gnu.org
> Date: Thu, 10 Jun 2021 17:09:19 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I'm not sure I follow: what are you trying to improve/fix/change by
> > that, apart of the doc strings?
>
> Doc strings mostly -- if we had a section in the lispref manual that
> explains this, we could have the doc strings just refer to that.
I'm not sure it's worth it. Describing what "C-u -" does is usually
easy and doesn't take too many words.
> If it's always "like 'p' but an entire page if the prefix isn't
> numerical", then that would be a win (and the four commands discussed
> here fit that pattern), but I'm not sure how prevalent this pattern is,
> so it may not be worth it.
Not all the commands that react to "C-u -" work on stuff where "page"
is meaningful, I think.
next prev parent reply other threads:[~2021-06-10 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 15:16 bug#44503: 27.1; image-scroll-up and image-scroll-down Roland Winkler
2020-11-07 15:26 ` Eli Zaretskii
2020-11-09 20:03 ` Roland Winkler
2021-06-06 10:37 ` Lars Ingebrigtsen
2021-06-08 15:34 ` Roland Winkler
2021-06-09 9:56 ` Lars Ingebrigtsen
2021-06-09 11:51 ` Eli Zaretskii
2021-06-10 8:19 ` Lars Ingebrigtsen
2021-06-10 12:52 ` Lars Ingebrigtsen
2021-06-10 14:24 ` Eli Zaretskii
2021-06-10 15:09 ` Lars Ingebrigtsen
2021-06-10 15:33 ` Eli Zaretskii [this message]
2021-06-12 12:11 ` Lars Ingebrigtsen
2022-05-07 13:06 ` Lars Ingebrigtsen
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=83r1h9bup4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44503@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=winkler@gnu.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.