Ken Miller | 3 Jun 2004 06:21
Picon
Favicon

problem with bbdb as xemacs 21.4.14 pkg 1.23 in i386 mandrake 9.2

I have been using vm with bbdb under xemacs for quite a while.  I've
just been switched from mandrake 8.2 to mandrake 9.2.  It has xemacs
21.4 (patch 14), and vm 7.14.  I'm not certain of the bbdb version but
apparently it is xemacs pkg 1.23, because the Changelog in
/usr/share/xemacs/xemacs-packages/lisp/bbdb starts with

> 2003-05-18  Norbert Koch  <viteno <at> xemacs.org>
> 
>         * Makefile (VERSION): XEmacs package 1.23 released.
> 
> 2003-05-14  Vin Shelton  <acs <at> xemacs.org>
> 
>         * Makefile (REQUIRES): Added os-utils to find jka-compr,
> necessary
>         to compile mhe.
> 
> 2003-05-14  Norbert Koch  <viteno <at> xemacs.org>
> 
>         * Makefile (VERSION): XEmacs package 1.22 released.

When I run xemacs in a terminal window -- 'xemacs -nw' -- then vm/bbdb
work fine.  But when I run xemacs as an X application -- 'xemacs &' --
and then start vm, I get an error with the following at the top of the
debug output:

Signaling: (invalid-function (macro . #<compiled-function nil "...(2)"
[(mapcar-extents (quote identity))] 1>))
  bbdb-list-extents()
  bbdb-fontify-buffer()
  run-hooks(bbdb-fontify-buffer)
(Continue reading)

Adrian Aichner | 5 Jun 2004 00:09
X-Face
Picon
Favicon

Re: problem with bbdb as xemacs 21.4.14 pkg 1.23 in i386 mandrake 9.2

Ken Miller <ken <at> phy.ucsf.edu> writes:

> I have been using vm with bbdb under xemacs for quite a while.  I've
> just been switched from mandrake 8.2 to mandrake 9.2.  It has xemacs
> 21.4 (patch 14), and vm 7.14.  I'm not certain of the bbdb version but
> apparently it is xemacs pkg 1.23, because the Changelog in
> /usr/share/xemacs/xemacs-packages/lisp/bbdb starts with
>
>> 2003-05-18  Norbert Koch  <viteno <at> xemacs.org>
>> 
>>         * Makefile (VERSION): XEmacs package 1.23 released.
>> 
>> 2003-05-14  Vin Shelton  <acs <at> xemacs.org>
>> 
>>         * Makefile (REQUIRES): Added os-utils to find jka-compr,
>> necessary
>>         to compile mhe.
>> 
>> 2003-05-14  Norbert Koch  <viteno <at> xemacs.org>
>> 
>>         * Makefile (VERSION): XEmacs package 1.22 released.
>
> When I run xemacs in a terminal window -- 'xemacs -nw' -- then vm/bbdb
> work fine.  But when I run xemacs as an X application -- 'xemacs &' --
> and then start vm, I get an error with the following at the top of the
> debug output:
>
> Signaling: (invalid-function (macro . #<compiled-function nil "...(2)"
> [(mapcar-extents (quote identity))] 1>))
>   bbdb-list-extents()
(Continue reading)

Stephen J. Turnbull | 4 Jun 2004 14:03
Picon
Favicon

Re: problem with bbdb as xemacs 21.4.14 pkg 1.23 in i386 mandrake 9.2

