From: Eric Schulte <schulte.eric@gmail.com>
To: Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com>
Cc: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Org Tutorials need more structure
Date: Sat, 28 Sep 2013 06:36:45 -0600 [thread overview]
Message-ID: <871u49w21y.fsf@gmail.com> (raw)
In-Reply-To: CAD-VTcG5uauTER8rCJmTXAPLu+yN5KUkK1GL47JP_eGaMJdhJQ@mail.gmail.com
Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
> Hi,
>
> 2013/9/28 Suvayu Ali <fatkasuvayu+linux@gmail.com>
>
>> Your example is not beginner's tutorial at all! Nor is it something
>> that the manual can cover.
>>
>
> I do not understand why. Every beginner intested in org-mode is interested
> for such or such application, and that's a strange reply to make to a
> beginner like me to reply : "sorry but your request is not a beginner's
> request". And if I am interested in org-mode mainly for the feature?
>
>
Org-mode is an application for the following (from the manual).
> Org is a mode for keeping notes, maintaining TODO lists, and doing
> project planning with a fast and effective plain-text system.
Email is not mentioned in this description and is not core to what
Org-mode does. I think the point made in the previous email is that
your use case is neither basic nor typical Org-mode usage.
>
> I have not found a clear tutorial to help me on this point, and even in the
> org-mode manual, the relationship between org-mode and emacs email client
> like gnus is very difficult to understand. Again, I have not seen an easy
> example to follow.
>
The feature (sending email with embedded equations compiled from latex)
is provided by org-mime, which is a contributed package build on top of
Org-mode. It is not mentioned in the Org-mode manual because it is
*not* part of Org-mode, it is built on top of Org-mode.
See [1] for a tutorial on using org-mime. Sometimes when using a tool
like Org-mime which leverages other tools (e.g., message-mode and
org-mode) it is necessary to learn all of the sub-tools at once which
can result in a great deal of reading, there's no way to avoid this.
>
>
>>
>> Now to answer your question, I have seen people mention htmlize.el from
>> contrib for something like this. To integrate with LaTeX, you should be
>> able work out a solution with some dvipng magic. If memory serves me
>> right, there was a post from Eric[1] mentioning how to use htmlize from
>> gnus, and a thread on dvipng in the last month. Those might help you.
>>
>
> Thanks for this reference, I have tried these commands on a draft in my
> gnus, of course nothing work. I suspect that I need to configure gnus
> before...
>
I doubt this is related to your gnus configuration. Please try the
tutorial linked below, and if you run into a problem then provide a
complete reproducible recipe for what you've tried and how it failed and
maybe we can help you to use these packages.
>
> My point in this discussion was to pointing out that it is not only
> structure of tutorials can be a problem, but the content of explanations.
> Again, if no example is given for each task that one can realize with
> org-mode, only geeks expert in emacs will be able to read manuals for
> org-mode, and in my opinion it's too bad.
>
There is a need to balance between spending time spent documenting and
spending time developing (fixing bugs and adding features etc...). More
documentation and more examples in the documentation would be welcome,
but given the time constraints of Org-mode developers and contributors
not every desirable task can be accomplished.
Cheers,
>
> Best wishes,
>
> Jo.
Footnotes:
[1] http://orgmode.org/worg/org-contrib/org-mime.html
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2013-09-28 12:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 6:11 Org Tutorials need more structure Carsten Dominik
2013-09-28 7:22 ` Joseph Vidal-Rosset
2013-09-28 8:37 ` Marcin Borkowski
2013-09-28 10:30 ` Suvayu Ali
2013-09-28 11:59 ` Joseph Vidal-Rosset
2013-09-28 12:36 ` Eric Schulte [this message]
2013-09-28 13:10 ` Joseph Vidal-Rosset
2013-09-28 16:02 ` Suvayu Ali
2013-09-28 17:19 ` Joseph Vidal-Rosset
2013-10-01 7:59 ` Eric S Fraga
2013-10-01 20:34 ` David Rogers
2013-10-01 21:00 ` Marcin Borkowski
2013-09-28 8:48 ` Marcin Borkowski
2013-09-28 10:09 ` Carsten Dominik
2013-09-28 14:26 ` Charles Millar
2013-09-28 16:35 ` Carsten Dominik
2013-09-28 17:14 ` Ian Barton
2013-09-28 17:43 ` Marcin Borkowski
2013-09-28 17:48 ` Carsten Dominik
2013-09-28 19:06 ` Ramon Diaz-Uriarte
2013-09-28 19:52 ` Thomas S. Dye
2013-09-28 20:50 ` Charles Millar
2013-09-28 21:31 ` Marcin Borkowski
2013-09-28 21:52 ` John Hendy
2013-09-28 23:14 ` Charles Millar
2013-09-28 23:29 ` Thomas S. Dye
2013-09-29 0:29 ` John Hendy
2013-09-29 7:28 ` Suvayu Ali
2013-09-30 8:04 ` Alan Schmitt
2013-09-30 17:01 ` Eric S Fraga
2013-09-30 18:36 ` Peter Neilson
2013-09-30 21:07 ` Eduardo Ochs
2013-10-01 8:52 ` Michael Brand
2013-10-01 5:34 ` Suvayu Ali
2013-10-01 8:55 ` Marcin Borkowski
2013-10-01 12:40 ` Joseph Vidal-Rosset
2013-09-30 17:56 ` Thomas S. Dye
2013-09-29 8:44 ` Eric Abrahamsen
2013-09-29 15:31 ` Matt Price
2013-09-30 7:25 ` Eric Abrahamsen
2013-10-01 14:08 ` William Denton
2013-10-02 1:10 ` M
2013-10-02 18:06 ` Alan E. Davis
-- strict thread matches above, loose matches on Subject: below --
2013-09-29 16:43 Rustom Mody
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871u49w21y.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=joseph.vidal.rosset@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.