From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <david@tethera.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: RFC: tag macros
Date: Wed, 18 Jan 2012 18:15:37 -0800 [thread overview]
Message-ID: <87d3agphdi.fsf@servo.finestructure.net> (raw)
In-Reply-To: <871uqwmuar.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Wed, 18 Jan 2012 20:04:44 -0400, David Bremner <david@tethera.net> wrote:
> If we're going to go the way of providing a toolkit/api for uses to make
> their own bindings, then I think that we should make the effort to
> provide a proper info document with the distribution, rather than
> relying on the wiki. Of course, that means more work, and yet another
> markup language, I guess.
Can't we just use the emacs build-in documentation?
My idea of documenting on the wiki was just as a starting point. It
could list some of the available functions, and how to use them, and
then have good references to emacs documentation and how to find it.
I'm guessing we also have a lot of functions that are marked interactive
that don't necessarily need to be. Weeding those out might make
documentation easier.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-01-19 2:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 14:45 RFC: tag macros David Bremner
2012-01-18 15:04 ` David Edmondson
2012-01-18 18:33 ` Austin Clements
2012-01-18 19:03 ` David Bremner
2012-01-18 19:11 ` Austin Clements
2012-01-18 19:28 ` Jameson Graef Rollins
2012-01-18 18:50 ` Jameson Graef Rollins
2012-01-19 0:04 ` David Bremner
2012-01-19 2:15 ` Jameson Graef Rollins [this message]
2012-01-19 2:37 ` David Bremner
2012-01-19 13:10 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3agphdi.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).