>>>>> "Ken" == Ken Miller <ken <at> phy.ucsf.edu> writes:

    Ken> Signaling: (invalid-function (macro . #<compiled-function nil
    Ken> "...(2)"

    Ken> I am guessing this means there is something wrong with the
    Ken> compilation of bbdb-list-extents()? This appears to live in
    Ken> bbdb-gui.elc.

That's a good guess.

Somebody has to recompile bbdb, but it need not be you (or your
sysadmin).  You can update packages from the menu Tools->Packages.
The XEmacs package is at 1.24, and it's somewhat possible that
Mandrake built their own in some erroneous way.  There's a good chance
that you can fix it that way.  If our distribution is buggy, then
(depending on his convenience) the Package Release Manager usually
gets a new downloadable binary package released for this kind of thing
in less than a week (that's not a promise, but he does hustle).

    Ken> nd does anyone know if this is a known problem and/or who if
    Ken> anyone should be alerted to fix it?

"viteno" (Norbert Koch) is a good start, but we'd prefer a CC to the
xemacs-beta <at> xemacs.org list on future correspondence.  In fact, this is
probably an XEmacs bug, as our package system is supposed to ensure
that all relevant macros get defined before compilation.

--

-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
(Continue reading)

Ken Miller | 5 Jun 2004 00:50
Picon
Favicon

Re: problem with bbdb as xemacs 21.4.14 pkg 1.23 in i386 mandrake 9.2

With respect to my previous post about a problem with starting up vm
with bbdb under xemacs since we just switched to mandrake 9.2:

Another hacker here tracked down the problem.  The problem was that
/etc/emacs/site-start-xemacs.el executed all the startup files in
/etc/emacs/site-start.d, and one of these was a bbdb-init.el file that
started with the line (add-to-list 'load-path
"/usr/share/emacs/site-lisp/bbdb").  So I guess that meant that xemacs
was using the files in the emacs bbdb directory instead of, or in
addition to, the files in the xemacs bbdb directory.  At any rate, he
made a directory /etc/emacs/site-start-xemacs.d containing the same
files as site-start.d except lacking the bbdb-init.el, and modified
site-start-xemacs.el to read from site-start-xemacs.d instead of
site-start.d, and this fixed the problem.

So there was nothing wrong with the xemacs bbdb package, just a
problem with the system setup.

Thanks to all who have responded --

Ken Miller

>>>>> "-" == Stephen J Turnbull <stephen <at> xemacs.org> writes:

>>>>> "Ken" == Ken Miller <ken <at> phy.ucsf.edu> writes:
Ken> Signaling: (invalid-function (macro . #<compiled-function nil
Ken> "...(2)"

Ken> I am guessing this means there is something wrong with the
Ken> compilation of bbdb-list-extents()? This appears to live in
(Continue reading)

Dan Jacobson | 21 Jun 2004 00:30
Favicon
Gravatar

don't crack open window if found nothing

If one does M-x bbdb someone_one_has_never_heard_about, bbdb cracks
open an empty window.  Just say you are sorry in the minibuffer in
this case. No need to go splitting people's windows.

-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
bbdb-info <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Michael Richardson | 22 Jun 2004 03:09
Picon

updating timestamp on every access


Does someone have a simple formula to update the timestamp every time
the record is viewed? I think this may be a FAQ, but I haven't found it
on the web pages.

I want to then do a LRU algorithm to clear out my .bbdb. Anyone I
haven't talked to in a year gets purged. Also, anyone whose
creation-date==timestamp (i.e. I heard from them once) was likely a
spammer that I added inadvertedly.

--
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr <at> xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
Jochen Küpper | 22 Jun 2004 08:25
Face
Picon

Re: updating timestamp on every access

On Mon, 21 Jun 2004 21:09:53 -0400 Michael Richardson wrote:

Michael> Does someone have a simple formula to update the timestamp every time
Michael> the record is viewed? I think this may be a FAQ, but I haven't found it
Michael> on the web pages.

Check out bbdb-expire. 

I attach the file I have around (and use), there might be newer
versions. 

Greetings,
Jochen
--

-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)
Attachment (bbdb-expire.el): application/emacs-lisp, 18 KiB
Doug Alcorn | 23 Jun 2004 21:38
Gravatar

bbdb-dial problems

Using a terminal package (like seyon or minicom) I can connect to a
serial port tied to my cell phone and dial voice calls.  What I'd
like to do is be able to use bbdb-dial to do the same.  I've 

 (setq bbdb-modem-dial "ATD "
       bbdb-modem-device "/dev/rfcomm0")

What I get is that write-region complains: "save-current-buffer: IO
error writing /dev/rfcomm0: Invalid argument".

I'm wondering if anyone else is able to dial in a similar manner or
is write-region just has problems with character device files.
--

-- 
 (__) Doug Alcorn - Unix/Linux/Web Developing
 oo / PGP 02B3 1E26 BCF2 9AAF 93F1  61D7 450C B264 3E63 D543
 |_/  mailto:doug <at> lathi.net http://www.lathi.net

-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
bbdb-info <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Nix | 26 Jun 2004 16:12
Picon

Re: updating timestamp on every access

On Tue, 22 Jun 2004, Jochen Küpper said:
> I attach the file I have around (and use), there might be newer
> versions. 

Nope, that's the newest to date.

A tarball with readmes and such is available from
<http://www.esperi.demon.co.uk/nix/downloads/bbdb-expire-1.6.tar.gz>.

--

-- 
`We in no way believe that this Christ was a space alien.'
                    --- A creationist website goes completely bonkers

-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
bbdb-info <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Nix | 26 Jun 2004 19:50
Picon

Re: updating timestamp on every access

On Mon, 21 Jun 2004, Michael Richardson stipulated:
> I want to then do a LRU algorithm to clear out my .bbdb. Anyone I
> haven't talked to in a year gets purged.

In bbdb-expire, set `bbdb-expire-this-old' to 365 (assuming that
`bbdb-expire-record-old-p' is on the `bbdb-expire-expiry-functions'
list, which is the default).

(bbdb-expire lets you use, well, whatever algorithm you like, or
a combination of them: several are provided, mostly on the LRU
principle, but not all. Sometimes I consider adding LFU, but I've
not done that yet.)

>                                          Also, anyone whose
> creation-date==timestamp (i.e. I heard from them once) was likely a
> spammer that I added inadvertedly.

That's an interesting algorithm. You probably also want the constraint
that the user must be at least, ooh, a week old, otherwise you'd have
trouble adding new records at all.

It's tricky, actually: the default BBDB date format is too
low-resolution to indicate hits reasonably by comparing
creation-dates. The two simplest methods that spring to mind are to
create a hit counter for each record, or to create a tag on record
creation that's updated by the timestamp-access code and erased by it
on the second access.

This is in priciple quite easy to do, but it's thrown off by the way the
bbdb-notice-hook is called. It's called from
(Continue reading)


Gmane