From: Matt Price <moptop99@gmail.com>
To: Matt Price <moptop99@gmail.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: managing aggressive link activation within lines?
Date: Thu, 19 Dec 2019 06:57:39 -0500 [thread overview]
Message-ID: <CAN_Dec9eJvsfN9puujNHmX2vGA4CVG5MjQhgcjmoP+h6oMj-yQ@mail.gmail.com> (raw)
In-Reply-To: <87a77o92ba.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On Thu, Dec 19, 2019 at 2:55 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Matt Price <moptop99@gmail.com> writes:
>
> > MWE:
> > test.org:
> > --
> > This is a paragraph with [[https://google.com][a link]]
> > ---
> > steps to reproduce:
> >
> > put cursor at beginning of file and type ~[[~. The paragraph text will
> > collapse into the link definition, and (point) will move to the ~a~ in ~a
> > link~, so manual typing of a new link will fail. Is there anything I can
> > do to stop this from happening?
>
> IIUC, this is related to the link syntax change introduced in Org 9.3,
> which allows, among other things, "[[" within a link. In this situation,
> once you write
>
> [[This is a paragraph with [[https://google.com][a link]]
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> the underlined part becomes the link.
>
> I agree this is not optimal. Yet, I'm not sure about how to deal with
> this.
>
> 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.
>
>
[-- Attachment #2: Type: text/html, Size: 2137 bytes --]
next prev parent reply other threads:[~2019-12-19 11:57 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 [this message]
2019-12-19 13:03 ` Nicolas Goaziou
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=CAN_Dec9eJvsfN9puujNHmX2vGA4CVG5MjQhgcjmoP+h6oMj-yQ@mail.gmail.com \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).