From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: new setup.exe doesn't collapse package sets in full view.
Date: Tue, 13 Dec 2016 23:10:00 -0000 [thread overview]
Message-ID: <b24b5362-0cfe-82a0-7d13-14f4f3be62a8@cornell.edu> (raw)
In-Reply-To: <20161213230223.GA4640@fedora.wp.comcast.net>
On 12/13/2016 6:02 PM, Stephen Paul Carrier wrote:
> I downloaded the new setup program (2.877, 32-bit) and ran it on a
> cygwin installation that hadn't been updated in over a year (2008R2).
> I first got the Pending view, OK, then switched to Full and found that
> the packages were not aggregated into tabs-- they were in one very long
> alphabetical list. I am wondering whether the more convenient tabbed
> view is still available and if others are also seeing this issue.
I think what you want is the "Category" view.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-12-13 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 23:02 Stephen Paul Carrier
2016-12-13 23:10 ` Ken Brown [this message]
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=b24b5362-0cfe-82a0-7d13-14f4f3be62a8@cornell.edu \
--to=kbrown@cornell.edu \
--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).