unofficial mirror of bug-gnu-emacs@gnu.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: Sun, 28 May 2023 08:16:53 +0300	[thread overview]
Message-ID: <83ttvxhw6y.fsf@gnu.org> (raw)
In-Reply-To: <CACTmS+iM51+dVJMwiu07a7QCvQK0Fh4OYKCmY2Mkq7AuiFVmmQ@mail.gmail.com> (message from Zaz Brown on Sat, 27 May 2023 11:39:35 -0700)

> From: Zaz Brown <zazbrown@zazbrown.com>
> Date: Sat, 27 May 2023 11:39:35 -0700
> Cc: dalanicolai@gmail.com, 63626@debbugs.gnu.org
> 
> On Sat, May 27, 2023 at 12:02 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > 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?
> 
> I can't think of a good example and wasn't able to find an example of
> a forward-to-word lambda on GitHub code search.  So perhaps I'm
> mistaken that this would be useful.  I'll have to leave that
> discussion to those who are more familiar with Emacs and Lisp.

Thanks.

Does anyone else here have an opinion on this changeset?





  reply	other threads:[~2023-05-28  5:16 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 [this message]
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

  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=83ttvxhw6y.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 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).