public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: cygwin, Coda and symbolic links
Date: Fri, 04 Aug 2006 20:55:00 -0000	[thread overview]
Message-ID: <eb0c5m$o4r$2@sea.gmane.org> (raw)
In-Reply-To: <Pine.GSO.4.63.0608041648270.17434@access1.cims.nyu.edu>

Igor Peshansky wrote:
> On Fri, 4 Aug 2006, Adam Wolbach wrote:
> 
>>> http://www.google.com/search?as_q=windows+shortcut+file+format
>>>
>>> The first match
>>>
>>> http://mediasrv.ns.ac.yu/extra/fileformat/windows/lnk/shortcut.pdf
>>>
>>> is what you're looking for and what I used when implementing the
>>> shortcut stuff.
>> Thanks, this gets me more than halfway to what I need to know -- the
>> missing piece is how these fields need to be filled out to appear as a
>> symbolic link to cygwin. Worst case I can just hunt through the cygwin
>> source, but if you happen to know or have notes lying around somewhere,
>> it might be useful to more than just us to post them somewhere. Thanks
>> again.
> 
> Your best source of information is probably symlink_worker() in
> <http://cygwin.com/cgi-bin/cvsweb.cgi/~checkout~/src/winsup/cygwin/path.cc?content-type=text/plain&cvsroot=src&only_with_tag=HEAD>.
> HTH,
> 	Igor

Ah, yes, the RTFSC I saw coming a mile away. ;-)

...but it's a very helpful pointer to a specific place (and being a link 
makes it easy to read; no mucking with downloading files or whatnot). I 
hope Adam will appreciate your thoughtfulness. :-)

-- 
Matthew
Only Joe suffers from schizophrenia. The rest of us enjoy it.

           reply	other threads:[~2006-08-04 20:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.GSO.4.63.0608041648270.17434@access1.cims.nyu.edu>]

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='eb0c5m$o4r$2@sea.gmane.org' \
    --to=mwoehlke@tibco.com \
    --cc=cygwin-talk@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).