emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@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 18:02:06 +0200	[thread overview]
Message-ID: <20130928160206.GQ12411@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <CAD-VTcG5uauTER8rCJmTXAPLu+yN5KUkK1GL47JP_eGaMJdhJQ@mail.gmail.com>

Hi Joseph,

On Sat, Sep 28, 2013 at 01:59:28PM +0200, Joseph Vidal-Rosset wrote:
> 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?

I'm sorry my response came off that way.  All that I wanted to say was:
you are trying to leverage Org into doing something that it was not
designed to do.  That is not a bad thing at all.  The community always
welcomes such creative efforts and always makes an effort to document it
(usually on Worg).  Partly, this is also the reason why navigating
through the information available on Worg can be daunting.  I believe
Eric echoed the same sentiment in another message.

> >  For esoteric/specific needs like this
> > "advanced tutorials" are more appropriate.
> >
> 
> 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.

This actually proves my point.  Tutorials are written by volunteers like
you and me.  If there is no tutorial, it means no one has encoutered the
problem or encoutered and solved it (at least did not put effort into
documenting it).  In such a case please feel free to ask on the mailing
list.  Tell us what you want to achieve, what you have tried, and
someone with a bright idea will chime in.  I'm sure you have noticed it
by now, the Org community is one of the most welcoming and friendly out
there.

Good luck following up on Eric's suggestions with regards to your
particular request.  If you do get it working, I would encourage you to
document it on Worg or the mailing list.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

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

  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=20130928160206.GQ12411@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@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 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).