From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailsrv.cs.umass.edu (mailsrv.cs.umass.edu [128.119.240.136]) by sourceware.org (Postfix) with ESMTPS id 7FC293858418 for ; Sat, 2 Apr 2022 10:38:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7FC293858418 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.umass.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.umass.edu Received: from [192.168.0.144] (rrcs-50-74-66-18.nyc.biz.rr.com [50.74.66.18]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id C8715401DC93; Sat, 2 Apr 2022 06:38:32 -0400 (EDT) Reply-To: moss@cs.umass.edu 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 To: Backwoods BC , cygwin@cygwin.com References: <20220402063105.6E1DAA8098C@calimero.vinschen.de> From: Eliot Moss Message-ID: <669071ad-d78a-409b-0fe5-7998a67ec2ba@cs.umass.edu> Date: Sat, 2 Apr 2022 06:38:33 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2022 10:38:34 -0000 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