Re: [ANNOUNCE] autoconf support for BBDB
I wrote: This message is to announce that I now have this working. Ronan would like to have this in 2.2, so I will start to commit my work shortly. Done (see the ChangeLog below). Some notes: - new files are present in the repository, including the configure script. - some files are removed, notably the Makefiles in ./ lisp/ and texinfo/ - All of this is based on autoconf 2.13 which is the last public release. I will upgrade to autoconf 2.50 as soon as it is released (the release date is hoped to be on feb.). More specifically for you Ronan: I haven't touched the html version of the documentation, since I suppose you have some special way of buiding it from the texinfo source. 2001-01-03 Didier Verna [EMAIL PROTECTED] * aclocal.m4: new file (Autoconf support). * configure.in: ditto. * install-sh: ditto. * Makefile.in: ditto. * lisp/Makefile.in: ditto. * texinfo/Makefile.in: ditto. * configure: new file (generated by Autoconf, but should be present in the archive/distribution). * Makefile: removed from the archive (generated by configure). * lisp/Makefile: ditto. * texinfo/Makefile: ditto. * INSTALL: update for the Autoconf support. * texinfo/bbdb.texinfo (Normal User): ditto. (XEmacs Package): ditto. -- / / _ _ Didier Vernahttp://www.inf.enst.fr/~verna/ - / / - / / /_/ /EPITA / LRDE mailto:[EMAIL PROTECTED] /_/ / /_/ / /__ / 14-16 rue VoltaireTel. +33 (1) 53 14 59 47 94276 Kremlin-Bictre cedex Fax. +33 (1) 44 08 01 99 ___ bbdb-info mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/mailman/listinfo/bbdb-info
Re: Fails to generate bbdb-autoloads.el
Sridhar Boovaraghavan [EMAIL PROTECTED] wrote: BBDB (CVS), Emacs 21.0.94, Win2k. I updated today and got the opportunity to try out the new configure script. The configure worked fine. I was unable to generate the bbdb-autoloads.el. It gives me an empty file with a single ^L character. Running this through bash and cmd.exe produced the same results. Could you please go to the lisp directory, type `make autoloads' and show us the make output ? This target is not affected by the autoconf support, apart from the fact that it uses the make variable `EMACS' which should appear with a correct value at the top of lisp/Makefile. -- / / _ _ Didier Vernahttp://www.inf.enst.fr/~verna/ - / / - / / /_/ /EPITA / LRDE mailto:[EMAIL PROTECTED] /_/ / /_/ / /__ / 14-16 rue VoltaireTel. +33 (1) 53 14 59 47 94276 Kremlin-Bictre cedex Fax. +33 (1) 44 08 01 99 ___ bbdb-info mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/mailman/listinfo/bbdb-info
Re: cvs update blew away configure; and I don't have autoconf
Ronan Waide wrote: On January 26, [EMAIL PROTECTED] said: Fair enough. Modifying .cvsignore to include configure seems to have solved the problem. I guess I don't grok CVS well enough to understand the problem but I don't want to cause any pain. I wonder if adding configure to .cvsignore in the repository would be appropriate, though since it's already set up to ignore the other generated files (like Makefile, config.status etc). Yep, that's right. On the list of things to do, if Didier doesn't beat me to it. For the record, I'm *against* removing the configure script from the CVS archive. The rule generated files don't go in CVS is in general too strict for many situations. My arguments are the following: 1/ there are different kinds of generated files. Makefile's are generated at build time, and depend on the _user_ environment. They're very likely to be different from build to build so it is obvious to exclude them from the archive. `configure', on the contrary, is the same file for _everybody_ so it makes a lot of sense to have it in the archive. Put it another way, why would you require every single person to rebuild the _same_ file locally ? 2/ building the `configure' script requires a working autoconf. This is already a supplementary burden for each CVS user: we shouldn't force them to have a working autoconf to build BBDB, and I mean it, even for CVS users that are expected to be willing to leave on the bleeding edge. But there is worse: having a working autoconf is not in general sufficient. You have to use preferably the same autoconf as the one I'm using. For now (for the release I mean), I stayed on autoconf 2.3 on purpose. But my plan is also to move quickly to autoconf 2.50, which is not yet released. As a consequence, this will impose that *all* of our CVS users move to this autoconf version, and what's more, the number of erroneous bug reports that we will receive because of version mismatch is very likely to be important. We're shooting ourselves in the foot. 3/ the only real argument in favor of excluding configure from CVS is that this sort of file usually generates more conflicts that common files, and these conflicts are very difficult to edit by hand. However, the script is not likely to change very often, and 'rm configure ; cvs update configure' is not very painful to type, as a conflict resolution mechanism ;-) That's why I think configure should stay in CVS. That is the case for many softwares, including XEmacs. -- / / _ _ Didier Verna http://www.lrde.epita.fr/~didier - / / - / / /_/ /EPITA / LRDE mailto:[EMAIL PROTECTED] /_/ / /_/ / /__ / 14-16 rue VoltaireTel. +33 (1) 53 14 59 47 94276 Kremlin-Bictre cedex Fax. +33 (1) 44 08 01 99 ___ [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
[PATCH] install-pkg fixes
done ; \
+ fi ; \
+fi
+
+uninstall-pkg:
+ -$(RM) $(PACKAGEDIR)/info/bbdb.info*
+
info: bbdb.info
bbdb.info: bbdb.texinfo
@@ -28,14 +59,14 @@
fi
clean:
- $(RM) -f *.aux *.cp *.cps *.dvi *.pdf *.fn *.fns *.ky *.log *.pg \
+ -$(RM) *.aux *.cp *.cps *.dvi *.pdf *.fn *.fns *.ky *.log *.pg \
*.toc *.tp *.vr *.vrs
+# Backward compatibility
reallyclean: distclean
distclean: clean
- $(RM) -f bbdb.info*
+ -$(RM) bbdb.info*
cvsclean: distclean
- $(RM) -f Makefile
-
+ -$(RM) Makefile
Index: texinfo/bbdb.texinfo
===
RCS file: /cvsroot/bbdb/bbdb/texinfo/bbdb.texinfo,v
retrieving revision 1.35
diff -u -w -r1.35 bbdb.texinfo
--- texinfo/bbdb.texinfo2001/01/08 15:37:26 1.35
+++ texinfo/bbdb.texinfo2001/02/02 13:44:38
@@ -533,54 +533,54 @@
This option sets the root of the XEmacs package directory. By default,
@file{/usr/local/lib/xemacs/site-packages} is used.
@item @code{--with-symlinks}
-If this option is used, the @file{lisp} and @file{info} directories will
-be installed as links to the source ones. Otherwise, they will be
-copied to the appropriate place.
+If this option is used, the installation will be done by making symbolic
+links to the sources instead of copying the files.
@item @code{--with-linkpath=PATH}
-Without this variable, the @file{lisp} and @file{info} directories will
-be linked in with the output of @code{pwd} as the source directory. If
-something else should be used as the source directory, you should pass
-the 'something else' to @code{--with-linkpath}. If, for example,
-@code{pwd} returns @file{/p/local/elisp/bbdb}, the @file{lisp},
-@file{info} and @file{etc} (which will include the files distributed in
-@file{tex} and @file{utils}) directories will be linked in from
-@file{/p/local/elisp/bbdb/@{lisp,info,etc@}}. If, however, you prefer
-that they be linked in from @file{/usr/local/elisp/bbdb/...}, say
+Without this option, the installation process uses the output of
+@code{pwd} to determine the current directory. If something else should
+be used, you should provide an alternate name for the BBDB toplevel
+directory by using @code{--with-linkpath}. If, for example, @code{pwd}
+returns @file{/p/local/elisp/bbdb}, but you prefer to use
+@file{/usr/local/elisp/bbdb/...} for the links, usr this:
@code{configure --with-linkpath=/usr/local/elisp/bbdb}. This option is
ignored if @code{--with-symlinks} is not used.
@end table
-To perform the installation, use the command @code{make install-pkg}.
+To perform the (un)installation, use the command @code{make (un)install-pkg}.
This will compile the @file{lisp/auto-autoloads.el} file and will
-install the source and documentation files at the appropriate places.
-The final installation tree will take the following form:
+install the appropriate files to the appropriate places. The final
+installation tree will take the following form:
@table @code
- @item $PACKAGEROOT/
+ @item $(PACKAGEDIR)/
@table @code
- @item etc/
+ @item lisp/
@table @code
@item bbdb/
- @table @code
-@item tex/
-@i{support files for bbdb-print, copied from the @file{tex} directory
-in the source distribution}
-@item utils/
-@i{miscellaneous utilities, copied from the @file{utils} directory in
-the source distribution}
- @end table
+ @i{@b{BBDB} lisp source files. This directory contains a copy of all
+@code{.el} and @code{.elc} files from the @file{lisp} source directory,
+or is a symbolic link to it.}
@end table
@item info/
@table @code
- @item bbdb/
- @i{@b{BBDB} documentation files, copied from the @file{info} directory
- in the source distribution}
+ @item bbdb.info*
+ @i{@b{BBDB} documentation files. These are either copies of the info
+files from the @file{texinfo} source directory, or are symbolic links to
+them.}
@end table
- @item lisp/
+ @item etc/
@table @code
@item bbdb/
- @i{@b{BBDB} lisp source files, copied from the @file{lisp} directory
- in the source distribution}
+ @table @code
+@item tex/
+@i{@b{BBDB} support files for bbdb-print. This directory contains a
+copy of the appropriate files from the @file{tex} source directory, or
+is a symbolic link to it.}
+@item utils/
+@i{@b{BBDB} miscellaneous utilities. This directory contains a copy
+of the appropriate files from the @file{utils} source directory, or is a
+symbolic link to it.}
+ @end table
@end table
@end table
@end table
--
/ / _ _ Didier Verna http://www.lrde.epita.fr/~didier
- / / - / / /_/ /EPITA / LRDE mailto:[EMAIL PROTECTED]
/_/ / /_/ / /__ / 14-16 rue VoltaireTel. +33 (1) 53 14 59 47
94276 Kremlin-Bictre cedex Fax. +33 (1) 44 08 01 99
___
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
Re: can't build without vm installed
Michael Harnois [EMAIL PROTECTED] wrote: Apparently the comment # this is lovely, isn't it? Surprisingly enough, it seems to work... isn't quite true, as the current cvs (and for the past week or so) won't build at all if vm isn't installed: ===[root] /usr/local/src/bbdb # make gnus cd lisp; make gnus xemacs -no-site-file -no-init-file -batch -q -eval "` dir=\". \"; echo \(setq load-path \(append \(list ; for i in $dir ; do echo \\"$i\\"\ ; done ; echo \) load-path\)\) ; `" -l ./bbdb.elc -eval '(progn (if (not (string-match "" "")) (setq load-path (cons "" load-path))) (if (load "vm-version" t) (cond (( (string-to-number vm-version) 5.31) (load "vm")) (t (load "vm-vars") (load "vm")' -f batch-byte-compile bbdb-hooks.el Loading vm-version... Cannot open load file: vm xemacs exiting I can't reproduce this. It seems that you have a reachable vm-version.el file somewhere in your path. Can you check this ? -- / / _ _ Didier Verna http://www.lrde.epita.fr/~didier - / / - / / /_/ /EPITA / LRDE mailto:[EMAIL PROTECTED] /_/ / /_/ / /__ / 14-16 rue VoltaireTel. +33 (1) 53 14 59 47 94276 Kremlin-Bictre cedex Fax. +33 (1) 44 08 01 99 ___ [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
[PATCH] compilation from an emacs shell buffer
NOTE: This patch has been committed.
Dear Big Brothers,
This fixes the problem people reported when configuring BBDB from an
Emacs shell buffer. I sincerely apologize for my being silent these days. I
just currently can't cope with all the things I have to do. I'm also preparing
an upgrade of the configure script to Autoconf 2.50. This should be there
around next week.
ChangeLog addition:
2001-05-23 Didier Verna [EMAIL PROTECTED]
* aclocal.m4 (BBDB_PROG_EMACS): fix Emacs detection problem when
configuring from an Emacs shell buffer.
BBDB Patch (runsocks cvs -q diff -u -t -b -B -w aclocal.m4):
Executing ssh-askpass to query the password...
Index: aclocal.m4
===
RCS file: /cvsroot/bbdb/bbdb/aclocal.m4,v
retrieving revision 1.1
diff -u -u -t -b -B -w -r1.1 aclocal.m4
--- aclocal.m4 2001/01/08 15:34:16 1.1
+++ aclocal.m4 2001/05/23 07:41:55
@@ -85,17 +85,27 @@
fi ])
dnl Choose an Emacs flavor:
-dnl If I were pedantic, I'd check that the user-specified executable is
-dnl actually working. I might do that someday.
+dnl NOTE: when running from an Emacs shell buffer, the variable EMACS is
+dnl set to t, which confuses AC_CHECK_PROG. The solution we adopt is to use
+dnl another variable (namely tmp_EMACS) to perform the checkings. However, we
+dnl also want to preserve the ability to override the executable name through
+dnl the EMACS env var as is standardly done in configure scripts. So we take
+dnl care of initializing tmp_EMACS to EMACS, unless the value is t.
AC_DEFUN([BBDB_PROG_EMACS],
- [ AC_SUBST(EMACS)
+ [ if test x${EMACS} != xt ; then
+ tmp_EMACS=${EMACS}
+fi
AC_ARG_WITH([emacs],
[ --with-emacs=PROG which flavor of Emacs to use],
-[ EMACS=${withval} ],
-[ AC_CHECK_PROGS(EMACS, emacs xemacs) ])
-if test x${EMACS} = x ; then
+[ tmp_EMACS=${withval} ],
+[ AC_CHECK_PROGS(tmp_EMACS, emacs xemacs) ])
+if test x${tmp_EMACS} = x ; then
dnl This is critical enough to generate an error and not a warning...
AC_MSG_ERROR([*** No Emacs program found.])
-fi ])
+fi
+dnl If I were pedantic, I'd check that the user-specified executable is
+dnl actually working. I might do that someday.
+EMACS=${tmp_EMACS}
+AC_SUBST(EMACS) ])
dnl aclocal.m4 ends here
--
Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 44 08 01 99 [EMAIL PROTECTED]
___
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
[PATCH] Autoconf 2.50 upgrade
NOTE: This patch has been committed.
Dear Big Brothers,
this is the promised upgrade to Autoconf 2.50. Nothing has changed
for the end-user. For developers, the important things to know are:
1/ you *must* now use autoconf 2.50 to regenerate the configure script. It is
*not* backward compatible with Autoconf 2.13.
2/ the source file for the configure script has been renamed from
`configure.in' to `configure.ac'.
I'll post a new configure script in a separate message.
ChangeLog addition:
2001-06-05 Didier Verna [EMAIL PROTECTED]
* aclocal.m4: upgrade to Autoconf 2.50.
* aclocal.m4 (BBDB_PRE_INIT): new.
* aclocal.m4 (BBDB_ARG_SUBST): new.
* configure.ac: renamed from configure.in. Upgrade to Autoconf
2.50.
BBDB Patch (runsocks cvs -q diff -u -t -b -B -w configure.in configure.ac aclocal.m4):
Executing ssh-askpass to query the password...
cvs server: configure.in was removed, no comparison available
cvs server: configure.ac is a new entry, no comparison available
Index: aclocal.m4
===
RCS file: /cvsroot/bbdb/bbdb/aclocal.m4,v
retrieving revision 1.2
diff -u -u -t -b -B -w -r1.2 aclocal.m4
--- aclocal.m4 2001/05/23 07:49:04 1.2
+++ aclocal.m4 2001/06/05 12:17:04
@@ -22,13 +22,58 @@
dnl Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-dnl Transforms a colon separated list into a space separated one:
+dnl BBDB_PRE_INIT
+dnl
+dnl Find BBDB version number and put it in the m4 macro BBDB_VERSION
+dnl
+dnl I fought really hard, but finally I got it accepted to make autoconf load
+dnl aclocal *before* AC_INIT is called. This is important for me, in
+dnl situations like this precise one, where I want to dynamically compute the
+dnl version number to pass to AC_INIT.
+dnl There's one minor glitch however, the AC_DEFUN mechanism is not available
+dnl before AC_INIT is called because of diversions. So this macro is defined
+dnl only in terms of m4 sugar.
+m4_define([BBDB_PRE_INIT],
+[ m4_define([_BBDB_VERSION],
+ m4_esyscmd([sed -n 's/^(defconst bbdb-version \(.*\))/\1/p'
+lisp/bbdb.el]))
+ m4_define([BBDB_VERSION],
+ m4_substr(_BBDB_VERSION, 0, decr(len(_BBDB_VERSION
+ m4_undefine([_BBDB_VERSION])
+])
+
+dnl BBDB_ARG_SUBST(VAR, OPTION, VAL, DESC[, DEFAULT[, ACTION]])
+dnl
+dnl Substitute the autoconf variable VAR to a value specified by the user
+dnl option --with-OPTION[=VAL] (described by DESC), or with a DEFAULT value.
+dnl If an additional ACTION is given, it is executed at the top of the
+dnl ACTION-IF-FOUND part of AC_ARG_WITH.
+dnl WARNING: pay attention to the quoting of ACTION if given !
+AC_DEFUN([BBDB_ARG_SUBST],
+[
+ AC_SUBST([$1])
+ AC_ARG_WITH([$2],
+AC_HELP_STRING([--with-][$2]ifelse($3, [], [], [=$3]),
+ [$4]ifelse($5, [], [], [ [[[$5)),
+[
+ ifelse($6, [], [], $6)
+ $1=${withval}
+],
+ifelse($5, [], [], [$1=$5]))
+])
+
+dnl BBDB_COLON_TO_SPACE(VAR)
+dnl
+dnl Transforms a (possibly) colon separated list VAR into a space separated
+dnl one. VAR needs not be quoted.
AC_DEFUN([BBDB_COLON_TO_SPACE],
[ case $$1 in *:*)
$1=`echo $$1 | sed -e 's/:/ /g'`;;
esac ])
-dnl Find GNU tar:
+dnl BBDB_PROG_GNU_TAR
+dnl
+dnl Find a (g)tar program and make sure it is GNU one. A failure is not fatal
+dnl since tar is needed for non critical targets only.
AC_DEFUN([BBDB_PROG_GNU_TAR],
[ AC_CHECK_PROGS(TAR, gtar tar)
if test x${TAR} = xtar ; then
@@ -45,7 +90,10 @@
AC_MSG_WARN([*** Some targets will be unavailable.])
fi ])
-dnl Choose a compression program:
+dnl BBDB_PROG_COMPRESS
+dnl
+dnl Find a gzip / compress compression program. A failure is not fatal, only
+dnl tarballs won't be compressed.
AC_DEFUN([BBDB_PROG_COMPRESS],
[ AC_CHECK_PROGS(COMPRESS, gzip compress)
AC_SUBST(COMPEXT)
@@ -60,7 +108,10 @@
COMPEXT=Z
fi ])
-dnl Find makeinfo:
+dnl BBDB_PROG_MAKEINFO
+dnl
+dnl Find a makeinfo program. A failure is not fatal, only info files won't be
+dnl built.
AC_DEFUN([BBDB_PROG_MAKEINFO],
[ AC_CHECK_PROG(MAKEINFO, makeinfo, makeinfo)
if test x${MAKEINFO} = x ; then
@@ -68,7 +119,10 @@
AC_MSG_WARN([*** Info files will not be built.])
fi ])
-dnl Find texi2dvi:
+dnl BBDB_PROG_TEXI2DVI
+dnl
+dnl Find a texi2dvi program. A failure is not fatal, only dvi and pdf files
+dnl won't be built.
AC_DEFUN([BBDB_PROG_TEXI2DVI],
[ AC_CHECK_PROG(TEXI2DVI, texi2dvi, texi2dvi)
if test x${TEXI2DVI} = x ; then
@@ -76,7 +130,10 @@
AC_MSG_WARN([*** DVI and PDF files will not be built.])
fi ])
-dnl Find etags:
+dnl BBDB_PROG_ETAGS
+dnl
+dnl Find an etags program. A failure is not fatal, only TAGS file won't be
+dnl built.
AC_DEFUN([BBDB_PROG_ETAGS],
[ AC_CHECK_PROG(ETAGS, etags, etags)
if test x${ETAGS} = x ; then
@@ -84,7 +141,10 @@
AC_MSG_WARN([*** Tags file will not be built.])
fi
Autoconf 2.50 generated `configure' script
configure.gz -- Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47 94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 44 08 01 99 [EMAIL PROTECTED]
Re: [A] Preserve hooks locality
Adrian Aichner wrote: Interesting! Didier, have you also observed bbdb losing coding cookie of line 1 on write? nope. This might be the reason for the coding system breakage reported on bbdb-info recently. See, e.g. http://www.mail-archive.com/bbdb-info@lists.sourceforge.net/index.html#04609 Could the issue you found have to do with this? At a first glance, I don't think so. BBDB uses only local-write-file-hooks, which is permanent-local. The bug I'm fixing was causing the *global* hooks values to be lost after their first execution. -- MySpace: http://www.myspace.com/didierverna Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 [EMAIL PROTECTED] - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
[COMMIT] Fix infinite loop (misplaced iteration)
NOTE: This patch has been committed. The version below is informational only (whitespace differences have been removed). Dear Big Brothers, The following patch fixes an infinite loop that was due to a misplaced iteration in bbdb-collect-all-aliases (you could see the effect when defining mail aliases for a record without a net field). ChangeLog addition: 2008-01-29 Didier Verna [EMAIL PROTECTED] * lisp/bbdb-com.el (bbdb-collect-all-aliases): Fix infite loop due to misplaced iteration. This occurred when triggering the warning. BBDB source patch: Diff command: cvs -q diff -u -t -b -B -w Files affected: lisp/bbdb-com.el === RCS Index: lisp/bbdb-com.el === RCS file: /cvsroot/bbdb/bbdb/lisp/bbdb-com.el,v retrieving revision 1.198 diff -u -u -t -b -B -w -r1.198 bbdb-com.el --- lisp/bbdb-com.el4 Dec 2007 23:25:11 - 1.198 +++ lisp/bbdb-com.el29 Jan 2008 10:50:02 - @@ -2680,13 +2680,13 @@ (let* ((aliases-field bbdb-define-all-aliases-field) (target (cons bbdb-define-all-aliases-field .)) (records (bbdb-search (bbdb-records) nil nil nil target)) - r nets aliases result) -(while records - (setq r (car records) -nets (bbdb-record-net r)) + nets aliases result) +(dolist (r records) + (setq nets (bbdb-record-net r)) (if (null nets) (if (not bbdb-silent-running) - (bbdb-warn record %S has no network address, but the aliases: %s + (bbdb-warn + record %S has no network address, but the aliases: %s (bbdb-record-name r) (bbdb-record-getprop r aliases-field))) (setq aliases (bbdb-split (bbdb-record-getprop r aliases-field) ,)) @@ -2702,7 +2702,8 @@ ;; the NTH net of the record (setq item (string-to-number (match-string 2 alias)) item (list (or (nth item nets) -(error net[%d] for alias %S does not exist! +(error + net[%d] for alias %S does not exist! item alias))) alias (match-string 1 alias))) ((string-match ^\\(.+\\)/\\(.+\\)$ alias) @@ -2721,8 +2722,7 @@ (if (setq match (assoc alias result)) (nconc match (cons item nil)) (setq result (cons (list alias item) result -(setq aliases (cdr aliases -(setq records (cdr records +(setq aliases (cdr aliases)) result)) (defun bbdb-expand-alias (alias-items aliases optional seen-aliases) -- Resistance is futile. You will be jazzimilated. Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (0)1 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (0)1 53 14 59 22 [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
[COMMIT] Fix for gnus-user-format-function-B
NOTE: This patch has been committed. The version below is informational only (whitespace differences have been removed). Dear Big Brothers, the following patch fixes the behavior of bbdb/gnus-user-format-function-B when gnus-ignored-mail-addresses is non nil. ChangeLog addition: 2008-01-29 Didier Verna [EMAIL PROTECTED] * lisp/bbdb-gnus.el (bbdb/gnus-summary-get-author): Use the proper nnheader interface for retrieving header values. BBDB source patch: Diff command: cvs -q diff -u -t -b -B -w Files affected: lisp/bbdb-gnus.el === RCS Index: lisp/bbdb-gnus.el === RCS file: /cvsroot/bbdb/bbdb/lisp/bbdb-gnus.el,v retrieving revision 1.103 diff -u -u -t -b -B -w -r1.103 bbdb-gnus.el --- lisp/bbdb-gnus.el 29 Jan 2008 14:50:18 - 1.103 +++ lisp/bbdb-gnus.el 29 Jan 2008 16:20:37 - @@ -338,9 +338,10 @@ (let* ((from (mail-header-from header)) (to (let ((gifa (bbdb/gnus-ignored-from-addresses))) (when (and gifa (string-match gifa from)) - (let* ((to (or (mail-header 'To) -(mail-header 'CC) -(mail-header 'Newsgroups + (let* ((extras (mail-header-extra header)) +(to (or (cdr (assoc 'To extras)) +(cdr (assoc 'CC extras)) +(cdr (assoc 'Newgroups extras) (if (and to (listp to)) (cdr (car to)) to) -- Resistance is futile. You will be jazzimilated. Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (0)1 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (0)1 53 14 59 22 [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
[COMMIT] Improve bbdb-define-all-aliases docstring
NOTE: This patch has been committed. The version below is informational only (whitespace differences have been removed). ChangeLog addition: 2008-01-29 Didier Verna [EMAIL PROTECTED] * lisp/bbdb-com.el (bbdb-define-all-aliases): Rewrite docstring and format it properly for describe-function. BBDB source patch: Diff command: cvs -q diff -u -t -b -B -w Files affected: lisp/bbdb-com.el === RCS Index: lisp/bbdb-com.el === RCS file: /cvsroot/bbdb/bbdb/lisp/bbdb-com.el,v retrieving revision 1.199 diff -u -u -t -b -B -w -r1.199 bbdb-com.el --- lisp/bbdb-com.el29 Jan 2008 10:56:06 - 1.199 +++ lisp/bbdb-com.el29 Jan 2008 14:45:54 - @@ -2786,33 +2786,37 @@ ;;;###autoload (defun bbdb-define-all-aliases () Define mail aliases for some of the records in the database. -Every record which has a `mail-alias' field will have a mail alias defined for -it which is the contents of that field. If there are multiple comma-separated -words in the `mail-alias' field, then all of those words will be defined as -aliases for that person. - -If multiple entries in the database have the same mail alias, then that alias -expands to a comma-separated list of the primary network addresses of all of -those people. - -An alias ending in \*\ it will be expanded to all the nets of the record. -An alias ending in \[NTH]\ will expand the the NTH net of the record. - -Special nets exist and expand to other nets using one of `bbdb-magic-net-*' or -`bbdb-magic-net-1' functions or user defined function. Still also magic nets -may not contain the comma character. If you have to use it put it into an -own magic net function or us the octal escape sequence \\\054\. - -Nets matching \FUNCTION/ARG\, i.e. they have at least one \/\ character in -them, will be passed to the function `bbdb-magic-net-FUNCTION' with the string -argument ARG. - -Nets starting with a \(\ will be considered as a lisp list, where the -first list element is prefixed by `bbdb-magic-net' and then called -as function with the rest of the list as arguments. - -Nets which do not contain an \@\ and exist as alias are expanded recursively. -This can be used to define hierarchical aliases. +Every record which has a `mail-alias' field \(but see +`bbdb-define-all-aliases-field') will have a mail alias defined for it +which is the contents of that field. If there are multiple +comma-separated words in this field, then all of those words will be +defined as aliases for that record. + +If multiple entries in the database have the same mail alias, then +that alias expands to a comma-separated list of the primary network +addresses of all of those people. + +An alias ending in \*\ will expand to all the nets of the record. +An alias ending in \[NTH]\ will expand the the NTH net of the +record. + +Special nets exist and expand to other nets using one of +`bbdb-magic-net-*', `bbdb-magic-net-1' or `bbdb-magic-net-SOMETHING'. +Magic nets may not contain any comma character. If you need one, please +put it into a custom magic net function or use the octal escape +sequence \\\054\. + +Nets matching \FUNCTION/ARG\ (i.e. containing at least one \/\) +will be passed to the function `bbdb-magic-net-FUNCTION' with the +string argument ARG. + +Nets starting with a \(\ will be considered as a lisp list where the +first element is prefixed by `bbdb-magic-net-' and then called as a +function with the rest of the list as arguments. + +Nets which do not contain an \@\ character and also exist as aliases +are expanded recursively. This can be used to define hierarchical +aliases. Other nets are formatted by `bbdb-dwim-net-address'. (interactive ) -- Resistance is futile. You will be jazzimilated. Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (0)1 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (0)1 53 14 59 22 [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Moving BBDB from CVS to BZR
Robert Widhopf-Fenk [EMAIL PROTECTED] wrote: I think about moving the BBDB repository from CVS to BZR and host it on https://launchpad.net instead of sourceforge.net. So what do the other developers with CVS write access think about this? I'm a bit reluctant to learn yet another VCS. In my lab, we went from CVS, PRCS to SVN and some of my collegues are starting to use Git. In XEmacs, we recently switched to Mercurial... Since I don't know bzr at all, I can't say anything about it. On the other hand, I guess my usage of BBDB's repo (even as a committer) is simple enough so that I wouldn't have to dig deep into bzr to be able to use it. So in short, I'm not really welcoming this change (although I would welcome a move to hg) but I'm not strongly opposed to it. -- 5th European Lisp Workshop at ECOOP 2008, July 7: http://elw.bknr.net/2008/ Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (0)1 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (0)1 53 14 59 22 [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Moving BBDB from CVS to BZR
Gour [EMAIL PROTECTED] wrote: dvl == Didier Verna [EMAIL PROTECTED] writes: dvl I'm a bit reluctant to learn yet another VCS. In my lab, we went dvl from CVS, PRCS to SVN and some of my collegues are starting to use dvl Git. In XEmacs, we recently switched to Mercurial... Heh, now it's time for darcs-2 ;) Which I use for my local personal projects ;-) -- 5th European Lisp Workshop at ECOOP 2008, July 7: http://elw.bknr.net/2008/ Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (0)1 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (0)1 53 14 59 22 [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Moving BBDB from CVS to BZR
Robert Widhopf-Fenk [EMAIL PROTECTED] wrote: And you didn't advocate hg or darcs ;-) I got fed up with fighting :-) In XEmacs, we recently switched to Mercurial... I know. Do you have any reference on the decisions-making, I am always curious how projects switching from CVS select one of the may new vcs. hg has a lot of following. AFAICR, the two final candidates were hg and git, but almost everybody agreed that they were pretty much equivalent. It was decided to use hg probably because it is a bit simpler, much more (and better) documented and requires less repo administration (if any). Maybe also a question of internals code quality, but I'm not sure. There was a thread about that on our private review-board mailing list. I can dig into it if you want more details; but not just right now. Things are pretty hectic overhere. Has proper rename support finally landed in hg? I think hg still does this the usual^H^H^Hwrong way ;-) -- 5th European Lisp Workshop at ECOOP 2008, July 7: http://elw.bknr.net/2008/ Didier Verna, [EMAIL PROTECTED], http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (0)1 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (0)1 53 14 59 22 [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: BBDB beginners guide?
Roland Winkler wink...@gnu.org wrote: However, while I do not know the details of such formats, I expect that nonetheless it should not be too difficult to develop some code to import / export bbdb records from / into these formats. I believe I even once saw some code that allowed the old bbdb to interface with vcard. I haven't tried the new BBDB yet, but just in case, here's a library that I use to export my BBDB to vcards and subsequently import them in AddressBook. bbdb-vcard-export.el Description: application/emacs-lisp -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: [BBDB] Changelog 2010-04-10
Roland Winkler wink...@gnu.org wrote: First of all, the most noteworthy change is that BBDB has been transfered from CVS to git. So for anonymous checkout, you should now use For those of us who had write access to the old repo, is that still the case ? What are the changes in the latest code? Is the net field still a list of email addresses? Thanks for the rejuvenation cure on BBDB! -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: [BBDB] builtbot
Roland Winkler wink...@gnu.org wrote: Is anybody interested in working on the XEmacs stuff? I do not know about XEmacs. My schedule is pretty hectic these days but I will at some point. I've already downloaded the new BBDB but it doesn't currently compile and there are a bunch of warnings about undefined functions (that will turn into run-time errors eventually). The Makefile will also need some tweaking (previously done at ./configure time, which I believe I wrote years ago, but configure seems to be gone). -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: BBDB release? [was: Fixing completion cycles]
Roland Winkler wink...@gnu.org wrote: Comments from other people on this list are welcome! I would consider switching (and hence start working on XEmacs portability) only if I had a clear view (read: printed somewhere ;-) of what has changed and what needs to be done on the DB structure in order to get a smooth transition. -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: BBDB release? [was: Fixing completion cycles]
Sam Steingold s...@gnu.org wrote: please take a look at http://www.emacswiki.org/emacs/UpgradeBBDB Thanks for the pointer. That looks like function/variable name changes only though. Are there other things that I need to know, like DB structure change (automatic upgrade ?) etc. ? -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
