emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: The less ambiguous math delimiters in tables
Date: Fri, 3 Jan 2025 22:14:25 +0700	[thread overview]
Message-ID: <vl8usj$118v$1@ciao.gmane.io> (raw)
In-Reply-To: <87v7uxqfzi.fsf@localhost>

On 03/01/2025 00:32, Ihor Radchenko wrote:
> Max Nikulin writes:
> 
>> On 31/12/2024 20:32, Ihor Radchenko wrote:
>>> | $10 | foo | $\alpha$ |
>>
>> pandoc result matches my expectation:
>>
>> \$10 & foo & \(\alpha\) \\
> 
> How so?
> I just tried

Sorry, I failed to express that the above example is handled perfectly 
by pandoc, while the following one I find unrealistic

> printf '%s\n' '| =10+20 | 30 | =foo= |' | pandoc -f org -t latex

I can not imagine when this construct may emerge in real life. Parsing 
with single cell is questionable, is a kind of pitfall, but still may be 
considered as valid.

Perhaps the following on is better

     | ~0.001 | ~func3(x)~ |

but there are workarounds like

     | \(~0.001\) | ~func3(x)~ |

On the other hand current approach has already known pitfalls (omitting 
links to mailing list messages)

     Descriptive list
     - goal :: src_haskell[:exports code]{monoidBSFold :: FilePath -> IO 
Counts}
     - term :: [[https://example.org][Bread :: Crumbs]]
     Verbatim inside emphasis
     - A _b =c_ d= e_ f
     Links (a workaround is to break emphasis on link borders)
     - /lorem [[https://ormode.org/?oops=1][ipsum]] dolor/
     - /lorem [[https://orgmode.org/,oops][ipsum]] dolor/
     The same with macro
     #+macro: Pathname =$1=
     /Open the file {{{Pathname(~/.bashrc)}}}/




  reply	other threads:[~2025-01-03 15:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24  9:20 The less ambiguous math delimiters in tables Rudolf Adamkovič
2024-12-24  9:25 ` Ihor Radchenko
2024-12-25 17:56   ` Rudolf Adamkovič
2024-12-25 18:05     ` Ihor Radchenko
2024-12-25 20:14       ` Rudolf Adamkovič
2024-12-26  9:17         ` Ihor Radchenko
2024-12-26 13:31           ` Rudolf Adamkovič
2024-12-26 13:51             ` Ihor Radchenko
2024-12-27 13:23               ` Rudolf Adamkovič
2024-12-27 13:35                 ` Ihor Radchenko
2024-12-30 21:02                   ` Rudolf Adamkovič
2024-12-31 17:47                     ` Ihor Radchenko
2024-12-27 17:17     ` Leo Butler
2024-12-28 16:39     ` Max Nikulin
2024-12-30 21:25       ` Rudolf Adamkovič
2025-01-02 17:02         ` Max Nikulin
2024-12-31  5:43       ` Ihor Radchenko
2024-12-31 12:20         ` Rudolf Adamkovič
2024-12-31 13:32           ` Ihor Radchenko
2024-12-31 15:57             ` Rudolf Adamkovič
2024-12-31 16:46               ` Ihor Radchenko
2025-01-02 17:20             ` Max Nikulin
2025-01-02 17:32               ` Ihor Radchenko
2025-01-03 15:14                 ` Max Nikulin [this message]
2024-12-24  9:50 ` Rudolf Adamkovič

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='vl8usj$118v$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).