From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: org-indent, org-inlinetask: patches on github
Date: Sat, 20 Nov 2010 20:50:14 +0000 [thread overview]
Message-ID: <871v6fiut5.fsf@ucl.ac.uk> (raw)
In-Reply-To: <807hg9mr01.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Fri, 19 Nov 2010 13:34:22 +0100")
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
[...]
>>> - Regarding LaTeX, my suggestion requires the =todonotes= LaTeX
>>> package to be loaded in the header.
>>
>> For that one I'm not sure adding one more package to those already inserted
>> by default is a good idea. Is =todonotes= standard in every LaTeX
>> distribution?
>
> I think so, but what really is standard?
>
> With TeXLive, almost all existing packages are installed nowadays (you can't
> not choose anymore for base or medium installation packages). So, yes, it's
> directly available.
>
> With MikTeX, I have no idea. But MiKTeX pops up the user for missing packages,
> allowing its installation in a couple of seconds. If not by default, shouldn't
> be a problem either.
>
>
>> I think default templates should be clean and very low on requirements. This
>> is not too hard for an user of this (undocumented) feature of Org to
>> configure it to its needs after all.
>
> I share your view on keeping trying to be as "basic" as possible in
> requirements. Though, I must admit that, at the time when I only used pure
> LaTeX for editing my stuff, the todonotes package appeared as the only
> valuable one.
>
> And, as its name says, it really is targetting TODO notes!
>
>
>> What do users (and maintainers) think about it?
>
> I'm interested as well by comments...
I tend to ensure that all packages that are available are installed so
this wouldn't be a problem for me.
However, I think that keeping the number of dependencies down is
advantageous so I would vote for having a very generic default template
for latex but with a good example of what is possible in the
documentation (e.g. the particular template definition proposed by
Sébastien).
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
: using Org-mode version 7.3 (release_7.3.104.gf692)
next prev parent reply other threads:[~2010-11-20 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 15:21 org-indent, org-inlinetask: patches on github Nicolas Goaziou
2010-11-07 17:09 ` Carsten Dominik
2010-11-08 4:00 ` Jeff Horn
2010-11-08 7:01 ` Nicolas Goaziou
2010-11-08 12:41 ` Jeff Horn
2010-11-08 13:25 ` Eric S Fraga
2010-11-08 14:41 ` Jeff Horn
2010-12-06 18:45 ` Nicolas Goaziou
2010-12-07 10:29 ` Sébastien Vauban
2010-11-07 18:25 ` Jeff Horn
2010-11-08 8:48 ` Eric S Fraga
2010-11-08 13:23 ` Eric S Fraga
2010-11-08 20:33 ` Sébastien Vauban
2010-11-18 22:22 ` Sébastien Vauban
2010-11-18 23:27 ` Nicolas Goaziou
2010-11-19 12:34 ` Sébastien Vauban
2010-11-20 20:50 ` Eric S Fraga [this message]
2010-11-28 12:17 ` Nicolas Goaziou
2010-11-28 17:16 ` Jeff Horn
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=871v6fiut5.fsf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).