From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: David Masterson <dsmasterson@gmail.com>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: LaTeX tutorial (focused on what Org exports) ??
Date: Mon, 2 Jan 2023 12:30:59 +0000 [thread overview]
Message-ID: <87edsd15ks.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87lemm74kz.fsf@localhost> (Ihor Radchenko's message of "Sun, 01 Jan 2023 13:43:40 +0000")
On Sunday, 1 Jan 2023 at 13:43, Ihor Radchenko wrote:
> I think that it is not very clear how to use it.
> Abstract says that it is self-explaining, but it appears that not every
> pdf viewer supports showing the explanations.
Yes, that's true. The PDF viewer has to support popups. I normally use
zathura to view PDF documents but that's one example of a viewer that
doesn't work with this document. In cases like this, I switch to evince
(others also work).
But I find this document very useful.
--
: Eric S Fraga, with org release_9.6-124-g036cc0 in Emacs 30.0.50
next prev parent reply other threads:[~2023-01-02 12:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 21:29 LaTeX tutorial (focused on what Org exports) ?? David Masterson
2022-12-31 1:18 ` Thomas S. Dye
2022-12-31 10:32 ` Marcin Borkowski
2023-01-01 7:08 ` David Masterson
2023-01-02 18:31 ` William Denton
2023-01-03 3:25 ` David Masterson
2022-12-31 11:55 ` Fraga, Eric
2023-01-01 7:12 ` David Masterson
2023-01-01 7:19 ` Ihor Radchenko
2023-01-01 13:18 ` Fraga, Eric
2023-01-01 13:43 ` Ihor Radchenko
2023-01-02 12:30 ` Fraga, Eric [this message]
2023-01-03 3:23 ` David Masterson
2023-01-03 9:10 ` Fraga, Eric
2023-01-04 0:12 ` David Masterson
[not found] ` <87o7rgmhcs.fsf@penguin>
2023-01-03 3:28 ` David Masterson
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 7:18 Pedro Andres Aranda Gutierrez
2023-01-06 6:21 ` David Masterson
2023-01-06 18:07 ` William Denton
2023-01-06 23:57 ` David Masterson
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=87edsd15ks.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).