RE: bbdb-print.el lexical binding breaks bbdb-print-record

2017-07-12 Thread Roland Winkler
On Tue Jul 11 2017 Vincent Belaïche wrote: > Just to mention that the code based on cl-progv which I have > supplied does not work. I don't have any time to investigate why, > so if you want to take my patch, please take the 1st one (that > based on lambda). I believe the purpose of cl-progv is

RE: bbdb-print.el lexical binding breaks bbdb-print-record

2017-07-11 Thread Vincent Belaïche
ent@hotmail.fr> Envoyé : jeudi 29 juin 2017 15:05 À : Roland Winkler; BBDB info list Objet : RE: bbdb-print.el lexical binding breaks bbdb-print-record Ooops... there was some mistake in the code based on cl-progv which I supplied. Just to be 100% clear about this alternative solution, it

RE: bbdb-print.el lexical binding breaks bbdb-print-record

2017-06-30 Thread Vincent Belaïche
if the directory exists to provide a suitable error message. V. De : Bob Newell <bobnew...@bobnewell.net> Envoyé : vendredi 30 juin 2017 06:51:40 À : BBDB info list Objet : Re: bbdb-print.el lexical binding breaks bbdb-print-record I also ran into this a while ago.

Re: bbdb-print.el lexical binding breaks bbdb-print-record

2017-06-29 Thread Bob Newell
I also ran into this a while ago. I did a kludge fix in my initialization: (setq bbdb-print-require t) but of course this makes even blank records print, so it is not exactly recommended for anything other than a quick and sloppy workaround. By the way I also had to do this as I was having a

RE: bbdb-print.el lexical binding breaks bbdb-print-record

2017-06-29 Thread Vincent Belaïche
I can't find this suggest-v3.x branch which you refer to here: https://github.com/barak/BBDB/branches/all V. De : Barak A. Pearlmutter <ba...@pearlmutter.net> Envoyé : jeudi 29 juin 2017 15:16 À : Roland Winkler Cc : Vincent Belaïche; BBDB info list Objet : Re: bbdb-print.el lexical b

RE: bbdb-print.el lexical binding breaks bbdb-print-record

2017-06-29 Thread Vincent Belaïche
Ooops... there was some mistake in the code based on cl-progv which I supplied. Just to be 100% clear about this alternative solution, it would be as in the attached patch bug-1.diff. V. De : Vincent Belaïche Envoyé : jeudi 29 juin