From: Eli Zaretskii <eliz@gnu.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 44503@debbugs.gnu.org
Subject: bug#44503: 27.1; image-scroll-up and image-scroll-down
Date: Sat, 07 Nov 2020 17:26:02 +0200 [thread overview]
Message-ID: <835z6h6ved.fsf@gnu.org> (raw)
In-Reply-To: <47686.12087.468202.24486@gargle.gargle.HOWL> (winkler@gnu.org)
> Date: Sat, 7 Nov 2020 09:16:22 -0600
> From: "Roland Winkler" <winkler@gnu.org>
>
>
> My understanding of the doc strings of image-scroll-up and
> image-scroll-down is that the argument N should be a number, nil, or
> `-'." However, these commands use (interactive "P") with
> prefix-numeric-value inside the body of these commands. I suggest
> to document this behavior. (I guess it is not very clean to use
> prefix-numeric-value inside the body of these commands. But
> changing this behavior likely will break existing code that uses
> these commands.)
>
> I realized this when I looked at doc-view's scrolling commands
> doc-view-scroll-up-or-next-page and
> doc-view-scroll-down-or-previous-page
> that likewise use (interactive "P"), contrary, to what the
> docstrings of these commands say, and I was surprised that this
> gives a meaningful behavior. So these docstrings probably should be
> updated, too.
Thanks. Can you suggest the changes to the relevant doc strings?
next prev parent reply other threads:[~2020-11-07 15:26 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 [this message]
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
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=835z6h6ved.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44503@debbugs.gnu.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.