From: Thomas S. Dye <tsd@tsdye.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: ox-tufte-latex
Date: Wed, 03 Feb 2016 06:07:56 -1000 [thread overview]
Message-ID: <m2k2mleq03.fsf@tsdye.com> (raw)
In-Reply-To: <87si19dikj.fsf@mbork.pl>
Aloha Marcin,
Marcin Borkowski <mbork@mbork.pl> writes:
> On 2016-02-03, at 12:41, Rasmus <rasmus@gmx.us> wrote:
>
>> Marcin Borkowski <mbork@mbork.pl> writes:
>>
>>> On 2016-02-03, at 12:05, Rasmus <rasmus@gmx.us> wrote:
>>>
>>>> Marginnotes. I don’t think we have a concept like this. I
>>>> guess
>>>
>>> Inline todos?
>>
>> It's not really the same. Inline todos are for temporary notes
>> (say bugs in your document) that you’d not want to keep in your
>> final document, I guess.
>
> Well, this is more or less what I would use marginnotes for... See
> e.g. https://www.ctan.org/pkg/todonotes .
Tufte uses marginnotes to communicate with a reader. I think inline
todos and the todonotes package you linked are intended to communicate
with an author. It might be well to keep that distinction.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2016-02-03 16:08 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 ` Thomas S. Dye [this message]
2016-02-03 15:41 ` ox-tufte-latex Thomas S. Dye
2016-02-03 16:42 ` ox-tufte-latex Rasmus
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=m2k2mleq03.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
--cc=rasmus@gmx.us \
/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).