unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@fastmail.com>
To: emacs-devel@gnu.org
Subject: Re: RFC: Adding BBDB to Emacs core
Date: Sat, 14 Apr 2018 08:24:12 -0400	[thread overview]
Message-ID: <ygfvacuugb7.fsf@fastmail.com> (raw)
In-Reply-To: <m3zi265o49.fsf@fitzsim.org> (Thomas Fitzsimmons's message of "Sat, 14 Apr 2018 01:54:46 -0400")


That sounds pretty awesome, but does the bbdb package have any info
documentation?  Not that it really matters, but it would be nice to have.

Also, may I ask about ebdb?  Does ebdb ever have
a chance at making emacs core?

P.S.  I'm not a developer (at least not yet).  Just curious.


Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:

> Hi,
>
> Now that BBDB is copyright clear and available in GNU ELPA, thanks to
> Roland Winkler, I'd like to see what people think about also adding it
> to Emacs core.
>
> While maintaining EUDC in Emacs core, I've encountered many references
> to BBDB that are unresolved.  The only reason for this, as far as I can
> tell, is that historically BBDB's copyright status didn't allow it to be
> included in core.  Otherwise it probably would have been included all
> along.  Now it's possible to fix this properly.
>
> I've started an integration attempt on the scratch/eudc-bbdb-3 branch.
> I merged a recent version of BBDB from GNU ELPA into lisp/bbdb, then I
> resolved references to BBDB in EUDC.  For example, we can remove things
> like:
>
>    (declare-function bbdb-record-phones "ext:bbdb" t) ; via bbdb-defstruct
>
> and apply changes like:
>
> --- a/lisp/net/eudc-export.el
> +++ b/lisp/net/eudc-export.el
> @@ -31,10 +31,8 @@
>  ;;; Code:
>
>  (require 'eudc)
> -
> -;; NOERROR is so we can compile it.
> -(require 'bbdb nil t)
> -(require 'bbdb-com nil t)
> +(require 'bbdb)
> +(require 'bbdb-com)
>
>  (defun eudc-create-bbdb-record (record &optional silent)
>    "Create a BBDB record using the RECORD alist.
>
> This makes the code cleaner and easier to maintain.  We can also rely
> only on the version of BBDB in GNU Emacs (or a later one in GNU ELPA)
> and so all the BBDB < 3 compatibility code can be deleted without risk
> of breaking people's package sets (BBDB >= 3 auto-converts BBDB < 3
> databases to the updated format).
>
> I think applying this same type of effort to the other BBDB-dependent
> core packages would simplify them too.
>
> I'd like BBDB to become the default out-of-the-box local contact
> management library for GNU Emacs, in particular so that Gnus/EUDC/BBDB
> work together to provide email completion and snarfing out-of-the-box,
> without extra configuration or package installation.
>
> Thoughts?
>
> Thomas



  reply	other threads:[~2018-04-14 12:24 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14  5:54 RFC: Adding BBDB to Emacs core Thomas Fitzsimmons
2018-04-14 12:24 ` Joshua Branson [this message]
2018-04-14 22:06   ` Eric Abrahamsen
2018-04-14 22:46     ` Joshua Branson
2018-04-15  6:18       ` Bozhidar Batsov
2018-04-16  5:21         ` John Wiegley
2018-04-16 14:53           ` Thomas Fitzsimmons
2018-04-16 18:36             ` Stefan Monnier
2018-04-16 20:30               ` Eric Abrahamsen
2018-04-17  3:37               ` Thomas Fitzsimmons
2018-04-23 12:53             ` Phillip Lord
2018-04-23 13:21               ` Stefan Monnier
2018-04-23 16:21                 ` Phillip Lord
2018-04-23 17:45                   ` Stefan Monnier
2018-04-24 21:41                     ` Phillip Lord
2018-04-24 22:31                       ` Stefan Monnier
2018-04-25  0:42                         ` Paul Eggert
2018-04-25  1:50                           ` Stefan Monnier
2018-04-25  9:21                             ` Phillip Lord
2018-04-25 12:02                               ` Stefan Monnier
2018-04-25 16:31                                 ` Phillip Lord
2018-04-25 16:57                                   ` Stefan Monnier
2018-04-26 14:59                                     ` Phillip Lord
2018-04-25  9:19                         ` Phillip Lord
2018-04-25 16:04                         ` Radon Rosborough
2018-04-25 16:32                           ` Phillip Lord
2018-04-25 16:55                             ` Stefan Monnier
2018-04-25 20:16                               ` Radon Rosborough
2018-04-26 15:02                               ` Phillip Lord
2018-04-26 16:38                                 ` Stefan Monnier
2018-04-27  9:57                                   ` Phillip Lord
2018-04-27 13:32                                     ` Stefan Monnier
2018-04-17  3:23           ` Roland Winkler
2018-04-17  4:56             ` John Wiegley
2018-04-17 13:07             ` Stefan Monnier
2018-04-17 15:13               ` Roland Winkler
2018-04-18 23:11                 ` Stephen Leake
2018-04-23 12:57             ` Phillip Lord
2018-04-23 13:26             ` Stefan Monnier
2018-04-23 15:29               ` Roland Winkler
2018-04-14 22:13   ` Thomas Fitzsimmons
2018-04-14 13:34 ` Glenn Morris
2018-04-14 17:10   ` Radon Rosborough
2018-04-14 17:38   ` Thomas Fitzsimmons
2018-04-15 21:20   ` Phillip Lord
2018-04-16  3:11     ` Michael Welsh Duggan
2018-04-16 12:30       ` Stefan Monnier
2018-04-16 17:09     ` Achim Gratz
2018-04-16 18:10       ` Eli Zaretskii
2018-04-16 18:14         ` Achim Gratz
2018-04-23 12:45       ` Phillip Lord

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=ygfvacuugb7.fsf@fastmail.com \
    --to=jbranso@fastmail.com \
    --cc=emacs-devel@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.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).