Am 03.07.2016, 13:14 Uhr, schrieb Corinna Vinschen:
You don't even need a symlink. This will show the same result:
exec >out1
rm out1
[[ -w /dev/fd/1 ]] || echo /dev/fd/1 not writable 1>&2
I noticed that too meanwhile, but I thought you would not need that
information ;)
It's only ab
On Jul 1 22:40, Helmut Karlowski wrote:
> Cygwin seems to look up a symlink wrong:
>
> When the target-file is unlinked while it is used by a process the file
> still exists and the symlink should point to that file.
>
> Test:
>
> ln -s out1 lout1
> exec >lout1
> rm out1
> [[ -w /dev/fd/1 ]] ||
> -Original Message-
> Vinschen
> Sent: Thursday, April 10, 2014 9:00 AM
> Subject: Re: symlinks to scripts not found in path
>
> On Apr 10 15:51, KARR, DAVID wrote:
> > On my old 32-bit Win7 box running Cygwin 1.7.26, I have an executable
> > script that is
On Apr 10 15:51, KARR, DAVID wrote:
> On my old 32-bit Win7 box running Cygwin 1.7.26, I have an executable script
> that is intended to be symlinked to and executed as the symlink name. This
> works fine.
>
> On my new 64-bit Win7 box running Cygwin 1.7.29, I created the symlink using
> "ln -
On 12/16/2011 11:46 AM, Jon Clugston wrote:
On Fri, Dec 16, 2011 at 11:20 AM, Andrew DeFaria wrote:
On 12/15/2011 07:40 PM, Larry Hall (Cygwin) wrote:
I'm having difficulty seeing how what you have described could work unless
the consumers of these files are looking for symlinks only, which y
On Fri, Dec 16, 2011 at 11:20 AM, Andrew DeFaria wrote:
> On 12/15/2011 07:40 PM, Larry Hall (Cygwin) wrote:
>>
>> I'm having difficulty seeing how what you have described could work unless
>> the consumers of these files are looking for symlinks only, which your
>> example above contradicts. And
On 12/15/2011 07:40 PM, Larry Hall (Cygwin) wrote:
I'm having difficulty seeing how what you have described could work
unless the consumers of these files are looking for symlinks only,
which your example above contradicts. And both of the ".bashrc" files
are registering as plain files, so I t
On 12/15/2011 6:47 PM, Andrew DeFaria wrote:
On 12/14/2011 2:32 PM, Andrew DeFaria wrote:
On 12/14/2011 12:14 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Might CYGWIN=winsymlinks help?
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
I don't see how. I think that I need the .lnk portion o
On 12/14/2011 2:32 PM, Andrew DeFaria wrote:
On 12/14/2011 12:14 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Might CYGWIN=winsymlinks help?
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
I don't see how. I think that I need the .lnk portion of the file.
It's not clear to me from that lin
On 12/14/2011 12:14 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Might CYGWIN=winsymlinks help?
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
I don't see how. I think that I need the .lnk portion of the file. It's
not clear to me from that link's description that setting winsymlinks
give
Jeremy Bopp sent the following at Wednesday, December 14, 2011 3:01 PM
>On 12/14/2011 01:33 PM, Andrew DeFaria wrote:
>> I like having only one home directory. It's extremely convenient to have
>> the same settings and the like both when on Cygwin and when on Linux.
>>
>> Often home directories are
On 12/14/2011 01:33 PM, Andrew DeFaria wrote:
> I like having only one home directory. It's extremely convenient to have
> the same settings and the like both when on Cygwin and when on Linux.
>
> Often home directories are on NAS's and the like and served out via smb.
>
> Somewhere along the lin
Corinna Vinschen sent the following at Friday, March 05, 2010 10:33 AM
>On Mar 5 09:11, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>> Does someone have a script that converts symbolic links from "Windows
>> shortcuts with a special header and the R/O attribute set" to "plain files
>> with a magic n
On Mar 5 09:11, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Does someone have a script that converts symbolic links from "Windows
> shortcuts with a special header and the R/O attribute set" to "plain files
> with a magic number, a path and the system attribute set". (See
> "(no)winsymlinks" in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 10/4/2009 2:19 PM:
> The Cygwin symlink(2) call does not add the .exe suffix, neither in
> Cygwin 1.5, nor in Cygwin 1.7. It looks like a feature of the ln(1)
> tool from the Cygwin 1.5 coreutils, AFAICS.
Yes, the 1.5
David Antliff wrote:
In my experience, it should be possible to create symlinks to any
arbitrary target, regardless of whether it actually exists or not.
Therefore, if I create a symlink to "/bin/ls" then I'd expect that to
be the content of the symlink - the automatic behaviour of rewriting
it t
On Oct 5 09:12, David Antliff wrote:
> 2009/10/5 Vincent Rivière :
> > Do you agree this is a bug and it should be fixed ?
>
> I've got nothing to do with the code, but I am an interested observer.
>
> In my experience, it should be possible to create symlinks to any
> arbitrary target, regardle
2009/10/5 Vincent Rivière :
> Do you agree this is a bug and it should be fixed ?
I've got nothing to do with the code, but I am an interested observer.
In my experience, it should be possible to create symlinks to any
arbitrary target, regardless of whether it actually exists or not.
Therefore,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Vincent Rivière on 10/4/2009 6:21 AM:
> $ ln -s /bin/ls lls
> $ ls -l lls
> lrwxrwxrwx 1 vincent cygwin 11 Oct 4 14:13 lls -> /bin/ls.exe
>
> Do you agree this is a bug and it should be fixed ?
I'm not sure whether I agree that it is a
Jason -
Looks like just the right fix. Thanks for all the good work.
- Steve
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/fa
Steve,
On Tue, Apr 19, 2005 at 08:48:16AM -0400, Jason Tishler wrote:
> You can workaround the problem by defining PYTHONCASEOK:
>
> $ PYTHONCASEOK= python -c 'import bar'
> $
>
> I will work with the Python developers to try to come up with a better
> long term solution.
I have found t
Jason -
Thanks for all the good work. The PYTHONCASEOK workaround
indeed seems to solve the problem. From your description,
it seems that the trouble is that the real name (the name
of the symlink target) is used rather than the name of the
symlink; I should be able to circumvent naming problem
On Tue, Apr 19, 2005 at 10:27:08AM -0400, Igor Pechtchanski wrote:
>On Tue, 19 Apr 2005, Jason Tishler wrote:
>>On Fri, Apr 15, 2005 at 10:12:56PM -0400, Jason Tishler wrote:
>>>On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
Can you try my failing experiment (symlink bar.py to file
On Tue, 19 Apr 2005, Jason Tishler wrote:
> Steve,
>
> On Fri, Apr 15, 2005 at 10:12:56PM -0400, Jason Tishler wrote:
> > On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
> > > Can you try my failing experiment (symlink bar.py to file foo.py in
> > > same directory)?
> >
> > I was able
Steve,
On Fri, Apr 15, 2005 at 10:12:56PM -0400, Jason Tishler wrote:
> On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
> > Can you try my failing experiment (symlink bar.py to file foo.py in
> > same directory)?
>
> I was able reproduce your problem on my way out of work today.
>
>
Steve,
On Fri, Apr 08, 2005 at 01:39:23PM -0400, Steve Ward wrote:
> (3) Thinking that the realpath bug might be a key
> to the python import-thru-symlinks problem,
> I ran a simple test on recent cygwin/python
> combinations, finding:
>
> Cygwin version Python version
Steve,
On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
> Can you try my failing experiment (symlink bar.py to file foo.py in
> same directory)?
I was able reproduce your problem on my way out of work today.
> It seems using a different name for the symlink may cause the
> trouble...
Jason, RE:
Sorry, but I cannot reproduce the above problem with the latest
snapshot:
$ uname -a
CYGWIN_NT-5.1 gelpdevjt022 1.5.15s(0.126/4/2) 20050408 16:35:04 ...
$ python -V
Python 2.4
$ ls -l
total 0
lrwxrwxrwx1 jtishler Do
Steve,
On Wed, Apr 06, 2005 at 05:04:52PM -0400, Steve Ward wrote:
> I just upgraded to cygwin 1.5.14 from 1.5.12, and python (version 2.4
> in both cases) stopped being able to import thru symlinks.
>
> Test case: in a directory containing a symlink to foo.py,
>
>python
>import foo
>
>
RE:
> (3) Thinking that the realpath bug might be a key
> to the python import-thru-symlinks problem,
> I ran a simple test on recent cygwin/python
> combinations, finding:
>
> Cygwin version Python version realpath Import
> 1
[snip]
> (3) Thinking that the realpath bug might be a key
> to the python import-thru-symlinks problem,
> I ran a simple test on recent cygwin/python
> combinations, finding:
>
> Cygwin version Python version realpath Import
> 1.5.xx: 2.yy:
RE:
I just upgraded to cygwin 1.5.14 from 1.5.12, and python
(version 2.4 in both cases) stopped being able to import
thru symlinks.
Test case: in a directory containing a symlink to foo.py,
python
import foo
complains "no module named foo.py"; if I copy the file to
Thanks all it works now.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Hi Jorge,
try
$PROG2 = "C:cygwinbootplinuxinstall";
^^^^ ^^ ^^ ^^
Regards,
Jorg
>-Original Message-
>From: Jorge Goncalvez [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, February 06, 2002 11:31 AM
>To: [EMAIL PROTECTED]
>Subject: Re:s
34 matches
Mail list logo
