From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: Cygintl-3.dll was not found
Date: Thu, 10 Aug 2006 15:15:00 -0000 [thread overview]
Message-ID: <ebfiem$2t5$1@sea.gmane.org> (raw)
In-Reply-To: <20060810005356.GC8336@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> On Wed, Aug 09, 2006 at 05:34:02PM -0500, mwoehlke wrote:
>> Christopher Faylor wrote:
>>> On Wed, Aug 09, 2006 at 12:38:47PM -0700, infoterror wrote:
>>>> Under windows, programs are installed by default in "C:\Program Files."
>>>> cygwin's preferred "c:\cygwin" is foolish and makes an unnecessary mess
>>>> of installations.
>>> I disagree. Not all packages install in "c:\Program Files" and putting
>>> Cygwin's root directory there would mean extra typing, potential
>>> "filename with spaces" problems, and, most importantly, it would mean 10
>>> extra characters eaten from the MAX_PATH limit. Also, as is pointed out
>>> later in this thread, there is a whole filesystem underneath the
>>> c:\cygwin directory. Right or wrong, I've always considered Cygwin to
>>> be sort of a parallel to the Windows directory.
>>>
>>> You can, of course, choose your own location, however. I don't see why
>>> this should be a big issue for anyone who installs Cygwin. If they know
>>> about "c:\Program Files" and think that's the place that cygwin should
>>> go, they are welcome to put things there.
>>>
>>> What kind of problems do you think are being caused by installing to
>>> "c:\cygwin" and/or what kind of problems would be solved by installing
>>> to "c:\Program Files\cygwin"?
>> Whew. Thanks for wording that better than what I was managing. :-)
>
> Thanks.
>
> So what kind of response would you expect to my mail? More "thin
> intelligence", "foolish" responses?
Are you asking if I thought your response was reasonable and
non-inflammatory (yes; it helped /me/ step back and start thinking again
:-)), or if I think infoterror is a troll? Or do I just not understand
the question?
>> ...And for better or worse, Cygwin isn't breaking any rules Microsoft
>> themselves haven't broken.
>
> Yeah there is that and I resisted the urge to say something about
> foolish consistencies, too.
Right, I was also busy doing that, only all I was managing to write was
troll food. Fortunately I realized that, and gave up.
(Oh, look, *there's* one of the signatures that was still at 0 uses :-))
--
Matthew
vIMprove your life! Now on version 7!
next prev parent reply other threads:[~2006-08-10 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58fb98730601070837k26ad68f5l@mail.gmail.com>
[not found] ` <43BFEFB9.EA24C5B4@dessent.net>
[not found] ` <5718434.post@talk.nabble.com>
[not found] ` <003001c6bb9a$4e15b140$a501a8c0@CAM.ARTIMI.COM>
[not found] ` <5732487.post@talk.nabble.com>
[not found] ` <20060809210958.GA3815@trixie.casa.cgf.cx>
2006-08-09 22:34 ` mwoehlke
2006-08-10 0:07 ` Igor Peshansky
2006-08-10 0:37 ` mwoehlke
2006-08-10 9:58 ` Dave Korn
2006-08-10 12:21 ` Igor Peshansky
2006-08-10 0:54 ` Christopher Faylor
2006-08-10 15:15 ` mwoehlke [this message]
2006-08-10 16:04 ` vIMprovement? (Was Re: Cygintl-3.dll was not found) Igor Peshansky
2006-08-10 17:45 ` mwoehlke
2006-08-10 19:53 ` Cygintl-3.dll was not found Christopher Faylor
2006-08-10 20:24 ` Dave Korn
2006-08-10 20:35 ` Christopher Faylor
2006-08-10 23:01 ` mwoehlke
2006-08-10 20:25 ` mwoehlke
[not found] ` <7022170.post@talk.nabble.com>
[not found] ` <7042419.post@talk.nabble.com>
[not found] ` <20061028055933.GA19517@trixie.casa.cgf.cx>
[not found] ` <7065394.post@talk.nabble.com>
[not found] ` <20061029221805.GA1057@trixie.casa.cgf.cx>
[not found] ` <7106666.post@talk.nabble.com>
[not found] ` <20061101221317.GA3677@trixie.casa.cgf.cx>
[not found] ` <7124473.post@talk.nabble.com>
2006-11-01 23:46 ` Cary Jamison
2006-11-02 1:28 ` Christopher Faylor
2006-11-02 1:43 ` Christopher Faylor
2006-11-02 19:46 ` Dave Korn
2006-11-03 16:44 ` Igor Peshansky
2006-11-02 1:44 ` Brian Dessent
[not found] <7308368.post@talk.nabble.com>
2006-11-12 22:39 ` Dave Korn
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='ebfiem$2t5$1@sea.gmane.org' \
--to=mwoehlke@tibco.com \
--cc=cygwin-talk@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).