public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Backwoods BC <completely.and.totally.trash@gmail.com>, cygwin@cygwin.com
Subject: Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
Date: Sat, 2 Apr 2022 06:38:33 -0400	[thread overview]
Message-ID: <669071ad-d78a-409b-0fe5-7998a67ec2ba@cs.umass.edu> (raw)
In-Reply-To: <CAKwdsS-mOrmd+Z0TN5g3whkaqUgBRrS_eO4B9d+L-YqcoX=hdw@mail.gmail.com>

On 4/2/2022 3:37 AM, Backwoods BC wrote:
>> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
> 
> I've only been on this list a few months, but I've seen these
> "find_fast_cwd" questions about twice a month so far.
> 
> Might I suggest that replacing the
> "Please report this problem to the public mailing list cygwin@cygwin.com"
> message in 'bash' with something like:
> "Please visit https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
> for help with this issue"
> 
> This removes the need for an autoresponder and is more helpful at the
> same time. Users might be reluctant to join the mailing list just to
> report this and therefore they may waste their time needlessly trying
> to track down the problem.

The message is baked into ancient versions of Cygwin.
I believe the page the auto-responder points them to
indicates the fact that their version is old and should
be updated.  This often happens because someone bundled
Cygwin with something else and is not updating the
Cygwin version.

Modern versions no longer generate the message.

In sum, the auto-responder is the best thing we can do
about it.  At least we don't have to have a human respond.

Best wishes - Eliot Moss

  reply	other threads:[~2022-04-02 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02  6:28 James
2022-04-02  6:31 ` cygwinautoreply
2022-04-02  6:32   ` James
2022-04-02  7:37     ` Backwoods BC
2022-04-02 10:38       ` Eliot Moss [this message]
2022-04-02 14:40       ` Brian Inglis
2022-04-02  6:31 ` James
2022-04-04  7:29   ` Andrey Repin

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=669071ad-d78a-409b-0fe5-7998a67ec2ba@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=completely.and.totally.trash@gmail.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).