all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 jb@jeremybryant.net,  justin@burkett.cc, emacs-devel@gnu.org
Subject: Re: URGENT - which-key FSF contributor status
Date: Tue, 18 Jun 2024 19:23:37 +0000	[thread overview]
Message-ID: <87le32vyva.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmkWH5yBJ55P3+Lge4siXhTBUQ3uNPXQtFPFkKdnFzacDQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 18 Jun 2024 15:06:22 -0400")

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

Stefan Kangas <stefankangas@gmail.com> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Note these two warnings from package-lint when run on which-key.el:
>>
>> 806:0: error: "evil-state" doesn't start with package's prefix "which-key".
>> 2334:10: error: `next-event' was removed in Emacs version 28.1.
>
> Did you have a chance to look into these warnings?

Sorry, I forgot to respond to your message.

> The first one seems cosmetic, but we might want to fix the second one
> (assuming that it's a valid warning).

The first one is related to evil-support  I am not familiar with the
issue to find a better solution.

The second one is not a valid warning, apparently package-lint doesn't
distinguish between function calls and variable bindings.  If we really
wanted to fix it, then


[-- Attachment #2: Type: text/plain, Size: 698 bytes --]

diff --git a/lisp/which-key.el b/lisp/which-key.el
index 1de599e5497..8a61dd0edce 100644
--- a/lisp/which-key.el
+++ b/lisp/which-key.el
@@ -2336,9 +2336,9 @@ which-key-reload-key-sequence
 `which-key--current-key-list'.  Any prefix arguments that were
 used are reapplied to the new key sequence."
   (let* ((key-seq (or key-seq (which-key--current-key-list)))
-         (next-event (mapcar (lambda (ev) (cons t ev)) key-seq)))
+         (next-evt (mapcar (lambda (ev) (cons t ev)) key-seq)))
     (setq prefix-arg current-prefix-arg
-          unread-command-events next-event)))
+          unread-command-events next-evt)))
 
 (defun which-key-turn-page (delta)
   "Show the next page of keys."

[-- Attachment #3: Type: text/plain, Size: 51 bytes --]


would do it.

-- 
	Philip Kaludercic on peregrine

  reply	other threads:[~2024-06-18 19:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87le4r98m9.fsf@jeremybryant.net>
     [not found] ` <86le4rjv9p.fsf@gnu.org>
     [not found]   ` <87a5l78kc0.fsf@posteo.net>
     [not found]     ` <87msp6o9o4.fsf@jeremybryant.net>
2024-06-15  9:05       ` URGENT - which-key FSF contributor status Philip Kaludercic
2024-06-15 12:30         ` Eli Zaretskii
2024-06-15 12:58           ` Philip Kaludercic
2024-06-15 14:36             ` Stefan Kangas
2024-06-18 19:06               ` Stefan Kangas
2024-06-18 19:23                 ` Philip Kaludercic [this message]
2024-06-18 19:30                   ` Stefan Kangas
2024-06-18 19:41                     ` Philip Kaludercic
2024-06-18 19:42                       ` Stefan Kangas
2024-06-18 21:41                         ` Philip Kaludercic
2024-06-20 14:26                           ` Justin Burkett
2024-06-20 18:25                             ` Stefan Kangas
2024-06-20 19:22                               ` Philip Kaludercic
2024-06-20 21:16                               ` Justin Burkett
2024-06-20 21:45                                 ` Stefan Kangas
2024-06-15 15:19             ` Eli Zaretskii
2024-06-15 17:09               ` Philip Kaludercic
2024-06-15 17:42                 ` Justin Burkett
2024-06-15 17:50                   ` Eli Zaretskii
2024-06-18  8:49                 ` Philip Kaludercic
2024-06-18 17:37                   ` Eli Zaretskii
2024-06-16 19:07             ` Jeremy Bryant

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=87le32vyva.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=justin@burkett.cc \
    --cc=stefankangas@gmail.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.