This is both lenient and strict in what it will parse - whitespace may
appear (or not) between any of the groups of digits, parentheses around the
area code are optional, as is a dash between the exchange and number, and
-a '1' prece
eding the area code; but there must be three digits in the area
+a '1' preceding the area code; but there must be three digits in the area
code and exchange, and four in the number (if they are present). An error
-will be signalled if unparsable. All of these are unambigously parsable:
+will be signalled if unparsable. All of these are unambigously parsable:
( 415 ) 555 - 1212 x123 -> (415 555 1212 123)
(415)555-1212 123 -> (415 555 1212 123)
(defun bbdb-complete-name (&optional start-pos)
"Complete the user full-name or net-address before point (up to the
eding newline, colon, or comma). If what has been typed is unique,
+preceding newline, colon, or comma). If what has been typed is unique,
insert an entry of the form \"User Name <net-addr>\". If it is a valid
completion but not unique, a list of completions is displayed.
;;; /pub/gnu/emacs/elisp-archive/packages directory. EFS ships with XEmacs.
;;; Note that Ftp Site BBDB entries differ from regular entries by the
-;;; fact that the Name Field must have the ftp site prece
eded by the
+;;; fact that the Name Field must have the ftp site preceded by the
;;; bbdb-ftp-site-name-designator-prefix. This defaults to "Ftp Site:"
;;; BBDB Ftp Site entries also have two new fields added, the
;;; ftp-dir slot, and the ftp-user slot. These are added to the notes
(defun bbdb-record-ftp-site (record)
- "Acessor Function. Returns the ftp-site field of the BBDB record or nil."
+ "Acessor Function. Returns the ftp-site field of the BBDB record or nil."
(let* ((name (bbdb-record-name record))
(ftp-pfx-regexp (concat bbdb-ftp-site-name-designator-prefix " *"))
the information from the BBDB in the summary buffer (using
`bbdb/gnus-summary-get-author'). This format code is meant to replace
codes that insert sender names or addresses (like %A or %n). Unless
-you've alread got other code using user format B, you might as well
+you've alread got other code using user format B, you might as well
stick with the default. Additionally, if the value of this variable
is nil, no format function will be installed for
`bbdb/gnus-summary-get-author'. See also
where GET is the function to be used to retrieve the field to be
-modified, and SET is the function to be used t
e set the field to be
+modified, and SET is the function to be used t set the field to be
modified. FUNCTION will be applied to the result of GET, and its
results will be saved with SET."
The name comes first and other fields (address,
phone, email, web pages) are recognized by context.
addresses end with \"City, State ZIP\" or \"City, State\"
phones match bbdb-snarf-phone-regexp
(currently US-style phones)
(defcustom bbdb-auto-revert-p nil
"*If this variable is true and the BBDB file is noticed to have changed on
disk, it will be automatically reverted without prompting you first. Otherwise
-you will be asked. (But if the file has changed and you hae made changes in
+you will be asked. (But if the file has changed and you hae made changes in
memory as well, you will always be asked.)"
:type '(choice (const :tag "Revert unchanged database without prompting" t)
;; "flush your changes and revert" question. The only other
;; alternative is to save the file right now. If they answer
;; no to the following question, they will be asked the
- ;; prece
eding question again and again some large (but finite)
+ ;; preceding question again and again some large (but finite)
;; number of times. `bbdb-records' is called a lot, you see...
(defun bbdb-record-lessp-fn (record1 record2) ; for use as a funarg
(bbdb-record-lessp record1 record2))