From: David Masterson <dsmasterson@outlook.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: "35261@debbugs.gnu.org" <35261@debbugs.gnu.org>
Subject: bug#35261: 26.1; EBDB Documentation
Date: Fri, 19 Apr 2019 22:31:51 +0000 [thread overview]
Message-ID: <BYAPR07MB5734823D29B83E533A50840CA5270@BYAPR07MB5734.namprd07.prod.outlook.com> (raw)
In-Reply-To: <87zhonf3zs.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 18 Apr 2019 13:33:11 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> On 04/17/19 03:41 AM, David Masterson wrote:
>> Beyond this, I can see that lots of documentation (and, I assume,
>> functionality) is still needed:
>>
>> 1. Installation details of EBDB and related tools.
>> 2. Details on what type of records a database is composed of.
>> 3. Details on the fields of a record.
>> 4. Details on the type of a field.
>> 5. Import/Export functionality
>> 6. Hooks for add-ons
>>
>> * By 'details', I mean some Emacs Elisp and not just English to give us
>> real reference information.
>
> EBDB is only just stabilizing (the export stuff went through some big
> refactoring just recently) and I'm a little hesitant to lay all this
> stuff out in the manual. One of the long-term goals is definitely to
> make EBDB programmable and integratable with other packages, but I'm
> dragging my feet a little bit until I'm more confident that the API
> won't change. It'll get there, though.
Okay. Mostly consider #1 with:
* Installation as a package (and via savanah?)
* How to get help if needed (bug reports)
* Other packages to install/Use (Org and Gnus)
A primer as applies to EBDB for #2, #3, and #4 would be nice.
next prev parent reply other threads:[~2019-04-19 22:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 21:26 bug#35261: 26.1; EBDB Documentation David Masterson
2019-04-14 1:50 ` Eric Abrahamsen
2019-04-15 3:50 ` David Masterson
2019-04-15 5:07 ` Eric Abrahamsen
2019-04-15 20:56 ` David Masterson
2019-04-16 18:54 ` Eric Abrahamsen
2019-04-17 3:14 ` David Masterson
2019-04-18 19:51 ` Eric Abrahamsen
2019-04-19 22:22 ` David Masterson
2019-04-16 21:10 ` Eric Abrahamsen
2019-04-17 3:41 ` David Masterson
2019-04-18 20:33 ` Eric Abrahamsen
2019-04-19 22:31 ` David Masterson [this message]
2019-04-20 0:00 ` Eric Abrahamsen
2019-04-21 2:08 ` David Masterson
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR07MB5734823D29B83E533A50840CA5270@BYAPR07MB5734.namprd07.prod.outlook.com \
--to=dsmasterson@outlook.com \
--cc=35261@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
/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.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).