Gecko [ 122.154.134.11 ]

Name	Size	Permission
ange-ftp.elc	116.81 KB	-rw-r--r--
browse-url.el.xdg	57.99 KB	-rw-r--r--
browse-url.elc	46.94 KB	-rw-r--r--
dbus.elc	28.38 KB	-rw-r--r--
dig.elc	5.08 KB	-rw-r--r--
dns.elc	11.33 KB	-rw-r--r--
eudc-bob.elc	9.11 KB	-rw-r--r--
eudc-export.elc	5.9 KB	-rw-r--r--
eudc-hotlist.elc	5.71 KB	-rw-r--r--
eudc-vars.elc	14.61 KB	-rw-r--r--
eudc.elc	32.17 KB	-rw-r--r--
eudcb-bbdb.elc	5.41 KB	-rw-r--r--
eudcb-ldap.elc	5.18 KB	-rw-r--r--
eudcb-mab.elc	2.88 KB	-rw-r--r--
eudcb-ph.elc	6.44 KB	-rw-r--r--
goto-addr.elc	9.28 KB	-rw-r--r--
hmac-def.elc	2.07 KB	-rw-r--r--
hmac-md5.elc	2.15 KB	-rw-r--r--
imap.elc	104.58 KB	-rw-r--r--
ldap.elc	14.29 KB	-rw-r--r--
mairix.elc	24.37 KB	-rw-r--r--
net-utils.elc	25.21 KB	-rw-r--r--
netrc.elc	4.79 KB	-rw-r--r--
newst-backend.elc	66.66 KB	-rw-r--r--
newst-plainview.elc	51.17 KB	-rw-r--r--
newst-reader.elc	28.81 KB	-rw-r--r--
newst-ticker.elc	7.82 KB	-rw-r--r--
newst-treeview.elc	67.9 KB	-rw-r--r--
newsticker.elc	1.01 KB	-rw-r--r--
ntlm.elc	12.39 KB	-rw-r--r--
quickurl.elc	16.54 KB	-rw-r--r--
rcirc.elc	89.27 KB	-rw-r--r--
rcompile.elc	3.51 KB	-rw-r--r--
rlogin.elc	10.63 KB	-rw-r--r--
sasl-cram.elc	1.25 KB	-rw-r--r--
sasl-digest.elc	3.75 KB	-rw-r--r--
sasl-ntlm.elc	1.82 KB	-rw-r--r--
sasl.elc	7.39 KB	-rw-r--r--
snmp-mode.elc	15.08 KB	-rw-r--r--
socks.elc	16.21 KB	-rw-r--r--
telnet.elc	9.03 KB	-rw-r--r--
tls.elc	8.04 KB	-rw-r--r--
tramp-cache.elc	8.96 KB	-rw-r--r--
tramp-cmds.elc	9.4 KB	-rw-r--r--
tramp-compat.elc	6 KB	-rw-r--r--
tramp-fish.elc	54.2 KB	-rw-r--r--
tramp-ftp.elc	5.33 KB	-rw-r--r--
tramp-gw.elc	13.27 KB	-rw-r--r--
tramp-smb.elc	50.78 KB	-rw-r--r--
tramp-uu.elc	1.88 KB	-rw-r--r--
tramp.elc	278.99 KB	-rw-r--r--
trampver.elc	1.06 KB	-rw-r--r--
webjump.elc	13.86 KB	-rw-r--r--
xesam.elc	24.5 KB	-rw-r--r--
zeroconf.elc	17.98 KB	-rw-r--r--

Code Editor : eudc-vars.elc

;ELC���
;;; Compiled by mockbuild@c6b8.bsys.dev.centos.org on Thu Feb 19 13:04:31 2015
;;; from file /builddir/build/BUILD/emacs-23.1/lisp/net/eudc-vars.el
;;; in Emacs version 23.1.1
;;; with all optimizations.

