From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Agenda buffer and relative links
Date: Fri, 06 Jan 2012 14:16:23 +0100 [thread overview]
Message-ID: <80sjjtj7iw.fsf@somewhere.org> (raw)
In-Reply-To: 87zke1kptn.fsf@iro.umontreal.ca
Hi François,
François Pinard wrote:
> Nick Dokos <nicholas.dokos-VXdhtT5mjnY@public.gmane.org> writes:
>
>> François Pinard <pinard-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org> wrote:
>
>>> When Org mode defines a link for me, it sometimes changes it so it
>>> becomes relative. [...] This is OK in general, but not always.
>>> [...] I have feeling that there is something deeper which might
>>> likely affect many Org mode users, and for which I have no general
>>> solution to offer.
>
>> Check
>> (info "(org) Handling links")
>> in the manual, particularly the doc for C-u C-c C-l.
>
> Hi, Nick, and gang.
>
> Yes, I knew about prefixes to C-c C-l, which may be used to force links
> to be absolute. Systematic use of C-u C-u C-c C-l instead of C-c C-l
> would be tedious, that's why I think there is a deeper problem about the
> current defaults.
>
> There is a virtue in relative links which I recognize. So having an
> option to force all links to be absolute might not be a solution.
> Having all links relative just cannot work. Letting the user properly
> manage is quite error-prone, and fairly annoying at least.
Would this help you?
┏━━━━
┃ org-link-file-path-type is a variable defined in `org.el'.
┃ Its value is adaptive
┃
┃ Documentation:
┃ How the path name in file links should be stored.
┃ Valid values are:
┃
┃ relative Relative to the current directory, i.e. the directory of the file
┃ into which the link is being inserted.
┃ absolute Absolute path, if possible with ~ for home directory.
┃ noabbrev Absolute path, no abbreviation of home directory.
┃ adaptive Use relative path for files in the current directory and sub-
┃ directories of it. For other files, use an absolute path.
┗━━━━
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-01-06 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 3:39 Agenda buffer and relative links François Pinard
2012-01-06 4:43 ` Nick Dokos
2012-01-06 11:55 ` François Pinard
2012-01-06 13:16 ` Sebastien Vauban [this message]
2012-01-07 17:39 ` François Pinard
2012-01-07 19:26 ` François Pinard
2012-01-07 20:58 ` Sebastien Vauban
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=80sjjtj7iw.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).