From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Fwd: Mac OS Alias file links
Date: Mon, 14 Apr 2014 08:42:49 -0400 [thread overview]
Message-ID: <87y4z8hyk6.fsf@gmail.com> (raw)
In-Reply-To: m2y4z8ywmf.fsf@gmail.com
Ken Mankoff <mankoff@gmail.com> writes:
> Hi Bastien,
>
> Thanks for letting me know it displays properly and email received. The
> URL works for me this morning too.
>
> On 2014-04-14 at 05:22, Bastien wrote:
>> Even for those who uses MacOSX, you should perhaps be more specific
>> on how Org-mode would store such links, then somebody might step up.
>
> Aliases are a type of links ("ln" on linux, "shortcut" on Windows
> "alias" on OS X (OS X of course also supports "ln")). The difference
> between an OS X alias and "ln" is that if the target is moved, the OS X
> alias still points to it, and double-clicking on an alias (or issuing
> the "open" command in a terminal) will open the target, wherever it
> is. I just checked in a VM and Windows Shortcuts also behave this way.
>
> Therefore, if in addition to "file:" there were an "alias:" option, Org
> could link to files that move. I think this is a powerful feature. I
> imagine "alias:" would be an option when I press C-cl, and a way to set
> it as the default when I press C-ucl.
>
> That is, links would be [[alias:foo][FileName]] where "foo" is a string
> version (hashed?) of the alias.
>
> In BibDesk, "foo" is ~1200 characters long, and according to the BibDesk
> documentation, that ~1200 characters is:
>
>> The Bdsk-File entries store Mac OS aliases, which contain a file ID
>> and absolute path. Bdsk-File entries also store a relative path, which
>> is used if the alias is broken.
>
> So it looks like an Alias can be hashed some way and stored as just a
> string. An example BibDesk entry in by BibTeX file looks like:
>
> @article{citekey,
> Author = {Someone},
> Journal = {Nature},
> Pages = {24--42},
> Title = {{A Paper}},
> Bdsk-File-1 = {YnBsa...etc for 1200 characters...}}
>
> Opening the file with C-o would involve un-hashing it, and then treating
> it the same way a "file:" is opened.
>
> I imagine Org would mostly store the links the same way it stores file
> links. The change would be that since the link is the alias (long ugly
> string), the description would be required, and perhaps default to
> /path/to/filename. Although since the whole point is that the /path/to/
> can change, perhaps the default name would just be filename.
>
What does emacs do when you C-x C-f an alias?
If it opens it properly (i.e. opens the target file) then why is
anything needed in org? It seems to me that a file: link should just
work.
If it does not, then maybe that's where the capability should be added.
Org seems to be the wrong place for it.
But note that everything I know about aliases, I learnt in the last five
minutes, so I could be way off the mark.
--
Nick
next prev parent reply other threads:[~2014-04-14 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 7:03 Mac OS Alias file links Ken Mankoff
2014-04-13 22:39 ` Fwd: " Ken Mankoff
2014-04-14 9:22 ` Bastien
2014-04-14 11:32 ` Ken Mankoff
2014-04-14 12:42 ` Nick Dokos [this message]
2014-04-14 13:17 ` Ken Mankoff
2014-04-14 16:26 ` Achim Gratz
2014-04-14 16:48 ` Ken Mankoff
2014-04-14 17:42 ` Charles Berry
2014-04-14 18:36 ` Ken Mankoff
2014-04-14 23:19 ` Ivan Andrus
2014-04-15 0:21 ` Charles C. Berry
2014-04-15 1:58 ` Ken Mankoff
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4z8hyk6.fsf@gmail.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).