From f4c4910c9e72b4e3f3cbfed42b0203cde1e8f22f Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Mon, 4 Feb 2008 16:54:05 +0000 Subject: Comment changes. --- lisp/emacs-lisp/edebug.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lisp/emacs-lisp') diff --git a/lisp/emacs-lisp/edebug.el b/lisp/emacs-lisp/edebug.el index b988a8ac79d..e825f2434b4 100644 --- a/lisp/emacs-lisp/edebug.el +++ b/lisp/emacs-lisp/edebug.el @@ -1496,7 +1496,7 @@ expressions; a `progn' form will be returned enclosing these forms." (cond ((symbolp head) (cond - ((null head) nil) ; () is legal. + ((null head) nil) ; () is valid. ((eq head 'interactive-p) ;; Special case: replace (interactive-p) with variable (setq edebug-def-interactive 'check-it) @@ -2076,7 +2076,7 @@ expressions; a `progn' form will be returned enclosing these forms." ;; doesn't handle (a . ,b). The straightforward fix: ;; (backquote-form . [&or nil backquote-form]) ;; uses up too much stack space. - ;; Note that `(foo . ,@bar) is not legal, so we don't need to handle it. + ;; Note that `(foo . ,@bar) is not valid, so we don't need to handle it. (backquote-form [&rest [¬ ","] backquote-form] . [&or nil backquote-form]) ;; If you use dotted forms in backquotes, replace the previous line -- cgit v1.2.3 From 9b9a412286efca8257d18175941b6370115445d6 Mon Sep 17 00:00:00 2001 From: Juanma Barranquero Date: Tue, 5 Feb 2008 11:51:30 +0000 Subject: *** empty log message *** --- lisp/emacs-lisp/byte-run.el | 2 +- lisp/ffap.el | 2 +- lisp/follow.el | 2 +- lisp/isearch.el | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) (limited to 'lisp/emacs-lisp') diff --git a/lisp/emacs-lisp/byte-run.el b/lisp/emacs-lisp/byte-run.el index 48760d1e77e..ecf2ed57dac 100644 --- a/lisp/emacs-lisp/byte-run.el +++ b/lisp/emacs-lisp/byte-run.el @@ -227,7 +227,7 @@ In interpreted code, this is entirely equivalent to `progn'." ;; verbose t, nil byte-compile-verbose ;; optimize t, nil, source, byte byte-compile-optimize ;; warnings list of warnings byte-compile-warnings -;; Legal elements: (callargs redefine free-vars unresolved) +;; Valid elements: (callargs redefine free-vars unresolved) ;; file-format emacs18, emacs19 byte-compile-compatibility ;; ;; For example, this might appear at the top of a source file: diff --git a/lisp/ffap.el b/lisp/ffap.el index 3e62f2351c6..aaf92ebe306 100644 --- a/lisp/ffap.el +++ b/lisp/ffap.el @@ -426,7 +426,7 @@ Returned values: ;; (ffap-machine-p "mathcs" 5678 nil 'ping) ;; (ffap-machine-p "foo.bonk" nil nil 'ping) ;; (ffap-machine-p "foo.bonk.com" nil nil 'ping) - (if (or (string-match "[^-[:alnum:].]" host) ; Illegal chars (?) + (if (or (string-match "[^-[:alnum:].]" host) ; Invalid chars (?) (not (string-match "[^0-9]" host))) ; 1: a number? 2: quick reject nil (let* ((domain diff --git a/lisp/follow.el b/lisp/follow.el index ea5bf960dd9..e251d4c7b3c 100644 --- a/lisp/follow.el +++ b/lisp/follow.el @@ -300,7 +300,7 @@ ;; above for an example of how to bind the keys the way you like. ;; ;; Please note that the keymap is defined the first time this file is -;; loaded. Also note that the only legal way to manipulate the +;; loaded. Also note that the only valid way to manipulate the ;; keymap is to use `define-key'. Don't change it using `setq' or ;; similar! diff --git a/lisp/isearch.el b/lisp/isearch.el index e72df62d7f8..131bde71690 100644 --- a/lisp/isearch.el +++ b/lisp/isearch.el @@ -1461,7 +1461,7 @@ to the barrier." ;; removes all bracket-sets and groups that might be in the way, as ;; well as partial \{\} constructs that the code below leaves behind. ;; Also skip over postfix operators -- though horrid, - ;; 'ab?\{5,6\}+\{1,2\}*' is perfectly legal. + ;; 'ab?\{5,6\}+\{1,2\}*' is perfectly valid. (while (and previous (or (isearch-error-state frame) (let* ((string (isearch-string-state frame)) -- cgit v1.2.3 From 0138efd4b32f2209944704e627e514274e1c1e20 Mon Sep 17 00:00:00 2001 From: Juanma Barranquero Date: Tue, 5 Feb 2008 12:07:11 +0000 Subject: *** empty log message *** --- lisp/emacs-lisp/cl-specs.el | 2 +- lisp/eshell/esh-var.el | 2 +- lisp/gnus/deuglify.el | 2 +- lisp/net/ange-ftp.el | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) (limited to 'lisp/emacs-lisp') diff --git a/lisp/emacs-lisp/cl-specs.el b/lisp/emacs-lisp/cl-specs.el index d2d55204ef2..dc8ebef69d5 100644 --- a/lisp/emacs-lisp/cl-specs.el +++ b/lisp/emacs-lisp/cl-specs.el @@ -323,7 +323,7 @@ ;; Below is a complete spec for loop, in several parts that correspond ;; to the syntax given in CLtL2. The specs do more than specify where ;; the forms are; it also specifies, as much as Edebug allows, all the -;; syntactically legal loop clauses. The disadvantage of this +;; syntactically valid loop clauses. The disadvantage of this ;; completeness is rigidity, but the "for ... being" clause allows ;; arbitrary extensions of the form: [symbolp &rest &or symbolp form]. diff --git a/lisp/eshell/esh-var.el b/lisp/eshell/esh-var.el index 15ecb119c5e..0e5f4484279 100644 --- a/lisp/eshell/esh-var.el +++ b/lisp/eshell/esh-var.el @@ -47,7 +47,7 @@ variable value, a subcommand, or even the result of a Lisp form." ;; ;; $ALSO-VAR ;; -;; "-" is a legal part of a variable name. +;; "-" is a valid part of a variable name. ;; ;; $-TOO ;; diff --git a/lisp/gnus/deuglify.el b/lisp/gnus/deuglify.el index c17be0a1479..75880c8f76b 100644 --- a/lisp/gnus/deuglify.el +++ b/lisp/gnus/deuglify.el @@ -68,7 +68,7 @@ ;; > verb. This sentence no verb. This sentence no verb. This ;; > sentence no verb. ;; -;; Unwrapping "You forgot in all your sentences." would be illegal as +;; Unwrapping "You forgot in all your sentences." would be invalid as ;; this part wasn't intended to be cited text. ;; `gnus-article-outlook-unwrap-lines' will only unwrap lines if the resulting ;; citation line will be of a certain maximum length. You can control diff --git a/lisp/net/ange-ftp.el b/lisp/net/ange-ftp.el index 7428dcd380a..d53f740296a 100644 --- a/lisp/net/ange-ftp.el +++ b/lisp/net/ange-ftp.el @@ -297,7 +297,7 @@ ;; you would type: ;; C-x C-f /anonymous@ymir.claremont.edu:CSV/POLICY/RULES.MEM ;; -;; A legal VMS filename is of the form: FILE.TYPE;## +;; A valid VMS filename is of the form: FILE.TYPE;## ;; where FILE can be up to 39 characters ;; TYPE can be up to 39 characters ;; ## is a version number (an integer between 1 and 32,767) -- cgit v1.2.3