This is the mail archive of the
mailing list for the Cygwin project.
Re: [PATCH 1/4] Add the last element of URL path to site chooser, if interesting.
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 12 Dec 2010 13:08:41 +0100
- Subject: Re: [PATCH 1/4] Add the last element of URL path to site chooser, if interesting.
- References: <email@example.com> <firstname.lastname@example.org> <20101129125730.GZ18309@calimero.vinschen.de> <4D02744F.email@example.com> <20101210190314.GB22361@ednor.casa.cgf.cx>
- Reply-to: cygwin-apps at cygwin dot com
On Dec 10 14:03, Christopher Faylor wrote:
> On Fri, Dec 10, 2010 at 06:41:19PM +0000, Jon TURNEY wrote:
> >On 29/11/2010 12:57, Corinna Vinschen wrote:
> >> On Nov 26 13:48, Jon TURNEY wrote:
> >>> So, to make the site chooser list entries unique and distinguishable, add the last element of the URL path to
> >>> the site chooser, if it exists and isn't 'cygwin' (or some other alternatives used by current mirrors)
> >> That sounds a bit problematic. So two URLs on the same machine might
> >> again end up as the same string, undistinguishable, just because they
> >> both end in the same directory name?
> >Yes, this is true, but currently *any* two URLs on the same host are
Right. I was just trying to point out the obvious to kick off a
discussion. You were trying to improve the output so let's see if
there's some easy way to get rid of the remaining kinks, ok?
> >> And there are (right now) four
> >> such directory names, which are treated identically.
> >I'm sorry, I don't understand what you are referring to here.
I'm refering to the four hardcoded names "cygwin", "cygwin.com",
"cygwin32" and "gnu-win32".
> >> Don't get me wrong. It's certainly better than what we have today,
> >> and the full URL is almost unreadable. Nevertheless, I'd be more happy
> >> with a solution which fixes this problem even for such border cases...
> >Back to the bikeshed, then :-)
> >If we were starting from scratch, how would this work?
> If we were doing this from scratch then I think we should present a tree view by
> protocol dir
Sounds good. Or
But that's certainly a lot more work than to fix just the strings.
Assuming you're still heading for a interim solution, what about
shortcutting the path, similar to the Usenet style:
? Well, just an idea...
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com