Linux ns8.secondary29.go.th 2.6.32-754.28.1.el6.x86_64 #1 SMP Wed Mar 11 18:38:45 UTC 2020 x86_64
Apache/2.2.15 (CentOS)
: 122.154.134.11 | : 122.154.134.9
Cant Read [ /etc/named.conf ]
5.6.40
apache
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
emacs /
23.1 /
lisp /
mh-e /
[ HOME SHELL ]
Name
Size
Permission
Action
mh-acros.el
12.65
KB
-rw-r--r--
mh-alias.elc
17.61
KB
-rw-r--r--
mh-buffers.elc
2.74
KB
-rw-r--r--
mh-comp.elc
33.6
KB
-rw-r--r--
mh-compat.el
12.07
KB
-rw-r--r--
mh-e.elc
113.81
KB
-rw-r--r--
mh-folder.elc
61.68
KB
-rw-r--r--
mh-funcs.elc
12.23
KB
-rw-r--r--
mh-gnus.el
6.07
KB
-rw-r--r--
mh-identity.elc
7.9
KB
-rw-r--r--
mh-inc.elc
2.11
KB
-rw-r--r--
mh-junk.elc
15.3
KB
-rw-r--r--
mh-letter.elc
27.93
KB
-rw-r--r--
mh-limit.elc
10.43
KB
-rw-r--r--
mh-loaddefs.el
103.32
KB
-rw-r--r--
mh-mime.elc
55.16
KB
-rw-r--r--
mh-print.elc
8.59
KB
-rw-r--r--
mh-scan.elc
16.45
KB
-rw-r--r--
mh-search.elc
59.54
KB
-rw-r--r--
mh-seq.elc
37.48
KB
-rw-r--r--
mh-show.elc
130.77
KB
-rw-r--r--
mh-speed.elc
16.67
KB
-rw-r--r--
mh-thread.elc
43.78
KB
-rw-r--r--
mh-tool-bar.elc
26.7
KB
-rw-r--r--
mh-utils.elc
28.26
KB
-rw-r--r--
mh-xface.elc
14
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : mh-scan.elc
;ELC ;;; Compiled by mockbuild@c6b8.bsys.dev.centos.org on Thu Feb 19 13:04:25 2015 ;;; from file /builddir/build/BUILD/emacs-23.1/lisp/mh-e/mh-scan.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 "`mh-scan.el' was compiled for Emacs 19.29 or later")) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (require 'mh-e) #@561 *Scan format string for MH. This string is passed to the scan program via the -format argument. This format is identical to the default except that additional hints for fontification have been added to the fifth column (remember that in Emacs, the first column is 0). The values of the fifth column, in priority order, are: "-" if the message has been replied to, t if an address on the To: line matches one of the mailboxes of the current user, "c" if the Cc: line matches, "b" if the Bcc: line matches, and "n" if a non-empty Newsgroups: header is present. (defvar mh-scan-format-mh "%4(msg)%<(cur)+%| %>%<{replied}-%?(nonnull(comp{to}))%<(mymbox{to})t%>%?(nonnull(comp{cc}))%<(mymbox{cc})c%>%?(nonnull(comp{bcc}))%<(mymbox{bcc})b%>%?(nonnull(comp{newsgroups}))n%>%<(zero) %>%02(mon{date})/%02(mday{date})%<{date} %|*%>%<(mymbox{from})%<{to}To:%14(friendly{to})%>%>%<(zero)%17(friendly{from})%> %{subject}%<{body}<<%{body}%>" (#$ . -627)) #@559 *Scan format string for nmh. This string is passed to the scan program via the -format arg. This format is identical to the default except that additional hints for fontification have been added to the fifth column (remember that in Emacs, the first column is 0). The values of the fifth column, in priority order, are: "-" if the message has been replied to, t if an address on the To: field matches one of the mailboxes of the current user, "c" if the Cc: field matches, "b" if the Bcc: field matches, and "n" if a non-empty Newsgroups: field is present. (defvar mh-scan-format-nmh "%4(msg)%<(cur)+%| %>%<{replied}-%?(nonnull(comp{to}))%<(mymbox{to})t%>%?(nonnull(comp{cc}))%<(mymbox{cc})c%>%?(nonnull(comp{bcc}))%<(mymbox{bcc})b%>%?(nonnull(comp{newsgroups}))n%>%<(zero) %>%02(mon{date})/%02(mday{date})%<{date} %|*%>%<(mymbox{from})%<{to}To:%14(decode(friendly{to}))%>%>%<(zero)%17(decode(friendly{from}))%> %(decode{subject})%<{body}<<%{body}%>" (#$ . -1577)) #@389 This regular expression matches the message body fragment. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the body text as in the default of "\\(<<\\([^\n]+\\)?\\)". If this regular expression is not correct, the body fragment will not be highlighted with the face `mh-folder-body'. (defvar mh-scan-body-regexp "\\(<<\\([^\n]+\\)?\\)" (#$ . 2551)) #@654 This regular expression matches the current message. It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of "^\\( *[0-9]+\\+\\).*". This expression includes the leading space and current message marker "+" within the parenthesis since it looks better to highlight these items as well. The highlighting is done with the face `mh-folder-cur-msg-number'. This regular expression should be correct as it is needed by non-fontification functions. See also `mh-note-cur'. (defvar mh-scan-cur-msg-number-regexp "^\\( *[0-9]+\\+\\).*" (#$ . 3011)) #@436 This regular expression matches a valid date. It must not be anchored to the beginning or the end of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain only one parenthesized expression which matches the date field as in the default of "\\([0-9][0-9]/[0-9][0-9]\\)"}. If this regular expression is not correct, the date will not be highlighted with the face `mh-folder-date'. (defvar mh-scan-date-regexp "\\([0-9][0-9]/[0-9][0-9]\\)" (#$ . 3745)) #@604 This regular expression matches deleted messages. It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of "^\\( *[0-9]+\\)D". This expression includes the leading space within the parenthesis since it looks better to highlight it as well. The highlighting is done with the face `mh-folder-deleted'. This regular expression should be correct as it is needed by non-fontification functions. See also `mh-note-deleted'. (defvar mh-scan-deleted-msg-regexp "^\\( *[0-9]+\\)D" (#$ . 4258)) #@585 This regular expression matches "good" messages. It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of "^\\( *[0-9]+\\)[^D^0-9]". This expression includes the leading space within the parenthesis since it looks better to highlight it as well. The highlighting is done with the face `mh-folder-msg-number'. This regular expression should be correct as it is needed by non-fontification functions. (defvar mh-scan-good-msg-regexp "^\\( *[0-9]+\\)[^D^0-9]" (#$ . 4935)) #@283 This regular expression finds the message number width in a scan format. Note that the message number must be placed in a parenthesized expression as in the default of "%\\([0-9]*\\)(msg)". This variable is only consulted if `mh-scan-format-file' is set to "Use MH-E scan Format". (defvar mh-scan-msg-format-regexp "%\\([0-9]*\\)(msg)" (#$ . 5597)) #@210 This is a format string for width of the message number in a scan format. Use "0%d" for zero-filled message numbers. This variable is only consulted if `mh-scan-format-file' is set to "Use MH-E scan Format". (defvar mh-scan-msg-format-string "%d" (#$ . 5954)) #@215 This regular expression extracts the message number. It must match from the beginning of the line. Note that the message number must be placed in a parenthesized expression as in the default of "^ *\\([0-9]+\\)". (defvar mh-scan-msg-number-regexp "^ *\\([0-9]+\\)" (#$ . 6222)) #@61 This regular expression matches overflowed message numbers. (defvar mh-scan-msg-overflow-regexp "^[?0-9][0-9]" (#$ . 6507)) #@199 This regular expression matches a particular message. It is a format string; use "%d" to represent the location of the message number within the expression as in the default of "^[^0-9]*%d[^0-9]". (defvar mh-scan-msg-search-regexp "^[^0-9]*%d[^0-9]" (#$ . 6638)) #@584 This regular expression specifies the recipient in messages you sent. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain two parenthesized expressions. The first is expected to match the "To:" that the default scan format file generates. The second is expected to match the recipient's name as in the default of "\\(To:\\)\\(..............\\)". If this regular expression is not correct, the "To:" string will not be highlighted with the face `mh-folder-to' and the recipient will not be highlighted with the face `mh-folder-address' (defvar mh-scan-rcpt-regexp "\\(To:\\)\\(..............\\)" (#$ . 6909)) #@606 This regular expression matches refiled messages. It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of "^\\( *[0-9]+\\)\\^". This expression includes the leading space within the parenthesis since it looks better to highlight it as well. The highlighting is done with the face `mh-folder-refiled'. This regular expression should be correct as it is needed by non-fontification functions. See also `mh-note-refiled'. (defvar mh-scan-refiled-msg-regexp "^\\( *[0-9]+\\)\\^" (#$ . 7572)) #@604 This regular expression matches messages sent to us. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least two parenthesized expressions. The first should match the fontification hint (see `mh-scan-format-nmh') and the second should match the user name as in the default of ^ *[0-9]+.\\([bct]\\).....[ ]*\\(..................\\) If this regular expression is not correct, the notation hints will not be highlighted with the face `mh-mh-folder-sent-to-me-hint' and the sender will not be highlighted with the face `mh-folder-sent-to-me-sender'. (defvar mh-scan-sent-to-me-sender-regexp "^ *[0-9]+.\\([bct]\\).....[ ]*\\(..................\\)" (#$ . 8253)) #@864 This regular expression matches the subject. It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least three parenthesized expressions. The first is expected to match the "Re:" string, if any, and is highlighted with the face `mh-folder-followup'. The second matches an optional bracketed number after "Re:", such as in "Re[2]:" (and is thus a sub-expression of the first expression) and the third is expected to match the subject line itself which is highlighted with the face `mh-folder-subject'. For example, the default (broken on multiple lines for readability) is ^ *[0-9]+........[ ]*................... \\([Rr][Ee]\\(\\\=[[0-9]+\\]\\)?:\\s-*\\)* \\([^<\n]*\\) This regular expression should be correct as it is needed by non-fontification functions. (defvar mh-scan-subject-regexp "^ *[0-9]+........[ ]*...................\\([Rr][Ee]\\(\\[[0-9]+\\]\\)?:\\s-*\\)*\\([^<\n]*\\)" (#$ . 8974)) #@137 This regular expression describes a valid scan line. This is used to eliminate error messages that are occasionally produced by "inc". (defvar mh-scan-valid-regexp "^ *[0-9]" (#$ . 9984)) #@210 Column for notations. This variable should be set with the function `mh-set-cmd-note'. This variable may be updated dynamically if `mh-adaptive-cmd-note-flag' is on. Note that columns in Emacs start with 0. (defvar mh-cmd-note 4 (#$ . 10180)) (make-variable-buffer-local 'mh-cmd-note) #@295 Number of columns consumed by the cmd-note field in `mh-scan-format'. This column will have one of the values: " ", "D", "^", "+" and where " " is the default value, "D" is the `mh-note-deleted' character, "^" is the `mh-note-refiled' character, and "+" is the `mh-note-cur' character. (defvar mh-scan-cmd-note-width 1 (#$ . 10474)) #@592 Number of columns consumed by the destination field in `mh-scan-format'. This column will have one of " ", "%", "-", "t", "c", "b", or "n" in it. " " blank space is the default character. "%" indicates that the message in in a named MH sequence. "-" indicates that the message has been annotated with a replied field. "t" indicates that the message contains mymbox in the To: field. "c" indicates that the message contains mymbox in the Cc: field. "b" indicates that the message contains mymbox in the Bcc: field. "n" indicates that the message contains a Newsgroups: field. (defvar mh-scan-destination-width 1 (#$ . 10822)) #@116 Number of columns consumed by the date field in `mh-scan-format'. This column will typically be of the form mm/dd. (defvar mh-scan-date-width 5 (#$ . 11470)) #@147 Number of columns consumed to flag (in)valid dates in `mh-scan-format'. This column will have " " for valid and "*" for invalid or missing dates. (defvar mh-scan-date-flag-width 1 (#$ . 11635)) #@195 Number of columns consumed with the "From:" line in `mh-scan-format'. This column will have a friendly name or e-mail address of the originator, or a "To: address" for outgoing e-mail messages. (defvar mh-scan-from-mbox-width 17 (#$ . 11836)) #@125 Number of columns consumed by whitespace after from-mbox in `mh-scan-format'. This column will only ever have spaces in it. (defvar mh-scan-from-mbox-sep-width 2 (#$ . 12086)) #@63 The offset from the `mh-cmd-note' for the destination column. (defvar mh-scan-field-destination-offset (+ mh-scan-cmd-note-width 0) (#$ . 12268)) #@73 The offset from the `mh-cmd-note' to find the start of "From:" address. (defvar mh-scan-field-from-start-offset (+ mh-scan-cmd-note-width mh-scan-destination-width mh-scan-date-width mh-scan-date-flag-width) (#$ . 12420)) #@71 The offset from the `mh-cmd-note' to find the end of "From:" address. (defvar mh-scan-field-from-end-offset (+ mh-scan-field-from-start-offset mh-scan-from-mbox-width) (#$ . 12648)) #@69 The offset from the `mh-cmd-note' to find the start of the subject. (defvar mh-scan-field-subject-start-offset (+ mh-scan-cmd-note-width mh-scan-destination-width mh-scan-date-width mh-scan-date-flag-width mh-scan-from-mbox-width mh-scan-from-mbox-sep-width) (#$ . 12836)) #@113 The current message (in MH, not in MH-E) is marked by this character. See also `mh-scan-cur-msg-number-regexp'. (defvar mh-note-cur 43 (#$ . 13116)) #@62 Messages that have been copied are marked by this character. (defvar mh-note-copied 67 (#$ . 13271)) #@102 Messages that have been deleted are marked by this character. See also `mh-scan-deleted-msg-regexp'. (defvar mh-note-deleted 68 (#$ . 13379)) #@69 Messages that have been redistributed are marked by this character. (defvar mh-note-dist 82 (#$ . 13527)) #@65 Messages that have been forwarded are marked by this character. (defvar mh-note-forw 70 (#$ . 13639)) #@63 Messages that have been printed are marked by this character. (defvar mh-note-printed 80 (#$ . 13747)) #@102 Messages that have been refiled are marked by this character. See also `mh-scan-refiled-msg-regexp'. (defvar mh-note-refiled 94 (#$ . 13857)) #@66 Messages that have been replied to are marked by this character. (defvar mh-note-repl 45 (#$ . 14005)) #@140 Messages in a user-defined sequence are marked by this character. Messages in the "search" sequence are marked by this character as well. (defvar mh-note-seq 37 (#$ . 14115)) #@55 Return value of variable `mh-scan-msg-number-regexp'. (defalias 'mh-scan-msg-number-regexp #[nil "\207" [mh-scan-msg-number-regexp] 1 (#$ . 14297)]) #@55 Return value of variable `mh-scan-msg-search-regexp'. (defalias 'mh-scan-msg-search-regexp #[nil "\207" [mh-scan-msg-search-regexp] 1 (#$ . 14453)]) #@71 Set `mh-cmd-note' to COLUMN. Note that columns in Emacs start with 0. (defalias 'mh-set-cmd-note #[(column) "\211\207" [column mh-cmd-note] 2 (#$ . 14609)]) #@57 Return the output format argument for the scan program. (defalias 'mh-scan-format #[nil "\304\232\203 \305\306\307\310\"\203 \311 \n\"C\202 \311 \n\"CD\207\312\232?\205' \313D\207" [mh-scan-format-file mh-scan-format-nmh mh-cmd-note mh-scan-format-mh t "-format" mh-variant-p nmh gnu-mh mh-update-scan-format nil "-form"] 4 (#$ . 14774)]) #@236 Return a scan format with the (msg) width in the FMT replaced with WIDTH. The message number width portion of the format is discovered using `mh-scan-msg-format-regexp'. Its replacement is controlled with `mh-scan-msg-format-string'. (defalias 'mh-update-scan-format #[(fmt width) "\306 \"\203 \307\224\307\225 \310 O\311\f \" \n\312OQ*\206 \207" [mh-scan-msg-format-regexp fmt end begin mh-scan-msg-format-string width string-match 1 0 format nil] 5 (#$ . 15126)]) #@64 Return the width of the largest message number in this FOLDER. (defalias 'mh-msg-num-width #[(folder) "\204 \306 \210\307 !\310\212 q\210\311 \210\312\313\314\f\"\315\316\315 \317\320\321F&\210eb\210\322\315\310\323$\2039 \323\224\323\225{G)\n*\207" [mh-progs mh-temp-buffer width tmp-buffer mh-scan-prog folder mh-find-path get-buffer-create 0 erase-buffer apply call-process expand-file-name nil (t nil) "last" "-format" "%(msg)" re-search-forward 1 mh-scan-msg-number-regexp] 10 (#$ . 15605)]) #@440 Return the column for notations given message number WIDTH. Note that columns in Emacs start with 0. If `mh-scan-format-file' is set to "Use MH-E scan Format" this means that either `mh-scan-format-mh' or `mh-scan-format-nmh' are in use. This function therefore assumes that the first column is empty (to provide room for the cursor), the following WIDTH columns contain the message number, and the column for notations comes after that. (defalias 'mh-msg-num-width-to-column #[(width) "\302=\203 T\303]\207\304\305\306\307#\207" [mh-scan-format-file width t 2 error "%s %s" "Can't call `mh-msg-num-width-to-column' when" "`mh-scan-format-file' is not set to \"Use MH-E scan Format\""] 4 (#$ . 16118)]) (provide 'mh-scan)
Close
