From: Bastien <bzg@altern.org>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: Bernt Hansen <bernt@norang.ca>,
emacs-orgmode@gnu.org,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: The reportmode report does not count the running clock
Date: Wed, 04 Jan 2012 11:14:10 +0100 [thread overview]
Message-ID: <8762gr93m5.fsf@gnu.org> (raw)
In-Reply-To: <8739bwuoo8.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Tue, 03 Jan 2012 22:33:43 -0500")
Hi François,
pinard@iro.umontreal.ca (François Pinard) writes:
> That's why I suggested an appendix. We search in them, more than we
> really read them. On the other hand, it would considerably augment the
> weight of a printed manual, and so, be more harmful to our forests.
That's why I tried to gather *all* functions and variables in an .org
file, which you can see as an appendix. Did you check it?
>> Wrt documentation, Emacs is its own reference, by letting you access
>> everything with C-h v org-*.
>
> Emacs has impressive ways to offer its own documentation. Still a bit
> uneasy to use C-h v (or C-h f) on everything. M-x apropos org- RET is
> more handy and searchable, yet the documentation is likely limited to
> the first line of each docstring (so at least this convention for a
> complete sentence in the first line of a docstring).
>
>> Another point: there is a lot to do to improve the current docstrings
>> and the manual. This is a matter of 1) pulling from git, 2) modifying
>> the file, 3) run `C-x v =' in the buffer, 4) send the patch. [...]
>> If you're interested in improving this, please go ahead, I'd be
>> interested in getting something working along these lines.
>
> Oh, the problem is surely not the lack of interest, but the sore lack of
> free hours in a week, and the quantity of ways to occupy those rare
> hours already (something Org mode is tremendously helpful at organizing,
> by the way).
Org should claim 10% of the time it spares you ;-)
> Surely that given enough free time, I would just love to
> contribute. The truth is that I can only offer tiny crumbs. In any
> case, I'm saving your message and notes (who knows the future!).
Indeed. My suggestion is to stick to the current collective workflow:
let's try to document small things in relevant places (manual or worg)
and let's avoid Big Projects (bikesheds).
Thanks!
--
Bastien
next prev parent reply other threads:[~2012-01-04 10:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 4:28 The reportmode report does not count the running clock François Pinard
2011-12-13 11:39 ` Bernt Hansen
2011-12-13 14:22 ` François Pinard
2011-12-13 15:30 ` Bernt Hansen
2011-12-13 17:17 ` Carsten Dominik
2011-12-14 18:10 ` [PATCH] * doc/org.texi (Agenda commands): Document org-clock-report-include-clocking-task Bernt Hansen
2011-12-14 18:15 ` Bastien
2011-12-15 2:41 ` Bernt Hansen
2012-01-03 21:30 ` Sebastien Vauban
2012-01-03 23:18 ` Bastien
2012-01-05 5:10 ` François Pinard
2012-01-04 12:13 ` Bernt Hansen
2012-01-03 15:50 ` The reportmode report does not count the running clock François Pinard
2012-01-04 1:37 ` Bastien
2012-01-04 3:33 ` François Pinard
2012-01-04 10:14 ` Bastien [this message]
2012-01-04 15:08 ` François Pinard
2012-01-06 1:59 ` François Pinard
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=8762gr93m5.fsf@gnu.org \
--to=bzg@altern.org \
--cc=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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).