There is a "stub" bbdb.texinfo file in the repo, which isn't in the
debian binary package because including an empty info file seemed
silly. However it would be a good place to push info like this.
Roland, how about a "installation and configuration" section? That
seems like the most pressing docu
Forwarding Debian bug report which is actually an "upstream" issue.
See http://bugs.debian.org/766518
-- Forwarded message --
From: 積丹尼 Dan Jacobson
Date: 23 October 2014 19:35
Subject: Bug#766518: cannot easily add new entries anymore in gnus
To: Debian Bug Tracking System
Pac
>> I've been having similar issues. When it happens I delete the
>> .bbdb and *BBDB* buffers and they get reloaded and everything
>> seems okay again.
>
> I have never encountered this. Could you possibly try to provide a
> reproducible recipe for this or look at this in the debugger to see
> what
I've been having similar issues. When it happens I delete the .bbdb and
*BBDB* buffers and they get reloaded and everything seems okay again.
--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find
I'd check for the function. Seems more robust. (E.g., if someone forks
an older version and updates the date string, or if the function is
renamed or removed in the future.) If there's a bug you need to check
for you can always complicate the guard later.
--Barak.
If the autotools-based stuff doesn't work on MSWindows, please report
the details.
That would be a bug, and we should be able to fix it, because
autotools-generated
scripts are intended to work in that environment (given an installed
bourne-compatible
shell, and make), and they are doing nothing fa
> > > bbdb-separator-alist defines the separator for almost all fields
> > > to be ", ". Only for AKAs it is "; ". I do not know anymore
> > > how this came about. But I find it confusing, and I am thinking
> > > about changing the default to ", " for all fields.
> > >
> > > Thoughts or comments
, but would happily
integrate tested patches from xemacs users.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
--
Learn Graph Datab
> ... I think it would be
> good to have a pre-built bbdb-site.el included in the distribution
> tarball. But ideally `make' should rebuild this file whenever the
> user re-runs make with a new value for pkgdatadir.
The dependency on ../config.something should cause it to be regenerated
when the
> > > I am just curious: In the sed regular expressions, you use "[@]"
> > > instead of plain "@". Is there a reason for this? Plain "@" seems
> > > to be working, too.
> >
> > To shield the regex from autoconf!
>
> But I guess this would be really needed only if bbdb-site.el.in was
> actually p
> I am just curious: In the sed regular expressions, you use "[@]"
> instead of plain "@". Is there a reason for this? Plain "@" seems
> to be working, too.
To shield the regex from autoconf!
--Barak.
--
Learn Graph Da
Thanks, got it.
Pushed into debian packaging branch, "uscan" now verifies the signature.
(Also put a pithy comment in the commit about how the key downloaded
as .gpg file when it is actually ascii armored, with DOS line
terminators of all things.)
--Barak.
---
Roland, the 3.1 release tarball is signed,
http://download.savannah.gnu.org/releases/bbdb/
bbdb-3.1.tar.gz 01-Mar-2014 05:40 366K
bbdb-3.1.tar.gz.sig 01-Mar-2014 05:40 287
which is great,
$ gpg ~/tmp/bbdb-3.1.tar.gz.sig
Detached signature.
Please en
"Roland Winkler" writes:
> Great, thank you, your new approach should work for everyone.
> Two minor things:
>
> - In bbdb-site.el.in, you kept the value of bbdb-print-tex-path
> '("/usr/local/share"). This seems to be a typo that has been
> there for some time and should probably be replaced
Okay, I've reworked it again to satisfy, I believe, all criteria!
The pathway is simply bbdb-site.el.in to bbdb-site.el.
This is accomplished solely at "make" time, not "./configure" time.
(Using "sed" to replace the @foo@ things as well as the path.)
A pre-built bbdb-site.el can be included in
The way I rewrote it this week maintained the property that all the earlier
files in the transformation chain were valid elisp, just maybe with
incorrect stuff in the strings. And with filename that are clearly destined
to be tweaked and renamed bbdb-site.el.
The difficulties I see with having bbd
> Please correct me if I am wrong: doesn't your approach require that
> $pkgdatadir is properly defined at compile time, though it is
> normally required by make only at install time?
The standard autotools way of "baking in" directories and such into
installed files is to do so at build time, usi
Okay, I pushed a modified patch to github.com/barak/bbdb3 suggest-v3.x
which re-jiggers things to go
bbdb-site-pre-sed.el.in -> bbdb-site-pre-sed.el -> bbdb-site.el
If you'd like me to smoosh the history to do this as an isolated branch
atop savannah/master I can do the appropriate git-fu.
> The problem about your patch was that it not only defined the value
> of the lisp variable bbdb-print-tex-path, but it also defined the
> variable itself. So if someone does not install BBDB via make, then
> the variable bbdb-print-tex-path remains undefined and it would be
> difficult for most
> Check it out at
>
> https://savannah.nongnu.org/projects/bbdb
Excellent news, Roland!
One very minor issue.
$ autoreconf --force --install
$ ./configure --prefix=/usr
$ make
$ make install DESTDIR=/xxx
$ find /xxx/usr/share/ -name '*.tex*'
/xxx/usr/share/bbdb/bbdb-cols.tex
/xxx/usr/s
> There are two such ".in" files, bbdb-pkg.el.in and bbdb-site.el.in
In general, GNU autoconf generates "too" from "foo.in" at ./configure time.
It basically fills in some templates indicated by @bar@.
In this case the filled-in values are just version numbers inside quoted
expressions, shouldn't
; runs the command
bbdb-mua-edit-field-sender") but disconcertingly not in the bbdb
window proper (BBDB mode, "; is undefined").
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
---
I have a version packaged for Debian in the branch debian-v3.x in git://
github.com/barak/bbdb3, it would be great if you'd try it. Reports of
problems particularly welcome. If there are instructions to make it easier
for users to get started, and they amount to startup code, I'd be happy to
includ
Good idea to make it easy to push our an ELPA tarball.
Technically speaking, according to the autotools documentation, wildcards
like
lisp/*.el aren't supposed to be used in
Makefile.am files. (Well, maybe in "clean" targets I suppose.) Just
sayin'...
Cheers,
--Barak.
-
> BBDB has been updated to use Automake.
That is great. I hope this means I can retire the automake-using mods
I've been maintaining in my bbdb3 repo on github. Will do a merge
flushing as many of the mods I've made as possible.
(You are of course free to snag any code from there you like. It
I'd happily take pull requests for this for the clone in
git://github.com/barak/bbdb3
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
although
I certainly concede that stickers are probably better at motivating
toddlers than computer programmers.
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamil
suggest-v2.x. It also might have some
random tags.
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.ha
issues.)
Since the BBDB 2.x CVS repository is effectively dead, patches to BBDB
2.x can be made similarly by forking the repository
github.com/barak/BBDB and issuing a pull request.
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept
e in maintenance-only mode at this point, at
best.)
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
--
hat it is dead due
to a rebase.
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
--
Colocation vs. Managed Host
> I'm working with Roland to migrate BBDB to a Git repository on Savannah.
> I can do the migration like you did but wanted to ensure that the
> contributor history is correctly mapped and Roland hasn't had time to
> work on it.
Not sure how much real names instead of uids on the commits is worth:
I've repaired a minor bug in RMAIL insinuation for GNU Emacs 23, and
also made misc other patches, mainly in the Debian packaging. Changes
available via
git clone git://github.com/barak/BBDB.git
Feedback welcome.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI May
33 matches
Mail list logo
