From: Ypo <email@example.com>
Subject: Emacs-orgmode Digest, Vol 185, Issue 7
Date: Tue, 6 Jul 2021 21:28:11 +0000 (UTC) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Several things around my mind. Pick one if you like, and I will try to explain it better.
- when using ediff, if there is an image near the text which has differences, it works wrong. Like if the image wouldn't allow ediff to scroll and show the difference. I just see the image, stationary, while jumping to the next difference.
- I have started to read Chassell's. Introduction... to Emacs Lisp. But my ideas grow much much faster than my reading. I even feel I won't be able to implement simple ideas in years. Example: I would like that every time "I see" a heading with a special TODO state, this heading is expanded. Should I keep reading the book to materialize this little idea or should I take different actions?
- when I export to latex, I get an error and no document is produced. Sorry I can't share here the error, since I am writing from the mobile, but it seems related to xelatex. Buuut, if I take the .tex produced file and I open it with an external latex editor, the document is compiled into a decent PDF. How could orgmode generate a valid tex document but not to be able to produce its PDF?
- some more bugs I found, I should share from the PC.
- oh, wait. I have an old PC I don't use much (2008 AD - Core 2 Duo). I was thinking about using it just for orgmode. Would you recommend me an OS?
Thanks for being there
next parent reply other threads:[~2021-07-06 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2021-07-06 21:28 ` Ypo [this message]
2021-07-06 21:34 ` Emacs-orgmode Digest, Vol 185, Issue 7 Samuel Banya
2021-07-06 21:38 ` Samuel Banya
2021-07-06 23:20 ` Tim Cross
2021-07-07 12:11 ` Eric S Fraga
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).