emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#65449: closed (30.0.50; [PATCH] strokes: Support running other funct


From: GNU bug Tracking System
Subject: bug#65449: closed (30.0.50; [PATCH] strokes: Support running other function when no stroke matches)
Date: Thu, 31 Aug 2023 09:33:02 +0000

Your message dated Thu, 31 Aug 2023 12:32:11 +0300
with message-id <83o7ineew4.fsf@gnu.org>
and subject line Re: bug#65449: 30.0.50; [PATCH] strokes: Support running other 
function when no stroke matches
has caused the debbugs.gnu.org bug report #65449,
regarding 30.0.50; [PATCH] strokes: Support running other function when no 
stroke matches
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
65449: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65449
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 30.0.50; [PATCH] strokes: Support running other function when no stroke matches Date: Tue, 22 Aug 2023 14:25:24 +0800
Hi,

This patch allows users to call another function when no stroke
matches, instead of signaling an error. I bind down-mouse-3 to
strokes-do-stroke, and would like to pop up the context menu when no
stroke matches. In addition, two arguments stroke and match can be
passed to the function for other uses (e.g. making the error message
more informative).

Attachment: 0001-strokes-Support-running-other-function-when-no-strok.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#65449: 30.0.50; [PATCH] strokes: Support running other function when no stroke matches Date: Thu, 31 Aug 2023 12:32:11 +0300
> Cc: 65449@debbugs.gnu.org
> Date: Tue, 22 Aug 2023 19:05:47 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Liu Hui <liuhui1610@gmail.com>
> > Date: Tue, 22 Aug 2023 21:50:58 +0800
> > Cc: 65449@debbugs.gnu.org
> > 
> > I have updated the doc string in the attached patch. However, the
> > return value cannot be specified because the return value of
> > `strokes-execute-stroke' is not specified, i.e., `command-execute'
> > could return any value.
> 
> Thanks, looks reasonable.
> 
> Let's wait for a few days, to give others a chance to chime in and
> voice comments.  If nothing serious comes up, I will install this in a
> few days.

No further comments, so I've now installed this on the master branch,
and I'm closing the bug.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]