From: Tony Zorman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: stefankangas@gmail.com, 66567@debbugs.gnu.org
Subject: bug#66567: [PATCH] use-package: Add ignored-files support to :vc keyword
Date: Tue, 07 Nov 2023 20:39:07 +0100 [thread overview]
Message-ID: <87bkc59wv8.fsf@hyperspace> (raw)
In-Reply-To: <871qd91l9e.fsf@posteo.net>
On Wed, Nov 01 2023 16:38, Philip Kaludercic wrote:
> Tony Zorman <tonyzorman@mailbox.org> writes:
>> On Wed, Nov 01 2023 12:48, Philip Kaludercic wrote:
>>> Tony Zorman <tonyzorman@mailbox.org> writes:
>>>> On Wed, Nov 01 2023 09:09, Philip Kaludercic wrote:
>>>>
>>>>> Why is use-package checking for valid keywords in the first place?
>>>>
>>>> Better error messages, mostly. Especially people switching from
>>>> quelpa/straight/vc-use-package might be surprised that :vc is not a
>>>> drop-in replacement for those packages. I feel like alerting them to
>>>> this fact sooner rather than later makes for a better experience.
>>>
>>> IIUC this would raise an error when an unknown keyword is encountered,
>>> right?
>>
>> Yes, a declaration like
>>
>> (use-package foo
>> :vc (:url "url" :blargh "123"))
>>
>> would result in the following message
>>
>> ⛔ Error (use-package): Failed to parse package foo: use-package: Keyword :vc received unknown argument: :blargh. Supported keywords are: (:url :branch :lisp-dir :main-file :vc-backend :rev :shell-command :make :ignored-files)
>>
>> Things get a bit muddier if ':blargh' would be passed down to
>> package-vc-install.
>
> What I was wondering, was if it would make sense to raise an warning
> instead.
Now I'm a bit confused: where exactly? Inside of use-package or
package-vc? Either way, I think raising an error when the user inputs
nonsense is totally justified—I'd just like that error to be
understandable as quickly as possible.
Tony
--
Tony Zorman | https://tony-zorman.com/
next prev parent reply other threads:[~2023-11-07 19:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 16:42 bug#66567: [PATCH] use-package: Add ignored-files support to :vc keyword Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.66567.B.169739278328671.ack@debbugs.gnu.org>
2023-11-01 7:43 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-01 9:09 ` Philip Kaludercic
2023-11-01 10:13 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-01 12:48 ` Philip Kaludercic
2023-11-01 14:36 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-01 16:38 ` Philip Kaludercic
2023-11-07 19:39 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-07 21:24 ` Philip Kaludercic
2023-11-10 12:00 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 7:32 ` Philip Kaludercic
2024-05-02 18:57 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-03 6:35 ` Eli Zaretskii
2024-05-04 6:16 ` John Wiegley
2024-05-14 16:08 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 1:19 ` John Wiegley
2024-05-18 10:32 ` 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=87bkc59wv8.fsf@hyperspace \
--to=bug-gnu-emacs@gnu.org \
--cc=66567@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.com \
--cc=tonyzorman@mailbox.org \
/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).