From: Galaxy Being <borgauf@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Formatting content in a footnote for ox-tufte
Date: Wed, 2 Jun 2021 11:22:11 -0500 [thread overview]
Message-ID: <CAFAhFSUYg6noE9AG_4D9nBV6p_+0_bFR_U550FPAOVpbrbnoUg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]
I'm using the org tufte <https://github.com/dakrone/ox-tufte> ox-tufte and
started tweaking the underlying tufte.css
<https://edwardtufte.github.io/tufte-css/>to my needs. It's really meant
for org html export, not like the more elaborate org-to-latex Tufte
formatting from org mode luminary Thomas Dye. As such, it gives you the
Tufte look-and-feel with fonts and the famed sidenote/margin note feature
-- all for just making a footnote (that appears beside its link in the text
rather than the usual at the bottom of the page). The margin note
capability is gnarlier in that it is just a link in the main text that then
appears to the right of the main text
[[mn:1][Here is some text that will appear as a side column block]][[mn:2][And
putting one right after the first one makes it look like a new paragraph]]
Obviously, this is a limiting factor on how elaborate and expressive these
side columns can be, especially the margin note which has your content
inside the link. However, the sidenote as a redirected footnote isn't too
bad. Still, I'd like to be able to fully format what goes into a footnote
without jumping through a lot of hoops. Here's an example of one footnote
as sidenote that comes out looking okay despite the kludginess
[fn:1] Star chart for.... \\
\\
file:./images//Celestial_map_Hyi.png \\
\\
Just text for a few lines of text that is just meant as filler, not
anything important. Just here to show how text looks in a
sidenote. Cool, I think this is enough.\\
\\
~foldr :: (a → b → b) → b → [a] → b~ \\
~foldr f e [ ] = e~\\
~foldr f e (x : xs) = f x (foldr f e xs)~ \\
\begin{align*}
v = \frac{x}{t}
\end{align*}
[[
https://learning.edx.org/course/course-v1:EPFLx+MatlabeOctaveBeginnersX+1T2017/home][MatLab
and Octave training]]
For one, I couldn't get any sort of normal org block formatting (e.g.,
#+BEGIN_example...) for the code snippet to be recognized. Is there any
sort of "normal" content formatting for org footnotes? Obviously, the worst
is the margin note [[mn:... situation. That simply needs to be redone. But
a margin note differs from a sidenote only because the margin note is not
numbered. I tried the org-footnote-auto-label set to confirm, but it always
reverts back to plain numbering.
Any ideas for improvement appreciated. This would be a really good-looking
org html export option if it was bit more user-friendly.
⨽
Lawrence Bottorff
Grand Marais, MN, USA
borgauf@gmail.com
[-- Attachment #2: Type: text/html, Size: 3139 bytes --]
next reply other threads:[~2021-06-02 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 16:22 Galaxy Being [this message]
2021-06-03 18:35 ` Galaxy Being
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=CAFAhFSUYg6noE9AG_4D9nBV6p_+0_bFR_U550FPAOVpbrbnoUg@mail.gmail.com \
--to=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
--subject='Re: Formatting content in a footnote for ox-tufte' \
/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
Code repositories for project(s) associated with this 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).