all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Zaz Brown <zazbrown@zazbrown.com>
Cc: dalanicolai@gmail.com, 63626@debbugs.gnu.org
Subject: bug#63626: [PATCH] Make forward and backward-to-word arg optional
Date: Sat, 27 May 2023 10:02:55 +0300	[thread overview]
Message-ID: <837csujly8.fsf@gnu.org> (raw)
In-Reply-To: <CACTmS+g93z7ns6AD9v-a+-TRVkVuTLt5RGi5YVTGUA8J1BM3dw@mail.gmail.com> (message from Zaz Brown on Fri, 26 May 2023 12:54:19 -0700)

[Please use Reply All to reply, to keep everyone on the CC list.]

> From: Zaz Brown <zazbrown@zazbrown.com>
> Date: Fri, 26 May 2023 12:54:19 -0700
> 
> It's more convenient to be able to use forward-to-word without the
> argument.  For example, this would allow passing the function
> forward-to-word without having to use a lambda.
> 
> Most importantly, though, the current definition of forward-to-word
> does not match the doc string.  The doc string implies that with no
> argument, it goes forward 1 word.  And this has already caused
> confusion.

The doc string says "with argument", most probably meaning "with
prefix numeric argument".  IOW, it talks about interactive invocation.
In any case, the doc string is easy to fix/clarify.

But I'm still not convinced we need to change the signature of the
function.  What are the use cases where you'd want to pass
forward-to-word as a function argument to another function?





  parent reply	other threads:[~2023-05-27  7:02 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 [this message]
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
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=837csujly8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63626@debbugs.gnu.org \
    --cc=dalanicolai@gmail.com \
    --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.