From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: ox-tufte-latex
Date: Wed, 03 Feb 2016 17:42:50 +0100 [thread overview]
Message-ID: <878u31ycc5.fsf@gmx.us> (raw)
In-Reply-To: m2lh71er7z.fsf@tsdye.com
Thomas S. Dye <tsd@tsdye.com> writes:
> Oops, I meant margintable instead of marginnote.
Tables have an environment. Is that sufficient (coupled with
:float nil)?
>> I've skimmed through the "sample-handout.pdf" of the
>> tufte-latex pkg. marginfigure seems to be pretty similar to a
>> figure except that the environment is changed. I wonder if it
>> would be enough to allow an :environment attribute to an
>> image?
>
> My solution was :float margin.
Hmm. How about a attr :environment for figures? Wouldn't that be
sufficient for this problem.
>> Marginnotes. I don’t think we have a concept like this. I
>> guess it would be an attribute to a footnote. Which you
>> incidentally asked about. Would you use more than one type of
>> footnotes in a single document?
>
> Marginnotes aren't numbered. I don't think there is a similar
> Org mode concept. I use a link to make them, so I don't need an
> Org-mode counterpart.
>
> ,------------------------------------------------------------- |
> [[latex-opt:marginnote][The journals of Captain Cook and his |
> crew contain the first written descriptions of old |
> Hawai`i.;-3\baselineskip]]
> `-------------------------------------------------------------
As you might’ve guessed, I’m not a fan of this solution. Whether
it’s numbered or not in the output, a [mn:N] or [sn:N] reference
is more Orgish. I cannot, however, speak to how difficult it
would be to add more note types.
Rasmus
--
Sådan en god dansk lagereddike kan man slet ikke bruge mere
next prev parent reply other threads:[~2016-02-03 16:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 0:26 ox-tufte-latex Thomas S. Dye
2016-02-02 1:10 ` ox-tufte-latex Titus von der Malsburg
2016-02-02 1:49 ` ox-tufte-latex Thomas S. Dye
2016-02-03 21:57 ` ox-tufte-latex Spencer Boucher
2016-02-02 8:52 ` ox-tufte-latex Eric S Fraga
2016-02-03 0:28 ` ox-tufte-latex Rasmus
2016-02-03 1:35 ` ox-tufte-latex Thomas S. Dye
2016-02-03 2:29 ` ox-tufte-latex Lawrence Bottorff
2016-02-03 11:05 ` ox-tufte-latex Rasmus
2016-02-03 11:26 ` ox-tufte-latex Marcin Borkowski
2016-02-03 11:41 ` ox-tufte-latex Rasmus
2016-02-03 13:33 ` ox-tufte-latex Marcin Borkowski
2016-02-03 16:07 ` ox-tufte-latex Thomas S. Dye
2016-02-03 15:41 ` ox-tufte-latex Thomas S. Dye
2016-02-03 16:42 ` Rasmus [this message]
2016-02-03 17:15 ` ox-tufte-latex Thomas S. Dye
2016-02-12 18:28 ` ox-tufte-latex Eduardo Mercovich
2016-02-12 19:02 ` ox-tufte-latex Thomas S. Dye
2016-02-18 18:43 ` ox-tufte-latex Eduardo Mercovich
2016-02-19 3:03 ` ox-tufte-latex Thomas S. Dye
2016-02-19 3:54 ` ox-tufte-latex Thomas S. Dye
2016-02-22 17:59 ` ox-tufte-latex Eduardo Mercovich
2016-02-22 18:52 ` ox-tufte-latex Thomas S. Dye
2016-02-22 19:35 ` ox-tufte-latex John Hendy
2016-02-23 0:00 ` ox-tufte-latex Thomas S. Dye
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=878u31ycc5.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/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).