bbdb-info

Re: BBDB and twinkle

[Frank D. <fr...@do...>]

I have used your example as a template and made a function for dialing
with twinkle which seems to work. Here it is for anyone who runs into
the same problem:

(defun twinkle-dial (phone-number)
  "Call the phone number with twinkle"
  (start-process
   "twinkle-telephony-call"
   (get-buffer-create "*twinkle-dial*")
   "twinkle" "--immediate" "--hide" "--call"
   phone-number))

So many thanks for your help.
Frank


Bernd Wachter <ber...@wa...> writes:

> Frank Dordowsky <fr...@do...> writes:
>
>> I understand that it is possible to dial a number noted in BBDB by
>> pressing M-d. I use twinkle as a SIP phone and I have set the variable
>> bbdb-modem-dial to the string "twinkle --immediate --hide --call" which
>> works when using it in a console. However, when pressing M-d, BBDB opens
>> a web page in a browser. Do I need setting some other variables? Is
>> there a description or example on how to use BBDB with a softphone?
>
> Set bbdb-dial-function. I have a configuration which dials through
> asterisk from my desktop, or through the Android API when running on my
> phone:
>
> (if running-in-termux
>     (setq bbdb-dial-function 'aard-dial-termux-telephony)
>   (setq bbdb-dial-function 'aard-dial-ami))
>
> (defun aard-dial-termux-telephony (phone-number)
>   "Dial a phone number through termux-telephony-call script"
>   (start-process
>    "termux-telephony-call"
>    (get-buffer-create "*termux-dial*")
>    "termux-telephony-call"
>    phone-number))
>
> (defun aard-dial-ami (phone-number)
>   "Dial a phone number through AMI script"
>   (let ((records (bbdb-search (bbdb-records) nil nil nil nil phone-number)))
>     (start-process
>      "ami-dial"
>      (get-buffer-create "*ami-dial*")
>      "ami-dial"
>      (concat "--number=" phone-number)
>      (if records
>          (concat "--message=To: " (bbdb-record-name (car records)))
>        ("--message=Name not found"))
>      )))
>
>
> Bernd


-- 
Frank Dordowsky
Säntisstr. 37
81825 München

Re: BBDB and twinkle

[Bob N. <bob...@bo...>]

I do something like this which uses Google Voice. It's pretty
easy on Termux with Android. It's a bit more complex with
Linux on a laptop or desktop but it does work quite nicely,
although it's fragile and subject to Google's change without
notice to their UI.

Some surprising things can be done with BBDB 3.

>> Set bbdb-dial-function. I have a configuration which dials through
>> asterisk from my desktop, or through the Android API when running on my
>> phone:
>>
>> (if running-in-termux
>>     (setq bbdb-dial-function 'aard-dial-termux-telephony)
>>   (setq bbdb-dial-function 'aard-dial-ami))
>>
>> (defun aard-dial-termux-telephony (phone-number)
>>   "Dial a phone number through termux-telephony-call script"
>>   (start-process
>>    "termux-telephony-call"
>>    (get-buffer-create "*termux-dial*")
>>    "termux-telephony-call"
>>    phone-number))
>>
>> (defun aard-dial-ami (phone-number)
>>   "Dial a phone number through AMI script"
>>   (let ((records (bbdb-search (bbdb-records) nil nil nil nil phone-number)))
>>     (start-process
>>      "ami-dial"
>>      (get-buffer-create "*ami-dial*")
>>      "ami-dial"
>>      (concat "--number=" phone-number)
>>      (if records
>>          (concat "--message=To: " (bbdb-record-name (car records)))
>>        ("--message=Name not found"))
>>      )))
>>
>>
>> Bernd
-- 
Bob Newell
Honolulu, Hawai`i

- Via GNU/Linux/Emacs/Gnus/BBDB

Re: BBDB and twinkle

[Frank D. <fr...@do...>]

Thanks for info, I have installed version 3.2. I'll try the bbdb-dial-function.
Frank

"Roland Winkler" <wi...@gn...> writes:

> On Sun, Oct 24 2021, Frank Dordowsky wrote:
>> I understand that it is possible to dial a number noted in BBDB by
>> pressing M-d. I use twinkle as a SIP phone and I have set the variable
>> bbdb-modem-dial to the string "twinkle --immediate --hide --call" which
>> works when using it in a console. However, when pressing M-d, BBDB opens
>> a web page in a browser. Do I need setting some other variables? Is
>> there a description or example on how to use BBDB with a softphone?
>
> Which version of BBDB are you using?  There was a variable
> bbdb-modem-dial in BBDB 2, but not anymore in BBDB 3.  In BBDB 3, by
> default (see the user variable bbdb-dial-function bound to
> bbdb--dial-default), BBDB will pass the string "tel:<phone number>" to
> browse-url.  The latter function is the emacs standard interface for all
> kinds of url.  You can set up the user variable browse-url-browser-function
> to handle a url "tel:<phone number>" by passing it to something like
> twinkle (which I do not know at all).  This is essentially outside BBDB,
> but the browse-url interface can be used by other emacs packages, too.
>
> Roland


-- 
Frank Dordowsky
Säntisstr. 37
81825 München

Re: BBDB and twinkle

[Frank D. <fr...@do...>]

Thanks for the example. I will try to adapt it to twinkle.
Frank

Bernd Wachter <ber...@wa...> writes:

> Frank Dordowsky <fr...@do...> writes:
>
>> I understand that it is possible to dial a number noted in BBDB by
>> pressing M-d. I use twinkle as a SIP phone and I have set the variable
>> bbdb-modem-dial to the string "twinkle --immediate --hide --call" which
>> works when using it in a console. However, when pressing M-d, BBDB opens
>> a web page in a browser. Do I need setting some other variables? Is
>> there a description or example on how to use BBDB with a softphone?
>
> Set bbdb-dial-function. I have a configuration which dials through
> asterisk from my desktop, or through the Android API when running on my
> phone:
>
> (if running-in-termux
>     (setq bbdb-dial-function 'aard-dial-termux-telephony)
>   (setq bbdb-dial-function 'aard-dial-ami))
>
> (defun aard-dial-termux-telephony (phone-number)
>   "Dial a phone number through termux-telephony-call script"
>   (start-process
>    "termux-telephony-call"
>    (get-buffer-create "*termux-dial*")
>    "termux-telephony-call"
>    phone-number))
>
> (defun aard-dial-ami (phone-number)
>   "Dial a phone number through AMI script"
>   (let ((records (bbdb-search (bbdb-records) nil nil nil nil phone-number)))
>     (start-process
>      "ami-dial"
>      (get-buffer-create "*ami-dial*")
>      "ami-dial"
>      (concat "--number=" phone-number)
>      (if records
>          (concat "--message=To: " (bbdb-record-name (car records)))
>        ("--message=Name not found"))
>      )))
>
>
> Bernd


-- 
Frank Dordowsky
Säntisstr. 37
81825 München

Re: BBDB and twinkle

[Roland W. <wi...@gn...>]

On Sun, Oct 24 2021, Frank Dordowsky wrote:
> I understand that it is possible to dial a number noted in BBDB by
> pressing M-d. I use twinkle as a SIP phone and I have set the variable
> bbdb-modem-dial to the string "twinkle --immediate --hide --call" which
> works when using it in a console. However, when pressing M-d, BBDB opens
> a web page in a browser. Do I need setting some other variables? Is
> there a description or example on how to use BBDB with a softphone?

Which version of BBDB are you using?  There was a variable
bbdb-modem-dial in BBDB 2, but not anymore in BBDB 3.  In BBDB 3, by
default (see the user variable bbdb-dial-function bound to
bbdb--dial-default), BBDB will pass the string "tel:<phone number>" to
browse-url.  The latter function is the emacs standard interface for all
kinds of url.  You can set up the user variable browse-url-browser-function
to handle a url "tel:<phone number>" by passing it to something like
twinkle (which I do not know at all).  This is essentially outside BBDB,
but the browse-url interface can be used by other emacs packages, too.

Roland

BBDB and twinkle

[Frank D. <fr...@do...>]

I understand that it is possible to dial a number noted in BBDB by
pressing M-d. I use twinkle as a SIP phone and I have set the variable
bbdb-modem-dial to the string "twinkle --immediate --hide --call" which
works when using it in a console. However, when pressing M-d, BBDB opens
a web page in a browser. Do I need setting some other variables? Is
there a description or example on how to use BBDB with a softphone?

Thanks in advance
Frank


-- 
Frank Dordowsky
Säntisstr. 37
81825 München

Re: help for newbie

[Michael <bs...@ac...>]

* Roland Winkler <wi...@gn...> [2018-09-04 16:04:40 -0500]:

> On Tue Sep 4 2018 Michael wrote:
> > I am curious if there is a list or irc channel for a total newbie.
> 
> I suggest to post your questions to hel...@gn...
> see also the help-gnu-emacs archieve at
> https://lists.gnu.org/archive/html/help-gnu-emacs/
> 
> This list is more suited for getting started.
> 
> Roland
>
Thank you Greg and Roland. I'll look into both suggestions.

Mike 

Re: help for newbie

[Roland W. <wi...@gn...>]

On Tue Sep 4 2018 Michael wrote:
> I am curious if there is a list or irc channel for a total newbie.

I suggest to post your questions to hel...@gn...
see also the help-gnu-emacs archieve at
https://lists.gnu.org/archive/html/help-gnu-emacs/

This list is more suited for getting started.

Roland

help for newbie

[Michael <bs...@ac...>]

Hello
I am curious if there is a list or irc channel for a total newbie.
I don't know the first thing about lisp and what I read in comments here.
I have used mutt and abook for many years, but like the way gnus looks, so may try that or vm. I know nothing about rmail or wanderlust.
So, is there somewhere I can ask beginner questions without being a bother on this list? Also, I read the README, and of course, it's over my head :)
I'm sure it's great for those that understand lisp.

Maybe I've bitten off more than I can chew. I just want to try and use bbdb with email.

Thanks for any help!
Mike

oh, btw, I use OpenBSD and FreeBSD if that makes any difference. If there is a linux distro that helps set up the programs, I'm willing to try till I learn how to manage bbdb on my own with these systems.
I do have bbdb installed via elpa.

bbdb3 - bbdb-refile-record?

[Andreas H. <ah...@it...>]

Hi!

I recently switched from bbdb2 to bbdb3 (bbdb-20171017.817 from melpa)
and am quite impressed how easy the upgrade was.

Since I used to autocreate entries, a lot of duplicate entries have been
found. While cleaning up I noticed bbdb-refile-record[1] is not available
any more - I also found no obvious replacement in the sources.

Best regards,
Andreas

[1] <http://bbdb.sourceforge.net/bbdb.html#SEC33> --> "r"
-- 
Andreas Hirczy <ah...@it...>                  https://itp.tugraz.at/~ahi/
Graz University of Technology                       phone: +43/316/873-   8190
Institute of Theoretical and Computational Physics    fax: +43/316/873-10 8190
Petersgasse 16, A-8010 Graz                        mobile: +43/664/859 23 57

~/.bbdb with multiple emacs instnaces

[Ernesto A. <erj...@gm...>]

Hi,

Because of gnus limitations, I use one emacs intance per IMAP/SMTP server,
for example for work and personal email.

It seems that bbdb leaves the ~/.bbdb file open, causing problems with
locks. Sometimes if I send email from instance A when I've previously
sent from instance B, I must steal the ~/.bbdb file in A.

Is there a bbdb option to help with this problem?

Thanks,

Ernesto

Re: new mailing list bbdb-user@nongnu.org

[Roland W. <wi...@gn...>]

On Fri Aug 11 2017 Roland Winkler wrote:
> So I tried to subscribe the new list to the old list as if it was
> a regular user.  But the confirmation email from the sourceforge
> mail server has not appeared in the inbox for the new list.  It
> seems it was caught by a spam filter of the gnu mailserver.

With some delay I finally received a confirmation email from the
sourceforege mailserver.  So if things work the way they should,
this email sent to the old list will be cross-posted on the new
list, too.  Yet I suggest that everyone knowing about the new list
should only use the new list, and I'll try to make sure that any
discussions that are still started on the old list will continue on
the new list.

Re: new mailing list bbdb-user@nongnu.org

[Roland W. <wi...@gn...>]

On Fri Aug 11 2017 Piet van Oostrum wrote:
> So what are you going to do with the old list? Should messages on
> that list be replied to on that list? Or should replies go to the
> new list? Or to both?
> 
> Or will messages to the old list be redirected to the new one?
> A bit of policy would be nice to have.

You are raising good questions.  I am not an adminstrator for the
old list, but I am just a regular subscriber of this list like
anybody else.  (This is certainly one of the problems with the old
list).  So I tried to subscribe the new list to the old list as if
it was a regular user.  But the confirmation email from the
sourceforge mail server has not appeared in the inbox for the new
list.  It seems it was caught by a spam filter of the gnu
mailserver.  -- These systems are too smart for me!  Does anybody
who is reading this know how this can be solved?

Thanks!

Re: new mailing list bbdb-user@nongnu.org

[Piet v. O. <pi...@va...>]

"Roland Winkler" <wi...@gn...> writes:

> I want to announce the new mailing list bbd...@no...
> for discussion and development of BBDB for GNU Emacs.
>
> Recently the old list bbd...@li... has been
> rather quiet.  This may be due to the fact that lately sourceforge
> required that all subscribers of this list renewed their
> subscription and it seems that many of them dropped out.  Instead of
> trying to keep the old list alive, I've created the new list which
> matches also where the development of BBDB v3 takes place.

So what are you going to do with the old list? Should messages on that list be replied to on that list? Or should replies go to the new list? Or to both?

Or will messages to the old list be redirected to the new one?
A bit of policy would be nice to have.
-- 
Piet van Oostrum <pi...@va...>
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]

new mailing list bbdb-user@nongnu.org

[Roland W. <wi...@gn...>]

I want to announce the new mailing list bbd...@no...
for discussion and development of BBDB for GNU Emacs.

Recently the old list bbd...@li... has been
rather quiet.  This may be due to the fact that lately sourceforge
required that all subscribers of this list renewed their
subscription and it seems that many of them dropped out.  Instead of
trying to keep the old list alive, I've created the new list which
matches also where the development of BBDB v3 takes place.

BBDB is available at
http://savannah.nongnu.org/projects/bbdb/
To check it out, use
git clone git://git.savannah.nongnu.org/bbdb.git

bbdb-layout-prefix

[Roland W. <wi...@gn...>]

A bunch of BBDB commands have an optional arg LAYOUT that controls
which layout is used to display BBDB records (multi-line or one-line).
Interactively the value of LAYOUT is supposed to be set by the
function bbdb-layout-prefix.  But this code is broken for many of
these commands, and it must have been broken for quite some time
without anybody being concerned about this.  (To identify these
commands, search for bbdb-layout-prefix.  This fails if
bbdb-layout-prefix is called after something like read-string in the
interactive spec.)

While it's pretty straightforward to fix this, I noticed all this
when I thought that it would be nice for one of these commands to
use the prefix for something else.  Generally, I find the Emacs
prefix arg too precious to waste it with something useless.  So if
nobody noticed the broken LAYOUT prefix, maybe it is a good
opportunity to remove the prefix binding for the LAYOUT arg -- even
if right now I cannot propose a better use of the prefix for most of
these command.  But if next year someone comes up with a better idea
for how to use the prefix, it would still be available without
breaking backward compatibility.  (All these commands can certainly
keep the optional arg LAYOUT.  But if this arg is not bound to the
prefix, you would need a wrapper or advice to give it the value of
your choice.)

Any thoughts or comments?

Is anyone using the LAYOUT arg with one of the commands where the
code does work?

[BBDB] new branch uuid

[Roland W. <wi...@gn...>]

I've pushed a branch `uuid' to savannah that adds a new field uuid
to all bbdb records.  Also, one cannot delete anymore the
creation-date and timestamp fields.

Please check it out and let me know any comments you might have
before I'll merge this branch into master.  But watch out: The
format of the database has changed.  So first make a copy of your
database.

The basic advantage of using uuids lies in the fact that they allow
better "tracking" of records, say, when importing and exporting
records.  Right now, if you try to add a record to BBDB that has the
same uuid as an existing record, this will merge the new record with
the existing one by calling bbdb-merge-records.  You can also
customize this action via bbdb-merge-records-function.  In the long
run, it will probably be good to provide a more flexible built-in
mechanism for handling such cases instead of letting users hack
their own ones.

If you already have uuid xfields for your records, these can be
recycled.  The variable bbdb-migrate-uuid-xfield tells bbdb-migrate
the name of the xfield holding the uuid.  I bumped the file format
from 7 to 9 because I believe some people used their own format 8
for a uuid xfield.



2017-08-09  Roland Winkler  <wi...@gn...>
	* lisp/bbdb-migrate.el (bbdb-migrate-uuid-xfield): New variable.

2017-08-09  Roland Winkler  <wi...@gn...>
	New field uuid.  Make creation-date and timestamp immutable.
	* lisp/bbdb.el (bbdb-create-hook, bbdb-change-hook): Use
	defcustom.
	(bbdb-merge-records-function): New variable.
	(bbdb-layout-alist): Omit uuid.
	(bbdb-xfields-sort-order, bbdb-merge-xfield-function-alist):
	Ignore creation-date and timestamp.
	(bbdb-file-format): Bump to 9.
	(bbdb-record-type): Include uuid, creation-date and timestamp.
	(bbdb-uuid-table): New variable.
	(bbdb-timestamp, bbdb-creation-date): Declare obsolete.
	(bbdb-uuid): New function.
	(bbdb-hash-record): Hash uuid.
	(bbdb-record-field, bbdb-record-set-field, bbdb-buffer)
	(bbdb-display-record-one-line, bbdb-display-record-multi-line)
	(bbdb-display-record): Handle uuid, creation-date and timestamp.
	(bbdb-change-record): Use uuid.
	* lisp/bbdb-com.el (bbdb-search): Use keywords for args.  Handle
	uuid, creation-date and timestamp.  New option :bool.
	(bbdb, bbdb-search-name, bbdb-search-organization)
	(bbdb-search-address, bbdb-search-mail, bbdb-search-phone)
	(bbdb-search-xfields, bbdb-mail-aliases, bbdb-get-mail-aliases):
	Change accordingly.
	(bbdb-compare-records): Compare any fields.
	(bbdb-timestamp-older, bbdb-timestamp-newer, bbdb-creation-older)
	(bbdb-creation-newer): Fix interactive spec.
	(bbdb-creation-no-change): Use bbdb-record-timestamp.
	(bbdb-read-record): Use bbdb-empty-record.
	(bbdb-create): Fix call of bbdb-change-record.
	(bbdb-split-maybe): New function.
	(bbdb-create-internal): Use keywords for args.
	(bbdb-edit-field, bbdb-edit-foo, bbdb-merge-records): Handle uuid,
	creation-date and timestamp.
	(bbdb-delete-records): Ignore records not known to BBDB.
	* lisp/bbdb-snarf.el (bbdb-snarf)
	* lisp/bbdb-mua.el (bbdb-annotate-message): Fix call of
	bbdb-change-record.
	* lisp/bbdb-migrate.el (bbdb-migration-features): Remove.
	(bbdb-peel-the-onion): Merge with bbdb-migrate.
	(bbdb-migrate): Handle format 9.
	(bbdb-migrate-alist): Rename from bbdb-migration-spec.
	(bbdb-migrate-record-lambda): Merge with bbdb-migrate-lambda.
	(bbdb-migrate-lambda): Rename from bbdb-migrate-versions-lambda.
	(bbdb-migrate-postcode-to-string): Rename from
	bbdb-migrate-postcodes-to-strings.  Simplify.
	(bbdb-migrate-dates): Rename from bbdb-migrate-change-dates.
	Simplify.
	(bbdb-migrate-add-country): Rename from
	bbdb-migrate-add-country-field.
	(bbdb-undocumented-variables): Handle byte-obsolete-variable.

[BBDB] branch latex merged into master

[Roland W. <wi...@gn...>]

I have merged the branch latex into master.  This doesn't mean the
features for feeding BBDB into LaTeX are now frozen in stone.  But
the main ideas should be in place.  Suggestions are welcome, as always.

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

[Roland W. <wi...@gn...>]

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 to provide a let binding where
the var list is determined at run time.  This is achieved by
`eval'ing the let form.  Yet to deal with lexical bindings, `eval'
needs to know the lexical environment (as a 2nd arg for eval) that
cl-progv does not provide.

Barak's patch has done exactly that and I also used the same
approach in bbdb-tex.el.

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

[Vincent B. <vin...@ho...>]

Hello,


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).


  Vincent.


________________________________
De : Vincent Belaïche <vin...@ho...>
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 would be as in the attached patch bug-1.diff.


   V.

________________________________
De : Vincent Belaïche <vin...@ho...>
Envoyé : jeudi 29 juin 2017 13:24:53
À : Roland Winkler; BBDB info list
Objet : bbdb-print.el lexical binding breaks bbdb-print-record

Hello Roland,

With lexical binding bbdb-print-record makes a void variable error on address variable.

Attached is a fix. I use a lambda expression to make the binding dynmical so that bbdb-print-require can be evalled in the correct context. An alternative fix would have been to use :

(cl-progv '(first-letter name organization mail phone address xfields) (list first-letter name organization mail phone address xfields)).

Well, to avoid any duplication in this case, it would be better to use some macro like this:

(defmacro bbdb-do-cl-progv (&rest l)
   `(cl-progv (quote ,l) (list ,@l)))

and then in bdbd-print-record:

(bbdb-do-cl-progv first-letter name organization mail phone address xfields)(list first-letter name organization mail phone address xfields)

Anyway, I prefer the lambda trick, I don't like cl-progv and eval. Probably lambdas are more portable to old Emacs versions.

  Vincent.

[BBDB] New branch latex (was: bbdb-print.el lexical binding breaks bbdb-print-record)

[Roland W. <wi...@gn...>]

> With lexical binding bbdb-print-record makes a void variable error
> on address variable.

As I told you before, I really didn't like the old / outdated code
used in bbdb-print.el, and I didn't want to invest in it anymore.

So I created a branch latex in the BBDB repository on savannah that
is really a re-write of bbdb-print.el, based on the idea that
nowadays LaTeX is the better way to go than plain tex.

To avoid confusion, I renamed the file to bbdb-tex.el.

I put all this into a branch because I am open for comments and
suggestions.  Also, there might be bugs I have overlooked.

The basic idea underlying bbdb-tex.el is described in the commentary
section of this file:

;; Generally, lisp customizations in bbdb-tex are intended to provide control
;; of what appears in the TeX listing.  But there are no lisp customization
;; options to control the actual layout that should be handled by LaTeX.
;; BBDB is shipped with one basic LaTeX style file bbdb.sty to handle
;; the TeX macros listed above.  You should customize this LaTeX style file
;; to match your taste and / or your needs.  Note also that `bbdb-tex-alist'
;; allows you to specify an arbitrary number of rules that may use different
;; style files for the above TeX macros.

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

[Vincent B. <vin...@ho...>]

Hello Bob,

I did not have any problem with the Bbdb Print Tex Path. Certainly because on my machine it was already customized with the usual customization interface (M-x cutomize-variable...) to an existing path.

Problably, if not, bbdb-print.el should be robust to that and test if the directory exists to provide a suitable error message.

  V.

________________________________
De : Bob Newell <bob...@bo...>
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. 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 problem with the
tex-path being undefined:

(setq bbdb-print-tex-path '("/home/bnewell/.emacs.d/elpa/"))

and, in addition, the melpa package didn't seem to have the .tex files
so I had to fetch the git distribution and copy them over.

--
Bob Newell
Honolulu, Hawai`i

Sent via Linux Mint 17.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
bbd...@li...
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

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

[Bob N. <bob...@bo...>]

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 problem with the
tex-path being undefined:

(setq bbdb-print-tex-path '("/home/bnewell/.emacs.d/elpa/"))

and, in addition, the melpa package didn't seem to have the .tex files
so I had to fetch the git distribution and copy them over.

-- 
Bob Newell
Honolulu, Hawai`i

Sent via Linux Mint 17.

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

[Vincent B. <vin...@ho...>]

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...@pe...>
Envoyé : jeudi 29 juin 2017 15:16
À : Roland Winkler
Cc : Vincent Belaïche; BBDB info list
Objet : Re: bbdb-print.el lexical binding breaks bbdb-print-record
    
I've also made a fix for this, see github.com/barak/bbdb3 commit
7469e6e which is the tip of branch suggest-v3.x

It uses a slightly different mechanism to accomplish similar ends.
    

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

[Vincent B. <vin...@ho...>]

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 <vin...@ho...>
Envoyé : jeudi 29 juin 2017 13:24:53
À : Roland Winkler; BBDB info list
Objet : bbdb-print.el lexical binding breaks bbdb-print-record

Hello Roland,

With lexical binding bbdb-print-record makes a void variable error on address variable.

Attached is a fix. I use a lambda expression to make the binding dynmical so that bbdb-print-require can be evalled in the correct context. An alternative fix would have been to use :

(cl-progv '(first-letter name organization mail phone address xfields) (list first-letter name organization mail phone address xfields)).

Well, to avoid any duplication in this case, it would be better to use some macro like this:

(defmacro bbdb-do-cl-progv (&rest l)
   `(cl-progv (quote ,l) (list ,@l)))

and then in bdbd-print-record:

(bbdb-do-cl-progv first-letter name organization mail phone address xfields)(list first-letter name organization mail phone address xfields)

Anyway, I prefer the lambda trick, I don't like cl-progv and eval. Probably lambdas are more portable to old Emacs versions.

  Vincent.