public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Resizing problem
Date: Fri, 16 Jul 2010 15:40:00 -0000	[thread overview]
Message-ID: <AANLkTin6sBfgLcfu0Om0zZeiYb5FGS1TEKze4qWPPV5b@mail.gmail.com> (raw)
In-Reply-To: <AANLkTintI7yq-joB2YwprEDsbdKwjN0u4TJQXrvQm6Bz@mail.gmail.com>

On 16 July 2010 15:39, Olwe Melwasul wrote:
> On Fri, Jul 16, 2010 at 8:50 AM, Jon TURNEY wrote:
>>> I installed cygwin/xcygwin 1.7.5 with KDE.
>>
>> I don't know where you got KDE from, but it's not in the standard cygwin
>> distribution.  If you have problems with KDE, perhaps you should try the
>> place you got it from.
>>
>>> I tried clicking on XWin
>>> Server from the Start menue, but nothing happened. I tried startx from
>>> the
>>> cygwin basic terminal. Nothing. After some Google archaeology, I found
>>> someone that had done this:
>>>
>>> cd \cygwin\bin
>>> ash
>>> PATH=. rebaseall -v
>>>
>>> at the DOS command. Good. It worked. Running startx at the cygwin
>>> command did start a twm session. But how the KDE would run, I couldn't
>>> figure out from any amount of documentation or Googling.
>>
>> Given the rest of this email, I find it hard to believe that the
>> documentation you read included 'man Xwin' or the Cygwin/X User Guide [1]
>>
>> If you did, and you found it unclear, I'd welcome your suggestions as to how
>> to improve that documentation.
>
> I don't think I'd want to try. I'd likely have "too many questions."
>
> And my feelings would either be bolstered by people like Ken Brown who
> answered these initial questions promptly and accurately with
> patience, or trampled rudely and brusquely as is Jon Turney's habit.
> Yes, I've seen other Jon Turney's responses, and they're not winning
> the cygwin cause many friends.

That's both insulting and untrue. Jon's doing a great job maintaining
and supporting one of the most complex pieces of Cygwin, and as far as
I remember, his responses are always helpful and accurate.

You did get answers to your questions, and Jon acknowledged that the
documentation needs improvement, so what exactly are you taking
umbrage at anyway? The suggestion that reading the actual manual
instead of just googling around might have helped?


> I'm a GNU/Linux user who has to teach a course on GNU text/file
> manipulation tools to students who've never seen GNU/Linux and will
> probably not want to install it on their laptops.

You do realise that you don't need Cygwin/X to run a Cygwin console or terminal?

Andy

--
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/


  reply	other threads:[~2010-07-16 15:40 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 [this message]
2010-07-16 16:00       ` Christopher Faylor
2010-07-16 20:03         ` Olwe Melwasul
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=AANLkTin6sBfgLcfu0Om0zZeiYb5FGS1TEKze4qWPPV5b@mail.gmail.com \
    --to=andy.koppe@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: 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).