emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marco <domanov@gmail.com>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Create course material with org-mode
Date: Mon, 11 Mar 2013 21:59:49 +0100	[thread overview]
Message-ID: <CAFcvSsFKgjcTBoAgQJax+J=ZnXCuA6o9XMu=NnFoV-Mo02h97Q@mail.gmail.com> (raw)
In-Reply-To: <87zjy9he6m.fsf@lapcat.tftorrey.com>

Hi list, and Terry,

> This is more or less precisely the structure I use for managing my work.
> I maintain each project as one Org file, keeping together all related
> text, todo lists, spreadsheets, web pages, letters, and even files like
> SVG files.  This way I can add just one file (per project) to my agenda
> and not miss any tasks, and backing up my critical work is just a matter
> of copying my Org files.  When needed, I also export the individual
> nodes as HTML, PDF, OpenDocument, csv, or whatever.

> I'd be happy to give you more information about how to set up an Org
> file to export to different formats the way I use mine, but really the
> information is very clear in the manual.

I find it would be great, at least for me, to have a "working example"
plus a couple of hints. I will be glad if you can provide a
stripped-down version of your working solution, so that I could just
try the workflow "hands on"!
Greets (and keep up the great work),
Marco

  reply	other threads:[~2013-03-11 21:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 22:21 Create course material with org-mode Torsten Wagner
2013-03-09 23:20 ` Thorsten Jolitz
2013-03-11 10:52   ` Torsten Wagner
2013-03-11 11:07     ` Andreas Röhler
2013-03-12 15:08       ` Torsten Wagner
2013-03-11 15:40     ` W. Greenhouse
2013-03-12 15:27       ` Torsten Wagner
2013-03-11 20:30     ` T.F. Torrey
2013-03-11 20:59       ` Marco [this message]
2013-03-11 22:02       ` Marcin Borkowski
2013-03-12 16:47         ` Marcin Borkowski
2013-03-12 17:21           ` Jay Kerns
2013-03-12 15:30       ` Torsten Wagner
2013-03-11 21:56 ` Brian van den Broek
2013-03-12 15:43   ` Torsten Wagner

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='CAFcvSsFKgjcTBoAgQJax+J=ZnXCuA6o9XMu=NnFoV-Mo02h97Q@mail.gmail.com' \
    --to=domanov@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tftorrey@tftorrey.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).