emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Clemente <n142857@gmail.com>
To: emacs-orgmode@gnu.org, n.goaziou@gmail.com
Subject: <<< >>> radio links should not match empty text
Date: Tue, 01 Apr 2014 11:42:41 +0700	[thread overview]
Message-ID: <878urp64ou.wl%n142857@gmail.com> (raw)

Hi, recently this syntax: <<< >>> started highlighting all spaces (spaces between words) as if they were links. I see them with a blue underline.
  I found this because I used some Unicode-art like <<<<<<<<< >>>>>>>>> where I certainly didn't mean to define a radio link.

  This happens since this change:

commit 1c1936fbb1f0c42e5c7e1d3c903626aa5993a357
Author: Nicolas Goaziou <n.goaziou@gmail.com>
Date:   Tue Mar 25 10:15:25 2014 +0100

    Allow radio links after an apostrophe and mid-word
    * lisp/org.el (org-make-target-link-regexp): Allow radio links after
      an apostrophe and mid-word.  Small refactoring.
    * testing/lisp/test-ox.el (test-org-export/resolve-radio-link): Add
    See http://permalink.gmane.org/gmane.emacs.orgmode/84108.


             reply	other threads:[~2014-04-01  4:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  4:42 Daniel Clemente [this message]
2014-04-02 12:59 ` <<< >>> radio links should not match empty text Nicolas Goaziou
2014-04-02 16:46   ` radio links in middle of words. (was: Re: <<< >>> radio links should not match empty text) Daniel Clemente
2014-04-02 16:57     ` radio links in middle of words Nicolas Goaziou
2014-04-04 14:25       ` Daniel Clemente
2014-04-04 18:59         ` Nicolas Goaziou
2014-04-10 12:40           ` Daniel Clemente
2014-04-10 21:43             ` Nicolas Goaziou
2014-04-11  9:42               ` Bastien
2014-04-11 19:33                 ` Nicolas Goaziou
2014-04-15  7:27               ` Daniel Clemente

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878urp64ou.wl%n142857@gmail.com \
    --to=n142857@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).