On Wed Apr 2 2014 Aric Gregson wrote:
> I am now getting constant errors like this when using bbdb with gnus and
> trying to auto-complete email addresses. It will successfully complete
> the email address, but each 'tab' brings about a 'beep' noise and this
>
Hello,
I am now getting constant errors like this when using bbdb with gnus and
trying to auto-complete email addresses. It will successfully complete
the email address, but each 'tab' brings about a 'beep' noise and this
error associated with different emails, none of
Aric Gregson writes:
> Yes, I think it is in melpa. I can confirm that tomorrow.
I confirm it's in melpa (it's the version I use).
You can search packages in melpa through their webpage:
http://melpa.milkbox.net/
Alan
-
Yes, I think it is in melpa. I can confirm that tomorrow.
Aric
On February 22, 2014 3:58:06 AM PST, Stephen Leake
wrote:
>Aric Gregson writes:
>
>> I recently altered my emacs configuration to use as many packages
>from
>> ELPA as possible. This resulted in me inadvertantly changing from
>BB
Aric Gregson writes:
> I recently altered my emacs configuration to use as many packages from
> ELPA as possible. This resulted in me inadvertantly changing from BBDB
> 2.36 to v3 something.
Which ELPA repository has bbdb v3? I don't see it in Gnu ELPA
(http://elpa.gnu.org/packages/).
--
--
Roland,
Thanks for the ideas. I think that I have removed all my customizations
in bbdb, but I am not completely certain. Other than anniversary or
birthday there should have been no changes from default. Below is the debug.
Debugger entered--Lisp error: (wrong-type-argument listp [nil nil
Roland,
I sent the backtrace, but now the problem appears to have gone away. I
updated packages just now from ELPA and removed some lines in my init
file that may have been old. Now all my Emacs buffers can load and
search my database without problems. Not sure what was wrong, but am
very happy no
On Tue Feb 18 2014 Aric Gregson wrote:
> However, I cannot even search my database for names without getting the
> following error:
>
> setq: Wrong type argument: listp, #
>
> I see nothing wrong in that row of the file. Looks no different from any
> other entry. Deleting t
my database for names without getting the
following error:
setq: Wrong type argument: listp, #
I see nothing wrong in that row of the file. Looks no different from any
other entry. Deleting the entry on that line does not resolve the
problem.
I am using GNU Emacs 24.3.50.1 (amd64-portbld
Do you have a recipe to reproduce the backtrace below?
On Mon Aug 20 2012 Sam Steingold wrote:
> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
> bbdb-cache-set-fl-name(nil "XXX XXX")
> (let ((fl-name (bbdb-concat (quote name-first-last) first last)) (lf-
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
bbdb-cache-set-fl-name(nil "XXX XXX")
(let ((fl-name (bbdb-concat (quote name-first-last) first last)) (lf-name
(bbdb-concat (quote name-last-first) last first)) (cache (bbdb-record-cache
record))) (bbdb-cache-set-fl-
"Roland Winkler" wrote:
> On Sun Aug 5 2012 Ivan Kanis wrote:
>> I am running emacs bzr. I get the following error from time to
>> time:
>
> I am sorry, this backtrace is rather difficult to read because of
> extra linebreaks added by some mail program. Could
On Sun Aug 5 2012 Ivan Kanis wrote:
> I am running emacs bzr. I get the following error from time to
> time:
Does this solve your problem?
2012-08-05 Roland Winkler
* lisp/bbdb-com.el (bbdb-complete-mail): Do not call quit-window.
Instead, rely on set-window-configuratio
On Sun Aug 5 2012 Stephen Leake wrote:
> This is the error I just reported/fixed, in bbdb-complete-mail; it's
> attempting to kill the completion window after it's already been killed
> by (set-window-configuration bbdb-complete-mail-saved-window-config)
I guess I understand n
"Roland Winkler" writes:
> On Sun Aug 5 2012 Ivan Kanis wrote:
>> I am running emacs bzr. I get the following error from time to
>> time:
>
> I am sorry, this backtrace is rather difficult to read because of
> extra linebreaks added by some mail program. Could
On Sun Aug 5 2012 Ivan Kanis wrote:
> I am running emacs bzr. I get the following error from time to
> time:
I am sorry, this backtrace is rather difficult to read because of
extra linebreaks added by some mail program. Could you please send
it again in some mime encoded / compressed forma
Hi Roland,
I am running emacs bzr. I get the following error from time to time:
Debugger entered--Lisp error: (error "# is not a live window")
signal(error ("# is not a live window"))
error("%s is not a live window" #)
window-normalize-window(# t)
quit-wind
thanks, got it working now (with some fiddling).
looks like `calendar-date-style' is not honored /at all/, if you don't
use -MM-DD format (as stated in the org-bbdb.el header, admittedly),
it just blows up in your face :)
--
Philipp Haselwarter
-
Philipp Haselwarter writes:
> On 2011-05-16 14:08 UT, Matt Lundin wrote:
>
> ML> I have anniversaries working in my own setup, so between the two
> ML> sets of modifications, I should be able to provide a full set of
> ML> fixes.More soon...
>
> Would you mind sharing the working bits of your se
Leo writes:
> On 2011-05-16 00:58 +0800, Matt Lundin wrote:
>> I'd be happy to take this on. AFAICT, there are three functions in
>> org-bbdb that no longer exist in bbdb v3.
>
> If you want you can build on top of my version. The anniversaries is
> still broken since I don't use BBDB-anniv.el. T
"Roland Winkler" writes:
> On Sun May 15 2011 Matt Lundin wrote:
>> I'd be happy to take this on. AFAICT, there are three functions in
>> org-bbdb that no longer exist in bbdb v3.
>>
>> bbdb-name
>> bbdb-company
>> bbdb-record-getprop
>>
>> The first two can easily be defaliased to bbdb-search-
On Sun May 15 2011 Matt Lundin wrote:
> I'd be happy to take this on. AFAICT, there are three functions in
> org-bbdb that no longer exist in bbdb v3.
>
> bbdb-name
> bbdb-company
> bbdb-record-getprop
>
> The first two can easily be defaliased to bbdb-search-organization and
> bbdb-search-name.
"Roland Winkler" writes:
> On Sat May 14 2011 Johnny wrote:
>> I have set up an org-agenda that includes anniversaries in the agenda
>> view from the bbdb database, but this breaks with bbdb 3.02 giving the
>> error 'bad sexp'.
>>
>> I s
On Sun May 15 2011 Roland Winkler wrote:
> It would probably be good if the needs of org-mode could be
> incorporated into the new BBDB before we declare that BBDB v3 has
> reached a beta stage.)
I forgot to say:
It is an item on the todo list for BBDB v3 to provide a more complete
list for how t
On Sat May 14 2011 Johnny wrote:
> I have set up an org-agenda that includes anniversaries in the agenda
> view from the bbdb database, but this breaks with bbdb 3.02 giving the
> error 'bad sexp'.
>
> I set up the agenda file using (from org-mode 6.33x info section 10.3
I just went back to bbdb 3.02 after having lingered with bbdb 2.35 for a
while.
I have set up an org-agenda that includes anniversaries in the agenda
view from the bbdb database, but this breaks with bbdb 3.02 giving the
error 'bad sexp'.
I set up the agenda file using (from org-
On Sat Jan 15 2011 Stefan Monnier wrote:
> > The spirit of the current approach in BBDB for displaying buffers is
> > still the one which I guess was implemented years ago. I guess the
> > above makes more sense. Yet implementing this properly might break
> > again some backward compatibility... (A
> > The spirit of the current approach in BBDB for displaying buffers is
> > still the one which I guess was implemented years ago. I guess the
> > above makes more sense. Yet implementing this properly might break
> > again some backward compatibility... (And it might take a little
> > while since
On Fri Jan 14 2011 Stefan Monnier wrote:
> > No surprise! -- I've never used a minibuffer-only frame. What kind
> > of behavior would you consider appropriate? Use a new frame?
>
> Call display-buffer or pop-to-buffer (this has the major advantage of
> letting the user customize the resulting be
On Sat Jan 15 2011 Stefan Monnier wrote:
> > No surprise! -- I've never used a minibuffer-only frame. What kind
> > of behavior would you consider appropriate? Use a new frame?
>
> Call display-buffer or pop-to-buffer (this has the major advantage of
> letting the user customize the resulting be
On Fri Jan 14 2011 Stefan Monnier wrote:
> When I invoke M-x bbdb from my minibuffer-only frame, BBDB burps with
> the above error. The Elisp backtrace is:
>
> split-window(# 0)
> bbdb-pop-up-buffer(t nil)
> bbdb-display-records-internal((...) multi-line nil t nil)
>
When I invoke M-x bbdb from my minibuffer-only frame, BBDB burps with
the above error. The Elisp backtrace is:
split-window(# 0)
bbdb-pop-up-buffer(t nil)
bbdb-display-records-internal((...) multi-line nil t nil)
bbdb-display-records((...) multi-line nil t)
bbdb("" multi-li
I have been using gnus for almost a year and recently
installed bbdb. I
can't describe how happy I am with it. There is, however, an
annoying
error that shows up in the following two cases (from what I
can tell,
it is apparently the same error).
1. When, while composing a message, I com
On viewing this post in
uk.net.news.config, I get the following error
bbdb-get-addresses: Wrong type argument: listp, "(Unparsable address -- Strange
character \\. found: \"._^_mother \")"
The from address is actually
.mother
Emacs : GNU Emacs 23.0.90.1 (i6
s, bbdb will fail with the "Args out of range: 0, 31" error.
>> If I close both and restart Emacs and then Gnus, everything works. If I
>> then close Emacs and Gnus and restart both, bbdb will again fail ... and
>> so forth.
> If a precise recipe to reproduce the bug
ial, I've discovered that bbdb works every
> other time I start Emacs and Gnus. That is, if I start Emacs and then
> start Gnus, bbdb will fail with the "Args out of range: 0, 31" error.
> If I close both and restart Emacs and then Gnus, everything works. If I
> then cl
hat bbdb works every
other time I start Emacs and Gnus. That is, if I start Emacs and then
start Gnus, bbdb will fail with the "Args out of range: 0, 31" error.
If I close both and restart Emacs and then Gnus, everything works. If I
then close Emacs and Gnus and restart both, bbdb will aga
Bill Harris <[EMAIL PROTECTED]> writes:
> I don't yet know what causes it to work occasionally and fail most of
> the time. My perception is that it is a random event that changes with
> each new restart of Gnus or perhaps with each new restart of Emacs and
> then Gnus.
FWIW, I figured out that
at's
associated with a BBDB entry.
I don't yet know what causes it to work occasionally and fail most of
the time. My perception is that it is a random event that changes with
each new restart of Gnus or perhaps with each new restart of Emacs and
then Gnus.
Here's an error trace for
There appears to be a minor bug in bbdb-rfc822-addresses in the handling
of bad addresses according to RFC 822. I encountered a
wrong-type-argument error while using Gnus with BBDB support.[1] The
error occurred in rfc822-bad-address. I submitted a patch for this
function which eliminated that
On Tuesday, September 26, 2006 at 11:04:29, CHENG Gao wrote:
> Line 91:
> ,
> | (replace-string "\r\n" "\n")
> `
>
> byte-compiling error:
> ,
> | In bbdb-whois-sentinel:
> | bbdb-whois.el:94:45:Warning: `replace-string' used from Li
Line 91:
,
| (replace-string "\r\n" "\n")
`----
byte-compiling error:
,
| In bbdb-whois-sentinel:
| bbdb-whois.el:94:45:Warning: `replace-string' used from Lisp code
| That command is designed for interactive use only
`
should it be
bbdb.el, line 1542:
,
| (insert (replace-in-string notes "[\r\n\t ]+" " "))
`
should this be:
,
| (insert (bbdb-replace-in-string notes "[\r\n\t ]+" " "))
`
?
replace-in-string is xemacs-specific function.
--
I'm completing a mail address with TAB when suddenly,
Debugger entered--Lisp error: (error "record doubleplus unpresent!")
But it nor the manual doesn't say what to do about it.
All I know is I'm now doubleplus-positive. A doubleplus carrier in t
On August 3, [EMAIL PROTECTED] said:
> forward in the file for "(name ." to find the errant record. If you
> fix this, M-x bbdb should work fine. Obviously this is something I
> should trap in the code, of course.
further investigation reveals that the current code certainly tries to
stop you from
ling foul of this chunk of
code:
(defun bbdb-record-getprop (record property)
(if (memq property '(name address addresses phone phones net aka AKA))
(error "bbdb: cannot access the %s field this way" property))
That suggests you're trying to access a field called name usi
n example. The only way I have found to
avoid the error is to type a single "." at the prompt.
(bbdb-version)
"BBDB version 2.35 ($Date: 2003/08/05 12:29:30 $)"
(emacs-version)
"GNU Emacs 21.3.50.2 (i686-pc-linux-gnu, GTK+ Version 2.2.4)
of 2004-08-02 on oops.
The message contains Unicode characters and has been sent as a binary attachment.
<>
On Monday, July 21, 2003 at 18:50:24, Vladimir G. Ivanovic wrote:
> Whenever I delete a record in the database, I get the appended
> message when I view another MH message.
>
> I display the database by `M-x bbdb RET RET' I navigate to the
> appropriate record with successive `n' and then I type `
Whenever I delete a record in the database, I get the appended message
when I view another MH message.
I display the database by `M-x bbdb RET RET' I navigate to the
appropriate record with successive `n' and then I type `d RET y RET'
followed by `s' to save the database.
I can fix the problem by
On Thursday, March 27, 2003 at 12:35:39, Sridhar Boovaraghavan wrote:
> Until recently, I used to type in the mail-alias of a person in the
> From/To fields and then hit C-n. This expanded the alias and moved
> the cursor to the next line. Now, I am getting this message in the
> *Messages* buffer a
Setting debug-on-error doesn't produce a backtrace. Records for which
this seems to happen have a mail alias defined like this:
["First" "Last" nil nil nil nil ("[EMAIL PROTECTED]") ((creation-date . "2003-03-27")
(timestamp . "2003-03-27") (
s,
> Waider.
O.k. I tried it again with the following record:
Dummy Foo
net: [EMAIL PROTECTED], [EMAIL PROTECTED]
-- in the .bbdb
["Dummy" "Foo" nil nil nil nil ("[EMAIL PROTECTED]" "[EMAIL PROTECTED]") ((creation-date .
"2002-04-04&q
On March 26, [EMAIL PROTECTED] said:
>
> I have a bbdb entry with 2 email addresses.
> When I want to change the net addresses I hit e over the net line.
> When I just hit enter to keep the current net address I get an error:
>
> bbdb-record-edit-net: Wrong type argument:
I have a bbdb entry with 2 email addresses.
When I want to change the net addresses I hit e over the net line.
When I just hit enter to keep the current net address I get an error:
bbdb-record-edit-net: Wrong type argument: arrayp, (["Stefan" "Reichör" nil nil nil
ni
On March 8, [EMAIL PROTECTED] said:
>
>
>
> This is the first error of the sort I receive, however I also suspect
> my .bbdb file to be corrupt, I don't know a way of checking this.
Okay, I think I can see what's happening, but it'd help if you (a) run
BBDB uncom
This is the first error of the sort I receive, however I also suspect
my .bbdb file to be corrupt, I don't know a way of checking this.
# bind (standard-output stack-trace-on-signal debug-on-signal stack-trace-on-error
debug-on-error record)
bbdb-record-sortkey(nil)
# bind
On January 15, [EMAIL PROTECTED] said:
>
> Not sure what it does on XEmacs.
>
> kai
Seems to do this on all that I have access to, but damned if I'm
making large-scale code changes right now! I've rearranged (I think)
enough of the compiler placation that it shouldn't trip up anyone.
Cheers,
W
On January 16, [EMAIL PROTECTED] said:
>
> How same is "same"? I mean, you could write the compiler's version
> string into a variable and compare for equality, but that seems a bit
> extreme.
By same I mean that the same features are available. I really don't
know how generous this is, so prac
> "Ronan" == Ronan Waide <[EMAIL PROTECTED]> writes:
Ronan> I would really, REALLY like to force the compile
Ronan> environment to be the same as the run environment;
Ronan> specifically, if you compile BBDB under Emacs Y, then it
Ronan> will only run under Emacs Y.
How same
[EMAIL PROTECTED] (Kai Großjohann) writes:
> | ELISP> (defvar xyzzy)
> | xyzzy
> | ELISP> (boundp 'xyzzy)
> | nil
Heh, learn a new thing every day. :)
Alex.
--
http://www.emacswiki.org/
___
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/list
> "Kai" == Kai Großjohann <[EMAIL PROTECTED]> writes:
Kai> Alex Schroeder <[EMAIL PROTECTED]> writes:
>> This is exactly the kind of thing which will screw other code in the
>> long run. That other package might test (boundp 'foo) and we used
>> defvar foo to silence the comp
Alex Schroeder <[EMAIL PROTECTED]> writes:
> This is exactly the kind of thing which will screw other code in the
> long run. That other package might test (boundp 'foo) and we used
> defvar foo to silence the compiler... It might work (and many people
> do this), but we'll need to really make
Ronan Waide <[EMAIL PROTECTED]> writes:
> On January 12, [EMAIL PROTECTED] said:
>>
>> I am not sure, but it seems to me that autoloads are more desireable,
>> 'cause then we defer the possible need/availability check to runtime.
>
> Yep, except the compiler warnings I was attempting to hush up
Benjamin Rutt <[EMAIL PROTECTED]> writes:
> Maybe people who want the luxury of running BBDB with multiple emacsen
> can live with running BBDB uncompiled? Or, they could maintain
> multiple installation dirs and compile for multiple emacsen.
If you run Debian, I think this is what happens, eve
Ronan Waide <[EMAIL PROTECTED]> writes:
[...]
> I would really, REALLY like to force the compile environment to be
> the same as the run environment; specifically, if you compile BBDB
> under Emacs Y, then it will only run under Emacs Y. This would allow
> a lot more compile-time optimizing of t
On January 12, [EMAIL PROTECTED] said:
> What's the best solution for library writers then? Do you know
> of any code examples where this is handled well?
I think the right way to go about this, and certainly the way I intend
pushing the BBDB source, is to firstly centralise all the versioning
n
On January 12, [EMAIL PROTECTED] said:
>
> I am not sure, but it seems to me that autoloads are more desireable,
> 'cause then we defer the possible need/availability check to runtime.
Yep, except the compiler warnings I was attempting to hush up are for
variables, not functions/macros, and auto
On January 12, [EMAIL PROTECTED] said:
> featurep of XEmacs 21.1 and newer has fairly sophisticated emacs
> version testing support. Has this been implemented for GNU Emacs
> yet?
See, this is still a problem, because if you're on XEmacs 21.1 the
feature already exists and there's no testing to
Chris Beggy <[EMAIL PROTECTED]> writes:
> From: Alex Schroeder <[EMAIL PROTECTED]>
>>
>> Lots of packages define missing functions in order to run on Emacs and
>> XEmacs. Other packages test wethere critical functions are bound or
>> not, and then assume they are on Emacs or XEmacs. :(
>>
>>
> "Chris" == Chris Beggy <[EMAIL PROTECTED]> writes:
Chris> From: Alex Schroeder <[EMAIL PROTECTED]>
>>
>> Lots of packages define missing functions in order to run on Emacs and
>> XEmacs. Other packages test wethere critical functions are bound or
Hi Alex, All!
featurep o
From: Alex Schroeder <[EMAIL PROTECTED]>
>
> Lots of packages define missing functions in order to run on Emacs and
> XEmacs. Other packages test wethere critical functions are bound or
> not, and then assume they are on Emacs or XEmacs. :(
>
> I've had a similar problem with one package or an
On , January 12, 2002 at 10:11:38, Jochen Küpper wrote:
[...]
> I am not sure, but it seems to me that autoloads are more desireable,
> 'cause then we defer the possible need/availability check to runtime.
But you would not get meaningful compile errors and when you
use macros it becomes even wor
retrieving revision 1.68
diff -u -r1.68 bbdb-hooks.el
- --- lisp/bbdb-hooks.el 2002/01/06 22:09:42 1.68
+++ lisp/bbdb-hooks.el 2002/01/12 15:09:56
@@ -42,9 +42,9 @@
(condition-case() (require 'gnus) (error nil))
(condition-case () (require 'vm) (error nil))
(autoload
Galen Boyer <[EMAIL PROTECTED]> writes:
> I found the issue. table.el has caused me a few headaches now.
> For some reason, it finds its way into the middle of compilations
> and then the resultant compiled code has issues. I ran the bbdb
> uncompiled (whew, is it slow) and I was able to perfor
> This looks more like an *.elc File which is incompatible, but
> you should (setq debug-on-error) and send a backtrack
> in order to identify the problem.
I found the issue. table.el has caused me a few headaches now.
For some reason, it finds its way into the middle of compilations
and
At Friday, 11 January 2002, you wrote:
>
>Is this desirable? Why should I install VM when I never use it, just
>to get BBDB with Gnus?
Nope, it's overzealous compiler-hushing on my part, precisely the sort
of thing I'm cleaning up at the moment. In reality, of course, you
shouldn't need the VM s
le: /cvsroot/bbdb/bbdb/lisp/bbdb-hooks.el,v
retrieving revision 1.68
diff -u -r1.68 bbdb-hooks.el
--- lisp/bbdb-hooks.el 2002/01/06 22:09:42 1.68
+++ lisp/bbdb-hooks.el 2002/01/11 16:42:41
@@ -42,7 +42,7 @@
(condition-case() (require 'gnus) (error nil))
(condition-case () (requi
On January 10, [EMAIL PROTECTED] said:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> With latest cvs sources on Linux, XEmacs-21.4 I get
Note that you must have VM sources to compile BBDB. A compiled VM is
insufficient. Mind you, I'm not saying that that's where the problem
lies!
Cheers
On January 10, [EMAIL PROTECTED] said:
>
> Was this the problem the original poster had? Is he trying to
> alter a record which somehow has face information, since records
> can be created this way? That was the point of my post.
>
> Chris
Where this problem seems to occur most frequently is i
ks.el...
| Loading bbdb-snarf... (file bbdb-snarf.el is newer)
| While compiling toplevel forms in file /home/software/emacs/bbdb/lisp/bbdb-hooks.el:
| !! File error (("Cannot open load file" "vm-autoload"))
| >>Error occurred processing bbdb-hooks.el: Cannot open load file:
From: Robert Fenk <[EMAIL PROTECTED]>
> On Thursday, January 10, 2002 at 10:34:09, Chris Beggy wrote:
> [...]
> > I think that I have gotten errors like this, in reading the .bbdb
> > file, when I have snarfed records with "face" in the buffer.
>
> We had a report on similar problems before.
> A
On Thursday, January 10, 2002 at 10:34:09, Chris Beggy wrote:
[...]
> I think that I have gotten errors like this, in reading the .bbdb
> file, when I have snarfed records with "face" in the buffer.
We had a report on similar problems before.
As far as I remember you have to edit .bbdb
by hand an
From: Robert Fenk <[EMAIL PROTECTED]>
> On , January 9, 2002 at 23:34:01, Galen Boyer wrote:
> > Invalid face text property value: red [12 times]
>
> Hmm, I think there is no face in BBDB which is red unless you
> defined/changed one yourself. Have you made any changes to the
> config/sources r
he
config/sources recently which might be responsible?
> Invalid function: (macro . #[(vector) "ÁÂEÂ" [vector aref 1] 3])
This looks more like an *.elc File which is incompatible, but
you should (setq debug-on-error) and send a backtrack
in order to identify
I am continually getting the following type of message.
Invalid face text property value: red [12 times]
Invalid function: (macro . #[(vector) "ÁÂEÂ" [vector aref 1] 3])
I have shut down and restarted Emacs a few times after seeing
this, just to make sure it wasn't something boneheaded I did.
Here's patch against 2.32 to correct a message-mode-keymap error:
Chris
--- lisporig/bbdb.elMon Nov 19 09:30:39 2001
+++ lisp/bbdb.elMon Nov 19 09:31:06 2001
@@ -38,6 +38,7 @@
;;
(require 'timezone)
+(require 'message)
(defconst bbdb-version "2.32"
Trying to open a mail (in gnus) from [EMAIL PROTECTED] produces a lisp error. Backtrace
pasted below. Please contact me directly if you need to see my .bbdb file.
Thanks,
Mike Slass
WRQ, Inc.
Seattle, WA
cut here
Debugger entered--Lisp error: (wrong-type-argument
This one is somewhat hard to describe. Please let me know if you
can't make it out.
Whenever mh-e calls bbdb/mh-update-record for a message WITHOUT an
existing entry in the database TWICE, emacs will error as below. To
reproduce, you need to have bbdb/mail-auto-create-p nil, select a
me
byte code (("variable reference to constant symbol :group"))
>> >> >>Error occurred processing bbdb-gnus.el:
>> >> Invalid byte code: "variable reference to constant symbol :group"
>>
I have more information. I tried the things you sugges
On August 29, [EMAIL PROTECTED] said:
> >> While compiling toplevel forms in file
>/home/lconrad/src/bbdb/bbdb/lisp/bbdb-gnus.el:
> >> !! Invalid byte code (("variable reference to constant symbol :group"))
> >> >>Error occurred proces
cs/site-start.d/rpm.el...
>> Compiling /home/lconrad/src/bbdb/bbdb/lisp/bbdb-gnus.el...
>> While compiling toplevel forms in file
/home/lconrad/src/bbdb/bbdb/lisp/bbdb-gnus.el:
>> !! Invalid byte code (("variable reference to constant symbol :group"))
>
conrad/src/bbdb/bbdb/lisp/bbdb-gnus.el:
> !! Invalid byte code (("variable reference to constant symbol :group"))
> >>Error occurred processing bbdb-gnus.el:
> Invalid byte code: "variable reference to constant symbol :group"
>
>
> Done
Hi Laura,
what
.
Loading /etc/emacs/site-start.d/python.el...
Loading /etc/emacs/site-start.d/rpm.el...
Compiling /home/lconrad/src/bbdb/bbdb/lisp/bbdb-gnus.el...
While compiling toplevel forms in file /home/lconrad/src/bbdb/bbdb/lisp/bbdb-gnus.el:
!! Invalid byte code (("variable reference to constant sy
On June 2, [EMAIL PROTECTED] said:
> Hi!
>
> Emacs 20.7 + Oort Gnus 0.04 + latest BBDB from CVS
>
> Adding a record with `:' and pressing '?' for further help produces
> the following backtrace:
>
> Signaling: (void-function window-list)
> window-list()
This is fixed, after a fashion. I'm n
Hi!
Emacs 20.7 + Oort Gnus 0.04 + latest BBDB from CVS
Adding a record with `:' and pressing '?' for further help produces
the following backtrace:
Signaling: (void-function window-list)
window-list()
bbdb-get-help-window("Your answer controls how BBDB updates/searches for
records.\n\nTyp
On February 28, [EMAIL PROTECTED] said:
> Hello,
>
> I upgraded from XEmacs 20.4 to v21.1.8 without modifying my
> .emacs file.
> Whenever I want to get a record from BBDB (e.g. by entering
> VMail) I get the error message
>
>
> Signaling: (wrong-type-argumen
Hello,
I upgraded from XEmacs 20.4 to v21.1.8 without modifying my
.emacs file.
Whenever I want to get a record from BBDB (e.g. by entering
VMail) I get the error message
Signaling: (wrong-type-argument arrayp -A)
parse-bbdb-frobnicate((["2POL" nil ("Lemaire Michel"
On Friday, February 2 2001 23:07:24, patrick finerty jr. wrote:
[...]
> Michael J Fox <[EMAIL PROTECTED]>
[...]
>
> is this a bug or a feature?
It is a bug. I gonna commit a fix for this next week.
Bye Robert
___
[EMAIL PROTECTED]
http://lists.sour
i've noticed something else odd with the new bbdb. many people use
middle initials in the full name part of their email address such as:
Michael J. Fox <[EMAIL PROTECTED]>
how to reproduce:
create a new record with a middle initial. the initial should be
terminated with a '.' as above. next, se
1 - 100 of 106 matches
Mail list logo
