From: Nick Dokos <nicholas.dokos@hp.com>
To: Stefano Zacchiroli <zack@upsilon.cc>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: how to customize (inactive) timestamp textual format
Date: Tue, 22 Jun 2010 14:30:28 -0400 [thread overview]
Message-ID: <8822.1277231428@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from Stefano Zacchiroli <zack@upsilon.cc> of "Tue, 22 Jun 2010 18:40:51 +0200." <20100622164051.GA25088@upsilon.cc>
Stefano Zacchiroli <zack@upsilon.cc> wrote:
> On Tue, Jun 22, 2010 at 10:35:11AM -0400, Nick Dokos wrote:
> > Next time you are online, just git clone the Worg repository to your
> > machine. Then periodically, git pull. Problem solved.
>
> Sure, the problem will be solved for *me* (in fact, it already is: I
> cloned the Worg repo just a minute later reading some of the other posts
> in that thread :-)). I'm fairly sure that others will have the same
> problem, until they discover the Worg repo, whereas they surely already
> know about the in-Emacs org-mode documentation. YMMV.
>
... and others can see this thread in the mailing list and follow suit.
Or they can use the info doc (section 1.1, "Summary") to find the org
website and follow the link to Worg. Or they can ask on the list. And
once they know how to get there, there will be no need for another
documentation blob to land on *everybody's* disk. Besides, if they can't
find it in one of those ways, what makes you think that they will be able
to find it even if it is on their disk?
> Take this just as a feature request entitled "please ship Worg snapshots
> as part of the org-mode documentation"; as a feature request, feel free
> to ignore it if you don't think it's worth implementing.
>
Just in case it's not clear already :-) I personally don't think it's
worth it (but I am a marginal voice at best.) What might be worth it is
adding a sentence or two in the Summary section of the orgmode manual,
pointing out Worg's existence: if you don't know about it, it's impossible
to find, but once you know, the problem becomes trivial.
Regards,
Nick
next prev parent reply other threads:[~2010-06-22 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 9:49 how to customize (inactive) timestamp textual format Stefano Zacchiroli
2010-06-21 20:10 ` Carsten Dominik
2010-06-22 7:23 ` Stefano Zacchiroli
2010-06-22 10:17 ` Ian Barton
2010-06-22 10:37 ` Carsten Dominik
2010-06-22 10:41 ` Stefano Zacchiroli
2010-06-22 11:24 ` Giovanni Ridolfi
2010-06-22 11:45 ` Richard Riley
2010-06-22 12:36 ` Giovanni Ridolfi
2010-06-22 13:49 ` Richard Riley
2010-06-22 11:30 ` Eric S Fraga
2010-06-22 14:35 ` Nick Dokos
2010-06-22 15:34 ` Sebastian Rose
2010-06-22 16:40 ` Stefano Zacchiroli
2010-06-22 18:30 ` Nick Dokos [this message]
2010-06-23 8:00 ` Stefano Zacchiroli
2010-06-23 9:52 ` Giovanni Ridolfi
2010-06-23 10:02 ` Stefano Zacchiroli
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=8822.1277231428@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=zack@upsilon.cc \
/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).