emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: AW <alexander.willand@t-online.de>
To: emacs-orgmode@gnu.org, alan.schmitt@polytechnique.org
Subject: Re: org-review-schedule
Date: Mon, 28 Apr 2014 09:20:16 +0200	[thread overview]
Message-ID: <4848913.XN1uMPlBq6@linux-j9m3.site> (raw)
In-Reply-To: <m261lv8a80.fsf@polytechnique.org>

Am Sonntag, 27. April 2014, 10:09:35 schrieb Alan Schmitt:
> On 2014-04-25 10:02, Nicolas Goaziou <n.goaziou@gmail.com> writes:
> > Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> >> I guess I should have asked: who decides what goes in contrib?
> > 
> > The Org maintainer. Another option is to turn it into an ELPA package.
> I need to learn how to do this. In the meantime, I've put the code on
> github: https://github.com/brabalan/org-review
> Alan

I'm really interessted in a more sophisticated review system than to put 
"REVIEW" on the list of TODO | DONE items. I guess you are having a good point 
here and your code will improve orgmode. 

But after reading your initial post and the README on github I'm not sure how 
to use your code. 

Could you complete your Example in the README, please?

1. Probably -- sorry, I'm lacking of lisp understanding -- we need to put the 
file org-review.el into a place where Emacs can find it.

2. It is probably necessary to add (require 'org-review) before the code in 
the example into the ".emacs" file, or am I wrong?

3. Usually people have something like 


in their org-file or an equivalent in their .emacs file. What will happen to 
such customisations? 

In short, could you elaborate for users without much understanding of lisp?

Thank you for your time and effort!


  reply	other threads:[~2014-04-28  7:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 20:27 org-review-schedule Alan Schmitt
2014-04-19  8:14 ` org-review-schedule Bastien
2014-04-19 11:16   ` org-review-schedule Alan Schmitt
2014-04-19 11:51     ` org-review-schedule Bastien
2014-04-24 11:51   ` org-review-schedule Alan Schmitt
2014-04-25  6:51     ` org-review-schedule Nicolas Goaziou
2014-04-25  7:43       ` org-review-schedule Alan Schmitt
2014-04-25  8:02         ` org-review-schedule Nicolas Goaziou
2014-04-27  8:09           ` org-review-schedule Alan Schmitt
2014-04-28  7:20             ` AW [this message]
2014-04-28 11:29               ` org-review-schedule Alan Schmitt
2014-05-06  9:27             ` org-review-schedule Bastien
2014-05-15 10:07             ` org-review-schedule Bastien
2014-05-20 12:48               ` org-review-schedule Alan Schmitt
2014-05-21 12:08                 ` org-review-schedule Bastien
2014-05-21 12:58                   ` org-review-schedule Alan Schmitt
2014-04-26  8:57       ` org-review-schedule Alan Schmitt
2014-04-26 10:38         ` org-review-schedule Thorsten Jolitz
2014-04-26 12:25           ` org-review-schedule Nicolas Goaziou
2014-04-27  8:08             ` org-review-schedule Alan Schmitt

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:

  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=4848913.XN1uMPlBq6@linux-j9m3.site \
    --to=alexander.willand@t-online.de \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).