From mboxrd@z Thu Jan 1 00:00:00 1970 From: ST Subject: Re: Link abbreviations: include abbreviation table and linkwords with spaces Date: Tue, 13 Mar 2018 13:53:23 +0200 Message-ID: <1520942003.1930.32.camel@gmail.com> References: <1520886927.1793.99.camel@gmail.com> <87r2ooanzd.fsf@nicolasgoaziou.fr> <1520931065.1930.4.camel@gmail.com> <871sgo8hbj.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45373) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eviUl-0004yS-CI for Emacs-orgmode@gnu.org; Tue, 13 Mar 2018 07:53:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eviUh-0003jL-GF for Emacs-orgmode@gnu.org; Tue, 13 Mar 2018 07:53:31 -0400 Received: from mail-wr0-x236.google.com ([2a00:1450:400c:c0c::236]:40339) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eviUh-0003ip-8n for Emacs-orgmode@gnu.org; Tue, 13 Mar 2018 07:53:27 -0400 Received: by mail-wr0-x236.google.com with SMTP id m4so9003987wrb.7 for ; Tue, 13 Mar 2018 04:53:26 -0700 (PDT) In-Reply-To: <871sgo8hbj.fsf@nicolasgoaziou.fr> 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" To: Nicolas Goaziou Cc: Emacs-orgmode@gnu.org > >> > after reading "4.6 Link abbreviations" of the manual I have two > >> > questions: > >> > > >> > 1. is it possible to define linkwords with spaces, like this: [[Harry > >> > Potter:Chapter1]], it looks much more nice than > >> > [[Harry_Potter:Chapter1]]? > >> > >> I think so. > > > > If yes, then it's really worth mentioning this fact in the manual (4.6 > > Link abbreviations) because ones get the impression that only - and _ > > are allowed. One of the most strong sides of org is its readability as > > raw text and in this case space makes link more readable. > > My bad. Spaces are not allowed, because > > #+LINK: linkword URL > > would not be parse-able. #+LINK: link word URL Why should this not be parse-able? Cut #+LINK: from the beginning, URL (last token) from the end, and the rest will be "link word", even with (several) spaces in between... Thanks.