From: Nicolas Goaziou <email@example.com>
To: Daniel Clemente <firstname.lastname@example.org>
Subject: Re: radio links in middle of words.
Date: Fri, 04 Apr 2014 20:59:20 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Daniel Clemente's message of "Fri, 04 Apr 2014 21:25:03 +0700")
Daniel Clemente <email@example.com> writes:
> „Related thread“: http://comments.gmane.org/gmane.emacs.orgmode/82923
> I don't see in there any argument to have midword links, it's
> presented as a consequence of other patch.
I didn't say there was an argument there. I just pointed out that your
report was a known fact and that it was discussed elsewhere.
> I have notes about programs I tried, like <<<R>>>, <<<at>>> or
> <<<ps>>>, <<<C>>>, <<<CR>>> vs <<<LF>>> vs <<<CRLF>>>, 3-letter stock
> tickers, … so now I'm seeing blue links everywhere in the middle of
> words. I can get used to it, but it's ugly and not useful.
I can understand that.
> Can't we break at non-letters? Not at non-„word-constituents“, but at
> non-letters. If emacs doesn't provide that concept, better build it.
I don't know. Could you define precisely that concept?
next prev parent reply other threads:[~2014-04-04 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 4:42 <<< >>> radio links should not match empty text Daniel Clemente
2014-04-02 12:59 ` 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 [this message]
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
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 \
* 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).