emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Rudolf Adamkovič" <salutis@me.com>
To: emacs-orgmode@gnu.org
Subject: Re: Inequalities in math blocks
Date: Thu, 07 Oct 2021 21:48:21 +0200	[thread overview]
Message-ID: <m2lf348vlm.fsf@me.com> (raw)
In-Reply-To: <sjn2cn$1748$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> If you submitted HTML file, you might suggest to open sources to make it obvious that the mistake was not intentional.

One day! The university system switches to a read-only mode at the end of every week, and I cannot open-source anything for two years after the submission. I ended up posting an "errata" comment.

> […] "idf" typed in straight font instead of italics and to avoid additional space between characters.

Yes, the three letters denote a function name, not a product of three variables. I simplified the snippet for the mailing list. In reality, I typed $\mathrm{idf}(t)>c$, as one should. Thank you for caring!

> It is matter of taste, but "{}" after "\in" looks a bit strange for me. "$t\in q$ is even shorter, "$t \in q$", having the same length, is more readable from my point of view.

Ha-ha! Yeah, I avoid spaces because they make me think for much too long about where to put them. Knuth would write $t\in q$, like you said, but that looks "unbalanced" to me. Of course, $t \in q$ looks best, but that sends me to back to the "whitespace paralysis" mode. Help wanted.

"'Contrariwise,' continued Tweedledee, 'if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic.'" -- Lewis Carroll, Through the Looking Glass

Rudolf Adamkovič <salutis@me.com>
Studenohorská 25
84103 Bratislava


  reply	other threads:[~2021-10-07 19:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 11:04 Inequalities in math blocks Rudolf Adamkovič
2021-10-03 12:19 ` Max Nikulin
2021-10-03 13:12   ` Timothy
2021-10-05  7:55     ` Rudolf Adamkovič
2021-10-05  7:58       ` Timothy
2021-10-05 12:19         ` Eric S Fraga
2021-10-05 12:00       ` Max Nikulin
2021-10-05 12:50         ` Rudolf Adamkovič
2021-10-03 13:14   ` Rudolf Adamkovič
2021-10-12  1:11     ` Nick Dokos
2021-10-12 12:02       ` Max Nikulin
2021-10-03 16:17   ` [PATCH] org-manual.org: Update links to MathJax docs Max Nikulin
2022-08-21  5:53     ` Ihor Radchenko
2022-08-21  6:20       ` Max Nikulin
2022-08-22  2:39         ` Ihor Radchenko
2022-08-22 14:52           ` Max Nikulin
2022-08-23  2:32             ` Update Woof! version at updates.orgmode.org? (was: [PATCH] org-manual.org: Update links to MathJax docs) Ihor Radchenko
2022-08-23 15:02               ` Update Woof! version at updates.orgmode.org? Max Nikulin
2022-09-01  9:07                 ` Bastien
2022-09-01  9:02               ` Bastien
2021-10-06  7:39 ` Inequalities in math blocks Rudolf Adamkovič
2021-10-07 11:30   ` Greg Minshall
2021-10-07 11:33     ` Timothy
2021-10-07 12:13       ` Greg Minshall
2021-10-07 12:53     ` Rudolf Adamkovič
2021-10-07 13:05       ` Timothy
2021-10-07 15:05         ` Max Nikulin
2021-10-07 19:48           ` Rudolf Adamkovič [this message]
2022-11-05 13:06           ` Max Nikulin
2022-11-06  3:05             ` [BUG] Escaping "<" and ">" inside math blocks when exporting to HTML/MathJax (was: Inequalities in math blocks) Ihor Radchenko
2021-10-07 19:25         ` Inequalities in math blocks Rudolf Adamkovič
2021-10-08 12:37       ` Greg Minshall

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=m2lf348vlm.fsf@me.com \
    --to=salutis@me.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).