From: Ihor Radchenko <yantar92@posteo.net>
To: Alexandros Prekates <aprekates@posteo.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: link can not be created in a line with another link.
Date: Mon, 29 Apr 2024 13:19:15 +0000 [thread overview]
Message-ID: <877cggcnn0.fsf@localhost> (raw)
In-Reply-To: <20240429154540.3917dd8c@enoush2o>
Alexandros Prekates <aprekates@posteo.net> writes:
> The same behavior happens with emacs -Q.
>
> Having <<foo>> and <<boo>> anchors somewhere in an org file
> in a line a have an internal link :
>
> bla [[foo]]
>
> If i add :
> [[boo]] bla [[foo]]
> org will create the two links.
>
> But if i add:
> [[boo][ bla [[foo]]
> with the intention to type: [[boo][description]] bla [[foo]]
> then what i will get is: a link to boo with description : bla [[foo
This is expected, as per Org mode's link syntax [[path][description]].
[[boo][ bla [[foo]]
is indeed a link with path "boo" and description spanning between [...]:
" blah [[foo".
For you workflow, it may be more convenient to set
`org-link-descriptive' to nil. Then, Org mode will not hide the path
part of the links and you can edit the plain text as you wish without
being distracted by Org mode trying to detect the markup as you type.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-04-29 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 6:33 link can not be created in a line with another link Alexandros Prekates
2024-04-28 12:40 ` Ihor Radchenko
2024-04-29 12:45 ` Alexandros Prekates
2024-04-29 13:19 ` Ihor Radchenko [this message]
2024-04-29 22:33 ` Alexandros Prekates
2024-05-01 20:08 ` Alexandros Prekates
2024-05-01 20:57 ` Ihor Radchenko
2024-05-01 10:59 ` Max Nikulin
2024-05-01 16:36 ` Alexandros Prekates
2024-05-02 11:15 ` Ihor Radchenko
2024-05-03 10:39 ` Max Nikulin
2024-05-03 13:32 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cggcnn0.fsf@localhost \
--to=yantar92@posteo.net \
--cc=aprekates@posteo.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.