emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Martin Steffen <msteffen@ifi.uio.no>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: About exporting
Date: Wed, 31 Mar 2021 20:28:37 +0200	[thread overview]
Message-ID: <864kgrch4a.fsf@login.ifi.uio.no> (raw)
In-Reply-To: <87pmzfhcep.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 31 Mar 2021 10:59:10 +0100")

>>>>> "Eric" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:

    Eric> On Tuesday, 30 Mar 2021 at 17:44, Juan Manuel Macías wrote:
    >> However, *I would not recommend anyone to use LaTeX for
    >> writing*. A light markup language is more comfortable and
    >> efficient for me.

    Eric> Totally agree!  Although, over the years, I have written many
    Eric> papers in LaTeX directly, in the past decade I have
    Eric> increasingly relied on org as the writing tool.  It imposes
    Eric> much less friction on the creative process and, as you say, it
    Eric> enables better management of the writing task.  And, as it
    Eric> gives direct access to LaTeX when necessary, you lose nothing
    Eric> by writing in org.

I would not go so far as not recommend latex (over org) for _anyone_ at
all. I for my part will stick with latex for a certain documents; for
others, org is better (has to do with the mentioned creative process,
and other advantages).


However, I write papers heavy in  math-notation (in the more theoretical
corners of conmputer science). There is a lot of math discplay (and I
like to rely heavily on macros etc).

For me, part of the preference of latex is the ratio between math and
similar things over ``text''. a blog-like text (not heavy on math), or a
note, or a wiki-like document etc, all that's great with org.

For math-typesetting, that's less of a ``creative flow of ideas
thing''. Of course, as having been mentioned, I can always escape to
latex inline or for displays etc. And I can also import my
macro-definitions etc (and I do that).

But actually, when typing, I think I am faster in latex. There are a
couple of features, I like (and my muscle-memory of my fingers rely in
them) in latex-modes of emacs.

Tab completion for environments and macros, remembering the last
environments I used, support of bibtex (like also completion or showing
the reference). Indentention of environments plus highlighting. And last
not least; if I ``compile'' the document (firing off latex, bibtex, or
index or whatever), the compilation runs in the background. As far as I
do that in org (exporting to pdf), it blocks emacs. Not that it's a
huge  delay even, at least for smaller documents, I hate that an editor
or some tool is slower than me, it gets on my nerves if the computer
slows me down. And there is a final thing which (for me) seem to work
better in latex-mode compared to org. That's jumping to the ``next
error'' with some key stroke. That's important,  LaTeX's own error
output it quite poor, but jumping to error locations is vital.


I would not be surprised if some of that is somehow supported by org as
well (for TeX), only I have not figured it out, or perhaps I was too
lazy to figure it out how. Too lazy because LateX mode works for me fine
even for challenging and long documents (where for simpler ones or where
the focus is not on typesetting org works).

Martin






    Eric> And *tables*!  Enough said. :-)

    Eric> But, as always, YMMV.

    Eric> -- : Eric S Fraga via Emacs 28.0.50, Org
    Eric> release_9.4.4-254-g37749c



  reply	other threads:[~2021-03-31 18:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.51.1617033608.26133.emacs-orgmode@gnu.org>
2021-03-29 19:37 ` About exporting Ypo
2021-03-29 20:15   ` William Denton
2021-03-29 20:46   ` autofrettage
2021-03-29 21:39     ` Samuel Wales
2021-03-29 21:31   ` Juan Manuel Macías
2021-03-29 22:06   ` Tim Cross
2021-03-30  6:17     ` Eric S Fraga
2021-03-30  8:01       ` Colin Baxter
2021-03-30  8:13         ` Detlef Steuer
2021-03-30 10:15           ` Eric S Fraga
2021-03-30 11:40             ` Joost Kremers
2021-03-30  8:17         ` Eric S Fraga
2021-03-30 11:04       ` Juan Manuel Macías
2021-03-29 22:26   ` Thomas S. Dye
2021-03-30  4:47   ` Greg Minshall
2021-03-30 11:54   ` Martin Steffen
2021-03-30 12:44     ` autofrettage
2021-03-30 14:35       ` Martin Steffen
2021-03-30 14:44         ` autofrettage
2021-03-30 15:44         ` Juan Manuel Macías
2021-03-31  9:59           ` Eric S Fraga
2021-03-31 18:28             ` Martin Steffen [this message]
2021-04-01  6:52               ` Eric S Fraga
2021-04-01  7:00                 ` Tim Cross
2021-04-01  7:29                   ` Eric S Fraga
2021-04-01  8:50                 ` Timothy
2021-04-01 11:33                   ` Eric S Fraga
2021-04-01 13:25                     ` Timothy
2021-04-02 14:06                       ` Eric S Fraga
2021-04-01 14:21                 ` Juan Manuel Macías
2021-03-30 20:49     ` Tim Cross
2021-03-31 18:56 Juan Manuel Macías

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=864kgrch4a.fsf@login.ifi.uio.no \
    --to=msteffen@ifi.uio.no \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \
    /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).