From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Corneli Subject: Re: Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)] Date: Fri, 21 Apr 2017 00:02:53 +0100 Message-ID: References: <871ssnqjh6.fsf@gmail.com> <878tmu6fe0.fsf@nicolasgoaziou.fr> <87zifa4tkd.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52793) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d1L6G-0001cK-GS for emacs-orgmode@gnu.org; Thu, 20 Apr 2017 19:02:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d1L6F-0001fA-8q for emacs-orgmode@gnu.org; Thu, 20 Apr 2017 19:02:56 -0400 Received: from mail-ua0-x232.google.com ([2607:f8b0:400c:c08::232]:36284) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d1L6F-0001ew-3d for emacs-orgmode@gnu.org; Thu, 20 Apr 2017 19:02:55 -0400 Received: by mail-ua0-x232.google.com with SMTP id a1so67714885uaf.3 for ; Thu, 20 Apr 2017 16:02:54 -0700 (PDT) In-Reply-To: <87zifa4tkd.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: Org-mode mailing list The (xxx) form for a link target, especially one outside of a block, doesn't seem to have meaning within the document model that Org understands. So, yes, this explains *why* I am seeing the error described above. But I still think there is a legitimate bug report here, since the behaviour is not likely to be expected by the user. Someone in my position has no interest in code refs, I was only trying to link to a bit of text in the buffer. Saying "oh but you can't link to this *one* kind of text" is perhaps a fair move. On the other hand, given that "following a link" just means "run a search process", that search process *could* be smart enough to notice that "no coderef was found, maybe the user meant to link to some plain text in parentheses". Then I wouldn't see an error. On Thu, Apr 20, 2017 at 11:12 PM, Nicolas Goaziou wrote: > Joe Corneli writes: > >> In my opinion, capture and/or search should do something different for >> text beginning "(" and ending with ")", when this text is a link >> target that is not within a code block. > > See below. > >> The docs say: >> >> "In literal examples, Org will interpret strings like =E2=80=98(ref:name= )=E2=80=99 as >> labels" >> >> But the text (like this) in my example wasn't inside of a code block, >> nor was it presented as (ref:like this). > > There are two syntaxs: the one within the code block, which is (ref:xxx) > by default and can be changed, and the one outside the block, which is > (xxx), and cannot be changed. See the following example from the manual: > > #+BEGIN_SRC emacs-lisp -n -r > (save-excursion (ref:sc) > (goto-char (point-min))) (ref:jump) > #+END_SRC > In line [[(sc)]] we remember the current position. [[(jump)][Line (= jump)]] > jumps to point-min. > > Regards,