public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: Cygwin Apps List <cygwin-apps@cygwin.com>,
	Warren Young <warren@etr-usa.com>
Subject: Re: [PATCH] setup.exe case-insensitive package sorting
Date: Wed, 19 Sep 2012 16:21:00 -0000	[thread overview]
Message-ID: <20120919162052.GA14018@ednor.casa.cgf.cx> (raw)
In-Reply-To: <5051650A.5030702@etr-usa.com>

On Wed, Sep 12, 2012 at 10:46:02PM -0600, Warren Young wrote:
>This patch is incomplete, but I've been fighting this for four hours 
>now.  I'm tired, hungry, and frustrated, so in case I don't get back to 
>finishing this, I decided to just post what I have so far.
>
>The point of the patch is to get the Select Packages screen's package 
>lists to sort case-insensitively.
>
>(This saga began after I spent far too long looking for the R package 
>down in the bottom third of the Interpreters category.)
>
>The patch works for the flat views only.  I have yet to figure out how 
>to do the same for the Category tree view, since that is treated as a 
>completely separate exception case in the code.
>
>(Any setup.exe hackers want to opine on whether it's reasonable for it 
>to have required 3 hours of spelunking through the package DB reader, 
>the INI file parser, and the dialog chaining system to find out where to 
>even begin attempting the patch?  Did I make par?  Was there a map to 
>this twisty maze of global variables that I missed?)

You want us to weigh in on your being tired and frustrated and unable
to figure out source code?  I'm going to carefully lay down that loaded
weapon.

I modified "upset" to do case insensitive sorting of packages.  This seems
preferable to adding YA level of complexity to setup.

cgf

      reply	other threads:[~2012-09-19 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13  4:46 Warren Young
2012-09-19 16:21 ` Christopher Faylor [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=20120919162052.GA14018@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=warren@etr-usa.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).