susam

texme

JavaScript2018–2022

susam / texme

texme

Self-rendering Markdown + LaTeX documents

Explore on GitHub Read Hacker News discussions

17Distinct people

33Mentions

1Explicit recommenders

2.4KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Self-rendering Markdown + LaTeX documents

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

This is an update to the above comment. TeXMe and MdMe (stripped down fork of TeXMe) now support Markdeep style of putting the content directly in the <body> element (i.e.,…

susam used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

susam/mdme · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:36:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year33 dated mentions

Observed mentions: 2018-10-26 09:07:40 UTC to 2022-09-17 10:14:02 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	5	1	4
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	8	0	8
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	8	3	5
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	10	3	7
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	2	0	2

What Hacker News says

5 sources

vanderZwan·Nov 13, 2018

Depending on how simple you want it, you could just use MarkDeep, TexMe or MdMe plus something like NeoCities or a Github repo. You'd miss out on some benefits of a full generator, like automatically creating an archive page and RSS feeds and stuff like that, but you'd gain that 90's simplicity. [0] https://casual-effects.com/markdeep/ [1] https://github.com/susam/texme [2] https://github.com/susam/mdme [3] https://neocities.org/

In Medium is a poor choice for blogging

susam·Oct 28, 2018Recommendation phrase

This is an update to the above comment. TeXMe and MdMe (stripped down fork of TeXMe) now support Markdeep style of putting the content directly in the <body> element (i.e., without a <textarea> element) and then putting the <script> tag to load TeXMe/MdMe at the end of content. But this method has the same caveats that Markdeep has, i.e., an HTML syntax error in the content can lead to broken rendering. Therefore, I recommend using TeXMe's original method of putting the content in textarea for more robust parsing and rendering. For further details, please see: * https://github.com/susam/texme#content-in-textarea (TexMe's original method of writing content in textarea that leads to robust parsing and rendering). * https://github.com/susam/texme#content-in-body (The new method of writing content in body that makes the content look neat but

Read the rest

has some caveats. See the "Caveats" subsection in this section for details.)

In Show HN: TeXMe – Self-Rendering Markdown and LaTeX Documents

susam·Oct 27, 2018

> Markdeep works by appending similar code to the end, which is much more innocuous when viewing the file outside a browser or when its rendered by other software (e.g. on Github). Thank you for highlighting this feature of Markdeep. I have now added this feature in TeXMe and MdMe too. We can now put the `<script>` tag to load TeXMe or MdMe at the end of content. Here is an example: # Euler's Identity In mathematics, **Euler's identity** is the equality $$ e^{i \pi} + 1 = 0. $$ <script src="https://cdn.jsdelivr.net/npm/texme"></script> However, like I have explained in another comment[1], this method of writing content requires the content to not have any HTML syntax errors, otherwise the output would be mangled. Markdeep has this limitation too. There is a 'Caveats' section[2] in the README now that discusses this in detail. T

Read the rest

he original method of writing content with a single line of HTML code at the beginning of the content does not have this limitation. But if the HTML code in the beginning feels distracting, we can now put the `<script>` tag in the end too. [1]: https://news.ycombinator.com/item?id=18314175 [2]: https://github.com/susam/texme#caveats

In Show HN: TeXMe – Self-Rendering Markdown and LaTeX Documents

susam·Oct 26, 2018

Thank you for your reply. The <body> element's start and end tags can indeed be omitted under certain conditions (which are being met in the "Valid HTML5" example). Here is the actual specification quoted from https://www.w3.org/TR/html52/syntax.html#optional-tags: "A body element's start tag may be omitted if the element is empty, or if the first thing inside the body element is not a space character or a comment, except if the first thing inside the body element is a meta, link, script, style, or template element." Then in "Example 6", it provides the following as an example of a valid HTML5 document: <!DOCTYPE HTML> <title>Hello</title> <p>Welcome to this example.</p> Now coming back to your issue, perhaps the selectors in your style do not match the actual elements that TeXMe is setting in the page? I am just guessing her

Read the rest

e because I need the actual code to be able to nail down the cause of the issue. If you can share the complete code you have either here or at https://github.com/susam/texme/issues/new, it would really help in determining the cause of the issue.

In Show HN: TeXMe – Self-Rendering Markdown and LaTeX Documents

susam·Oct 26, 2018Submission

Show HN: TeXMe – Self-Rendering Markdown and LaTeX Documents

209 points · Open discussion