unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: dalanicolai <dalanicolai@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Zaz Brown <zazbrown@zazbrown.com>,
	63626@debbugs.gnu.org
Subject: bug#63626: [PATCH] Make forward and backward-to-word arg optional
Date: Mon, 29 May 2023 19:46:59 +0300	[thread overview]
Message-ID: <86wn0r6q7s.fsf@mail.linkov.net> (raw)
In-Reply-To: <CACJP=3nZVXvu8rZ4Ls00-=pEAawHeknjXYtvk1NU6xyJ0kr7aQ@mail.gmail.com> (dalanicolai@gmail.com's message of "Mon, 29 May 2023 17:24:14 +0200")

> I have no opinion about how this 'should work'.
> I was just confused by the docstring, and I assumed from the docstring,
> that the intention was for the argument to be optional like in
> forward-word/line

Aren't all forward-like commands more permissive and allow their arg
to be optional?  It looks like the standard signature, e.g.:

  (defun forward-page (&optional count)
    (interactive "p")
    (or count (setq count 1))

  (defun forward-paragraph (&optional arg)
    (interactive "^p")
    (or arg (setq arg 1))

  (defun forward-sentence (&optional arg)
    (interactive "^p")
    (or arg (setq arg 1))

  ...





  reply	other threads:[~2023-05-29 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21  4:33 bug#63626: [PATCH] Make forward and backward-to-word arg optional Zaz Brown
2023-05-26 11:24 ` Eli Zaretskii
     [not found]   ` <CACTmS+g93z7ns6AD9v-a+-TRVkVuTLt5RGi5YVTGUA8J1BM3dw@mail.gmail.com>
2023-05-27  7:02     ` Eli Zaretskii
2023-05-27 18:39       ` Zaz Brown
2023-05-28  5:16         ` Eli Zaretskii
2023-05-29 15:24           ` dalanicolai
2023-05-29 16:46             ` Juri Linkov [this message]
2023-05-31 13:15               ` Eli Zaretskii

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=86wn0r6q7s.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=63626@debbugs.gnu.org \
    --cc=dalanicolai@gmail.com \
    --cc=eliz@gnu.org \
    --cc=zazbrown@zazbrown.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 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).