emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexander Poslavsky <alexander.poslavsky@gmail.com>
To: Memnon Anon <gegendosenfleisch@googlemail.com>
Subject: Re: Re: Basic orgmode tutorial
Date: Tue, 23 Mar 2010 20:40:52 +0100	[thread overview]
Message-ID: <016226EB-F811-4ECC-B968-4ED971DA377C@gmail.com> (raw)
In-Reply-To: <87634n5vdp.fsf@mean.albasani.net>


On Mar 23, 2010, at 6:37 PM, Memnon Anon wrote:

> Hi,
> Alexander Poslavsky <alexander.poslavsky@gmail.com> writes:
> 
>> attached is an updated version of the file, added agenda and some lines on gtd and exporting.
> 
> I just read it and you did a great job so far; I will have a closer look
> later again, sadly I am very busy right now :(.
> 
> Just one suggestion: I think it would be nice to have a "Further
> Reading" Subsection at the end of each Section, containing links to the 
> org manual pages, tutorials on this topic, FAQ Entries, screencasts,
> whatever.
> 
> Tutorials are an excellent starting point, but they also great to look
> up what you recently learned and are tinkering with. Lets say I read the
> tutorial and tried the "Clocking". Then, suddenly, I realize I am not
> sure how I can really integrate this feature into a workflow. First
> thing I would do is return to my tutorial and reread the section.
> If the limited information there [its a tutorial, it is by definition
> limited], I would really appreciate a "Further Reading" Section, linking
> e.g. to Bernt Hansens excellent infos on his clock usage, like:
> 
> * [[http://doc.norang.ca/org-mode.html#Clocking][Bernt Hansens extensive
>   description Time Clocking: Usage, Customization, Workflow
>   description.]]
> * [[http://orgmode.org/manual/Clocking-work-time.html#Clocking-work-time][The
>   orgmode Clocking Section]]
> * [[http://orgmode.org/worg/org-tutorials/index.php#sec-3.3][Clock
>   related Links on Worg]]
> 
> etc.
> 
> OTOH, this seems a bit redundant, given the fact that there is already
> org-tutorials on worg. It might be more convenient to only have a link
> to the proper sections on worg …
<snip>
thanks, just added a bunch of links for further reading. Even if redundant, it still might ease the pain of learning.

,alex

  parent reply	other threads:[~2010-03-23 19:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 18:59 Basic orgmode tutorial Alexander Poslavsky
2010-03-22 20:09 ` Adam
2010-03-22 20:51   ` John Hendy
2010-03-22 21:47     ` Alexander Poslavsky
2010-03-22 21:56       ` Dan Davison
2010-03-23 17:37       ` Memnon Anon
2010-03-23 18:14         ` Richard Riley
2010-03-23 19:40         ` Alexander Poslavsky [this message]
2010-03-23 22:07 ` Russell Adams
2010-03-24 10:52   ` Carsten Dominik
2010-03-24 17:18     ` Russell Adams
2010-03-24 19:07       ` Dan Davison
2010-03-24 20:49         ` Memnon Anon
2010-03-25  7:33           ` Carsten Dominik
2010-03-24 23:07         ` Stefan Vollmar
2010-04-09 22:07       ` 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=016226EB-F811-4ECC-B968-4ED971DA377C@gmail.com \
    --to=alexander.poslavsky@gmail.com \
    --cc=gegendosenfleisch@googlemail.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).