all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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 17:24:14 +0200	[thread overview]
Message-ID: <CACJP=3nZVXvu8rZ4Ls00-=pEAawHeknjXYtvk1NU6xyJ0kr7aQ@mail.gmail.com> (raw)
In-Reply-To: <83ttvxhw6y.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

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
(the docstring does not say that this command is meant for interactive use
only).

My idea was just to report this very low priority issue about the
'confusing' docstring
(and ask if maybe that argument was intended to be optional).

Here <https://emacs.stackexchange.com/a/77278/26163> is the motive for this
patch. It is used in an evil function, so I guess we could
just have used `evil-forward-WORD-begin` instead, and it is not necessary
to change
the `forward-to-word` function.

[-- Attachment #2: Type: text/html, Size: 893 bytes --]

  reply	other threads:[~2023-05-29 15:24 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 [this message]
2023-05-29 16:46             ` Juri Linkov
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACJP=3nZVXvu8rZ4Ls00-=pEAawHeknjXYtvk1NU6xyJ0kr7aQ@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=63626@debbugs.gnu.org \
    --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 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.