emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: emacs-devel@gnu.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Deprecating BBDB 2.x support [in EUDC] for Emacs 26.1
Date: Sun, 29 Oct 2017 14:48:21 -0500	[thread overview]
Message-ID: <87fua17n22.fsf@gnu.org> (raw)
In-Reply-To: m3iney4v8y.fsf@fitzsim.org

On Sat, Oct 28 2017, Thomas Fitzsimmons wrote:
> For EUDC in the Emacs 26.1 release, I'd like to deprecate backward
> compatibility support for BBDB versions less than 3, and then
> subsequently remove that support, maybe as soon as Emacs 27.1.  Doing so
> would simplify eudcb-bbdb.el and allow it to take advantage of new
> features that Roland has been adding in BBDB 3.x, like UUIDs.

I am cross-posting this to the org-mode mailing list.  If there is more
to be said about the following from the perspective of org-mode, let's
continue the discussion on that list only.

I believe org mode interacts with BBDB, too.  Yet I know little to
nothing about the details.  From the org-mode perspective, is there a
similar issue with BBDB 2 vs. BBDB 3, as mentioned by Thomas about EUDC?

The long-term goal is to make at least the core of BBDB 3 part of GNU
Emacs to provide a more coherent framework for other packages like EUDC
and Org mode, see

https://lists.gnu.org/archive/html/emacs-devel/2015-11/msg01888.html

Are there any thoughts about this from the org community?

Here I am thinking also about the code in BBDB: my re-write of BBDB
mostly focused on BBDB "by itself" and its interface with MUAs like
Gnus, Rmail, etc.  Is there anything you would like to see to facilitate
the interaction of BBDB with other packages like Org mode (or EUDC)?

Roland

           reply	other threads:[~2017-10-29 19:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <m3iney4v8y.fsf@fitzsim.org>]

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=87fua17n22.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@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/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).