On Sat Aug 2 2014 Eric Abrahamsen wrote:
> I think this is just a misunderstanding about what
> `bbdb-name-face-alist' does. It *only* provides font-locking for the
> actual name of the record, not the other fields. You give the record an
> xfield called 'name-face, and the *value* of that field po
On Sat Aug 2 2014 stardiviner wrote:
> When I use =bbdb-snarf= to add email to a new record.
> report error:
> When I try to re-add this email, after lost the record, it report error:
> =(error "BBDB: marker absent")=
>
> I think BBDB show check the database before really do write action.
> If da
On Fri Aug 1 2014 stardiviner wrote:
> Let BBDBv3 support adjust field sorting manually with =[M-Up/Down]=.
> So I can see important field first, instead have to be limited by the time of
> field added.
You can transpose fields of the same type (two phone numbers, two
addresses, etc.) via bbdb-tra
On Mon Jul 28 2014 H. Dieter Wilhelm wrote:
> is it normal that bbdb-do-all-records is *not* working for all entries
> in conjunction with mail-aliases "*a", only the entry where the cursor
> is sitting?
>
> I'm using emacs "24.3.92.2" and bbdb "3.1.2"...
The patch below should fix that.
2014-08
stardiviner writes:
> I try to define custom faces to be applied in variable =bbdb-name-face-alist=
> for
> variant field names.
>
> Here is my try:
>
> #+BEGIN_SRC emacs-lisp
> ;;; define variant faces for variant xfields
>
> ;; TODO: improve it
> (setq bbdb-name-face-alist '((mail . bbdb-field
I try to define custom faces to be applied in variable =bbdb-name-face-alist=
for
variant field names.
Here is my try:
#+BEGIN_SRC emacs-lisp
;;; define variant faces for variant xfields
;; TODO: improve it
(setq bbdb-name-face-alist '((mail . bbdb-field-mail)
(mai
When I use =bbdb-snarf= to add email to a new record.
report error:
When I try to re-add this email, after lost the record, it report error:
=(error "BBDB: marker absent")=
I think BBDB show check the database before really do write action.
If database has exist the email, then raise exist recor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Let BBDBv3 support adjust field sorting manually with =[M-Up/Down]=.
So I can see important field first, instead have to be limited by the time of
field added.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBAgAGBQJT214jAAoJELjEuOVHwyQzfKMIAK