public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: is it an FAQ: cygwin startup sequence
Date: Mon, 22 Dec 2008 01:10:00 -0000	[thread overview]
Message-ID: <20081222010909.GA25305@ednor.casa.cgf.cx> (raw)
In-Reply-To: <2537421b0812211656t3f667eb4r890fcbbb829dfd8a@mail.gmail.com>

On Sun, Dec 21, 2008 at 06:56:23PM -0600, Kermit Tensmeyer wrote:
>On Sun, Dec 21, 2008 at 6:21 PM, Eric Blake <ebb9@byu.net> wrote:
>>My guess is that you might have PATH problems.  But if you had followed
>>these directions:
>
>and that's why I'm asking for the documentation.  I don't need/want you
>to solve a problem that apparently only I have.  but yes I checked the
>complete path to see if there were other sed's.  No there wasn't.
>
>but 7 day's ago sed.exe was in /bin and the documentation was in
>/usr/share.  And today it isn't there anymore.

FYI, it is "days" not "day's".

>>>Problem reports:       http://cygwin.com/problems.html
>>
>>and attached the output of 'cygcheck -svr' as a text file, we'd know
>>better how to help you.
>
>my assumption is that something is wrong with my setup, not that there
>is a bug in the cygwin delivery.  cygcheck can check on the parameters
>used to build the install.  I

Nonetheless, you are asking for help in the cygwin list.  The above page
was created to help you ask intelligent questions so that problems can
be diagnosed.  cygcheck is a tool devised to help diagnose problems.

If you don't want help then all of the documentation is available at the
cygwin.com site.  It's pretty clearly labelled.  If you do want help
then please don't argue with people trying to help.  We really do need
cygcheck output.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2008-12-22  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22  0:15 Kermit Tensmeyer
2008-12-22  0:22 ` Eric Blake
2008-12-22  0:57   ` Kermit Tensmeyer
2008-12-22  1:10     ` Christopher Faylor [this message]
2008-12-22  1:14     ` Yitzchak Scott-Thoennes
2008-12-22  7:41     ` Thorsten Kampe
2008-12-22 12:51     ` Eric Blake

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=20081222010909.GA25305@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@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).