From: Philip Kaludercic <philipk@posteo.net>
To: Sean Devlin <spd@toadstyle.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
73932@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#73932: [PATCH] Add noconfirm to 'package-autoremove'
Date: Mon, 18 Nov 2024 03:36:32 +0000 [thread overview]
Message-ID: <87ttc5usan.fsf@posteo.net> (raw)
In-Reply-To: <85D8E91F-CBAE-4314-BDA9-B36C5FF81452@toadstyle.org> (Sean Devlin's message of "Fri, 15 Nov 2024 12:07:50 -0500")
Sean Devlin <spd@toadstyle.org> writes:
> Hi folks,
>
>> On Nov 5, 2024, at 12:45 PM, Sean Devlin <spd@toadstyle.org> wrote:
>>
>> Hi folks,
>>
>>> On Oct 28, 2024, at 10:48 AM, Sean Devlin <spd@toadstyle.org> wrote:
>>>
>>> Hi folks,
>>>
>>>> On Oct 27, 2024, at 5:53 AM, Stefan Kangas
>>>> <stefankangas@gmail.com> wrote:
>>>>
>>>> Philip Kaludercic <philipk@posteo.net> writes:
>>>>
>>>>> Is the variation interesting, where NOCONFIRM is a predicate so that
>>>>> we can selectively remove packages?
>>>>
>>>> Do you have a use case in mind?
>>>>
>>>>>> Sure, that might make sense. If we do that, should we do the
>>>>> same in package-install-selected-packages? It uses its NOCONFIRM
>>>>> argument in a similar way.
>>>>>
>>>>> We can do that in a subsequent patch.
>>>>
>>>> Feel free to post such a patch, indeed. Thanks in advance.
>>>
>>> Here’s two patches:
>>>
>>> <0001-Add-noconfirm-to-package-autoremove.patch><0002-Use-prefix-argument-in-package-install-selected-pack.patch>
>>>
>>> The first is the same as before, but it adds the prefix argument
>>> usage Eli suggested.
>>>
>>> The second patch adds a matching prefix argument to
>>> package-install-selected-packages (if this is desired).
>>>
>>> I didn’t implement a predicate option for NOCONFIRM yet, since I
>>> couldn’t think of a use case, and the intended semantics are not
>>> quite clear to me.
>>>
>>> Please let me know what else is needed, and thanks!
>>
>> Are there any outstanding issues? If so, how can I help resolve them?
>>
>> Thanks!
>
> Just checking in again. Is there anything I can do to help resolve this?
Sorry for the delay, I can apply it to master if nobody objects.
> Thanks!
>
--
Philip Kaludercic on siskin
next prev parent reply other threads:[~2024-11-18 3:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 15:58 bug#73932: [PATCH] Add noconfirm to 'package-autoremove' Sean Devlin
2024-10-21 16:35 ` Eli Zaretskii
2024-10-21 18:04 ` Sean Devlin
2024-10-26 7:31 ` Philip Kaludercic
2024-10-27 9:53 ` Stefan Kangas
2024-10-28 14:48 ` Sean Devlin
2024-11-05 17:45 ` Sean Devlin
2024-11-15 17:07 ` Sean Devlin
2024-11-18 3:36 ` Philip Kaludercic [this message]
2024-11-21 21:17 ` Philip Kaludercic
2024-11-22 16:30 ` Sean Devlin
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=87ttc5usan.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=73932@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=spd@toadstyle.org \
--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 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).