;;; This file uses dynamic docstrings, first added in Emacs 19.29.
(if (and (boundp 'emacs-version)
	 (< (aref emacs-version (1- (length emacs-version))) ?A)
	 (or (and (boundp 'epoch::version) epoch::version)
	     (string-lessp emacs-version "19.29")))
    (error "`eudc-vars.el' was compiled for Emacs 19.29 or later"))

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

(byte-code "\300\301!\210\302\303\304\305\306\307\310\311\312\313\312\314&\207" [require custom custom-declare-group eudc nil "Emacs Unified Directory Client." :version "21.1" :link (info-link "(eudc)") :group mail comm] 12)
#@224 *The name or IP address of the directory server.
A port number may be specified by appending a colon and a
number to the name of the server.  Use `localhost' if the directory
server resides on your computer (BBDB backend).
(custom-declare-variable 'eudc-server 'nil '(#$ . -840) :type '(choice (string :tag "Server") (const :tag "None" nil)) :group 'eudc)
(byte-code "\301B\302\301!\204�\303\301\304\"\210\301\207" [current-load-list eudc-known-protocols default-boundp set-default (bbdb ph ldap)] 3)
#@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 (#$ . 1351))
#@118 *The directory protocol to use to query the server.
Supported protocols are specified by `eudc-supported-protocols'.
(custom-declare-variable 'eudc-protocol 'nil '(#$ . -1543) :type (byte-code "\301\302\303\304\305\306\"\307\"BBB\207" [eudc-known-protocols choice :menu-tag "Protocol" append mapcar #[(s) "\301\302\303!F\207" [s const :tag symbol-name] 4] ((const :tag "None" nil))] 7) :group 'eudc)
#@112 *Ignore or allow entries not containing all requested return attributes.
If non-nil, such entries are ignored.
(custom-declare-variable 'eudc-strict-return-matches 't '(#$ . -1953) :type 'boolean :group 'eudc)
#@197 *A list of default attributes to extract from directory entries.
If set to the symbol `all', return all attributes.
A value of nil means return the default attributes as configured in the
server.
(custom-declare-variable 'eudc-default-return-attributes 'nil '(#$ . -2170) :type '(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"))) :group 'eudc)
#@277 *What to do when multiple entries match an inline expansion query.
Possible values are:
`first' (equivalent to nil) which means keep the first match only,
`select' pop-up a selection buffer,
`all' expand to all matches,
`abort' the operation is aborted, an error is signaled.
(custom-declare-variable 'eudc-multiple-match-handling-method ''select '(#$ . -2685) :type '(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)) :group 'eudc)
#@560 *A method to handle entries containing duplicate attributes.
This is either an alist (ATTR . METHOD) or a symbol METHOD.
The alist form of the variable associates a method to an individual attribute,
the second form specifies a method applicable to all attributes.
Available methods are:
`list' or nil lets the value of the attribute be a list of values,
`first' keeps the first value and discards the others,
`concat' concatenates the values into a single multiline string,
`duplicate' duplicates the entire entry into as many instances as
different values.
(custom-declare-variable 'eudc-duplicate-attribute-handling-method ''((email . duplicate)) '(#$ . -3414) :type '(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))))) :group 'eudc)
#@650 *Format of an inline expansion query.
This is a list of FORMATs.  A FORMAT is itself a list of one or more
EUDC attribute names.  A FORMAT applies if it contains as many attributes as
there are individual words in the inline query string.
If several FORMATs apply then they are tried in order until a match
is found.
If nil, all the words are mapped onto the default server or protocol
attribute name.

The attribute names in FORMATs are not restricted to EUDC attribute names
but can also be protocol/server specific names.  In this case, this variable
must be set in a protocol/server-local fashion, see `eudc-server-set' and
`eudc-protocol-set'.
(custom-declare-variable 'eudc-inline-query-format ''((name) (firstname name)) '(#$ . -4595) :tag "Format of Inline Expansion Queries" :type '(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")))) :group 'eudc)
#@61 *If non-nil, expanding a query overwrites the query string.
(custom-declare-variable 'eudc-expansion-overwrites-query 't '(#$ . -5745) :type 'boolean :group 'eudc)
#@328 *A list specifying the format of the expansion of inline queries.
This variable controls what `eudc-expand-inline' actually inserts in
the buffer.  First element is a string passed to `format'.  Remaining
elements are symbols indicating attribute names; the corresponding values
are passed as additional arguments to `format'.
(custom-declare-variable 'eudc-inline-expansion-format ''("%s" email) '(#$ . -5916) :type '(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")))) :group 'eudc)
#@279 *Which servers to contact for the expansion of inline queries.
Possible values are:
  `current-server': the EUDC current server.
  `hotlist': the servers of the hotlist in the order they appear,
  `server-then-hotlist': the current server and then the servers of
  the hotlist.
(custom-declare-variable 'eudc-inline-expansion-servers ''server-then-hotlist '(#$ . -6726) :type '(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)) :group 'eudc)
#@136 *Maximum number of servers to query for an inline expansion.
If nil, query all servers available from `eudc-inline-expansion-servers'.
(custom-declare-variable 'eudc-max-servers-to-query 'nil '(#$ . -7337) :tag "Max Number of Servers to Query" :type '(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")) :group 'eudc)
#@52 *A list of attributes presented in the query form.
(custom-declare-variable 'eudc-query-form-attributes ''(name firstname email phone) '(#$ . -7841) :tag "Attributes in Query Forms" :type '(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"))) :group 'eudc)
#@321 *Alist of user-defined names for directory attributes.
These names are used as prompt strings in query/response forms
instead of the raw directory attribute names.
Prompt strings for attributes that are not listed here
are derived by splitting the attribute name
at `_' characters and capitalizing the individual words.
(custom-declare-variable '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")) '(#$ . -8348) :tag "User-defined Names of Directory Attributes" :type '(repeat (cons :tag "Field" (symbol :tag "Directory attribute") (string :tag "User friendly name "))) :group 'eudc)
#@185 *If non-nil, use attributes names as defined in the directory.
Otherwise, directory query/response forms display the user attribute
names defined in `eudc-user-attribute-names-alist'.
(custom-declare-variable 'eudc-use-raw-directory-names 'nil '(#$ . -9342) :type 'boolean :group 'eudc)
#@368 *An alist specifying methods to display attribute values.
Each member of the list is of the form (NAME . FUNC) where NAME is a lowercased
string naming a directory attribute (translated according to
`eudc-user-attribute-names-alist' if `eudc-use-raw-directory-names' is
non-nil) and FUNC a function that will be passed the corresponding
attribute values for display.
(custom-declare-variable 'eudc-attribute-display-method-alist 'nil '(#$ . -9636) :tag "Attribute Decoding Functions" :type '(repeat (cons :tag "Attribute" (symbol :tag "Name") (symbol :tag "Display Function"))) :group 'eudc)
#@375 *A list of viewer program specifications.
Viewers are programs which can be piped a directory attribute value for
display or arbitrary processing.  Each specification is a list whose
first element is a string naming the viewer.  The second element is the
executable program which should be invoked, and following elements are
arguments that should be passed to the program.
(custom-declare-variable 'eudc-external-viewers ''(("ImageMagick" "display" "-") ("ShowAudio" "showaudio")) '(#$ . -10235) :tag "External Viewer Programs" :type '(repeat (list :tag "Viewer" (string :tag "Name") (string :tag "Executable program") (repeat :tag "Arguments" :inline t (string :tag "Argument")))) :group 'eudc)
#@48 *A file where the `servers' hotlist is stored.
(custom-declare-variable 'eudc-options-file '"~/.eudc-options" '(#$ . -10938) :type '(file :Tag "File Name:") :group 'eudc)
#@41 *Normal hook run on entry to EUDC mode.
(custom-declare-variable 'eudc-mode-hook 'nil '(#$ . -11115) :type '(repeat (sexp :tag "Hook definition")) :group 'eudc)
(custom-declare-group 'eudc-ph nil "Emacs Unified Directory Client - CCSO PH/QI Backend." :group 'eudc)
#@1010 *A mapping from BBDB to PH/QI fields.
This is a list of cons cells (BBDB-FIELD . SPEC-OR-LIST) where
BBDB-FIELD is the name of a field that must be defined in your BBDB
environment (standard field names are `name', `company', `net', `phone',
`address' and `notes').  SPEC-OR-LIST is either a single SPEC or a list
of SPECs.  Lists of specs are valid only for the `phone' and `address'
BBDB fields.  SPECs are sexps which are evaluated:
  a string evaluates to itself,
  a symbol evaluates to the symbol value.  Symbols naming PH/QI fields
    present in the record evaluate to the value of the field in the record,
  a form is evaluated as a function.  The argument list may contain PH/QI
    field names which eval to the corresponding values in the
    record.  The form evaluation should return something appropriate for
    the particular BBDB-FIELD (see `bbdb-create-internal').
    `eudc-bbdbify-phone' and `eudc-bbdbify-address' are provided as convenience
    functions to parse phones and addresses.
(custom-declare-variable '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"))) '(#$ . -11388) :tag "BBDB to PH Field Name Mapping" :type '(repeat (cons :tag "Field Name" (symbol :tag "BBDB Field") (sexp :tag "Conversion Spec"))) :group 'eudc-ph)
(custom-declare-group 'eudc-ldap nil "Emacs Unified Directory Client - LDAP Backend." :group 'eudc)
#@1015 *A mapping from BBDB to LDAP attributes.
This is a list of cons cells (BBDB-FIELD . SPEC-OR-LIST) where
BBDB-FIELD is the name of a field that must be defined in your BBDB
environment (standard field names are `name', `company', `net', `phone',
`address' and `notes').  SPEC-OR-LIST is either a single SPEC or a list
of SPECs.  Lists of specs are valid only for the `phone' and `address'
BBDB fields.  SPECs are sexps which are evaluated:
  a string evaluates to itself,
  a symbol evaluates to the symbol value.  Symbols naming LDAP attributes
    present in the record evaluate to the value of the field in the record,
  a form is evaluated as a function.  The argument list may contain LDAP
    field names which eval to the corresponding values in the
    record.  The form evaluation should return something appropriate for
    the particular BBDB-FIELD (see `bbdb-create-internal').
    `eudc-bbdbify-phone' and `eudc-bbdbify-address' are provided as convenience
    functions to parse phones and addresses.
(custom-declare-variable 'eudc-ldap-bbdb-conversion-alist ''((name . cn) (net . mail) (address eudc-bbdbify-address postaladdress "Address") (phone (eudc-bbdbify-phone telephonenumber "Phone"))) '(#$ . -12901) :tag "BBDB to LDAP Attribute Names Mapping" :type '(repeat (cons :tag "Field Name" (symbol :tag "BBDB Field") (sexp :tag "Conversion Spec"))) :group 'eudc-ldap)
(custom-declare-group 'eudc-bbdb nil "Emacs Unified Directory Client - BBDB Backend." :group 'eudc)
#@194 If non-nil, BBDB address and phone locations are used as attribute names.
This has no effect on queries (you can't search for a specific location)
but influences the way records are displayed.
(custom-declare-variable 'eudc-bbdb-use-locations-as-attribute-names 't '(#$ . 14393) :type 'boolean :group 'eudc-bbdb)
#@112 If non-nil, authorize substring match in the same way BBDB does.
Otherwise records must match queries exactly.
(custom-declare-variable 'eudc-bbdb-enable-substring-matches 't '(#$ . 14713) :type 'boolean :group 'eudc-bbdb)
(provide 'eudc-vars)

${this.title}

Code Editor : eudc-vars.elc