From: Alexandros Prekates <aprekates@posteo.net>
To: Ihor Radchenko <yantar92@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: Wed, 1 May 2024 20:08:58 +0000 [thread overview]
Message-ID: <20240501230858.2647b8d9@enoush2o> (raw)
In-Reply-To: <877cggcnn0.fsf@localhost>
On Mon, 29 Apr 2024 13:19:15 +0000
Ihor Radchenko <yantar92@posteo.net> wrote:
> 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".
>
I give a couple of examples that i think highligth some foggy semantics
of links.
In the example below . is the pointer and single quotes is for
recognized links and $ for the start of the line.
$[[foo]].
$'foo'.
$.'foo' // here while we could think that the pointer is
// before the link , if we type a char it will
// be inserted into the link.
$'xfoo' // not x'foo'
Also what if we type :
$and [[foo]].
$and 'foo'.
$.and 'foo'
$[[goo. and 'foo' //Could not be seen as [[ goo and [[foo ]] ?
// 'goo and [[foo'
// But that doesnt happens.
// Org sees it as :
$[[goo. and 'foo'
$[[goo]] and 'foo'
$'goo' and 'foo'
Alexandros
next prev parent reply other threads:[~2024-05-01 20:10 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
2024-04-29 22:33 ` Alexandros Prekates
2024-05-01 20:08 ` Alexandros Prekates [this message]
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
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=20240501230858.2647b8d9@enoush2o \
--to=aprekates@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).