Greetings, Rainer Emrich!
> Ok, so I can't rely on powershell here. Is there a recommended procedure
> for what I try in a script?
> Check if the current cygwin environment is able to create native symlinks.
There's more than just Cygwin involved.
1. Target FS may not support symlinks.
2. User
Am 03.03.2020 um 17:41 schrieb Corinna Vinschen:
> On Mar 3 17:05, Rainer Emrich wrote:
>> Am 03.03.2020 um 16:49 schrieb Corinna Vinschen:
>>> On Mar 3 15:31, Corinna Vinschen wrote:
On Mar 3 15:19, Rainer Emrich wrote:
> Am 03.03.2020 um 14:39 schrieb Corinna Vinschen:
>> Aha! So
On Mar 3 17:05, Rainer Emrich wrote:
> Am 03.03.2020 um 16:49 schrieb Corinna Vinschen:
> > On Mar 3 15:31, Corinna Vinschen wrote:
> >> On Mar 3 15:19, Rainer Emrich wrote:
> >>> Am 03.03.2020 um 14:39 schrieb Corinna Vinschen:
> Aha! So powershell does not show the 'l'.
> >>> The most im
Am 03.03.2020 um 16:49 schrieb Corinna Vinschen:
> On Mar 3 15:31, Corinna Vinschen wrote:
>> On Mar 3 15:19, Rainer Emrich wrote:
>>> Am 03.03.2020 um 14:39 schrieb Corinna Vinschen:
Aha! So powershell does not show the 'l'.
>>> The most important thing is the difference between cygwin 3.0
On Mar 3 15:31, Corinna Vinschen wrote:
> On Mar 3 15:19, Rainer Emrich wrote:
> > Am 03.03.2020 um 14:39 schrieb Corinna Vinschen:
> > > Aha! So powershell does not show the 'l'.
> > The most important thing is the difference between cygwin 3.0.7 and
> > cygwin 3.1.4. For cygwin 3.0.7 the link
On Mar 3 15:19, Rainer Emrich wrote:
> Am 03.03.2020 um 14:39 schrieb Corinna Vinschen:
> > Aha! So powershell does not show the 'l'.
> The most important thing is the difference between cygwin 3.0.7 and
> cygwin 3.1.4. For cygwin 3.0.7 the link indicator is shown even in
> powershell on Windows
Am 03.03.2020 um 14:39 schrieb Corinna Vinschen:
> On Mar 3 14:17, Rainer Emrich wrote:
>> Dear Corinna,
>>
>> Am 02.03.2020 um 17:48 schrieb Corinna Vinschen:
>>> On Feb 29 14:10, Rainer Emrich wrote:
I try to reliably determine if native Windows symlink are working for a
current cygwin
On Mar 3 14:17, Rainer Emrich wrote:
> Dear Corinna,
>
> Am 02.03.2020 um 17:48 schrieb Corinna Vinschen:
> > On Feb 29 14:10, Rainer Emrich wrote:
> >> I try to reliably determine if native Windows symlink are working for a
> >> current cygwin environment in a shell script.
> >> [...]
> >> On cy
Dear Corinna,
Am 02.03.2020 um 17:48 schrieb Corinna Vinschen:
> On Feb 29 14:10, Rainer Emrich wrote:
>> I try to reliably determine if native Windows symlink are working for a
>> current cygwin environment in a shell script.
>>
>> Therefor I used a powershell snipped:
>>
>> mkdir asdfgh
>> ln -s
On Feb 29 14:10, Rainer Emrich wrote:
> I try to reliably determine if native Windows symlink are working for a
> current cygwin environment in a shell script.
>
> Therefor I used a powershell snipped:
>
> mkdir asdfgh
> ln -s asdfgh/ asdfgh-1
> powershell "& {Get-Item -Path asdfgh-1 | Select-Obj
Hi Andrey,
Am 01.03.2020 um 02:52 schrieb Andrey Repin:
>> I try to reliably determine if native Windows symlink are working for a
>> current cygwin environment in a shell script.
>
>> Therefor I used a powershell snipped:
>
>> mkdir asdfgh
>> ln -s asdfgh/ asdfgh-1
>> powershell "& {Get-Item -P
Greetings, Rainer Emrich!
> I try to reliably determine if native Windows symlink are working for a
> current cygwin environment in a shell script.
> Therefor I used a powershell snipped:
> mkdir asdfgh
> ln -s asdfgh/ asdfgh-1
> powershell "& {Get-Item -Path asdfgh-1 | Select-Object}"
> On cyg
I try to reliably determine if native Windows symlink are working for a
current cygwin environment in a shell script.
Therefor I used a powershell snipped:
mkdir asdfgh
ln -s asdfgh/ asdfgh-1
powershell "& {Get-Item -Path asdfgh-1 | Select-Object}"
On cygwin 3.0.7 the output is as follows:
13 matches
Mail list logo
