public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: WSL symbolic links
Date: Sat, 28 Mar 2020 12:30:06 +0100	[thread overview]
Message-ID: <70efa42d-1699-058c-34d6-7f473dd2e3fb@towo.net> (raw)
In-Reply-To: <f5beetc6a97.fsf@ecclerig.inf.ed.ac.uk>

Am 28.03.2020 um 11:31 schrieb Henry S. Thompson via Cygwin:
> Brian Inglis writes:
>
>> ...  wished for a while: a program that would classify a file name as
>> a (regular) hard link, a Windows directory or file link, a junction, a
>> Windows shortcut, a Cygwin symlink, a Unix/WSL symlink, a URL link,
>> and/or tell me where it links to etc. Thinking of hacking that plus
>> maybe bits of file, cygpath, readshortcut, readlink, lsattr together
>> to display otherwise awkward to access attributes and properties.
> Oh, yes please!  You could call it 'swan', for Swiss Army Knife :-).
Or maybe simply an additional option for `ls -l`?

  reply	other threads:[~2020-03-28 11:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  9:00 Thomas Wolff
2020-03-26 11:00 ` Corinna Vinschen
2020-03-26 16:15   ` Thomas Wolff
2020-03-26 19:12   ` Brian Inglis
2020-03-26 19:56     ` Corinna Vinschen
2020-03-26 23:52       ` Thomas Wolff
2020-03-27  5:46         ` ASSI
2020-03-27 11:21         ` Corinna Vinschen
2020-03-27 12:24           ` Thomas Wolff
2020-03-27 13:01             ` Corinna Vinschen
2020-03-27 14:43               ` Thomas Wolff
2020-03-26 20:05     ` Corinna Vinschen
2020-03-27 17:58       ` Brian Inglis
2020-03-27 18:53         ` Corinna Vinschen
2020-03-28  3:32           ` Brian Inglis
2020-03-28 10:31             ` Henry S. Thompson
2020-03-28 11:30               ` Thomas Wolff [this message]
2020-03-28 11:59             ` Andrey Repin
2020-03-28 20:45               ` Brian Inglis
2020-03-29 11:52                 ` Andrey Repin
2020-03-30  8:46             ` Corinna Vinschen
2020-04-04 14:32   ` Denis Excoffier
2020-04-05 15:22     ` 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=70efa42d-1699-058c-34d6-7f473dd2e3fb@towo.net \
    --to=towo@towo.net \
    --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).