From: Christopher Dimech <firstname.lastname@example.org>
To: Rob Sargent <email@example.com>
Subject: Latex highlighting for org-mode
Date: Thu, 24 Jun 2021 20:09:24 +0200 [thread overview]
Message-ID: <trinity-666d000c-a385-4a61-bf05-258d37675239-1624558163827@3c-app-mailcom-bs06> (raw)
The convenience of html output is the easiness by which one can zoom
in and out. Doing that in printed output is difficult because you need
typefaces with different sizes.
I use the latex for mathematical typesetting, with the other things I
wholeheartedly follow your drift. There is still so much work to do.
Things have become complicated, and the design has to get simplified,
for the next generation of hackers to work with.
> Sent: Friday, June 25, 2021 at 5:54 AM
> From: "Rob Sargent" <firstname.lastname@example.org>
> To: email@example.com
> Subject: Re: Latex highlighting for org-mode
> On 6/24/21 11:43 AM, Christopher Dimech wrote:
> > I only proposed colour highlighing for mathematical snippets. Nothing else.
> > Or making org able to export to html even when one is using LaTeX blocks.
> > In that sense, it would act in ways similar to texinfo, using a single
> > source file to produce output in a number of formats, both online and printed.
> Print and digital are vastly different worlds. Given that one can plop
> most any file in a web page I would rather see more work on making print
> layout easier without resorting to latex directives or other single
> target mark-ups. Even at the expense of html output.
prev parent reply other threads:[~2021-06-24 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 5:07 Latex highlighting for org-mode Christopher Dimech
2021-06-24 16:28 ` Rodrigo Morales
2021-06-24 17:25 ` Christopher Dimech
2021-06-24 17:30 ` Eric S Fraga
2021-06-24 17:43 ` Christopher Dimech
2021-06-24 17:54 ` Rob Sargent
2021-06-24 18:09 ` Christopher Dimech [this message]
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 \
* 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).