unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 09 Jun 2021 14:51:15 +0300	[thread overview]
Message-ID: <835yyndznw.fsf@gnu.org> (raw)
In-Reply-To: <8735trmkdl.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  09 Jun 2021 11:56:38 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 44503@debbugs.gnu.org,  Eli Zaretskii <eliz@gnu.org>
> Date: Wed, 09 Jun 2021 11:56:38 +0200
> 
> "Roland Winkler" <winkler@gnu.org> writes:
> 
> > I am sorry, I haven't had as much progress as I had wanted to.  I
> > realized that the discrepancy between documented behavior and actual
> > code exists in a larger number of commands than I had expected.  So
> > the question becomes: for how many commands do we want to include a
> > remark in the docstring saying that due to historical reasons they
> > call prefix-numeric-value not in their interactive specs, but
> > scroll_command calls prefix_numeric_value in its body, which defines
> > how these commands interpret the argument.  (The actual wording in the
> > docstrings should probably be different.)
> >
> > I guess for the built-in functions scroll-up and scroll-down as well
> > as image-scroll-up and image-scroll-down it is most important to
> > mention this and we could leave the docstrings of other commands
> > untouched.  What do you think?
> 
> Well, the doc strings for these commands don't really describe
> interactive usage at all, but I think most people would interpret what's
> there as "it's like (interactive "p"), but with no prefix at all it
> behaves differently".  (Which is what it does -- a full screen instead
> of a line.)

What about the value of '-' ?

> Stating this explicitly in the doc strings of these four commands would
> be nice.  So something like:
> 
> Interactively, giving this command a numerical prefix will scroll by
> that many lines.  Without a prefix, scroll by a full screen.

Btw, the doc strings also use both N and ARG, but should only use N.





  reply	other threads:[~2021-06-09 11:51 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 [this message]
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

  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=835yyndznw.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 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).