public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: BUG: cygwin warning: barfs on domain-based-mboxes; env corrupted by login(-p disabled)
Date: Thu, 30 Oct 2014 00:12:00 -0000	[thread overview]
Message-ID: <5451825C.2080602@tlinx.org> (raw)
In-Reply-To: <1107228111.20141029042128@yandex.ru>

Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>> The next Cygwin release will have CYGWIN=dosfilewarning set to OFF
>> by default.
> 
>> If anybody thinks it's really worth to keep this option available
>> and ON by default, please speak up.
> 
> I don't think it's worth the hassle. What little of the programs that is
> unable to deal with native paths are printing obvious enough error messages to
> convince the user that they should change their habits.
---
Not that I disagree with Corinna's decision, but Andrey's followup
doesn't necessarily apply (nor is it important in my case).

Bash is testing for the existence of a user's "mbox", in the spool
directory -- it prints no error if it is not found -- I don't know
that it is important that it should as one can [re]set the system mbox
path if they want, in the startup scripts.  Just that this mbox
check uses some internally compiled name that is checked before
any user scripts are run.

Still doesn't fix the problem of the ENV being zeroed in 'login'
which triggered this problem in the first place.


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

  reply	other threads:[~2014-10-30  0:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  6:09 Linda Walsh
2014-10-28 11:03 ` Corinna Vinschen
2014-10-28 13:23   ` cyg Simple
2014-10-29  1:35   ` Andrey Repin
2014-10-30  0:12     ` Linda Walsh [this message]
2014-12-02 16:01 ` Corinna Vinschen
2014-12-08 10:52   ` Corinna Vinschen

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=5451825C.2080602@tlinx.org \
    --to=cygwin@tlinx.org \
    --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).