From: "Dave Korn" <dave.korn@artimi.com>
To: "'some things make more sense backwardsdrawckab esnes erom ekam
sgniht emos'" <cygwin-talk@cygwin.com>
Subject: RE: Blind people using setup.exe?
Date: Tue, 28 Jun 2005 18:12:00 -0000 [thread overview]
Message-ID: <SERRANOtj8qSVyVqVp000000260@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <20050628153640.GC3606@trixie.casa.cgf.cx>
----Original Message----
>From: Christopher Faylor
>Sent: 28 June 2005 16:37
[Thread TITTTL'd, bock-bock-b'gawwwk!]
> On Tue, Jun 28, 2005 at 12:29:35PM +0100, Dave Korn wrote:
>> ----Original Message----
>>> From: Chris January
>>> Sent: 28 June 2005 12:06
>>
>>> You can use AttachConsole (ATTACH_PARENT_PROCESS) to attach to the
>>> parent process console. If the parent process does not have a console
>>> the call will fail and you can popup a message box instead. IMHO this is
>>> the most user-friendly way of doing things.
>>
>>
>> IMHO you should have finished reading the thread before sending this
>> reply....
>
> YSHFRTH
>
> If there was ever a need for an acryonym, I think we have one here.
> This is an epidemic in the cygwin lists.
>
> cgf
I once tried to avoid ever making that mistake by setting my mailer to
reverse-date-sort all the mail and reading my newest mail first and working
back to the earliest.
This worked very well, in that I never ended up posting a point that
someone had already made earlier in the thread, but at the same time it
worked quite badly, in that I never ended up posting at all because it's
incredibly hard to make sense of a conversation that's going the wrong
direction in time.
It also made for lots of non-sequiturs, but that was to be expected. I
could only call people out for making non-*pre*quiturs ...
cheers,
DaveK
--
Can't think of a witty .sigline today....
parent reply other threads:[~2005-06-28 15:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050628153640.GC3606@trixie.casa.cgf.cx>]
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=SERRANOtj8qSVyVqVp000000260@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.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).