From: matthew patton <pattonme@yahoo.com>
To: Andrey Repin via Cygwin <cygwin@cygwin.com>
Subject: Re: Cygwin tool to differ junctions from soft links?
Date: Thu, 16 Nov 2023 18:55:23 +0000 (UTC) [thread overview]
Message-ID: <1439487749.2493319.1700160923985@mail.yahoo.com> (raw)
In-Reply-To: <48998319.20231116114707@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
AFAIK no. what I do is re-implement 'ln' with a wrapper because the Cygwin behavior (Junctions) was driving me up the wall.
https://github.com/tb3088/shell-environment/blob/ccf7aa161899c2c4ebe2d9e980e674bc726a3ef3/.functions_os.CYGWIN_NT#L9
============
"In the information society, nobody thinks. We expected to banish paper, but we actually banished thought.” -- Michael Crichton, Jurassic Park
“Ours may become the first civilization destroyed, not by the power of our enemies, but by the ignorance of our teachers and the dangerous nonsense they are teaching our children. In an age of artificial intelligence, they are creating artificial stupidity.' - Thomas Sowell
On Thursday, November 16, 2023 at 03:50:24 AM EST, Andrey Repin via Cygwin <cygwin@cygwin.com> wrote:
Greetings, Martin Wege!
> Does Cygwin have a command line tool (Scriptable!) which can be used
> to differ between soft links and Windows junctions?
It would be easier to help you, if you specify the purpose of your request.
I.e. what you want to achieve with such tool.
--
With best regards,
Andrey Repin
Thursday, November 16, 2023 11:46:09
Sorry for my terrible english...
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2023-11-16 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 9:14 Martin Wege
2023-11-16 7:29 ` Martin Wege
2023-11-17 1:59 ` Doug Henderson
2023-11-16 8:47 ` Andrey Repin
2023-11-16 18:55 ` matthew patton [this message]
2023-11-16 20:30 ` Brian Inglis
2023-11-17 5:54 ` Thomas Wolff
2023-11-17 12:06 ` Corinna Vinschen
2023-11-17 14:56 ` Brian Inglis
2023-11-17 18:44 ` matthew patton
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=1439487749.2493319.1700160923985@mail.yahoo.com \
--to=pattonme@yahoo.com \
--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).