all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tshepang Lekhonkhobe <tshepang@gmail.com>
Cc: 14426@debbugs.gnu.org
Subject: bug#14426: 24.3; inaccurate statement in 7.10 of the manual
Date: Wed, 14 Aug 2019 21:55:49 -0700	[thread overview]
Message-ID: <87sgq310yy.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CAA77j2CFvHyHSUf-N-QgchM6zJ86GrD4V35Hq167-ogK9=pY0w@mail.gmail.com> (Tshepang Lekhonkhobe's message of "Mon, 20 May 2013 22:39:54 +0200")

Tshepang Lekhonkhobe <tshepang@gmail.com> writes:

> We see this in the opening paragraph, "no argument is equivalent to an
> argument of one". It's not always the case, as in the example for C-u
> 1
> C-k, which removes both the text and the newline. Maybe there's other
> examples I don't know about.

(I'm going through old bug reports that have unfortunately gotten no
responses yet.)

The paragraph says, in part:

--
Some commands interpret the argument as a repetition
count.  For example, giving @kbd{C-f} an argument of ten causes it to
move point forward by ten characters instead of one.  With these
commands, no argument is equivalent to an argument of one, and
negative arguments cause them to move or act in the opposite
direction.
--

I guess you could read that as a blanket statement on all commands that
somehow uses the prefix argument as a repetition command, but it does
say "for example" and "with these", so I think that should be a
sufficient hedge to intuit that this rule doesn't apply to all commands
that repeat.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-08-15  4:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 20:39 bug#14426: 24.3; inaccurate statement in 7.10 of the manual Tshepang Lekhonkhobe
2019-08-15  4:55 ` Lars Ingebrigtsen [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=87sgq310yy.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=14426@debbugs.gnu.org \
    --cc=tshepang@gmail.com \
    /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.