emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org Tutorials need more structure
Date: Sat, 28 Sep 2013 10:26:22 -0400	[thread overview]
Message-ID: <5246E70E.7000705@verizon.net> (raw)
In-Reply-To: <EF119E90-532F-4890-991C-0C55691A898E@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

Hi Carsten,

On 9/28/2013 2:11 AM, Carsten Dominik wrote:
> Hi everyone,
>
> today I looked at our tutorial page at
>
> http://orgmode.org/worg/org-tutorials/index.html
>
> and came away with the feeling that that this page has become
> somewhat useless for people who are really new to Org.
- I disagree. Your Google talk was just right - for me. It was my first 
exposure to Org Mode.
>
> Can we have a discussion here on how this path should look like?
> When you came to Org-mode as a newby, what were the three resources
> that really made an impression on by being accessible and
> providing feel and promise for digging deeper?
About three years ago I stumbled across Org Mode when I was searching 
Emacs in general. (I already was familiar with Emacs, but only to "fool 
around".)
After viewing the Google talk, I specifically searched Org Mode. The 
three resources that made an impression:
- the general tutorials, starting with David O'Toole's,
- the Compact Guide with the Further Readings, (I did not look at the 
ones in the Org Manual) since this gave me a sense of how Org is and can 
be used, and
- *the mailing list*, which was the one resource that has made the 
greatest impression on me from the beginning. It has been and is my best 
resource; it provides the greatest exposure to Org Mode both as to its 
uses and sense of the Org community.
- Thank you Carsten, Bastien and all the rest if you for Org Mode.

Charlie Millar


[-- Attachment #2: Type: text/html, Size: 2153 bytes --]

  parent reply	other threads:[~2013-09-28 14:26 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
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 [this message]
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

  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=5246E70E.7000705@verizon.net \
    --to=millarc@verizon.net \
    --cc=emacs-orgmode@gnu.org \
    /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).