public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Olwe Melwasul <hercynianforest@gmail.com> To: cygwin-xfree@cygwin.com Subject: Re: Resizing problem Date: Fri, 16 Jul 2010 20:03:00 -0000 [thread overview] Message-ID: <AANLkTilIPKlQWwGDKpykCGL2geShu_FSTPEuMEFIeJgH@mail.gmail.com> (raw) In-Reply-To: <20100716160022.GA30933@ednor.casa.cgf.cx> If you people simply want to flame me, fine. But everything I said is true: a) I had problems that no true Windows newbie could have solved from reading any amount of your "documentation". b) this or that man page is NOT documentation. (Man pages will eventually be outlawed under the Geneva Convention as a form of torture.) c) after not finding answers, I spent three days searching for this and that clue, scavenger-hunt-style... d) ... where I encountered many of Jon T's answers, and, yes, they were all quite brusque and patronizing -- which put me off wanting to get on your mailing list. e) ...where I got some good help from a nice young man, but then patronized by a not-so-nice person who blew off all my legitimate complains and problems to patronize me -- as he has done many others. f) Microsoft's main dig against "open source" software still has a ring of truth to it, i.e., whenever you leave the customer-provider business relationship (where there's money on the table and even laws), you very well might encounter this sort of attitude and behavior. That being, of course, providers who don't care about customers, or don't even see end-users as customers, but as hoards of pests sucking up their valuable time with frivolous questions. So if cygwin is on the front lines of trying to win Windows users over to GNU/Linux, then we have a problem. I, for one, would expect cygwin to be inundated with clueless newbies who are a) not very computer saavy (e.g. what newbie would have done a rebase all?) b) nervous and in a hurry about deviating so far from Big Redmond Brother, i.e., not good with "challenging" documentation, likely to do stupid things. c) needing lots of hand-holding and not much scolding. I could go on (and on and on), but I hope you got my drift. Olwe Grand Marais, MN -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2010-07-16 20:03 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-15 17:02 Olwe Melwasul 2010-07-15 18:12 ` Ken Brown 2010-07-15 19:51 ` Olwe Melwasul 2010-07-15 21:20 ` Ken Brown 2010-07-16 1:27 ` Olwe Melwasul 2010-07-16 2:04 ` Ken Brown 2010-07-16 2:20 ` Ken Brown 2010-07-16 4:10 ` Olwe Melwasul 2010-07-16 8:52 ` Csaba Raduly 2010-07-16 12:24 ` Ken Brown 2010-07-16 13:50 ` Jon TURNEY 2010-07-16 14:39 ` Olwe Melwasul 2010-07-16 15:40 ` Andy Koppe 2010-07-16 16:00 ` Christopher Faylor 2010-07-16 20:03 ` Olwe Melwasul [this message] 2010-07-16 21:19 ` Christopher Faylor 2010-07-16 21:40 ` Olwe Melwasul 2010-07-16 22:08 ` DePriest, Jason R. 2010-07-16 22:23 ` Olwe Melwasul 2010-07-16 22:46 ` Christopher Faylor 2010-07-16 22:34 ` Timares, Brian (EDS/HP) 2010-07-16 22:56 ` Christopher Faylor 2010-07-16 15:55 ` Larry Hall (Cygwin X)
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=AANLkTilIPKlQWwGDKpykCGL2geShu_FSTPEuMEFIeJgH@mail.gmail.com \ --to=hercynianforest@gmail.com \ --cc=cygwin-xfree@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: linkBe 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).