mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-15 18:40:39 -08:00
; Minor stylistic fixes found by checkdoc
This commit is contained in:
parent
36474a1e49
commit
63f419f133
326 changed files with 1158 additions and 1180 deletions
|
|
@ -230,7 +230,7 @@
|
|||
;;
|
||||
;; 1. For dired to work on a host which marks symlinks with a trailing @ in
|
||||
;; an ls -alF listing, you need to (setq dired-ls-F-marks-symlinks t).
|
||||
;; Most UNIX systems do not do this, but ULTRIX does. If you think that
|
||||
;; Most UNIX systems do not do this, but ULTRIX does. If you think that
|
||||
;; there is a chance you might connect to an ULTRIX machine (such as
|
||||
;; prep.ai.mit.edu), then set this variable accordingly. This will have
|
||||
;; the side effect that dired will have problems with symlinks whose names
|
||||
|
|
@ -241,34 +241,34 @@
|
|||
;; frequently, and ange-ftp seems to be unable to guess its host-type,
|
||||
;; then setting the appropriate host-type regexp
|
||||
;; (ange-ftp-vms-host-regexp, ange-ftp-mts-host-regexp, or
|
||||
;; ange-ftp-cms-host-regexp) accordingly should help. Also, please report
|
||||
;; ange-ftp-cms-host-regexp) accordingly should help. Also, please report
|
||||
;; ange-ftp's inability to recognize the host-type as a bug.
|
||||
;;
|
||||
;; 3. For slow connections, you might get "listing unreadable" error
|
||||
;; messages, or get an empty buffer for a file that you know has something
|
||||
;; in it. The solution is to increase the value of ange-ftp-retry-time.
|
||||
;; in it. The solution is to increase the value of ange-ftp-retry-time.
|
||||
;; Its default value is 5 which is plenty for reasonable connections.
|
||||
;; However, for some transatlantic connections I set this to 20.
|
||||
;;
|
||||
;; 4. Beware of compressing files on non-UNIX hosts. Ange-ftp will do it by
|
||||
;; 4. Beware of compressing files on non-UNIX hosts. Ange-ftp will do it by
|
||||
;; copying the file to the local machine, compressing it there, and then
|
||||
;; sending it back. Binary file transfers between machines of different
|
||||
;; architectures can be a risky business. Test things out first on some
|
||||
;; test files. See "Bugs" below. Also, note that ange-ftp copies files by
|
||||
;; moving them through the local machine. Again, be careful when doing
|
||||
;; sending it back. Binary file transfers between machines of different
|
||||
;; architectures can be a risky business. Test things out first on some
|
||||
;; test files. See "Bugs" below. Also, note that ange-ftp copies files by
|
||||
;; moving them through the local machine. Again, be careful when doing
|
||||
;; this with binary files on non-Unix machines.
|
||||
;;
|
||||
;; 5. Beware that dired over ftp will use your setting of dired-no-confirm
|
||||
;; (list of dired commands for which confirmation is not asked). You
|
||||
;; might want to reconsider your setting of this variable, because you
|
||||
;; might want confirmation for more commands on remote direds than on
|
||||
;; local direds. For example, I strongly recommend that you not include
|
||||
;; compress and uncompress in this list. If there is enough demand it
|
||||
;; local direds. For example, I strongly recommend that you not include
|
||||
;; compress and uncompress in this list. If there is enough demand it
|
||||
;; might be a good idea to have an alist ange-ftp-dired-no-confirm of
|
||||
;; pairs ( TYPE . LIST ), where TYPE is an operating system type and LIST
|
||||
;; is a list of commands for which confirmation would be suppressed. Then
|
||||
;; remote dired listings would take their (buffer-local) value of
|
||||
;; dired-no-confirm from this alist. Who votes for this?
|
||||
;; dired-no-confirm from this alist. Who votes for this?
|
||||
|
||||
;; ---------------------------------------------------------------------
|
||||
;; Non-UNIX support:
|
||||
|
|
@ -277,7 +277,7 @@
|
|||
;; VMS support:
|
||||
;;
|
||||
;; Ange-ftp has full support for VMS hosts. It should be able to
|
||||
;; automatically recognize any VMS machine. However, if it fails to do
|
||||
;; automatically recognize any VMS machine. However, if it fails to do
|
||||
;; this, you can use the command ange-ftp-add-vms-host. Also, you can
|
||||
;; set the variable ange-ftp-vms-host-regexp in your init file. We
|
||||
;; would be grateful if you would report any failures to automatically
|
||||
|
|
@ -308,46 +308,46 @@
|
|||
;; Therefore, to access a VMS file, you must enter the filename with upper
|
||||
;; case letters.
|
||||
;; 2. To access the latest version of file under VMS, you use the filename
|
||||
;; without the ";" and version number. You should always edit the latest
|
||||
;; version of a file. If you want to edit an earlier version, copy it to a
|
||||
;; new file first. This has nothing to do with ange-ftp, but is simply
|
||||
;; good VMS operating practice. Therefore, to edit FILE.TXT;3 (say 3 is
|
||||
;; latest version), do C-x C-f /ymir.claremont.edu:FILE.TXT. If you
|
||||
;; without the ";" and version number. You should always edit the latest
|
||||
;; version of a file. If you want to edit an earlier version, copy it to a
|
||||
;; new file first. This has nothing to do with ange-ftp, but is simply
|
||||
;; good VMS operating practice. Therefore, to edit FILE.TXT;3 (say 3 is
|
||||
;; latest version), do C-x C-f /ymir.claremont.edu:FILE.TXT. If you
|
||||
;; inadvertently do C-x C-f /ymir.claremont.edu:FILE.TXT;3, you will find
|
||||
;; that VMS will not allow you to save the file because it will refuse to
|
||||
;; overwrite FILE.TXT;3, but instead will want to create FILE.TXT;4, and
|
||||
;; attach the buffer to this file. To get out of this situation, M-x
|
||||
;; attach the buffer to this file. To get out of this situation, M-x
|
||||
;; write-file /ymir.claremont.edu:FILE.TXT will attach the buffer to
|
||||
;; latest version of the file. For this reason, in dired "f"
|
||||
;; latest version of the file. For this reason, in dired "f"
|
||||
;; (dired-find-file), always loads the file sans version, whereas "v",
|
||||
;; (dired-view-file), always loads the explicit version number. The
|
||||
;; (dired-view-file), always loads the explicit version number. The
|
||||
;; reasoning being that it reasonable to view old versions of a file, but
|
||||
;; not to edit them.
|
||||
;; 3. EMACS has a feature in which it does environment variable substitution
|
||||
;; in filenames. Therefore, to enter a $ in a filename, you must quote it
|
||||
;; in filenames. Therefore, to enter a $ in a filename, you must quote it
|
||||
;; by typing $$.
|
||||
|
||||
;; MTS support:
|
||||
;;
|
||||
;; Ange-ftp has full support for hosts running
|
||||
;; the Michigan terminal system. It should be able to automatically
|
||||
;; recognize any MTS machine. However, if it fails to do this, you can use
|
||||
;; recognize any MTS machine. However, if it fails to do this, you can use
|
||||
;; the command ange-ftp-add-mts-host. As well, you can set the variable
|
||||
;; ange-ftp-mts-host-regexp in your init file. We would be grateful if you
|
||||
;; ange-ftp-mts-host-regexp in your init file. We would be grateful if you
|
||||
;; would report any failures to automatically recognize a MTS host as a bug.
|
||||
;;
|
||||
;; Filename syntax:
|
||||
;;
|
||||
;; MTS filenames are entered in a UNIX-y way. For example, if your account
|
||||
;; MTS filenames are entered in a UNIX-y way. For example, if your account
|
||||
;; was YYYY, the file FILE in the account XXXX: on mtsg.ubc.ca would be
|
||||
;; entered as
|
||||
;; /YYYY@mtsg.ubc.ca:/XXXX:/FILE
|
||||
;; In other words, MTS accounts are treated as UNIX directories. Of course,
|
||||
;; In other words, MTS accounts are treated as UNIX directories. Of course,
|
||||
;; to access a file in another account, you must have access permission for
|
||||
;; it. If FILE were in your own account, then you could enter it in a
|
||||
;; relative name fashion as
|
||||
;; /YYYY@mtsg.ubc.ca:FILE
|
||||
;; MTS filenames can be up to 12 characters. Like UNIX, the structure of the
|
||||
;; MTS filenames can be up to 12 characters. Like UNIX, the structure of the
|
||||
;; filename does not contain a TYPE (i.e. it can have as many "."'s as you
|
||||
;; like.) MTS filenames are always in upper case, and hence be sure to enter
|
||||
;; them as such! MTS is not case sensitive, but an EMACS running under UNIX
|
||||
|
|
@ -359,37 +359,37 @@
|
|||
;; CMS. It should be able to automatically recognize any CMS machine.
|
||||
;; However, if it fails to do this, you can use the command
|
||||
;; ange-ftp-add-cms-host. As well, you can set the variable
|
||||
;; ange-ftp-cms-host-regexp in your init file. We would be grateful if you
|
||||
;; ange-ftp-cms-host-regexp in your init file. We would be grateful if you
|
||||
;; would report any failures to automatically recognize a CMS host as a bug.
|
||||
;;
|
||||
;; Filename syntax:
|
||||
;;
|
||||
;; CMS filenames are entered in a UNIX-y way. In other words, minidisks are
|
||||
;; treated as UNIX directories. For example to access the file READ.ME in
|
||||
;; CMS filenames are entered in a UNIX-y way. In other words, minidisks are
|
||||
;; treated as UNIX directories. For example to access the file READ.ME in
|
||||
;; minidisk *.311 on cuvmb.cc.columbia.edu, you would enter
|
||||
;; /anonymous@cuvmb.cc.columbia.edu:/*.311/READ.ME
|
||||
;; If *.301 is the default minidisk for this account, you could access
|
||||
;; FOO.BAR on this minidisk as
|
||||
;; /anonymous@cuvmb.cc.columbia.edu:FOO.BAR
|
||||
;; CMS filenames are of the form FILE.TYPE, where both FILE and TYPE can be
|
||||
;; up to 8 characters. Again, beware that CMS filenames are always upper
|
||||
;; up to 8 characters. Again, beware that CMS filenames are always upper
|
||||
;; case, and hence must be entered as such.
|
||||
;;
|
||||
;; Tips:
|
||||
;; 1. CMS machines, with the exception of anonymous accounts, nearly always
|
||||
;; need an account password. To have ange-ftp send an account password,
|
||||
;; need an account password. To have ange-ftp send an account password,
|
||||
;; you can either include it in your .netrc file, or use
|
||||
;; ange-ftp-set-account.
|
||||
;; 2. Ange-ftp cannot send "write passwords" for a minidisk. Hopefully, we
|
||||
;; 2. Ange-ftp cannot send "write passwords" for a minidisk. Hopefully, we
|
||||
;; can fix this.
|
||||
;;
|
||||
;; BS2000 support:
|
||||
;;
|
||||
;; Ange-ftp has full support for BS2000 hosts. It should be able to
|
||||
;; automatically recognize any BS2000 machine. However, if it fails to
|
||||
;; automatically recognize any BS2000 machine. However, if it fails to
|
||||
;; do this, you can use the command ange-ftp-add-bs2000-host. As well,
|
||||
;; you can set the variable ange-ftp-bs2000-host-regexp in your .emacs
|
||||
;; file. We would be grateful if you would report any failures to auto-
|
||||
;; file. We would be grateful if you would report any failures to auto-
|
||||
;; matically recognize a BS2000 host as a bug.
|
||||
;;
|
||||
;; If you want to access the POSIX subsystem on BS2000 you MUST use
|
||||
|
|
@ -436,10 +436,10 @@
|
|||
;; Therefore, to access a BS2000 file, you must enter the filename with
|
||||
;; upper case letters.
|
||||
;; 2. EMACS has a feature in which it does environment variable substitution
|
||||
;; in filenames. Therefore, to enter a $ in a filename, you must quote it
|
||||
;; in filenames. Therefore, to enter a $ in a filename, you must quote it
|
||||
;; by typing $$.
|
||||
;; 3. BS2000 machines, with the exception of anonymous accounts, nearly
|
||||
;; always need an account password. To have ange-ftp send an account
|
||||
;; always need an account password. To have ange-ftp send an account
|
||||
;; password, you can either include it in your .netrc file, or use
|
||||
;; ange-ftp-set-account.
|
||||
;;
|
||||
|
|
@ -457,15 +457,15 @@
|
|||
;;
|
||||
;; 2. Some combinations of FTP clients and servers break and get out of sync
|
||||
;; when asked to list a non-existent directory. Some of the ai.mit.edu
|
||||
;; machines cause this problem for some FTP clients. Using
|
||||
;; machines cause this problem for some FTP clients. Using
|
||||
;; ange-ftp-kill-ftp-process can restart the ftp process, which
|
||||
;; should get things back in sync.
|
||||
;;
|
||||
;; 3. Ange-ftp does not check to make sure that when creating a new file,
|
||||
;; you provide a valid filename for the remote operating system.
|
||||
;; If you do not, then the remote FTP server will most likely
|
||||
;; translate your filename in some way. This may cause ange-ftp to
|
||||
;; get confused about what exactly is the name of the file. The
|
||||
;; translate your filename in some way. This may cause ange-ftp to
|
||||
;; get confused about what exactly is the name of the file. The
|
||||
;; most common causes of this are using lower case filenames on systems
|
||||
;; which support only upper case, and using filenames which are too
|
||||
;; long.
|
||||
|
|
@ -479,39 +479,39 @@
|
|||
;; disgusting way around this problem is to talk to the FTP process via
|
||||
;; rlogin which does the 'right' things with pty's.
|
||||
;;
|
||||
;; 6. For CMS support, we send too many cd's. Since cd's are cheap, I haven't
|
||||
;; worried about this too much. Eventually, we should have some caching
|
||||
;; 6. For CMS support, we send too many cd's. Since cd's are cheap, I haven't
|
||||
;; worried about this too much. Eventually, we should have some caching
|
||||
;; of the current minidisk.
|
||||
;;
|
||||
;; 7. Some CMS machines do not assign a default minidisk when you ftp them as
|
||||
;; anonymous. It is then necessary to guess a valid minidisk name, and cd
|
||||
;; to it. This is (understandably) beyond ange-ftp.
|
||||
;; anonymous. It is then necessary to guess a valid minidisk name, and cd
|
||||
;; to it. This is (understandably) beyond ange-ftp.
|
||||
;;
|
||||
;; 8. Remote to remote copying of files on non-Unix machines can be risky.
|
||||
;; Depending on the variable ange-ftp-binary-file-name-regexp, ange-ftp
|
||||
;; will use binary mode for the copy. Between systems of different
|
||||
;; will use binary mode for the copy. Between systems of different
|
||||
;; architecture, this still may not be enough to guarantee the integrity
|
||||
;; of binary files. Binary file transfers from VMS machines are
|
||||
;; particularly problematical. Should ange-ftp-binary-file-name-regexp be
|
||||
;; of binary files. Binary file transfers from VMS machines are
|
||||
;; particularly problematical. Should ange-ftp-binary-file-name-regexp be
|
||||
;; an alist of OS type, regexp pairs?
|
||||
;;
|
||||
;; 9. The code to do compression of files over ftp is not as careful as it
|
||||
;; should be. It deletes the old remote version of the file, before
|
||||
;; should be. It deletes the old remote version of the file, before
|
||||
;; actually checking if the local to remote transfer of the compressed
|
||||
;; file succeeds. Of course to delete the original version of the file
|
||||
;; file succeeds. Of course to delete the original version of the file
|
||||
;; after transferring the compressed version back is also dangerous,
|
||||
;; because some OS's have severe restrictions on the length of filenames,
|
||||
;; and when the compressed version is copied back the "-Z" or ".Z" may be
|
||||
;; truncated. Then, ange-ftp would delete the only remaining version of
|
||||
;; truncated. Then, ange-ftp would delete the only remaining version of
|
||||
;; the file. Maybe ange-ftp should make backups when it compresses files
|
||||
;; (of course, the backup "~" could also be truncated off, sigh...).
|
||||
;; Suggestions?
|
||||
;;
|
||||
;; 10. If a dir listing is attempted for an empty directory on (at least
|
||||
;; some) VMS hosts, an ftp error is given. This is really an ftp bug, and
|
||||
;; some) VMS hosts, an ftp error is given. This is really an ftp bug, and
|
||||
;; I don't know how to get ange-ftp work to around it.
|
||||
;;
|
||||
;; 11. Bombs on filenames that start with a space. Deals well with filenames
|
||||
;; 11. Bombs on filenames that start with a space. Deals well with filenames
|
||||
;; containing spaces, but beware that the remote ftpd may not like them
|
||||
;; much.
|
||||
;;
|
||||
|
|
@ -519,13 +519,13 @@
|
|||
;; It needs to be reimplemented by modifying the parse-...-listing
|
||||
;; functions to convert the directory listing to ls -l format.
|
||||
;;
|
||||
;; 13. The famous @ bug. As mentioned above in TIPS, ULTRIX marks symlinks
|
||||
;; with a trailing @ in a ls -alF listing. In order to account for this
|
||||
;; 13. The famous @ bug. As mentioned above in TIPS, ULTRIX marks symlinks
|
||||
;; with a trailing @ in a ls -alF listing. In order to account for this
|
||||
;; ange-ftp looks to chop trailing @'s off of symlink names when it is
|
||||
;; parsing a listing with the F switch. This will cause ange-ftp to
|
||||
;; parsing a listing with the F switch. This will cause ange-ftp to
|
||||
;; incorrectly get the name of a symlink on a non-ULTRIX host if its name
|
||||
;; ends in an @. ange-ftp will correct itself if you take F out of the
|
||||
;; dired ls switches (C-u s will allow you to edit the switches). The
|
||||
;; ends in an @. ange-ftp will correct itself if you take F out of the
|
||||
;; dired ls switches (C-u s will allow you to edit the switches). The
|
||||
;; dired buffer will be automatically reverted, which will allow ange-ftp
|
||||
;; to fix its files hashtable. A cookie to anyone who can think of a
|
||||
;; fast, sure-fire way to recognize ULTRIX over ftp.
|
||||
|
|
@ -576,26 +576,26 @@
|
|||
;; and the current code should eventually be made compliant.
|
||||
;;
|
||||
;; nil = local host type, whatever that is (probably unix).
|
||||
;; Think nil as in "not a remote host". This value is used by
|
||||
;; Think nil as in "not a remote host". This value is used by
|
||||
;; ange-ftp-dired-host-type for local buffers.
|
||||
;;
|
||||
;; t = a remote host of unknown type. Think t as in true, it's remote.
|
||||
;; t = a remote host of unknown type. Think t as in true, it's remote.
|
||||
;; Currently, `unix' is used as the default remote host type.
|
||||
;; Maybe we should use t.
|
||||
;;
|
||||
;; TYPE = a remote host of TYPE type.
|
||||
;;
|
||||
;; TYPE:LIST = a remote host of TYPE type, using a specialized ftp listing
|
||||
;; program called list. This is currently only used for Unix
|
||||
;; program called list. This is currently only used for Unix
|
||||
;; dl (descriptive listings), when ange-ftp-dired-host-type
|
||||
;; is set to `unix:dl'.
|
||||
|
||||
;; Bug report codes:
|
||||
;;
|
||||
;; Because of their naive faith in this code, there are certain situations
|
||||
;; which the writers of this program believe could never happen. However,
|
||||
;; which the writers of this program believe could never happen. However,
|
||||
;; being realists they have put calls to `error' in the program at these
|
||||
;; points. These errors provide a code, which is an integer, greater than 1.
|
||||
;; points. These errors provide a code, which is an integer, greater than 1.
|
||||
;; To aid debugging. the error codes, and the functions in which they reside
|
||||
;; are listed below.
|
||||
;;
|
||||
|
|
@ -1025,7 +1025,7 @@ or nil meaning don't change it."
|
|||
"Buffer name to hold directory listing data received from FTP process.")
|
||||
|
||||
(defvar ange-ftp-netrc-modtime nil
|
||||
"Last modified time of the netrc file from file-attributes.")
|
||||
"Last modified time of the netrc file from `file-attributes'.")
|
||||
|
||||
(defvar ange-ftp-user-hashtable (make-hash-table :test 'equal)
|
||||
"Hash table holding associations between HOST, USER pairs.")
|
||||
|
|
@ -2641,7 +2641,7 @@ away in the internal cache."
|
|||
(ange-ftp-error host user
|
||||
(concat "DIR failed: " (cdr result)))))
|
||||
(ange-ftp-del-tmp-name temp))))
|
||||
(error "Should never happen. Please report. Bug ref. no.: 1"))))
|
||||
(error "This should never happen; please report this as a bug"))))
|
||||
|
||||
;;;; ------------------------------------------------------------
|
||||
;;;; Directory information caching support.
|
||||
|
|
@ -5134,7 +5134,7 @@ NEWNAME should be the name to give the new compressed or uncompressed file.")
|
|||
(concat "/" drive "/"))
|
||||
dir (and dir "/")
|
||||
file))
|
||||
(error "name %s didn't match" name))
|
||||
(error "Name %s didn't match" name))
|
||||
(let (drive dir file tmp quote)
|
||||
(if (string-match "\\`\".+\"\\'" name)
|
||||
(setq name (substring name 1 -1)
|
||||
|
|
@ -5662,7 +5662,7 @@ Other orders of $ and _ seem to all work just fine.")
|
|||
(setq file (match-string 2 name))
|
||||
(concat (and acct (concat "/" acct "/"))
|
||||
file))
|
||||
(error "name %s didn't match" name))
|
||||
(error "Name %s didn't match" name))
|
||||
(if (string-match "\\`/\\([^:]+:\\)/\\(.*\\)\\'" name)
|
||||
(concat (match-string 1 name) (match-string 2 name))
|
||||
;; Let's hope that mts will recognize it anyway.
|
||||
|
|
@ -6096,7 +6096,7 @@ Other orders of $ and _ seem to all work just fine.")
|
|||
(and pubset (concat "_/" pubset "/"))
|
||||
(and userid (concat userid "/"))
|
||||
filename))
|
||||
(error "name %s didn't match" name))
|
||||
(error "Name %s didn't match" name))
|
||||
;; and here we (maybe) have to remove the inserted "_/" 'cause
|
||||
;; of our prevention of the special escape prefix above:
|
||||
(if (string-match (concat "^/_/") name)
|
||||
|
|
|
|||
|
|
@ -1754,11 +1754,11 @@ from `browse-url-elinks-wrapper'."
|
|||
(define-key map [mouse-2] #'browse-url-button-open)
|
||||
(define-key map "w" #'browse-url-button-copy)
|
||||
map)
|
||||
"The keymap used for browse-url buttons.")
|
||||
"The keymap used for `browse-url' buttons.")
|
||||
|
||||
(defface browse-url-button
|
||||
'((t :inherit link))
|
||||
"Face for browse-url buttons (i.e., links)."
|
||||
"Face for `browse-url' buttons (i.e., links)."
|
||||
:version "27.1")
|
||||
|
||||
(defun browse-url-add-buttons ()
|
||||
|
|
|
|||
|
|
@ -1312,9 +1312,9 @@ allows editing it."
|
|||
"Turn off or on support for the dictionary tooltip mode.
|
||||
|
||||
It is normally internally called with 1 to enable support for the
|
||||
tooltip mode. The hook function will check the value of the
|
||||
variable dictionary-tooltip-mode to decide if some action must be
|
||||
taken. When disabling the tooltip mode the value of this variable
|
||||
tooltip mode. The hook function will check the value of the
|
||||
variable `dictionary-tooltip-mode' to decide if some action must be
|
||||
taken. When disabling the tooltip mode the value of this variable
|
||||
will be set to nil."
|
||||
(interactive)
|
||||
(tooltip-mode on)
|
||||
|
|
@ -1345,10 +1345,10 @@ active it will overwrite that mode for the current buffer."
|
|||
|
||||
;;;###autoload
|
||||
(defun global-dictionary-tooltip-mode (&optional arg)
|
||||
"Enable/disable dictionary-tooltip-mode for all buffers.
|
||||
"Enable/disable `dictionary-tooltip-mode' for all buffers.
|
||||
|
||||
Internally it provides a default for the dictionary-tooltip-mode.
|
||||
It can be overwritten for each buffer using dictionary-tooltip-mode.
|
||||
Internally it provides a default for the `dictionary-tooltip-mode'.
|
||||
It can be overwritten for each buffer using `dictionary-tooltip-mode'.
|
||||
|
||||
Note: (global-dictionary-tooltip-mode 0) will not disable the mode
|
||||
any buffer where (dictionary-tooltip-mode 1) has been called."
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
;;; Commentary:
|
||||
;; This package provides a common interface to query directory servers using
|
||||
;; different protocols such as LDAP, CCSO PH/QI or BBDB. Queries can be
|
||||
;; made through an interactive form or inline. Inline query strings in
|
||||
;; made through an interactive form or inline. Inline query strings in
|
||||
;; buffers are expanded with appropriately formatted query results
|
||||
;; (especially used to expand email addresses in message buffers). EUDC
|
||||
;; also interfaces with the BBDB package to let you register query results
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@
|
|||
(eval-when-compile (require 'subr-x))
|
||||
|
||||
(defgroup eww nil
|
||||
"Emacs Web Wowser"
|
||||
"Emacs Web Wowser."
|
||||
:version "25.1"
|
||||
:link '(custom-manual "(eww) Top")
|
||||
:group 'web
|
||||
|
|
|
|||
|
|
@ -226,7 +226,7 @@ trust and key files, and priority string."
|
|||
trustfiles crlfiles keylist min-prime-bits
|
||||
verify-flags verify-error verify-hostname-error
|
||||
&allow-other-keys)
|
||||
"Negotiate a SSL/TLS connection. Returns proc. Signals gnutls-error.
|
||||
"Negotiate a SSL/TLS connection. Return proc. Signal gnutls-error.
|
||||
|
||||
Note that arguments are passed CL style, :type TYPE instead of just TYPE.
|
||||
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ will have no effect.")
|
|||
"Keymap to hold goto-addr's mouse key defs under highlighted URLs.")
|
||||
|
||||
(defun goto-address-context-menu (menu click)
|
||||
"Populate MENU with goto-address commands at CLICK."
|
||||
"Populate MENU with `goto-address' commands at CLICK."
|
||||
(when (mouse-posn-property (event-start click) 'goto-address)
|
||||
(define-key menu [goto-address-separator] menu-bar-separator)
|
||||
(define-key menu [goto-address-at-mouse]
|
||||
|
|
|
|||
|
|
@ -51,7 +51,8 @@ a separator."
|
|||
|
||||
(defcustom ldap-default-port nil
|
||||
"Default TCP port for LDAP connections.
|
||||
Initialized from the LDAP library at build time. Default value is 389."
|
||||
Initialized from the LDAP library at build time.
|
||||
Default value is 389."
|
||||
:type '(choice (const :tag "Use library default" nil)
|
||||
(integer :tag "Port number")))
|
||||
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ The elements of the list are alists of the following structure
|
|||
(type . MIME-TYPE)
|
||||
(test . TEST))
|
||||
|
||||
where VIEWER is either a lisp command, e.g., a major-mode, or a
|
||||
where VIEWER is either a Lisp command, e.g., a major mode, or a
|
||||
string containing a shell command for viewing files of the
|
||||
defined MIME-TYPE. In case of a shell command, %s will be
|
||||
replaced with the file.
|
||||
|
|
@ -101,7 +101,7 @@ replaced with the file.
|
|||
MIME-TYPE is a regular expression being matched against the
|
||||
actual MIME type. It is implicitly surrounded with ^ and $.
|
||||
|
||||
TEST is a lisp form which is evaluated in order to test if the
|
||||
TEST is a Lisp form which is evaluated in order to test if the
|
||||
entry should be chosen. The `test' entry is optional.
|
||||
|
||||
When selecting a viewer for a given MIME type, the first viewer
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@
|
|||
(defvar nsm-temporary-host-settings nil)
|
||||
|
||||
(defgroup nsm nil
|
||||
"Network Security Manager"
|
||||
"Network Security Manager."
|
||||
:version "25.1"
|
||||
:group 'comm)
|
||||
|
||||
|
|
@ -446,8 +446,8 @@ this check has no effect on GnuTLS >= 3.2.0.
|
|||
|
||||
Reference:
|
||||
|
||||
[1]: Schneier, Bruce (1996). Applied Cryptography (Second ed.). John
|
||||
Wiley & Sons. ISBN 0-471-11709-9.
|
||||
[1]: Schneier, Bruce (1996). Applied Cryptography (Second ed.).
|
||||
John Wiley & Sons. ISBN 0-471-11709-9.
|
||||
[2]: N. Mavrogiannopoulos, FSF (Apr 2015). \"GnuTLS NEWS -- History
|
||||
of user-visible changes.\" Version 3.4.0,
|
||||
`https://gitlab.com/gnutls/gnutls/blob/master/NEWS'"
|
||||
|
|
@ -466,7 +466,7 @@ man-in-the-middle attacks.
|
|||
|
||||
Reference:
|
||||
|
||||
GnuTLS authors (2018). \"GnuTLS Manual 4.3.3 Anonymous
|
||||
GnuTLS authors (2018). \"GnuTLS Manual 4.3.3 Anonymous
|
||||
authentication\",
|
||||
`https://www.gnutls.org/manual/gnutls.html#Anonymous-authentication'"
|
||||
(let ((kx (plist-get status :key-exchange)))
|
||||
|
|
|
|||
|
|
@ -24,19 +24,19 @@
|
|||
;;; Commentary:
|
||||
;;
|
||||
;; This package provides a simple method of inserting a URL based on the
|
||||
;; text at point in the current buffer. This is part of an on-going effort
|
||||
;; text at point in the current buffer. This is part of an on-going effort
|
||||
;; to increase the information I provide people while reducing the amount
|
||||
;; of typing I need to do. No-doubt there are undiscovered Emacs packages
|
||||
;; of typing I need to do. No-doubt there are undiscovered Emacs packages
|
||||
;; out there that do all of this and do it better, feel free to point me to
|
||||
;; them, in the mean time I'm having fun playing with Emacs Lisp.
|
||||
;;
|
||||
;; The URLs are stored in an external file as a list of either cons cells,
|
||||
;; or lists. A cons cell entry looks like this:
|
||||
;; or lists. A cons cell entry looks like this:
|
||||
;;
|
||||
;; (<Lookup> . <URL>)
|
||||
;;
|
||||
;; where <Lookup> is a string that acts as the keyword lookup and <URL> is
|
||||
;; the URL associated with it. An example might be:
|
||||
;; the URL associated with it. An example might be:
|
||||
;;
|
||||
;; ("GNU" . "https://www.gnu.org/")
|
||||
;;
|
||||
|
|
@ -45,8 +45,8 @@
|
|||
;; (<Lookup> <URL> <Comment>)
|
||||
;;
|
||||
;; where <Lookup> and <URL> are the same as with the cons cell and <Comment>
|
||||
;; is any text you like that describes the URL. This description will be
|
||||
;; used when presenting a list of URLS using `quickurl-list'. An example
|
||||
;; is any text you like that describes the URL. This description will be
|
||||
;; used when presenting a list of URLS using `quickurl-list'. An example
|
||||
;; might be:
|
||||
;;
|
||||
;; ("FSF" "https://www.fsf.org/" "The Free Software Foundation")
|
||||
|
|
@ -215,8 +215,8 @@ Note that this function is a setfable place."
|
|||
(defun quickurl-url-comment (url)
|
||||
"Get the comment from a URL.
|
||||
|
||||
If the URL has no comment an empty string is returned. Also note that this
|
||||
function is a setfable place."
|
||||
If the URL has no comment an empty string is returned. Also note
|
||||
that this function is a setfable place."
|
||||
(declare
|
||||
(gv-setter (lambda (store)
|
||||
`(if (quickurl-url-commented-p ,url)
|
||||
|
|
|
|||
|
|
@ -24,6 +24,8 @@
|
|||
|
||||
;;; Commentary:
|
||||
|
||||
;;; Code:
|
||||
|
||||
(require 'sasl)
|
||||
(require 'hmac-md5)
|
||||
|
||||
|
|
|
|||
|
|
@ -29,9 +29,9 @@
|
|||
;; It is caller's responsibility to base64-decode challenges and
|
||||
;; base64-encode responses in IMAP4 AUTHENTICATE command.
|
||||
;;
|
||||
;; Passphrase should be longer than 16 bytes. (See RFC 2195)
|
||||
;; Passphrase should be longer than 16 bytes. (See RFC 2195)
|
||||
|
||||
;;; Commentary:
|
||||
;;; Code:
|
||||
|
||||
(require 'sasl)
|
||||
(require 'hmac-md5)
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@
|
|||
"Whether there is a daemon offering the Secret Service API.")
|
||||
|
||||
(defvar secrets-debug nil
|
||||
"Write debug messages")
|
||||
"Write debug messages.")
|
||||
|
||||
(defconst secrets-service "org.freedesktop.secrets"
|
||||
"The D-Bus name used to talk to Secret Service.")
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@
|
|||
(eval-when-compile (require 'cl-lib))
|
||||
|
||||
(defgroup shr-color nil
|
||||
"Simple HTML Renderer colors"
|
||||
"Simple HTML Renderer colors."
|
||||
:group 'shr)
|
||||
|
||||
(defcustom shr-color-visible-luminance-min 40
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@
|
|||
(require 'text-property-search)
|
||||
|
||||
(defgroup shr nil
|
||||
"Simple HTML Renderer"
|
||||
"Simple HTML Renderer."
|
||||
:version "25.1"
|
||||
:group 'web)
|
||||
|
||||
|
|
|
|||
|
|
@ -410,7 +410,7 @@ If BUFFER is nil, the current buffer is used."
|
|||
|
||||
(defun sieve-manage-capability (&optional name value buffer)
|
||||
"Check if capability NAME of server BUFFER match VALUE.
|
||||
If it does, return the server value of NAME. If not returns nil.
|
||||
If it does, return the server value of NAME. If not return nil.
|
||||
If VALUE is nil, do not check VALUE and return server value.
|
||||
If NAME is nil, return the full server list of capabilities."
|
||||
(with-current-buffer (or buffer (current-buffer))
|
||||
|
|
|
|||
|
|
@ -132,7 +132,7 @@
|
|||
(modify-syntax-entry ?\} "){" st)
|
||||
(modify-syntax-entry ?\" "\"" st)
|
||||
st)
|
||||
"Syntax table in use in sieve-mode buffers.")
|
||||
"Syntax table in use in `sieve-mode' buffers.")
|
||||
|
||||
|
||||
;; Key map definition
|
||||
|
|
|
|||
|
|
@ -224,7 +224,7 @@ require \"fileinto\";
|
|||
(substitute-command-keys "\\[sieve-upload]"))))
|
||||
|
||||
(defmacro sieve-change-region (&rest body)
|
||||
"Turns off sieve-region before executing BODY, then re-enables it after.
|
||||
"Turn off sieve-region before executing BODY, then re-enables it after.
|
||||
Used to bracket operations which move point in the sieve-buffer."
|
||||
(declare (indent 0) (debug t))
|
||||
`(progn
|
||||
|
|
|
|||
|
|
@ -328,7 +328,7 @@ Tab indents for C code.
|
|||
Comments start with -- and end with newline or another --.
|
||||
Delete converts tabs to spaces as it moves back.
|
||||
\\{snmp-mode-map}
|
||||
Turning on snmp-mode runs the hooks in `snmp-common-mode-hook', then
|
||||
Turning on `snmp-mode' runs the hooks in `snmp-common-mode-hook', then
|
||||
`snmp-mode-hook'."
|
||||
(interactive)
|
||||
|
||||
|
|
@ -361,7 +361,7 @@ Tab indents for C code.
|
|||
Comments start with -- and end with newline or another --.
|
||||
Delete converts tabs to spaces as it moves back.
|
||||
\\{snmp-mode-map}
|
||||
Turning on snmp-mode runs the hooks in `snmp-common-mode-hook',
|
||||
Turning on `snmp-mode' runs the hooks in `snmp-common-mode-hook',
|
||||
then `snmpv2-mode-hook'."
|
||||
(interactive)
|
||||
|
||||
|
|
|
|||
|
|
@ -453,7 +453,7 @@ When ATYPE indicates an IP, param ADDRESS must be given as raw bytes."
|
|||
|
||||
;; Replacement functions for open-network-stream, etc.
|
||||
(defvar socks-noproxy nil
|
||||
"List of regexps matching hosts that we should not socksify connections to")
|
||||
"List of regexps matching hosts that we should not socksify connections to.")
|
||||
|
||||
(defun socks-find-route (host _service)
|
||||
(let ((route socks-server)
|
||||
|
|
|
|||
|
|
@ -83,8 +83,9 @@ LOGIN-NAME, which is optional, says what to log in as on that machine.")
|
|||
"Program to run to open a telnet connection.")
|
||||
|
||||
(defvar telnet-initial-count -50
|
||||
"Initial value of `telnet-count'. Should be set to the negative of the
|
||||
number of terminal writes telnet will make setting up the host connection.")
|
||||
"Initial value of `telnet-count'.
|
||||
Should be set to the negative of the number of terminal writes
|
||||
telnet will make setting up the host connection.")
|
||||
|
||||
(defvar telnet-maximum-count 4
|
||||
"Maximum value `telnet-count' can have.
|
||||
|
|
|
|||
|
|
@ -5800,8 +5800,8 @@ This command is returned only if `delete-by-moving-to-trash' is non-nil."
|
|||
;; Some predefined connection properties.
|
||||
(defun tramp-get-inline-compress (vec prop size)
|
||||
"Return the compress command related to PROP.
|
||||
PROP is either `inline-compress' or `inline-decompress'. SIZE is
|
||||
the length of the file to be compressed.
|
||||
PROP is either `inline-compress' or `inline-decompress'.
|
||||
SIZE is the length of the file to be compressed.
|
||||
|
||||
If no corresponding command is found, nil is returned."
|
||||
(when (and (integerp tramp-inline-compress-start-size)
|
||||
|
|
|
|||
|
|
@ -1929,7 +1929,7 @@ The outline level is equal to the verbosity of the Tramp message."
|
|||
(put #'tramp-trace-buffer-name 'tramp-suppress-trace t)
|
||||
|
||||
(defvar tramp-trace-functions nil
|
||||
"A list of non-Tramp functions to be traced with tramp-verbose > 10.")
|
||||
"A list of non-Tramp functions to be traced with `tramp-verbose' > 10.")
|
||||
|
||||
(defun tramp-debug-message (vec fmt-string &rest arguments)
|
||||
"Append message to debug buffer of VEC.
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@
|
|||
(require 'dbus)
|
||||
|
||||
(defvar zeroconf-debug nil
|
||||
"Write messages during service discovery")
|
||||
"Write messages during service discovery.")
|
||||
|
||||
(defconst zeroconf-service-avahi "org.freedesktop.Avahi"
|
||||
"The D-Bus name used to talk to Avahi.")
|
||||
|
|
@ -375,7 +375,7 @@ type used when registering FUNCTION."
|
|||
(defun zeroconf-get-service (name type)
|
||||
"Return the service description of service NAME as list.
|
||||
NAME must be a string. The service must be of service type
|
||||
TYPE. The resulting list has the format
|
||||
TYPE. The resulting list has the format
|
||||
|
||||
(INTERFACE PROTOCOL NAME TYPE DOMAIN FLAGS)."
|
||||
;; Due to the service browser, all known services are kept in
|
||||
|
|
@ -387,7 +387,7 @@ TYPE. The resulting list has the format
|
|||
(defun zeroconf-resolve-service (service)
|
||||
"Return all service attributes SERVICE as list.
|
||||
NAME must be a string. The service must be of service type
|
||||
TYPE. The resulting list has the format
|
||||
TYPE. The resulting list has the format
|
||||
|
||||
(INTERFACE PROTOCOL NAME TYPE DOMAIN HOST APROTOCOL ADDRESS PORT TXT FLAGS)."
|
||||
(let* ((name (zeroconf-service-name service))
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue