From mboxrd@z Thu Jan 1 00:00:00 1970 From: pinard@iro.umontreal.ca (=?utf-8?Q?Fran=C3=A7ois?= Pinard) Subject: Re: Agenda buffer and relative links Date: Sat, 07 Jan 2012 14:26:44 -0500 Message-ID: <87hb07l3ez.fsf@iro.umontreal.ca> References: <87zke1ebyj.fsf@iro.umontreal.ca> <8067.1325825020@alphaville.dokosmarshall.org> <87zke1kptn.fsf@iro.umontreal.ca> <80sjjtj7iw.fsf@somewhere.org> <87mx9zl8df.fsf@iro.umontreal.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:38370) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rjbug-0002n3-8u for emacs-orgmode@gnu.org; Sat, 07 Jan 2012 14:26:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rjbuf-0005AM-CS for emacs-orgmode@gnu.org; Sat, 07 Jan 2012 14:26:46 -0500 Received: from 206-248-137-202.dsl.teksavvy.com ([206.248.137.202]:58392 helo=mercure.epsilon-ti.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rjbuf-0005AI-8C for emacs-orgmode@gnu.org; Sat, 07 Jan 2012 14:26:45 -0500 In-Reply-To: <87mx9zl8df.fsf@iro.umontreal.ca> (=?utf-8?Q?=22Fran=C3=A7ois?= Pinard"'s message of "Sat, 07 Jan 2012 12:39:40 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org pinard@iro.umontreal.ca (Fran=C3=A7ois Pinard) writes: > The following message is a courtesy copy of an article > that has been posted to gmane.emacs.orgmode as well. Hmph, I now wonder if the link is bidirectional, and if messages posted to gmane.emacs.orgmode actually end up on emacs-orgmode@gnu.org. I'm repeating it all below, quoted. (Would someone be kind enough to tell me if it was seen on the mailing list?) A good solution imposed itself to my mind, a few minutes ago. I do not know how easy to implement it would be however. The real problem is that relative links within the agenda buffer are interpreted relative to the directory (M-x pwd) of the agenda buffer. Happily enough, each line of the agenda buffer is somehow associated with the buffer it comes from. Links within the agenda should be interpreted relative to the base directory of the buffer they come from, rather than from the agenda buffer itself. Fran=C3=A7ois > "Sebastien Vauban" > writes: >> Hi Fran=C3=A7ois, > Hello, Sebastien! >> Fran=C3=A7ois Pinard wrote: >>> Nick Dokos writes: >>>> Fran=C3=A7ois Pinard = 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. >>> 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. >> Would this help you? >> =E2=94=8F=E2=94=81=E2=94=81=E2=94=81=E2=94=81 >> =E2=94=83 org-link-file-path-type is a variable defined in `org.el'. >> =E2=94=97=E2=94=81=E2=94=81=E2=94=81=E2=94=81 > Maybe, I might even end up using it, who knows. It does not solve the > problem I tried to describe. Relative links allow for moving whole > hierarchies elsewhere, so the current default Org behaviour is good. > But not good enough for the agenda buffer. Links do not always work in > there, and this is the problem to solve. The problem has ramifications. > Fran=C3=A7ois > P.S. Nice way to quote, by the way! :-)