Fix capitalization ELisp -> Elisp
* configure.ac (libgccjit_not_found_err) (libgccjit_dev_not_found_err): * doc/emacs/buffers.texi (List Buffers): * doc/lispref/elisp.texi (Tree-sitter C API): * doc/lispref/functions.texi (What Is a Function): * doc/lispref/parsing.texi (Parsing Program Source) (Tree-sitter C API): * doc/misc/gnus.texi (The Gnus Registry): * etc/DEBUG: * etc/NEWS: * etc/NEWS.25: * etc/NEWS.26: * etc/NEWS.28: * etc/NEWS.30: * etc/TODO: * lib-src/emacsclient.c (print_help_and_exit): * lisp/auth-source.el (auth-source-search): * lisp/cedet/semantic/bovine/el.el (emacs-lisp-mode): * lisp/cedet/semantic/wisent/comp.el (wisent-automaton-lisp-form): * lisp/cedet/srecode/el.el (srecode-semantic-apply-tag-to-dict): * lisp/editorconfig.el (editorconfig-get-local-variables-functions): * lisp/emacs-lisp/bindat.el (bindat-type): * lisp/emacs-lisp/byte-opt.el (byte-compile-inline-expand): * lisp/emacs-lisp/cconv.el (cconv-make-interpreted-closure): * lisp/emacs-lisp/cl-macs.el (cl--labels-convert): * lisp/emacs-lisp/lisp-mode.el (lisp-fdefs) (lisp-fill-paragraphs-as-doc-string): * lisp/emacs-lisp/macroexp.el (macroexp--fgrep): * lisp/emacs-lisp/oclosure.el (cconv--interactive-helper): * lisp/emacs-lisp/re-builder.el: * lisp/erc/erc-button.el (erc-emacswiki-lisp-url): * lisp/help-fns.el (help-fns--describe-function-or-command-prompt): * lisp/menu-bar.el (menu-bar-search-documentation-menu): * lisp/net/tramp-message.el (tramp-debug-font-lock-keywords): * lisp/org/org-capture.el (org-capture): * lisp/org/org.el (org-category, org-todo): * lisp/org/ox.el (org-export-async-start): * lisp/progmodes/elisp-mode.el (emacs-lisp-mode): * lisp/progmodes/peg.el (peg-translate-exp): * lisp/progmodes/ruby-ts-mode.el: * lisp/woman.el (woman-mode, woman-parse-numeric-arg): * src/chartab.c (map_char_table_for_charset): * src/fns.c (extract_data_from_object): * src/frame.c (do_switch_frame): * src/keyboard.c (make_lispy_event): * test/lisp/emacs-lisp/cl-macs-tests.el (cl-&key-arguments): * test/lisp/emacs-lisp/shortdoc-tests.el (shortdoc-help-fns-examples-function-test): * test/manual/etags/c-src/emacs/src/keyboard.c (make_lispy_event): Fix capitalization ELisp -> Elisp.
This commit is contained in:
parent
dd1b11d34c
commit
60c0524ad2
45 changed files with 78 additions and 78 deletions
|
@ -5078,16 +5078,16 @@ AC_DEFUN([libgccjit_smoke_test], [
|
|||
}]])])
|
||||
|
||||
AC_DEFUN([libgccjit_not_found_err], [
|
||||
AC_MSG_ERROR([ELisp native compiler was requested, but libgccjit was not found.
|
||||
AC_MSG_ERROR([Elisp native compiler was requested, but libgccjit was not found.
|
||||
Please try installing libgccjit or a similar package.
|
||||
If you are sure you want Emacs be compiled without ELisp native compiler,
|
||||
If you are sure you want Emacs be compiled without Elisp native compiler,
|
||||
pass the --without-native-compilation option to configure.])])
|
||||
|
||||
AC_DEFUN([libgccjit_dev_not_found_err], [
|
||||
AC_MSG_ERROR([ELisp native compiler was requested, but libgccjit header files were
|
||||
AC_MSG_ERROR([Elisp native compiler was requested, but libgccjit header files were
|
||||
not found.
|
||||
Please try installing libgccjit-dev or a similar package.
|
||||
If you are sure you want Emacs be compiled without ELisp native compiler,
|
||||
If you are sure you want Emacs be compiled without Elisp native compiler,
|
||||
pass the --without-native-compilation option to configure.])])
|
||||
|
||||
AC_DEFUN([libgccjit_broken_err], [
|
||||
|
|
|
@ -205,7 +205,7 @@ Here is an example of a buffer list:
|
|||
|
||||
@smallexample
|
||||
CRM Buffer Size Mode File
|
||||
. * .emacs 3294 ELisp/l ~/.emacs
|
||||
. * .emacs 3294 Elisp/l ~/.emacs
|
||||
% *Help* 101 Help
|
||||
search.c 86055 C ~/cvs/emacs/src/search.c
|
||||
% src 20959 Dired by name ~/cvs/emacs/src/
|
||||
|
|
|
@ -1388,7 +1388,7 @@ Parsing Program Source
|
|||
* Pattern Matching:: Pattern matching with query patterns.
|
||||
* Multiple Languages:: Parse text written in multiple languages.
|
||||
* Tree-sitter Major Modes:: Develop major modes using tree-sitter.
|
||||
* Tree-sitter C API:: Compare the C API and the ELisp API.
|
||||
* Tree-sitter C API:: Compare the C API and the Elisp API.
|
||||
|
||||
Syntax Descriptors
|
||||
|
||||
|
|
|
@ -219,7 +219,7 @@ function. For example:
|
|||
|
||||
@defun compiled-function-p object
|
||||
This function returns @code{t} if @var{object} is a function object
|
||||
that is not in the form of ELisp source code but something like
|
||||
that is not in the form of Elisp source code but something like
|
||||
machine code or byte code instead. More specifically it returns
|
||||
@code{t} if the function is built-in (a.k.a.@: ``primitive'',
|
||||
@pxref{What Is a Function}), or byte-compiled (@pxref{Byte
|
||||
|
|
|
@ -48,7 +48,7 @@ source files that mix multiple programming languages.
|
|||
* User-defined Things:: User-defined ``Things'' and Navigation.
|
||||
* Multiple Languages:: Parse text written in multiple languages.
|
||||
* Tree-sitter Major Modes:: Develop major modes using tree-sitter.
|
||||
* Tree-sitter C API:: Compare the C API and the ELisp API.
|
||||
* Tree-sitter C API:: Compare the C API and the Elisp API.
|
||||
@end menu
|
||||
|
||||
@node Language Grammar
|
||||
|
@ -2305,8 +2305,8 @@ Null nodes are converted to @code{nil}.
|
|||
@end itemize
|
||||
|
||||
Below is the correspondence between all C API functions and their
|
||||
ELisp counterparts. Sometimes one ELisp function corresponds to
|
||||
multiple C functions, and many C functions don't have an ELisp
|
||||
Elisp counterparts. Sometimes one Elisp function corresponds to
|
||||
multiple C functions, and many C functions don't have an Elisp
|
||||
counterpart.
|
||||
|
||||
@example
|
||||
|
|
|
@ -26271,7 +26271,7 @@ etc.@: backends.
|
|||
@item
|
||||
Store arbitrary data
|
||||
|
||||
Through a simple ELisp API, the registry can remember any data for a
|
||||
Through a simple Elisp API, the registry can remember any data for a
|
||||
message. A built-in inverse map, when activated, allows quick lookups
|
||||
of all messages matching a particular set of criteria.
|
||||
@end enumerate
|
||||
|
|
|
@ -260,7 +260,7 @@ from a shell prompt, like this:
|
|||
|
||||
where Emacs-PID is the process ID of Emacs being debugged. Other
|
||||
useful signals to send are SIGUSR1 and SIGUSR2; see "Error Debugging"
|
||||
in the ELisp manual for how to use those.
|
||||
in the Elisp manual for how to use those.
|
||||
|
||||
When Emacs is displaying on a text terminal, it is useful to have a
|
||||
separate terminal for the debug session. This can be done by starting
|
||||
|
@ -805,7 +805,7 @@ not exit when it should.
|
|||
On GNU and Unix systems, you can also try sending Emacs SIGUSR2,
|
||||
which, if 'debug-on-event' has its default value, will cause Emacs to
|
||||
attempt to break out of its current loop and enter the Lisp
|
||||
debugger. (See the node "Debugging" in the ELisp manual for the
|
||||
debugger. (See the node "Debugging" in the Elisp manual for the
|
||||
details about the Lisp debugger.) This feature is useful when a
|
||||
C-level debugger is not conveniently available.
|
||||
|
||||
|
|
2
etc/NEWS
2
etc/NEWS
|
@ -1564,7 +1564,7 @@ for writing code that can work across different Emacs versions.
|
|||
|
||||
---
|
||||
** You can change the default value of 'lexical-binding'.
|
||||
While the default is still the use dynamic binding dialect of ELisp
|
||||
While the default is still the use dynamic binding dialect of Elisp
|
||||
in those places that don't explicitly set 'lexical-binding' you can
|
||||
change it globally with:
|
||||
|
||||
|
|
|
@ -275,7 +275,7 @@ to produce its authentication key.
|
|||
*** Successive single-char deletions are collapsed in the undo-log just like
|
||||
successive char insertions. Which commands invoke this behavior is
|
||||
controlled by the new 'undo-auto-amalgamate' function. See the node
|
||||
"Undo" in the ELisp manual for more details.
|
||||
"Undo" in the Elisp manual for more details.
|
||||
|
||||
*** The heuristic used to insert 'undo-boundary' after each command
|
||||
has changed, so that if a command causes changes in more than just the
|
||||
|
@ -1418,10 +1418,10 @@ continued to the next line.
|
|||
** New macro 'define-advice'.
|
||||
|
||||
** Emacs Lisp now supports generators.
|
||||
See the "Generators" section of the ELisp manual for the details.
|
||||
See the "Generators" section of the Elisp manual for the details.
|
||||
|
||||
** New finalizer facility for running code when objects become unreachable.
|
||||
See the "Finalizer Type" subsection in the ELisp manual for the
|
||||
See the "Finalizer Type" subsection in the Elisp manual for the
|
||||
details.
|
||||
|
||||
** Lexical closures can use '(:documentation FORM)' to build their docstring.
|
||||
|
|
22
etc/NEWS.26
22
etc/NEWS.26
|
@ -309,7 +309,7 @@ explicitly yields. Global variables are shared among all threads, but
|
|||
a 'let' binding is thread-local. Each thread also has its own current
|
||||
buffer and its own match data.
|
||||
|
||||
See the chapter "(elisp) Threads" in the ELisp manual for full
|
||||
See the chapter "(elisp) Threads" in the Elisp manual for full
|
||||
documentation of these facilities.
|
||||
|
||||
** The new user variable 'electric-quote-chars' provides a list
|
||||
|
@ -471,7 +471,7 @@ See the doc string of 'dir-locals-file' for more information.
|
|||
|
||||
** Connection-local variables can be used to specify local variables
|
||||
with a value depending on the connected remote server. For details,
|
||||
see the node "(elisp) Connection Local Variables" in the ELisp manual.
|
||||
see the node "(elisp) Connection Local Variables" in the Elisp manual.
|
||||
|
||||
** International domain names (IDNA) are now encoded via the new
|
||||
puny.el library, so that one can visit Web sites with non-ASCII URLs.
|
||||
|
@ -946,7 +946,7 @@ rotation, as well as saving the image to a file. These commands are
|
|||
also available in 'image-mode'.
|
||||
|
||||
*** A new library for creating and manipulating SVG images has been
|
||||
added. See the "(elisp) SVG Images" section in the ELisp reference
|
||||
added. See the "(elisp) SVG Images" section in the Elisp reference
|
||||
manual for details.
|
||||
|
||||
*** New setf-able function to access and set image parameters is
|
||||
|
@ -1106,7 +1106,7 @@ environments or ANTLR programs with embedded Python code.
|
|||
A major mode can provide indentation context for a sub-mode. To
|
||||
support this, modes should use 'prog-first-column' instead of a
|
||||
literal zero and avoid calling 'widen' in their indentation functions.
|
||||
See the node "(elisp) Mode-Specific Indent" in the ELisp manual for
|
||||
See the node "(elisp) Mode-Specific Indent" in the Elisp manual for
|
||||
more details.
|
||||
|
||||
** ERC
|
||||
|
@ -1441,7 +1441,7 @@ It has been renamed as internal function 'window--make-major-side-window',
|
|||
however applications should instead call 'display-buffer-in-side-window'
|
||||
(passing the SIDE and SLOT parameters as elements of ALIST). This approach
|
||||
is backwards-compatible with versions of Emacs in which the old function
|
||||
exists. See the node "Displaying Buffers in Side Windows" in the ELisp
|
||||
exists. See the node "Displaying Buffers in Side Windows" in the Elisp
|
||||
manual for more details.
|
||||
|
||||
* Lisp Changes in Emacs 26.1
|
||||
|
@ -1493,13 +1493,13 @@ range of indentation.
|
|||
|
||||
** New function 'secure-hash-algorithms' to list the algorithms that
|
||||
'secure-hash' supports.
|
||||
See the node "(elisp) Checksum/Hash" in the ELisp manual for details.
|
||||
See the node "(elisp) Checksum/Hash" in the Elisp manual for details.
|
||||
|
||||
** Emacs now exposes the GnuTLS cryptographic API with the functions
|
||||
'gnutls-macs' and 'gnutls-hash-mac'; 'gnutls-digests' and
|
||||
'gnutls-hash-digest'; 'gnutls-ciphers' and 'gnutls-symmetric-encrypt'
|
||||
and 'gnutls-symmetric-decrypt'.
|
||||
See the node "(elisp) GnuTLS Cryptography" in the ELisp manual for details.
|
||||
See the node "(elisp) GnuTLS Cryptography" in the Elisp manual for details.
|
||||
|
||||
** The function 'gnutls-available-p' now returns a list of capabilities
|
||||
supported by the GnuTLS library used by Emacs.
|
||||
|
@ -1707,7 +1707,7 @@ frame's outer border.
|
|||
frame.
|
||||
|
||||
**** 'parent-frame' makes a frame the child frame of another Emacs
|
||||
frame. The section "(elisp) Child Frames" in the ELisp manual
|
||||
frame. The section "(elisp) Child Frames" in the Elisp manual
|
||||
describes the intrinsics of that relationship.
|
||||
|
||||
**** 'delete-before' triggers deletion of one frame before that of
|
||||
|
@ -1782,12 +1782,12 @@ function 'display-buffer-in-side-window' will display its buffer in a
|
|||
side window. Functions for toggling all side windows on a frame,
|
||||
changing and reversing the layout of side windows and returning the
|
||||
main (major non-side) window of a frame are provided. For details
|
||||
consult the section "(elisp) Side Windows" in the ELisp manual.
|
||||
consult the section "(elisp) Side Windows" in the Elisp manual.
|
||||
|
||||
*** Support for atomic windows - rectangular compositions of windows
|
||||
treated by 'split-window', 'delete-window' and 'delete-other-windows'
|
||||
like a single live window - is now official. For details consult the
|
||||
section "(elisp) Atomic Windows" in the ELisp manual.
|
||||
section "(elisp) Atomic Windows" in the Elisp manual.
|
||||
|
||||
*** New 'display-buffer' alist entry 'window-parameters' allows the
|
||||
assignment of window parameters to the window used for displaying the
|
||||
|
@ -1826,7 +1826,7 @@ window's body.
|
|||
|
||||
*** The semantics of 'mouse-autoselect-window' has changed slightly.
|
||||
For details see the section "(elisp) Mouse Window Auto-selection" in
|
||||
the ELisp manual.
|
||||
the Elisp manual.
|
||||
|
||||
*** 'select-frame-by-name' now may return a frame on another display
|
||||
if it does not find a suitable one on the current display.
|
||||
|
|
|
@ -3906,7 +3906,7 @@ support these coding-systems.
|
|||
This new system is provided by the new macro 'bindat-type' and
|
||||
obsoletes the old data layout specifications. It supports
|
||||
arbitrary-size integers, recursive types, and more. See the Info node
|
||||
"(elisp) Byte Packing" in the ELisp manual for more details.
|
||||
"(elisp) Byte Packing" in the Elisp manual for more details.
|
||||
|
||||
** New macro 'with-environment-variables'.
|
||||
This macro allows setting environment variables temporarily when
|
||||
|
|
|
@ -2390,7 +2390,7 @@ This line typically looks something like
|
|||
|
||||
;;; My little pony mode -*- lexical-binding: t -*-
|
||||
|
||||
It is needed to inform the compiler about which dialect of ELisp
|
||||
It is needed to inform the compiler about which dialect of Elisp
|
||||
your code is using: the modern dialect with lexical binding or
|
||||
the old dialect with only dynamic binding.
|
||||
|
||||
|
|
6
etc/TODO
6
etc/TODO
|
@ -105,7 +105,7 @@ longer)."
|
|||
|
||||
** Do interactive mode tagging for commands
|
||||
Change "(interactive)" to "(interactive nil foo-mode)" for command
|
||||
completion purposes. Pick a major mode or ELisp library, and check
|
||||
completion purposes. Pick a major mode or Elisp library, and check
|
||||
all interactive commands to see if they are only relevant in one
|
||||
particular mode. This requires care as some commands might be useful
|
||||
outside of the mode they were written for.
|
||||
|
@ -730,9 +730,9 @@ H-S-C-M-s-double-wheel-up, ...
|
|||
|
||||
*** Support for the $ (paired delimiter) in parse-partial-sexp
|
||||
|
||||
*** Support for hook-chars whose effect is specified by ELisp code
|
||||
*** Support for hook-chars whose effect is specified by Elisp code
|
||||
Hook-chars could have their effect on the parsing-state specified by
|
||||
ELisp code. Thus a character could both close a string and open a
|
||||
Elisp code. Thus a character could both close a string and open a
|
||||
comment at the same time and do it in a context-sensitive way.
|
||||
|
||||
*** Ability to add mode-specific data to the partial-parse-state
|
||||
|
|
|
@ -700,7 +700,7 @@ The following OPTIONS are accepted:\n\
|
|||
", "\
|
||||
-F ALIST, --frame-parameters=ALIST\n\
|
||||
Set the parameters of a new frame\n\
|
||||
-e, --eval Evaluate the FILE arguments as ELisp expressions\n\
|
||||
-e, --eval Evaluate the FILE arguments as Elisp expressions\n\
|
||||
-n, --no-wait Don't wait for the server to return\n\
|
||||
-w, --timeout=SECONDS Seconds to wait before timing out\n\
|
||||
-q, --quiet Don't display messages on success\n\
|
||||
|
|
|
@ -638,7 +638,7 @@ will ensure that any results will actually have a :secret
|
|||
property.
|
||||
|
||||
:delete t means to delete any found entries. nil by default.
|
||||
Use `auth-source-delete' in ELisp code instead of calling
|
||||
Use `auth-source-delete' in Elisp code instead of calling
|
||||
`auth-source-search' directly with this parameter.
|
||||
|
||||
:type (X Y Z) will check only those backend types. `netrc' and
|
||||
|
|
|
@ -926,7 +926,7 @@ See `semantic-format-tag-prototype' for Emacs Lisp for more details."
|
|||
(defvar-mode-local emacs-lisp-mode semantic-stickyfunc-sticky-classes
|
||||
'(function type variable)
|
||||
"Add variables.
|
||||
ELisp variables can be pretty long, so track this one too.")
|
||||
Elisp variables can be pretty long, so track this one too.")
|
||||
|
||||
(with-suppressed-warnings ((obsolete define-child-mode))
|
||||
;; FIXME: We should handle this some other way!
|
||||
|
|
|
@ -3461,12 +3461,12 @@ Automatically called by the Emacs Lisp byte compiler as a
|
|||
|
||||
;; `wisent--compile-grammar' generates the actual parse table
|
||||
;; we need at run-time, but in order to be able to compile the code it
|
||||
;; contains, we need to "reify" it back into a piece of ELisp code
|
||||
;; contains, we need to "reify" it back into a piece of Elisp code
|
||||
;; which (re)builds it.
|
||||
;; This is needed for 2 reasons:
|
||||
;; - The parse tables include an obarray and these don't survive the print+read
|
||||
;; steps involved in generating a `.elc' file and reading it back in.
|
||||
;; - Within the parse table vectors/obarrays we have ELisp functions which
|
||||
;; - Within the parse table vectors/obarrays we have Elisp functions which
|
||||
;; we want to byte-compile, but if we were to just `quote' the table
|
||||
;; we'd get them with the same non-compiled functions.
|
||||
(defun wisent-automaton-lisp-form (automaton)
|
||||
|
|
|
@ -89,7 +89,7 @@ Calls `srecode-semantic-apply-tag-to-dict-default' first."
|
|||
(let* ((tag (oref tagobj prime))
|
||||
(doc (semantic-tag-docstring tag)))
|
||||
|
||||
;; It is much more common to have doc on ELisp.
|
||||
;; It is much more common to have doc on Elisp.
|
||||
(srecode-dictionary-set-value dict "DOC" doc)
|
||||
|
||||
(cond
|
||||
|
|
|
@ -604,7 +604,7 @@ This function also removes `unset' properties and calls
|
|||
Every function is called with one argument, a hash-table indexed by
|
||||
EditorConfig settings represented as symbols and whose corresponding value
|
||||
is represented as a string. It should return a list of (VAR . VAL) settings
|
||||
where VAR is an ELisp variable and VAL is the value to which it should be set.")
|
||||
where VAR is an Elisp variable and VAL is the value to which it should be set.")
|
||||
|
||||
(defun editorconfig--get-local-variables (props)
|
||||
"Get variables settings according to EditorConfig PROPS."
|
||||
|
|
|
@ -883,11 +883,11 @@ controlled in the following way:
|
|||
- If the list of fields is preceded with `:pack-var VAR' then the object to
|
||||
be packed is bound to VAR when evaluating the EXPs of `:pack-val'.
|
||||
|
||||
All the above BITLEN, LEN, LE, COUNT, and EXP are ELisp expressions evaluated
|
||||
All the above BITLEN, LEN, LE, COUNT, and EXP are Elisp expressions evaluated
|
||||
in the current lexical context extended with the previous fields.
|
||||
|
||||
TYPE can additionally be one of the Bindat type macros defined with
|
||||
`bindat-defmacro' (and listed below) or an ELisp expression which returns
|
||||
`bindat-defmacro' (and listed below) or an Elisp expression which returns
|
||||
a bindat type expression."
|
||||
(declare (indent 0) (debug (bindat-type)))
|
||||
`(progn
|
||||
|
|
|
@ -172,7 +172,7 @@ Earlier variables shadow later ones with the same name.")
|
|||
;; When the function comes from another file, we byte-compile
|
||||
;; the inlined function first, and then inline its byte-code.
|
||||
;; This also has the advantage that the final code does not
|
||||
;; depend on the order of compilation of ELisp files, making
|
||||
;; depend on the order of compilation of Elisp files, making
|
||||
;; the build more reproducible.
|
||||
(if (eq fn localfn)
|
||||
;; From the same file => same mode.
|
||||
|
|
|
@ -904,7 +904,7 @@ lexically and dynamically bound symbols actually used by FORM."
|
|||
|
||||
(defun cconv-make-interpreted-closure (args body env docstring iform)
|
||||
"Make a closure for the interpreter.
|
||||
This is intended to be called at runtime by the ELisp interpreter (when
|
||||
This is intended to be called at runtime by the Elisp interpreter (when
|
||||
the code has not been compiled).
|
||||
FUN is the closure's source code, must be a lambda form.
|
||||
ENV is the runtime representation of the lexical environment,
|
||||
|
@ -950,7 +950,7 @@ for the lexical bindings."
|
|||
(newenv (nconc (mapcar (lambda (fv) (assq fv env)) (car fvs))
|
||||
(cdr fvs))))
|
||||
;; Never return a nil env, since nil means to use the dynbind
|
||||
;; dialect of ELisp.
|
||||
;; dialect of Elisp.
|
||||
(make-interpreted-closure args expanded-fun-body (or newenv '(t))
|
||||
docstring iform)))))
|
||||
|
||||
|
|
|
@ -2060,7 +2060,7 @@ a `let' form, except that the list of symbols can be computed at run-time."
|
|||
(funcall (cdr found) cl--labels-magic)))))
|
||||
(if (and replacement (eq cl--labels-magic (car replacement)))
|
||||
(nth 1 replacement)
|
||||
;; FIXME: Here, we'd like to return the `&whole' form, but since ELisp
|
||||
;; FIXME: Here, we'd like to return the `&whole' form, but since Elisp
|
||||
;; doesn't have that, we approximate it via `cl--labels-convert-cache'.
|
||||
(let ((res `(function ,f)))
|
||||
(setq cl--labels-convert-cache (cons f res))
|
||||
|
|
|
@ -513,10 +513,10 @@ This will generate compile-time constants from BINDINGS."
|
|||
;; Constant values.
|
||||
(,(lambda (bound) (lisp-mode--search-key ":" bound))
|
||||
(0 font-lock-builtin-face))
|
||||
;; ELisp and Common Lisp `&' keywords as types.
|
||||
;; Elisp and Common Lisp `&' keywords as types.
|
||||
(,(lambda (bound) (lisp-mode--search-key "&" bound))
|
||||
(0 font-lock-type-face))
|
||||
;; ELisp regexp grouping constructs
|
||||
;; Elisp regexp grouping constructs
|
||||
(,(lambda (bound)
|
||||
(catch 'found
|
||||
;; The following loop is needed to continue searching after matches
|
||||
|
@ -568,10 +568,10 @@ This will generate compile-time constants from BINDINGS."
|
|||
;; Constant values.
|
||||
(,(lambda (bound) (lisp-mode--search-key ":" bound))
|
||||
(0 font-lock-builtin-face))
|
||||
;; ELisp and Common Lisp `&' keywords as types.
|
||||
;; Elisp and Common Lisp `&' keywords as types.
|
||||
(,(lambda (bound) (lisp-mode--search-key "&" bound))
|
||||
(0 font-lock-type-face))
|
||||
;; ELisp regexp grouping constructs
|
||||
;; Elisp regexp grouping constructs
|
||||
;; This is too general -- rms.
|
||||
;; A user complained that he has functions whose names start with `do'
|
||||
;; and that they get the wrong color.
|
||||
|
@ -1433,14 +1433,14 @@ Any non-integer value means do not use a different value of
|
|||
:version "30.1")
|
||||
|
||||
(defvar lisp-fill-paragraphs-as-doc-string t
|
||||
"Whether `lisp-fill-paragraph' should fill strings as ELisp doc strings.
|
||||
"Whether `lisp-fill-paragraph' should fill strings as Elisp doc strings.
|
||||
The default behavior of `lisp-fill-paragraph' is tuned for filling Emacs
|
||||
Lisp doc strings, with their special treatment for the first line.
|
||||
Specifically, strings are filled in a narrowed context to avoid filling
|
||||
surrounding code, which means any leading indent is disregarded, which
|
||||
can cause the filled string to extend passed the configured
|
||||
`fill-column' variable value. If you would rather fill the string in
|
||||
its original context, disregarding the special conventions of ELisp doc
|
||||
its original context, disregarding the special conventions of Elisp doc
|
||||
strings, and want to ensure the `fill-column' value is more strictly
|
||||
respected, set this variable to nil. Doing so makes
|
||||
`lisp-fill-paragraph' behave as it used to in Emacs 27 and prior
|
||||
|
|
|
@ -729,7 +729,7 @@ test of free variables in the following ways:
|
|||
- It does not distinguish variables from functions, so it can be used
|
||||
both to detect whether a given variable is used by SEXP and to
|
||||
detect whether a given function is used by SEXP.
|
||||
- It does not actually know ELisp syntax, so it only looks for the presence
|
||||
- It does not actually know Elisp syntax, so it only looks for the presence
|
||||
of symbols in SEXP and can't distinguish if those symbols are truly
|
||||
references to the given variable (or function). That can make the result
|
||||
include bindings which actually aren't used.
|
||||
|
|
|
@ -555,7 +555,7 @@ immutable fields are indeed not mutated."
|
|||
(defun cconv--interactive-helper (fun if)
|
||||
"Add interactive \"form\" IF to FUN.
|
||||
Returns a new command that otherwise behaves like FUN.
|
||||
IF can be an ELisp form to be interpreted or a function of no arguments."
|
||||
IF can be an Elisp form to be interpreted or a function of no arguments."
|
||||
(oclosure-lambda (cconv--interactive-helper (fun fun) (if if))
|
||||
(&rest args)
|
||||
(apply (if (called-interactively-p 'any)
|
||||
|
|
|
@ -77,7 +77,7 @@
|
|||
;; modes. For the `rx' syntax the function `rx-to-string' is applied to
|
||||
;; the evaluated expression read. So you can use quoted arguments
|
||||
;; with something like '("findme") or you can construct arguments to
|
||||
;; your hearts delight with a valid ELisp expression. (The compiled
|
||||
;; your hearts delight with a valid Elisp expression. (The compiled
|
||||
;; string form will be copied by `reb-copy') If you want to take
|
||||
;; a glance at the corresponding string you can temporarily change the
|
||||
;; input syntax.
|
||||
|
|
|
@ -219,7 +219,7 @@ PAR is a number of a regexp grouping whose text will be passed to
|
|||
:version "28.1")
|
||||
|
||||
(defcustom erc-emacswiki-lisp-url "https://www.emacswiki.org/elisp/"
|
||||
"URL of the EmacsWiki ELisp area."
|
||||
"URL of the EmacsWiki Elisp area."
|
||||
:type 'string)
|
||||
|
||||
(defvar erc-button-highlight-nick-once '(QUIT PART JOIN)
|
||||
|
|
|
@ -254,7 +254,7 @@ interactive command."
|
|||
(setq fn (intern val)))
|
||||
;; These error messages are intended to be less technical for the
|
||||
;; `describe-command' case, as they are directed at users that are
|
||||
;; not necessarily ELisp programmers.
|
||||
;; not necessarily Elisp programmers.
|
||||
(unless (and fn (symbolp fn))
|
||||
(user-error (if want-command
|
||||
"You didn't specify a command's symbol"
|
||||
|
|
|
@ -2087,7 +2087,7 @@ key, a click, or a menu-item"))
|
|||
'(menu-item "Look Up Key in User Manual..." Info-goto-emacs-key-command-node
|
||||
:help "Display manual section that describes a key"))
|
||||
(define-key menu [lookup-subject-in-elisp-manual]
|
||||
'(menu-item "Look Up Subject in ELisp Manual..." elisp-index-search
|
||||
'(menu-item "Look Up Subject in Elisp Manual..." elisp-index-search
|
||||
:help "Find description of a subject in Emacs Lisp manual"))
|
||||
(define-key menu [lookup-subject-in-emacs-manual]
|
||||
'(menu-item "Look Up Subject in User Manual..." emacs-index-search
|
||||
|
|
|
@ -109,7 +109,7 @@ When it is used for regexp matching, the regexp groups are
|
|||
3 for the verbosity level.")
|
||||
|
||||
(defconst tramp-debug-font-lock-keywords
|
||||
;; FIXME: Make it a function instead of an ELisp expression, so you
|
||||
;; FIXME: Make it a function instead of an Elisp expression, so you
|
||||
;; can evaluate it with `funcall' rather than `eval'!
|
||||
;; Also, in `font-lock-defaults' you can specify a function name for
|
||||
;; the "KEYWORDS" part, so font-lock calls it to get the actual keywords!
|
||||
|
|
|
@ -658,7 +658,7 @@ When called with a `C-0' (zero) prefix, insert a template at point.
|
|||
When called with a `C-1' (one) prefix, force prompting for a date when
|
||||
a datetree entry is made.
|
||||
|
||||
ELisp programs can set KEYS to a string associated with a template
|
||||
Elisp programs can set KEYS to a string associated with a template
|
||||
in `org-capture-templates'. In this case, interactive selection
|
||||
will be bypassed.
|
||||
|
||||
|
|
|
@ -3157,16 +3157,16 @@ There are multiple ways to set the category. One way is to set
|
|||
it in the document property drawer. For example:
|
||||
|
||||
:PROPERTIES:
|
||||
:CATEGORY: ELisp
|
||||
:CATEGORY: Elisp
|
||||
:END:
|
||||
|
||||
Other ways to define it is as an Emacs file variable, for example
|
||||
|
||||
# -*- mode: org; org-category: \"ELisp\"
|
||||
# -*- mode: org; org-category: \"Elisp\"
|
||||
|
||||
or for the file to contain a special line:
|
||||
|
||||
#+CATEGORY: ELisp
|
||||
#+CATEGORY: Elisp
|
||||
|
||||
If the file does not specify a category, then file's base name
|
||||
is used instead.")
|
||||
|
@ -9422,7 +9422,7 @@ With numeric prefix arg, switch to the Nth state.
|
|||
With a numeric prefix arg of 0, inhibit note taking for the change.
|
||||
With a numeric prefix arg of -1, cancel repeater to allow marking as DONE.
|
||||
|
||||
When called through ELisp, arg is also interpreted in the following way:
|
||||
When called through Elisp, arg is also interpreted in the following way:
|
||||
`none' -> empty state
|
||||
\"\" -> switch to empty state
|
||||
`done' -> switch to DONE
|
||||
|
|
|
@ -6660,7 +6660,7 @@ to `:default' encoding. If it fails, return S."
|
|||
"Call function FUN on the results returned by BODY evaluation.
|
||||
|
||||
FUN is an anonymous function of one argument. BODY should be a valid
|
||||
ELisp source expression. BODY evaluation happens in an asynchronous process,
|
||||
Elisp source expression. BODY evaluation happens in an asynchronous process,
|
||||
from a buffer which is an exact copy of the current one.
|
||||
|
||||
Use `org-export-add-to-stack' in FUN in order to register results
|
||||
|
|
|
@ -325,7 +325,7 @@ happens in interactive invocations."
|
|||
|
||||
;;;###autoload
|
||||
(define-derived-mode emacs-lisp-mode lisp-data-mode
|
||||
`("ELisp"
|
||||
`("Elisp"
|
||||
(lexical-binding (:propertize "/l"
|
||||
help-echo "Using lexical-binding mode")
|
||||
(:propertize "/d"
|
||||
|
|
|
@ -659,7 +659,7 @@ rulesets defined previously with `define-peg-ruleset'."
|
|||
|
||||
;; This is the main translation function.
|
||||
(defun peg-translate-exp (exp)
|
||||
"Return the ELisp code to match the PE EXP."
|
||||
"Return the Elisp code to match the PE EXP."
|
||||
;; FIXME: This expansion basically duplicates `exp' in the output, which is
|
||||
;; a serious problem because it's done recursively, so it makes the output
|
||||
;; code's size exponentially larger than the input!
|
||||
|
|
|
@ -35,7 +35,7 @@
|
|||
|
||||
;; This file defines ruby-ts-mode which is a major mode for editing
|
||||
;; Ruby files that uses Tree Sitter to parse the language. More
|
||||
;; information about Tree Sitter can be found in the ELisp Info pages
|
||||
;; information about Tree Sitter can be found in the Elisp Info pages
|
||||
;; as well as this website: https://tree-sitter.github.io/tree-sitter/
|
||||
|
||||
;; For this major mode to work, Emacs has to be compiled with
|
||||
|
|
|
@ -1861,7 +1861,7 @@ Argument EVENT is the invoking mouse event."
|
|||
|
||||
(define-derived-mode woman-mode man-common "WoMan"
|
||||
"Turn on (most of) Man mode to browse a buffer formatted by WoMan.
|
||||
WoMan is an ELisp emulation of much of the functionality of the Emacs
|
||||
WoMan is an Elisp emulation of much of the functionality of the Emacs
|
||||
`man' command running the standard UN*X man and ?roff programs.
|
||||
WoMan author: F.J.Wright@Maths.QMW.ac.uk
|
||||
See `Man-mode' for additional details.
|
||||
|
@ -3508,7 +3508,7 @@ The expression may be an argument in quotes."
|
|||
((memq (setq op (following-char)) '(?& ?:)) ; Boolean and / or
|
||||
(forward-char)
|
||||
(setq value
|
||||
;; and / or are special forms, not functions, in ELisp
|
||||
;; and / or are special forms, not functions, in Elisp
|
||||
(if (eq op ?&)
|
||||
;; and
|
||||
(if (> value 0)
|
||||
|
|
|
@ -1066,7 +1066,7 @@ map_char_table_for_charset (void (*c_function) (Lisp_Object, Lisp_Object),
|
|||
vector of property values (symbols nil, L, R, etc).
|
||||
|
||||
The full list of Unicode character properties supported by Emacs is
|
||||
documented in the ELisp manual, in the node "Character Properties".
|
||||
documented in the Elisp manual, in the node "Character Properties".
|
||||
|
||||
A table for Unicode character property has these characteristics:
|
||||
|
||||
|
|
|
@ -6196,7 +6196,7 @@ extract_data_from_object (Lisp_Object spec,
|
|||
/* Format: (iv-auto REQUIRED-LENGTH). */
|
||||
|
||||
if (! FIXNATP (start))
|
||||
error ("Without a length, `iv-auto' can't be used; see ELisp manual");
|
||||
error ("Without a length, `iv-auto' can't be used; see Elisp manual");
|
||||
else
|
||||
{
|
||||
EMACS_INT start_hold = XFIXNAT (start);
|
||||
|
|
|
@ -1892,7 +1892,7 @@ do_switch_frame (Lisp_Object frame, int track, int for_deletion, Lisp_Object nor
|
|||
|
||||
/* After setting `selected_frame`, we're temporarily in an inconsistent
|
||||
state where (selected-window) != (frame-selected-window). Until this
|
||||
invariant is restored we should be very careful not to run ELisp code.
|
||||
invariant is restored we should be very careful not to run Elisp code.
|
||||
(bug#58343) */
|
||||
selected_frame = frame;
|
||||
|
||||
|
|
|
@ -6349,7 +6349,7 @@ make_lispy_event (struct input_event *event)
|
|||
if (NILP (item))
|
||||
return Qnil;
|
||||
|
||||
/* ELisp manual 2.4b says (x y) are window
|
||||
/* Elisp manual 2.4b says (x y) are window
|
||||
relative but code says they are
|
||||
frame-relative. */
|
||||
position = list4 (event->frame_or_window,
|
||||
|
@ -6836,7 +6836,7 @@ make_lispy_event (struct input_event *event)
|
|||
if (NILP (item))
|
||||
return Qnil;
|
||||
|
||||
/* ELisp manual 2.4b says (x y) are window
|
||||
/* Elisp manual 2.4b says (x y) are window
|
||||
relative but code says they are
|
||||
frame-relative. */
|
||||
position = list4 (event->frame_or_window,
|
||||
|
|
|
@ -930,7 +930,7 @@ See Bug#57915."
|
|||
(cl-flet ((fn (&key x) x))
|
||||
(should-error (fn :x))
|
||||
(should (eq (fn :x :a) :a)))
|
||||
;; In ELisp function arguments are always statically scoped (bug#47552).
|
||||
;; In Elisp function arguments are always statically scoped (bug#47552).
|
||||
(let ((cl--test-a 'dyn)
|
||||
;; FIXME: How do we silence the "Lexical argument shadows" warning?
|
||||
(f
|
||||
|
|
|
@ -90,7 +90,7 @@
|
|||
(shortdoc-function-examples 'string-match-p)))))
|
||||
|
||||
(ert-deftest shortdoc-help-fns-examples-function-test ()
|
||||
"Test that `shortdoc-help-fns-examples-function' correctly prints ELisp function examples."
|
||||
"Test that `shortdoc-help-fns-examples-function' correctly prints Elisp function examples."
|
||||
(with-temp-buffer
|
||||
(shortdoc-help-fns-examples-function 'string-fill)
|
||||
(should (equal "\n Examples:\n\n (string-fill \"Three short words\" 12)\n => \"Three short\\nwords\"\n (string-fill \"Long-word\" 3)\n => \"Long-word\"\n\n"
|
||||
|
|
|
@ -5670,7 +5670,7 @@ make_lispy_event (struct input_event *event)
|
|||
}
|
||||
}
|
||||
|
||||
/* ELisp manual 2.4b says (x y) are window
|
||||
/* Elisp manual 2.4b says (x y) are window
|
||||
relative but code says they are
|
||||
frame-relative. */
|
||||
position = list4 (event->frame_or_window,
|
||||
|
|
Loading…
Add table
Reference in a new issue