From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Priority cookies in org-store-link Date: Mon, 24 Dec 2012 01:56:24 +0100 Message-ID: <87623sw9mv.fsf@bzg.ath.cx> References: <87ehj78usv.wl%william.lechelle@ens-lyon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40877) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TmwLD-0002rM-AE for emacs-orgmode@gnu.org; Sun, 23 Dec 2012 19:56:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TmwLC-0006we-3V for emacs-orgmode@gnu.org; Sun, 23 Dec 2012 19:56:27 -0500 Received: from mail-we0-f170.google.com ([74.125.82.170]:55855) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TmwLB-0006wa-TJ for emacs-orgmode@gnu.org; Sun, 23 Dec 2012 19:56:26 -0500 Received: by mail-we0-f170.google.com with SMTP id r1so3186842wey.29 for ; Sun, 23 Dec 2012 16:56:25 -0800 (PST) In-Reply-To: <87ehj78usv.wl%william.lechelle@ens-lyon.fr> ("William =?iso-8859-1?Q?L=E9chelle=22's?= message of "Mon, 03 Dec 2012 02:21:52 -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: William =?iso-8859-1?Q?L=E9chelle?= Cc: emacs-orgmode Hi William, William Léchelle writes: > As for a recent git version, calling org-store-link on a subtree records its > priority cookie in the link, which therefore breaks if the said priority is > changed (“no match - create this as a new heading ?”) > > Links not featuring the priority succeed at finding the headline which has such > a priority mark, so I suggest the priority is removed from the > captured link. This is now the case in master, it will be part of 8.0. Thanks for the suggestion. > As a side note, testing to ask this, it looks like captured links won't take > into account header text after < or >, hence capturing links to headlines > featuring these will fail, is there a known issue about accepted characters in > headlines that I'm not aware of ? There should be none, please test master if you can and report any problem. Best, -- Bastien