Warning cygwin

[Brian Inglis]

On 2021-02-22 17:59, Kaz Kylheku (Cygwin) wrote:
> On 2021-02-22 15:53, Brian Inglis wrote:
>> On 2021-02-22 16:41, Kaz Kylheku wrote:
>>> On 2021-02-22 11:19, cygwinautoreply wrote:
>>>> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

>>> It would be ideal if this auto-reply didn't include the Cygwin
>>> mailing list; there is no need for the mailing list to read this.
>>> Scratch that; it would be ideal if neither the original question
>>> nor the auto-reply were re-mailed.

>> What if Cygwin is up to date and you see that message?

> Right.
> In that case, the message from newer Cygwin will not be accompanied
> by a recommendation to post to the mailing list. Instead it points
> to some online resources about the problem.

winsup/cygwin/path.cc:
Cygwin WARNING:
   Couldn't compute FAST_CWD pointer.  This typically occurs if you're using
   an older Cygwin version on a newer Windows.  Please update to the latest
   available Cygwin version from https://cygwin.com/.  If the problem persists
   please see https://cygwin.com/problems.html

> Those resources could loudly warn the user that mailing list messages
> containing references to the FAST_CWD will receive a robot reply
> and not get posted (for he reason that old releases of Cygwin
> encouraged users to post reports of it, which keeps happening).

Newer Windows releases are likely to eventually re-trigger the problem.
The reporter may not be a Cygwin developer who could submit patches, or 
sufficiently bothered, or knowledgeable enough, to find the site, follow the 
problem reporting guidelines, and generate or attach a cygcheck log.
In either case of old or new messages, if users need more help understanding the 
messages, they should still be able to follow up to the mailing list.

Please feel free to compose a suitable update to the above FAQ entry and path.cc 
messages, and submit patches, suggesting the changes as preconditions required 
to enable the milter to suppress the post and reply. SHTDI

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]