;ELC
;;; Compiled by mockbuild@buildfarm06-new.corp.cloudlinux.com on Fri Oct 11 10:10:30 2024
;;; from file /builddir/build/BUILD/emacs-24.3/lisp/net/eudc-vars.el
;;; in Emacs version 24.3.1
;;; with all optimizations.

;;; This file uses dynamic docstrings, first added in Emacs 19.29.

;;; This file does not contain utf-8 non-ASCII characters,
;;; and so can be loaded in Emacs versions earlier than 23.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;


(byte-code "\300\301!\210\302\303\304\305\306\307\310\311\312\313\312\314&\210\315\316\304\317\320\321\312\303&\207" [require custom custom-declare-group eudc nil "Emacs Unified Directory Client." :version "21.1" :link (info-link "(eudc)") :group mail comm custom-declare-variable eudc-server "The name or IP address of the directory server.\nA port number may be specified by appending a colon and a\nnumber to the name of the server.  Use `localhost' if the directory\nserver resides on your computer (BBDB backend)." :type (choice (string :tag "Server") (const :tag "None" nil))] 12)
(defvar eudc-known-protocols '(bbdb ph ldap))
#@136 Protocols currently supported by EUDC.
This variable is updated when protocol-specific libraries
are loaded, *do not change manually*.
(defvar eudc-supported-protocols nil (#$ . 1192))
(byte-code "\301\302\303\304\305\306\307\310\311\312\313\"\314\"BBB\315\316&\210\301\317\320\321\305\322\315\316&\210\301\323\303\324\305\325\315\316&\210\301\326\327\330\305\331\315\316&\210\301\332\333\334\305\335\315\316&\210\301\336\337\340\341\342\305\343\315\316&	\210\301\344\320\345\305\322\315\316&\210\301\346\347\350\305\351\315\316&\210\301\352\353\354\305\355\315\316&\210\301\356\303\357\341\360\305\361\315\316&	\210\301\362\363\364\341\365\305\366\315\316&	\210\301\367\370\371\341\372\305\373\315\316&	\210\301\374\303\375\305\322\315\316&\210\301\376\303\377\341\201@\305\201A\315\316&	\210\301\201B\201C\201D\341\201E\305\201F\315\316&	\210\301\201G\201H\201I\305\201J\315\316&\210\301\201K\303\201L\305\201M\315\316&\210\201N\201O\303\201P\315\316%\210\301\201Q\201R\201S\341\201T\305\201U\315\201O&	\210\201N\201V\303\201W\315\316%\210\301\201X\201Y\201Z\341\201[\305\201\\\315\201V&	\210\201N\201]\303\201^\315\316%\210\301\201_\320\201`\305\322\315\201]&\210\301\201a\320\201b\305\322\315\201]&\210\201c\201d!\207" [eudc-known-protocols custom-declare-variable eudc-protocol nil "The directory protocol to use to query the server.\nSupported protocols are specified by `eudc-supported-protocols'." :type choice :menu-tag "Protocol" append mapcar #[(s) "\301\302\303!F\207" [s const :tag symbol-name] 4] ((const :tag "None" nil)) :group eudc eudc-strict-return-matches t "Ignore or allow entries not containing all requested return attributes.\nIf non-nil, such entries are ignored." boolean eudc-default-return-attributes "A list of default attributes to extract from directory entries.\nIf set to the symbol `all', return all attributes.\nA value of nil means return the default attributes as configured in the\nserver." (choice :menu-tag "Return Attributes" (const :menu-tag "Server defaults (nil)" nil) (const :menu-tag "All" all) (repeat :menu-tag "Attribute list" :tag "Attribute name" :value (nil) (symbol :tag "Attribute name"))) eudc-multiple-match-handling-method 'select "What to do when multiple entries match an inline expansion query.\nPossible values are:\n`first' (equivalent to nil) which means keep the first match only,\n`select' pop-up a selection buffer,\n`all' expand to all matches,\n`abort' the operation is aborted, an error is signaled." (choice :menu-tag "Method" (const :menu-tag "Use First" :tag "Use First" first) (const :menu-tag "Select Interactively" :tag "Select Interactively" select) (const :menu-tag "Use All" :tag "Use All" all) (const :menu-tag "Abort Operation" :tag "Abort Operation" abort) (const :menu-tag "Default (Use First)" :tag "Default (Use First)" nil)) eudc-duplicate-attribute-handling-method '((email . duplicate)) "A method to handle entries containing duplicate attributes.\nThis is either an alist (ATTR . METHOD) or a symbol METHOD.\nThe alist form of the variable associates a method to an individual attribute,\nthe second form specifies a method applicable to all attributes.\nAvailable methods are:\n`list' or nil lets the value of the attribute be a list of values,\n`first' keeps the first value and discards the others,\n`concat' concatenates the values into a single multiline string,\n`duplicate' duplicates the entire entry into as many instances as\ndifferent values." (choice (const :menu-tag "List" list) (const :menu-tag "First" first) (const :menu-tag "Concat" concat) (const :menu-tag "Duplicate" duplicate) (repeat :menu-tag "Per Attribute Specification" :tag "Per Attribute Specification" (cons :tag "Attribute/Method" :value (nil . list) (symbol :tag "Attribute name") (choice :tag "Method" :menu-tag "Method" (const :menu-tag "List" list) (const :menu-tag "First" first) (const :menu-tag "Concat" concat) (const :menu-tag "Duplicate" duplicate))))) eudc-inline-query-format '((name) (firstname name)) "Format of an inline expansion query.\nThis is a list of FORMATs.  A FORMAT is itself a list of one or more\nEUDC attribute names.  A FORMAT applies if it contains as many attributes as\nthere are individual words in the inline query string.\nIf several FORMATs apply then they are tried in order until a match\nis found.\nIf nil, all the words are mapped onto the default server or protocol\nattribute name.\n\nThe attribute names in FORMATs are not restricted to EUDC attribute names\nbut can also be protocol/server specific names.  In this case, this variable\nmust be set in a protocol/server-local fashion, see `eudc-server-set' and\n`eudc-protocol-set'." :tag "Format of Inline Expansion Queries" (repeat (repeat :menu-tag "Format" :tag "Format" (choice :tag "Attribute" (const :menu-tag "First Name" :tag "First Name" firstname) (const :menu-tag "Surname" :tag "Surname" name) (const :menu-tag "Email Address" :tag "Email Address" email) (const :menu-tag "Phone" :tag "Phone" phone) (symbol :menu-tag "Other" :tag "Attribute name")))) eudc-expansion-overwrites-query "If non-nil, expanding a query overwrites the query string." eudc-inline-expansion-format '("%s" email) "A list specifying the format of the expansion of inline queries.\nThis variable controls what `eudc-expand-inline' actually inserts in\nthe buffer.  First element is a string passed to `format'.  Remaining\nelements are symbols indicating attribute names; the corresponding values\nare passed as additional arguments to `format'." (list (string :tag "Format String") (repeat :inline t :tag "Attributes" (choice :tag "Attribute" (const :menu-tag "First Name" :tag "First Name" firstname) (const :menu-tag "Surname" :tag "Surname" name) (const :menu-tag "Email Address" :tag "Email Address" email) (const :menu-tag "Phone" :tag "Phone" phone) (symbol :menu-tag "Other") (symbol :tag "Attribute name")))) eudc-inline-expansion-servers 'server-then-hotlist "Which servers to contact for the expansion of inline queries.\nPossible values are:\n  `current-server': the EUDC current server.\n  `hotlist': the servers of the hotlist in the order they appear,\n  `server-then-hotlist': the current server and then the servers of\n  the hotlist." (choice :tag "Servers" :menu-tag "Servers" (const :menu-tag "Current server" current-server) (const :menu-tag "Servers in the hotlist" hotlist) (const :menu-tag "Current server then hotlist" server-then-hotlist)) eudc-max-servers-to-query "Maximum number of servers to query for an inline expansion.\nIf nil, query all servers available from `eudc-inline-expansion-servers'." "Max Number of Servers to Query" (choice :tag "Max. Servers" :menu-tag "Max. Servers" (const :menu-tag "No limit" nil) (const :menu-tag "1" 1) (const :menu-tag "2" 2) (const :menu-tag "3" 3) (const :menu-tag "4" 4) (const :menu-tag "5" 5) (integer :menu-tag "Set")) eudc-query-form-attributes '(name firstname email phone) "A list of attributes presented in the query form." "Attributes in Query Forms" (repeat (choice :tag "Attribute" (const :menu-tag "First Name" :tag "First Name" firstname) (const :menu-tag "Surname" :tag "Surname" name) (const :menu-tag "Email Address" :tag "Email Address" email) (const :menu-tag "Phone" :tag "Phone" phone) (symbol :menu-tag "Other" :tag "Attribute name"))) eudc-user-attribute-names-alist '((url . "URL") (callsign . "HAM Call Sign") (id . "ID") (email . "E-Mail") (firstname . "First Name") (cn . "Full Name") (sn . "Surname") (givenname . "First Name") (ou . "Unit") (labeledurl . "URL") (postaladdress . "Address") (postalcode . "Postal Code") (l . "Location") (c . "Country") (o . "Organization") (roomnumber . "Office") (telephonenumber . "Phone") (uniqueidentifier . "ID") (objectclass . "Object Class")) "Alist of user-defined names for directory attributes.\nThese names are used as prompt strings in query/response forms\ninstead of the raw directory attribute names.\nPrompt strings for attributes that are not listed here\nare derived by splitting the attribute name\nat `_' characters and capitalizing the individual words." "User-defined Names of Directory Attributes" (repeat (cons :tag "Field" (symbol :tag "Directory attribute") (string :tag "User friendly name "))) eudc-use-raw-directory-names "If non-nil, use attributes names as defined in the directory.\nOtherwise, directory query/response forms display the user attribute\nnames defined in `eudc-user-attribute-names-alist'." eudc-attribute-display-method-alist "An alist specifying methods to display attribute values.\nEach member of the list is of the form (NAME . FUNC) where NAME is a lowercased\nstring naming a directory attribute (translated according to\n`eudc-user-attribute-names-alist' if `eudc-use-raw-directory-names' is\nnon-nil) and FUNC a function that will be passed the corresponding\nattribute values for display." "Attribute Decoding Functions" (repeat (cons :tag "Attribute" (symbol :tag "Name") (symbol :tag "Display Function"))) eudc-external-viewers '(("ImageMagick" "display" "-") ("ShowAudio" "showaudio")) "A list of viewer program specifications.\nViewers are programs which can be piped a directory attribute value for\ndisplay or arbitrary processing.  Each specification is a list whose\nfirst element is a string naming the viewer.  The second element is the\nexecutable program which should be invoked, and following elements are\narguments that should be passed to the program." "External Viewer Programs" (repeat (list :tag "Viewer" (string :tag "Name") (string :tag "Executable program") (repeat :tag "Arguments" :inline t (string :tag "Argument")))) eudc-options-file "~/.eudc-options" "A file where the `servers' hotlist is stored." (file :Tag "File Name:") eudc-mode-hook "Normal hook run on entry to EUDC mode." (repeat (sexp :tag "Hook definition")) custom-declare-group eudc-ph "Emacs Unified Directory Client - CCSO PH/QI Backend." eudc-ph-bbdb-conversion-alist '((name . name) (net . email) (address eudc-bbdbify-address address "Address") (phone (eudc-bbdbify-phone phone "Phone") (eudc-bbdbify-phone office_phone "Office Phone"))) "A mapping from BBDB to PH/QI fields.\nThis is a list of cons cells (BBDB-FIELD . SPEC-OR-LIST) where\nBBDB-FIELD is the name of a field that must be defined in your BBDB\nenvironment (standard field names are `name', `company', `net', `phone',\n`address' and `notes').  SPEC-OR-LIST is either a single SPEC or a list\nof SPECs.  Lists of specs are valid only for the `phone' and `address'\nBBDB fields.  SPECs are sexps which are evaluated:\n  a string evaluates to itself,\n  a symbol evaluates to the symbol value.  Symbols naming PH/QI fields\n    present in the record evaluate to the value of the field in the record,\n  a form is evaluated as a function.  The argument list may contain PH/QI\n    field names which eval to the corresponding values in the\n    record.  The form evaluation should return something appropriate for\n    the particular BBDB-FIELD (see `bbdb-create-internal').\n    `eudc-bbdbify-phone' and `eudc-bbdbify-address' are provided as convenience\n    functions to parse phones and addresses." "BBDB to PH Field Name Mapping" (repeat (cons :tag "Field Name" (symbol :tag "BBDB Field") (sexp :tag "Conversion Spec"))) eudc-ldap "Emacs Unified Directory Client - LDAP Backend." eudc-ldap-bbdb-conversion-alist '((name . cn) (net . mail) (address eudc-bbdbify-address postaladdress "Address") (phone (eudc-bbdbify-phone telephonenumber "Phone"))) "A mapping from BBDB to LDAP attributes.\nThis is a list of cons cells (BBDB-FIELD . SPEC-OR-LIST) where\nBBDB-FIELD is the name of a field that must be defined in your BBDB\nenvironment (standard field names are `name', `company', `net', `phone',\n`address' and `notes').  SPEC-OR-LIST is either a single SPEC or a list\nof SPECs.  Lists of specs are valid only for the `phone' and `address'\nBBDB fields.  SPECs are sexps which are evaluated:\n  a string evaluates to itself,\n  a symbol evaluates to the symbol value.  Symbols naming LDAP attributes\n    present in the record evaluate to the value of the field in the record,\n  a form is evaluated as a function.  The argument list may contain LDAP\n    field names which eval to the corresponding values in the\n    record.  The form evaluation should return something appropriate for\n    the particular BBDB-FIELD (see `bbdb-create-internal').\n    `eudc-bbdbify-phone' and `eudc-bbdbify-address' are provided as convenience\n    functions to parse phones and addresses." "BBDB to LDAP Attribute Names Mapping" (repeat (cons :tag "Field Name" (symbol :tag "BBDB Field") (sexp :tag "Conversion Spec"))) eudc-bbdb "Emacs Unified Directory Client - BBDB Backend." eudc-bbdb-use-locations-as-attribute-names "If non-nil, BBDB address and phone locations are used as attribute names.\nThis has no effect on queries (you can't search for a specific location)\nbut influences the way records are displayed." eudc-bbdb-enable-substring-matches "If non-nil, authorize substring match in the same way BBDB does.\nOtherwise records must match queries exactly." provide eudc-vars] 12)