emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: managing aggressive link activation within lines?
Date: Thu, 19 Dec 2019 14:03:21 +0100	[thread overview]
Message-ID: <875zic8o2u.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAN_Dec9eJvsfN9puujNHmX2vGA4CVG5MjQhgcjmoP+h6oMj-yQ@mail.gmail.com> (Matt Price's message of "Thu, 19 Dec 2019 06:57:39 -0500")

Hello,

Matt Price <moptop99@gmail.com> writes:

> Ah, interesting. That makes a lot of sense.  Would it be unworkably
> destructive for me to revert the link syntax locally ? I have no particular
> need  for the new functionality and the current situation has been a
> significant cognitive burden, not least because I make so many typos that I
> am constantly re-editing existing text.

There is no new functionality. The new link syntax is an important step
forward because it solves recurring issues that has plagued links for
years, e.g., when using hex-encoded URL. I don't think reverting it,
assuming it is manageable in the long run, is a good solution.

IMO, it would be more productive to think about what can be done in your
situation instead. For example, one solution could be to require "[[" to
be escaped in a link (current syntax already requires closing brackets
to be escaped in some situations). I'm not yet sure how to deal with it,
tho.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2019-12-19 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 16:32 managing aggressive link activation within lines? Matt Price
2019-12-19  7:55 ` Nicolas Goaziou
2019-12-19 11:57   ` Matt Price
2019-12-19 13:03     ` Nicolas Goaziou [this message]
2019-12-22 14:00       ` Nicolas Goaziou

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=875zic8o2u.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=moptop99@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).