emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: A simple Lua filter for Pandoc
Date: Fri, 7 Jan 2022 21:29:33 +0700	[thread overview]
Message-ID: <sr9iof$2f8$1@ciao.gmane.io> (raw)
In-Reply-To: <87mtkaglfh.fsf@posteo.net>

On 06/01/2022 00:08, Juan Manuel Macías wrote:
> Max Nikulin writes:
>> It seems, lightweight markup is more annoyance than advantage for you.
>> Tom posted some thoughts on more rigorous syntax in the following message:
> It's generally the opposite: working in Org is a pleasant journey for
> me... except when there are dozens of "/" and "*" in a document, and
> they placed in 'unhappy' positions. For example, in phonetics the
> "/ ... /" notation is used a lot, and there may be cases like:
> #+begin_example
> /foo/ /bar/ /baz/
> #+end_example

Unless you were seeking for a lightweight markup I would remind you 
about macro:
---- >8 ----
#+macro: ph @@x:@@/@@x:@@$1@@x:@@/@@x:@@

/{{{ph(foo)}}} {{{ph(bar)}}} {{{ph(baz)}}}/
---- 8< ----

Form my point of view it is not worse than "\slash{}" entities.

LISP can bee easily transformed to a domain specific language by means 
of LISP macros (it is its strong and weak side simultaneously). I am 
unaware whether a comparable framework exists for creating custom 
lightweight markups. In LaTeX for your examples I expect something like 
\phonetic{foo} commands to have logical markup. Certainly with some 
hints /foo/ in particular part of text might be considered as "phonetic" 
rather than "italic" in intermediate representation keeping source 
easily readable.

> https://i.imgur.com/f6X7qLs.png

In this example there is no need to replace "<" by entity since it can 
not be confused with <http://te.st/> links.

  reply	other threads:[~2022-01-07 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 10:14 A simple Lua filter for Pandoc Juan Manuel Macías
2022-01-04 11:26 ` Timothy
2022-01-04 15:11   ` Juan Manuel Macías
2022-01-04 14:05 ` Max Nikulin
2022-01-04 15:06   ` Juan Manuel Macías
2022-01-05 16:29     ` Max Nikulin
2022-01-05 17:08       ` Juan Manuel Macías
2022-01-07 14:29         ` Max Nikulin [this message]
2022-01-07 15:14           ` Juan Manuel Macías
2022-01-04 16:28 ` Thomas S. Dye

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:

  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='sr9iof$2f8$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).