From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-review-schedule
Date: Fri, 25 Apr 2014 10:02:58 +0200 [thread overview]
Message-ID: <87bnvpltu5.fsf@gmail.com> (raw)
In-Reply-To: <m2sip1am6l.fsf@polytechnique.org> (Alan Schmitt's message of "Fri, 25 Apr 2014 09:43:46 +0200")
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.
> Is this mature/useful enough to be included? If so, I'll edit these as
> you suggest.
It seems useful. Maturity is not a problem since you have write access
to the repo. Anyway, Bastien will give you the definitive answer.
> After this many violations, I've added
>
> #+begin_src emacs-lisp
> (setq-default show-trailing-whitespace t)
> #+end_src
>
> to my configuration ;-)
FWIW, I use `whitespace-mode' instead.
> It works, so I guess it's not supposed to move the point. It's to be
> used with `org-agenda-skip-function', which says:
>
> ,-----------------------------------------------------------------------
> | Function to be called at each match during agenda construction.
> | If this function returns nil, the current match should not be skipped.
> | Otherwise, the function must return a position from where the search
> | should be continued.
> `-----------------------------------------------------------------------
Then I suggest to explain it in the docstring (both the return value and
that it will be used as `org-agenda-skip-function' value).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-04-25 8:02 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 ` Nicolas Goaziou [this message]
2014-04-27 8:09 ` org-review-schedule Alan Schmitt
2014-04-28 7:20 ` org-review-schedule AW
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:
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=87bnvpltu5.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=alan.schmitt@polytechnique.org \
--cc=bzg@gnu.org \
--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).