From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Links & images with different attributes in the same paragraph
Date: Wed, 13 Dec 2023 18:50:16 +0700 [thread overview]
Message-ID: <ulc5pq$par$1@ciao.gmane.io> (raw)
In-Reply-To: <871qbr7e5s.fsf@localhost>
On 12/12/2023 20:18, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> It is limitation of top-down parser that object of the same time can not
>> be nested, so I am unsure if special blocks would be solution in all cases.
>
> Nested objects of the same type are not really a limitation of top-down
> parser. It is the syntax of objects that might but does not have to be.
> We might come up with a syntax that allow nesting.
I would be glad to learn that I am wrong. The current parser picks first
terminating token ignoring other opening tokens in between. The only way
I see is unique identifiers for opening and closing tokens to allow
match them in pairs. It would be tedious to type and to copy fragments
from similar text.
A similar problem is importing and exporting fragments of mail messages
having multilevel quotes. #+begin_quote is not enough, it is necessary
to use something else for inner citations, e.g. #+begin_quote1.
Moreover I would prefer to have links as links even when they need some
special treatment.
next prev parent reply other threads:[~2023-12-13 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 15:54 Links & images with different attributes in the same paragraph Max Nikulin
2023-12-05 13:46 ` Ihor Radchenko
2023-12-12 11:08 ` Max Nikulin
2023-12-12 13:18 ` Ihor Radchenko
2023-12-13 11:50 ` Max Nikulin [this message]
2023-12-14 15:23 ` Ihor Radchenko
2023-12-16 8:06 ` Max Nikulin
2023-12-16 14:44 ` Ihor Radchenko
2023-12-19 14:39 ` Max Nikulin
2023-12-21 14:03 ` 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='ulc5pq$par$1@ciao.gmane.io' \
--to=manikulin@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).