From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Target and link text normalised to `orgtargetn' Date: Thu, 16 Apr 2015 12:11:24 +0200 Message-ID: <87egnk9ycz.fsf@gmx.us> References: <20150414092530.GC2957@chitra.no-ip.org> <20150414120852.GD2957@chitra.no-ip.org> <87zj699ez9.fsf@gmx.us> <20150416001830.GC14328@chitra.no-ip.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yiglo-000297-Qx for emacs-orgmode@gnu.org; Thu, 16 Apr 2015 06:11:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yiglk-0001DZ-HE for emacs-orgmode@gnu.org; Thu, 16 Apr 2015 06:11:40 -0400 Received: from plane.gmane.org ([80.91.229.3]:40393) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yiglk-0001DT-AU for emacs-orgmode@gnu.org; Thu, 16 Apr 2015 06:11:36 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Yiglj-00052M-2r for emacs-orgmode@gnu.org; Thu, 16 Apr 2015 12:11:35 +0200 Received: from tsn109-201-154-150.dyn.nltelcom.net ([109.201.154.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Apr 2015 12:11:35 +0200 Received: from rasmus by tsn109-201-154-150.dyn.nltelcom.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Apr 2015 12:11:35 +0200 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 Suvayu Ali writes: > Hi Rasmus, > > On Thu, Apr 16, 2015 at 12:57:46AM +0200, Rasmus wrote: >> >> Could you try the attached patches and see if they solve your issues? > > Seems to work nicely. I'll keep using them rest of the week. Pushed. I removed support for radio targets as I don't really see the point in those supporting custom labeling. They are transcoded as <<> → \hyperref{label}{target} It makes little sense to label be the same as target, though it probably would not create problems. —Rasmus -- A clever person solves a problem. A wise person avoids it