Am 07.08.2015 um 11:04 schrieb Corinna Vinschen:
Globally setting HOME in Windows for the sake of Cygwin was partially
necessary up to the early 2000s. For *at least* 12 years, it wasn't
anymore.
And people shouldn't be told to set HOME to a value not valid in the
environment they are setting it
On 8/7/2015 5:04 AM, Corinna Vinschen wrote:
>
> So, editing /etc/passwd or /etc/nsswitch.conf is *that* hard?
>
It could be difficult due to distribution of process. As others have
stated, leave it alone. It's worked since day 1 it should work for the
life of Cygwin. There is no good reason
On 8/5/2015 3:54 AM, Corinna Vinschen wrote:
>
> So the idea was:
>
> set HOME=foo<- ignored, set HOME from passwd DB entry
I agree.
> set HOME=C:/foo <- same
I strongly disagree. In fact I set HOME in the Windows environment
expecting Cygwin to map it correctly so tha
On Aug 6 14:03, Thomas Wolff wrote:
> On 05.08.2015 12:12, Corinna Vinschen wrote:
> >On Aug 5 11:09, Thomas Wolff wrote:
> >>Am 05.08.2015 um 09:54 schrieb Corinna Vinschen:
> >>...
> >>>So the idea was:
> >>>
> >>> set HOME=foo<- ignored, set HOME from passwd DB entry
> >>> set
On 05.08.2015 12:12, Corinna Vinschen wrote:
On Aug 5 11:09, Thomas Wolff wrote:
Am 05.08.2015 um 09:54 schrieb Corinna Vinschen:
...
So the idea was:
set HOME=foo <- ignored, set HOME from passwd DB entry
set HOME=C:/foo <- same
No, please don't!
set HOME=//foo/bar
Greetings, Nicholas Clark!
> You're certainly right that there are nicer ways to write that script.
> My point with the sample script above is that I'm currently using a
> Windows-style HOME path, and it works fine.
If it would stop working, you'll have to o and revisit your mess to pull the
cruf
You're certainly right that there are nicer ways to write that script.
My point with the sample script above is that I'm currently using a
Windows-style HOME path, and it works fine.
Chances are there are a bunch of other users out there who also use a
Windows-style HOME path in messy .bat files -
Greetings, Nicholas Clark!
> I totally agree that setting HOME to a relative-path is probably a Bad
> Idea, and can/should be undefined behavior. As for absolute paths (and
> whether they should be POSIX, Windows, or either), that's a little
> less cut and dry for me.
> I currently use a ton of s
I totally agree that setting HOME to a relative-path is probably a Bad
Idea, and can/should be undefined behavior. As for absolute paths (and
whether they should be POSIX, Windows, or either), that's a little
less cut and dry for me.
I currently use a ton of scripts of the general form:
Greetings, Corinna Vinschen!
> The problem the fix was *supposed* to fix (but it didn't) was to disallow
> incoming $HOME values which are non-POSIX or non-absolute paths. These
> $HOME values should be disregarded.
> So the idea was:
> set HOME=foo <- ignored, set HOME from passwd D
Greetings, Kiehl, Horst!
> Corinna Vinschen wrote:
>> The problem the fix was *supposed* to fix (but it didn't) was to disallow
>> incoming $HOME values which are non-POSIX or non-absolute paths. These
>> $HOME values should be disregarded.
>>
>> So the idea was:
>>
>> set HOME=foo
On Aug 5 11:09, Thomas Wolff wrote:
> Am 05.08.2015 um 09:54 schrieb Corinna Vinschen:
> >On Aug 4 20:53, Achim Gratz wrote:
> >>Warren Young writes:
> >>>Here’s an interesting experiment to try on your non-Cygwin POSIX boxes:
> >>>
> >>> $ HOME=/dfjkshkds bash -l
> >>> $ echo $HOME
> >>>
On Aug 5 09:19, Kiehl, Horst wrote:
> Corinna Vinschen wrote:
>
> > The problem the fix was *supposed* to fix (but it didn't) was to disallow
> > incoming $HOME values which are non-POSIX or non-absolute paths. These
> > $HOME values should be disregarded.
> >
> > So the idea was:
> >
> > se
Corinna Vinschen wrote:
> The problem the fix was *supposed* to fix (but it didn't) was to disallow
> incoming $HOME values which are non-POSIX or non-absolute paths. These
> $HOME values should be disregarded.
>
> So the idea was:
>
> set HOME=foo<- ignored, set HOME from pas
Am 05.08.2015 um 09:54 schrieb Corinna Vinschen:
On Aug 4 20:53, Achim Gratz wrote:
Warren Young writes:
Here’s an interesting experiment to try on your non-Cygwin POSIX boxes:
$ HOME=/dfjkshkds bash -l
$ echo $HOME
Guess what it prints.
Hint: It isn’t the second-to-last field in
On Aug 4 20:53, Achim Gratz wrote:
> Warren Young writes:
> > Here’s an interesting experiment to try on your non-Cygwin POSIX boxes:
> >
> > $ HOME=/dfjkshkds bash -l
> > $ echo $HOME
> >
> > Guess what it prints.
> >
> > Hint: It isn’t the second-to-last field in /etc/passwd. :)
This is
Am 04.08.2015 um 20:14 schrieb Warren Young:
On Aug 4, 2015, at 1:50 AM, Achim Gratz wrote:
Corinna Vinschen cygwin.com> writes:
It's ignored as $HOME in the Cygwin DLL. It's apparently not ignored in
the base-files package, but that's another problem.
...to which the possible solutions are
Warren Young writes:
> When you speak of this in terms of processes, I think you mean that
> the Cygwin DLL would need to filter the environment, which sounds
> heavy-handed.
Cygwin DLL already does some conversions of the Windows environment. It
could (hypothetically) do a more thorough job and/
On Aug 4, 2015, at 1:50 AM, Achim Gratz wrote:
>
> Corinna Vinschen cygwin.com> writes:
>> It's ignored as $HOME in the Cygwin DLL. It's apparently not ignored in
>> the base-files package, but that's another problem.
>
> ...to which the possible solutions are:
>
> 1. Not hand a botched HOME
Corinna Vinschen cygwin.com> writes:
> It's ignored as $HOME in the Cygwin DLL. It's apparently not ignored in
> the base-files package, but that's another problem.
...to which the possible solutions are:
1. Not hand a botched HOME environment variable to Cygwin processes.
2. Do the same check
On Aug 3 20:43, Thomas Wolff wrote:
> Am 03.08.2015 um 15:19 schrieb Corinna Vinschen:
> >- When started from a non-Cygwin process, check if $HOME starts with a
> > slash (absolute POSIX path). Otherwise ignore it.
> > Addresses: https://cygwin.com/ml/cygwin/2015-07/msg00344.html
> I would ex
Am 03.08.2015 um 15:19 schrieb Corinna Vinschen:
- When started from a non-Cygwin process, check if $HOME starts with a
slash (absolute POSIX path). Otherwise ignore it.
Addresses: https://cygwin.com/ml/cygwin/2015-07/msg00344.html
I would expect $HOME to be considered if it denotes an ab
Hi Cygwin friends and users,
I released another version of Cygwin. The version number is 2.2.0-1.
What's new:
---
- New APIs: getcontext, setcontext, makecontext, swapcontext.
- New functions: sigsetjmp, siglongjmp.
These were only available as macros up to now, but POSIX requires
23 matches
Mail list logo
