diff --git a/lisp/bbdb-com.el b/lisp/bbdb-com.el index a261c85..ba84aa9 100644 --- a/lisp/bbdb-com.el +++ b/lisp/bbdb-com.el @@ -877,7 +877,8 @@ FIRST-AND-LAST controls the reading mode: If it is 'first-last read first and last name separately. If it is 'last-first read last and first name separately. If it is 'fullname read full name at once. -If it is t read name parts separately, obeying `bbdb-read-name-format' if possible. +If it is t read name parts separately, obeying +`bbdb-read-name-format' if possible. Otherwise use `bbdb-read-name-format'. DFIRST and DLAST are default values for the first and last name. Return cons with first and last name." diff --git a/lisp/bbdb-mua.el b/lisp/bbdb-mua.el index 455900e..95e30d9 100644 --- a/lisp/bbdb-mua.el +++ b/lisp/bbdb-mua.el @@ -1004,19 +1004,19 @@ For use as an element of `bbdb-notice-record-hook'." (defun bbdb-mua-summary-unify (address) "Unify mail ADDRESS displayed for a message in the MUA Summary buffer. -Typically ADDRESS refers to the value of the From header of a message. -If ADDRESS matches a record in BBDB display a unified name instead of ADDRESS -in the MUA Summary buffer. +Typically ADDRESS refers to the value of the From header of a +message. If ADDRESS matches a record in BBDB display a unified +name instead of ADDRESS in the MUA Summary buffer. Unification uses `bbdb-mua-summary-unification-list' (see there). The first match in this list becomes the text string displayed -for a message in the MUA Summary buffer instead of ADDRESS. -If variable `bbdb-mua-summary-mark' is non-nil use it to precede known addresses. -Return the unified mail address. +for a message in the MUA Summary buffer instead of ADDRESS. If +variable `bbdb-mua-summary-mark' is non-nil use it to precede +known addresses. Return the unified mail address. -Currently this works with Gnus and VM. It requires the BBDB insinuation -of these MUAs. Also, the MUA Summary format string must use -`bbdb-mua-summary-unify-format-letter' (see there)." +Currently this works with Gnus and VM. It requires the BBDB +insinuation of these MUAs. Also, the MUA Summary format string +must use `bbdb-mua-summary-unify-format-letter' (see there)." ;; ADDRESS is analyzed as in `bbdb-get-address-components'. (let* ((data (bbdb-extract-address-components address)) (name (car data)) diff --git a/lisp/bbdb.el b/lisp/bbdb.el index 051b21d..20ea030 100644 --- a/lisp/bbdb.el +++ b/lisp/bbdb.el @@ -1351,9 +1351,10 @@ For merging xfield LABEL, this will use MERGE-FUN." (defcustom bbdb-mua-summary-unification-list '(name mail message-name message-mail message-address) "List of FIELDs considered by `bbdb-mua-summary-unify'. -For the RECORD matching the address of a message, `bbdb-mua-summary-unify' -returns the first non-empty field value matching an element FIELD from this list. -Each element FIELD may be a valid argument of `bbdb-record-field' for RECORD. +For the RECORD matching the address of a message, +`bbdb-mua-summary-unify' returns the first non-empty field value +matching an element FIELD from this list. Each element FIELD may +be a valid argument of `bbdb-record-field' for RECORD. In addition, this list may also include the following elements: message-name The name in the address of the message message-mail The mail in the address of the message