public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Adam Dinwoodie <adam@dinwoodie.org>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: setup (2.923)
Date: Mon, 21 Nov 2022 17:45:49 +0000	[thread overview]
Message-ID: <758f3276-0c54-3ae3-ba54-c890e0e48d2e@dronecode.org.uk> (raw)
In-Reply-To: <CA+kUOamJC-aY=o58nWSRXXDOnd882DMmhYN1=4Fda0V22o8c0w@mail.gmail.com>

On 21/11/2022 16:23, Adam Dinwoodie wrote:
> On Mon, 21 Nov 2022 at 12:46, Jon Turney wrote:
>> - Add view modes "Removable" and "Unneeded" (thanks to Christian Franke)
>>
>> -- "Removable" shows installed packages that were selected, but can now
>> be safely removed, as no installed package depends on them
>> -- "Unneeded" shows packages which were automatically installed, but can
>> now be safely removed, as no installed depends on them
> 
> Thank you, everyone involved in this! I'd been lamenting cygcheck-dep
> not getting updated for the new dependency declaration methods, but
> noticed these new options when I ran the installer yesterday, and was
> very appreciative!
> 
>> - Add Ctrl-I/R/U as keyboard accelerators for
>> install/reinstall/uninstall in the package chooser (thanks to Christian
>> Franke)
> 
> I am also very grateful for this, too – I'm a keyboard monkey and I
> find the current package selection process somewhat tedious – but I'm
> also wondering if there's a way to make it more obvious. I think a lot
> of folk would benefit from this function who probably aren't reading
> these announcements, including all the folk who sign up in future. I
> can think of a couple of obvious options, namely adding instructions
> in the grey areas above or below the chooser, or adding the shortcuts
> in brackets in the package selection drop-downs, but fundamentally I'd
> just like to have it suggested somewhere other than the mailing list
> archives for future users.

Yeah, we went around this a bit on cygwin-apps.

Marking these as accelerators in the drop-down menu is apparently 
problematic in some way I don't recall the details of now (and is 
usually hidden nowadays unless you opened the menu via a keypress).

>> This is not the place for setup feature requests.
> 
> Having probably just broken that rule, can you clarify what _is_ the
> place for setup feature requests? Neither
> https://sourceware.org/cygwin-apps/setup.html nor
> https://cygwin.com/lists.html seemed to suggest a better option…

The intended meaning is that replies to that email are for reporting 
problems with that release.

It's perfectly permissible to start a new email thread with a feature 
request for setup.  Of course, the likely response is "that's an idea, 
but someone has to do it" :)

I'll try to tweak that sentence for clarity in future.


  reply	other threads:[~2022-11-21 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3b24439b-2b4e-b392-11f9-c3790b42c827@dronecode.org.uk>
2022-11-21 12:44 ` Jon Turney
2022-11-21 16:23   ` Adam Dinwoodie
2022-11-21 17:45     ` Jon Turney [this message]
2022-11-22 16:05     ` Christian Franke
2022-11-20 17:14 Jon Turney

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=758f3276-0c54-3ae3-ba54-c890e0e48d2e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=adam@dinwoodie.org \
    --cc=cygwin@cygwin.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.
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).