From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Links & images with different attributes in the same paragraph
Date: Sat, 16 Dec 2023 15:06:19 +0700 [thread overview]
Message-ID: <uljlpt$fjd$1@ciao.gmane.io> (raw)
In-Reply-To: <878r5wq03g.fsf@localhost>
On 14/12/2023 22:23, Ihor Radchenko wrote:
>
> Not necessarily. The current parser also allows balanced brackets inside
> an object.
Thanks, I forgot about it. Balancing of brackets alleviates the issue
with nested objects. I am unsure if it is still pure top-down parser,
but it does not matter.
> @wrap{{outer wrap; @wrap{{inner wrap allowing } as well}}; back}}.
Are you assuming invisible zero-width space as a way to escape literal
{{ or }}? I would prefer some visible characters.
> As you see, my solution is conceptually similar to #+begin_quote1 idea.
It is better since balanced delimiters make adding unique suffix to
#+begin_... and #+end... unnecessary.
> What about @wrap[#+attr_html: :alt "Text"]{[[/path/to/image]]}?
Leaving aside precise syntax (that perhaps should be discussed in
another thread), it solves the issue.
Do you have any idea how to address the following complain?
https://list.orgmode.org/orgmode/875ykwvmz7.fsf@posteo.net
Juan Manuel Macías. Re: About 'inline special blocks' Sun, 19 Jun 2022
12:47:40 +0000
> Bringing that into the paragraph is
> unnecessarily overloading the paragraph and breaking the social contract
> of lightweight markup, where paragraphs should still look like
> paragraphs.
I consider it as a valid point, so I tried to take advantage of noweb
features. I am in doubts concerning *evaluation* of expressions in
addition to just substitutions. It allows to implement another kind of
#+link: macro, but it gives too much power to my taste.
next prev parent reply other threads:[~2023-12-16 8:06 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
2023-12-14 15:23 ` Ihor Radchenko
2023-12-16 8:06 ` Max Nikulin [this message]
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='uljlpt$fjd$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).