From: Ken Mankoff <mankoff@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Fwd: Mac OS Alias file links
Date: Mon, 14 Apr 2014 14:36:14 -0400 [thread overview]
Message-ID: <m2ha5vzrkx.fsf@gmail.com> (raw)
In-Reply-To: <loom.20140414T192503-957@post.gmane.org>
On 2014-04-14 at 13:42, Charles Berry wrote:
> The point of using an alias rather than a filename or the name of a
> symbolic link that points to the file is that it inherits the property
> of Mac OS X aliases that moving the file does not break the alias ---
> it still points to file.
Exactly!
> For this to work as you fantasize, you would need to enable the Finder
> application to modify the part of the *.org file that encodes the
> alias when you change the location of the aliased file just as the
> Finder does to the alias when the location of the aliased file is
> modified in the Finder.
I don't think so. I'm not sure how BibDesk handles it, but my BibTeX
file is not modified when I move the PDF that is linked to an entry via
that 1200 character field that encodes the alias. Clearly BibDesk does
something neat to encode and decode that field, but once created, the OS
nor Finder know anything about that line or the file containing it. I
don't think Finder would need to know about a string in an Org file
either.
> OTOH, writing an AppleScript to make an alias in a folder that is
> never moved, writing elisp to call that script and then make an
> org-mode link to the alias just created might work for you.
Yes this would work too as a hack.
-k.
next prev parent reply other threads:[~2014-04-14 18:36 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
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 [this message]
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=m2ha5vzrkx.fsf@gmail.com \
--to=mankoff@gmail.com \
--cc=ccberry@ucsd.edu \
--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).