Emacs Lispemacs lisp reference manual, emacs lisp
Emacs Lisp is a dialect of the Lisp programming language used as a scripting language by Emacs a text editor family most commonly associated with GNU Emacs and XEmacs It is used for implementing most of the editing functionality built into Emacs, the remainder being written in C as is the Lisp interpreter itself Emacs Lisp is also referred to as Elisp, although there is also an older, unrelated Lisp dialect with that name
Users of Emacs commonly write Emacs Lisp code to customize and extend Emacs Other options include the "Customize" feature that's been in GNU Emacs since version 20 Itself written in Emacs Lisp, Customize provides a set of preferences pages allowing the user to set options and preview their effect in the running Emacs session When the user saves their changes, Customize simply writes the necessary Emacs Lisp code to the user's config file, which can be set to a special file that only Customize uses, to avoid the possibility of messing up the users own file
Emacs Lisp can also function as a scripting language, much like the Unix Bourne shell or Perl, by calling Emacs in "batch mode" In this way it may be called from the command line or via an executable file, and its editing functions, such as buffers and movement commands are available to the program just as in the normal mode No user interface is presented when Emacs is started in batch mode; it simply executes the passed-in script and exits, displaying any output from the script
- 1 Compared to other Lisp dialects
- 2 Example
- 3 Source code
- 31 Byte code
- 4 Language features
- 41 From dynamic to lexical scoping
- 5 References
- 6 External links
Compared to other Lisp dialectsedit
Emacs Lisp is most closely related to Maclisp, with some later influence from Common Lisp1 It supports imperative and functional programming methods Richard Stallman chose Lisp as the extension language for his rewrite of Emacs the original used TECO as its extension language because of its powerful features, including the ability to treat functions as data Although the Common Lisp standard had yet to be formulated, Scheme existed at the time Stallman was rewriting Gosling Emacs into GNU Emacs He chose not to use it because of its comparatively poor performance on workstations as opposed to the minicomputers that were Emacs' traditional home, and he wanted to develop a dialect which he thought would be more easily optimized2
The Lisp dialect used in Emacs differs substantially from the more modern Common Lisp and Scheme dialects used for applications programming A prominent characteristic of Emacs Lisp is in its use of dynamic rather than lexical scope by default see below That is, a function may reference local variables in the scope it is called from, but not in the scope where it was defined
To understand the logic behind Emacs Lisp, it is important to remember that there is an emphasis on providing data structures and features specific to making a versatile text editor over implementing a general-purpose programming language For example, Emacs Lisp cannot easily read a file a line at a time—the entire file must be read into an Emacs buffer However, Emacs Lisp provides many features for navigating and modifying buffer text at a sentence, paragraph, or higher syntactic level as defined by modes
Here follows a simple example of an Emacs extension written in Emacs Lisp In Emacs, the editing area can be split into separate areas called windows, each displaying a different buffer A buffer is a region of text loaded into Emacs' memory possibly from a file which can be saved into a text document
Users can press the default "C-x 2" key binding to open a new window This runs the Emacs Lisp function split-window-vertically Normally, when the new window appears, it displays the same buffer as the previous one Suppose we wish to make it display the next available buffer In order to do this, the user writes the following Emacs Lisp code, in either an existing Emacs Lisp source file or an empty Emacs buffer:defun my-split-window-func interactive split-window-vertically set-window-buffer next-window other-buffer global-set-key "\C-x2" 'my-split-window-func
The first statement, defun , defines a new function, my-split-window-func, which calls split-window-vertically the old window-splitting function, then tells the new window to display another new buffer The second statement, global-set-key re-binds the key sequence "C-x 2" to the new function
This can also be written using the feature called advice, which allows the user to create wrappers around existing functions instead of defining their own This has the advantage of not requiring keybindings to be changed and working wherever the original function is called, as well as being simpler to write but the disadvantage of making debugging more complicated For this reason, advice is not allowed in the source code of GNU Emacs itself,3 but if a user wishes, the advice feature can be used in their own code to reimplement the above code as follows:defadvice split-window-vertically after my-window-splitting-advice first activate set-window-buffer next-window other-buffer
This instructs split-window-vertically to execute the user-supplied code whenever it is called, before executing the rest of the function Advice can also be specified to execute after the original function, around it—literally wrapping the original, or to conditionally execute the original function based on the results of the advice
Emacs 244 replaces4 this defadvice mechanism with advice-add, which is claimed to be more flexible and simpler5 The advice above could be reimplemented using the new system as:defun switch-to-next-window-in-split set-window-buffer next-window other-buffer advice-add 'split-window-vertically :before #'switch-to-next-window-in-split
These changes take effect as soon as the code is evaluated It is not necessary to recompile, restart Emacs, or even rehash a configuration file If the code is saved into an Emacs init file, then Emacs will load the extension the next time it starts Otherwise, the changes will have to be reevaluated manually when the user restarts Emacs
Emacs Lisp code is stored in filesystems as plain text files, by convention with the filename suffix "el" The user's init file is an exception, often appearing as "emacs" despite being evaluated as any Emacs Lisp code Recent versions of Emacs "recent" in a 40-year-old program meaning roughly any version released since the mid-1990s will also load ~/emacsel and ~/emacsd/initel Additionally, users may specify any file to load as a config file on the command line, or explicitly state that no config file is to be loaded When the files are loaded, an interpreter component of the Emacs program reads and parses the functions and variables, storing them in memory They are then available to other editing functions, and to user commands Functions and variables can be freely modified and redefined without restarting the editor or reloading the config file
In order to save time and memory space, much of the functionality of Emacs loads only when required Each set of optional features shipped with Emacs is implemented by a collection of Emacs code called a package or library For example, there is a library for highlighting keywords in program source code, and a library for playing the game of Tetris Each library is implemented using one or more Emacs Lisp source files Libraries can define one or more "major modes" to activate and control their functionality
Emacs developers write certain functions in C These are "primitives", also known as "built-in functions" or "subrs" Although primitives can be called from Lisp code, they can only be modified by editing the C source files and recompiling In GNU Emacs, primitives are not available as external libraries; they are part of the Emacs executable In XEmacs, runtime loading of such primitives is possible, using the operating system's support for dynamic linking Functions may be written as primitives because they need access to external data and libraries not otherwise available from Emacs Lisp, or because they are called often enough that the comparative speed of C versus Emacs Lisp makes a worthwhile difference
However, because errors in C code can easily lead to segmentation violations or to more subtle bugs, which crash the editor, and because writing C code that interacts correctly with the Emacs Lisp garbage collector is error-prone, the number of functions implemented as primitives is kept to a necessary minimum
"Byte-compilation" can make Emacs Lisp code execute faster Emacs contains a compiler which can translate Emacs Lisp source files into a special representation known as bytecode Emacs Lisp bytecode files have the filename suffix "elc" Compared to source files, bytecode files load faster, occupy less space on the disk, use less memory when loaded, and run faster
Bytecode still runs more slowly than primitives, but functions loaded as bytecode can be easily modified and re-loaded In addition, bytecode files are platform-independent The standard Emacs Lisp code distributed with Emacs is loaded as bytecode, although the matching source files are usually provided for the user's reference as well User-supplied extensions are typically not byte-compiled, as they are neither as large nor as computationally intensive
Notably, the "cl" package implements a fairly large subset of Common Lisp
Emacs Lisp unlike some other Lisp implementations does not do tail-call optimization6 Without this, tail recursions can eventually lead to stack overflow
The apel library aids in writing portable Emacs Lisp code, with the help of the polysylabi platform bridge
Emacs Lisp is a Lisp-2 meaning that it has a function namespace which is separate from the namespace it uses for other variables7
From dynamic to lexical scopingedit
Like MacLisp, Emacs Lisp uses dynamic scope, offering static or lexical as an option starting from version 248 It can be activated by setting the file local variable lexical-binding910
In dynamic scoping, if a programmer declares a variable within the scope of a function, it is available to subroutines called from within that function Originally, this was intended as an optimization; lexical scoping was still uncommon and of uncertain performance "I asked RMS when he was implementing emacs lisp why it was dynamically scoped and his exact reply was that lexical scope was too inefficient"11 Dynamic scoping was also meant to provide greater flexibility for user customizations However, dynamic scoping has several disadvantages Firstly, it can easily lead to bugs in large programs, due to unintended interactions between variables in different functions Secondly, accessing variables under dynamic scoping is generally slower than under lexical scopingcitation needed
Also, the lexical-let macro in the "cl" package does provide effective lexical scope to Emacs Lisp programmers, but while `cl' is widely used, lexical-let is rarely used
- ^ "GNU Emacs Lisp is largely inspired by Maclisp, and a little by Common Lisp If you know Common Lisp, you will notice many similarities However, many features of Common Lisp have been omitted or simplified in order to reduce the memory requirements of GNU Emacs Sometimes the simplifications are so drastic that a Common Lisp user might be very confused We will occasionally point out how GNU Emacs Lisp differs from Common Lisp" — from the "History" section of the "Introduction" to the Emacs Lisp Manual, as of Emacs 21
- ^ "So the development of that operating system, the GNU operating system, is what led me to write the GNU Emacs In doing this, I aimed to make the absolute minimal possible Lisp implementation The size of the programs was a tremendous concern There were people in those days, in 1985, who had one-megabyte machines without virtual memory They wanted to be able to use GNU Emacs This meant I had to keep the program as small as possible" — from "My Lisp Experiences and the Development of GNU Emacs"
- ^ "Re: Emacs-diffs /srv/bzr/emacs/trunk r111086: gmm-utilsel gmm-flet" Listsgnuorg 2012-12-05 Retrieved 2013-08-18
- ^ "NEWS244"
- ^ "Porting old advices"
- ^ "Lisp programmers will want to note that the current Emacs Lisp compiler does not optimize tail recursion" Gnuorg Retrieved 2013-08-18
- ^ https://groupsgooglecom/forum/#!topic/learn-elisp-for-emacs/RKRDc1Qw3Bs
- ^ "Emacs 241 released" Listsgnuorg Retrieved 2013-08-18
- ^ "Lexical binding" Listsgnuorg 2011-04-01 Retrieved 2013-08-18
- ^ "Dynamic Binding Vs Lexical Binding" EmacsWiki 2013-05-17 Retrieved 2013-08-18
- ^ "T" Peoplecsailmitedu Retrieved 2013-08-18
|Wikimedia Commons has media related to Emacs Lisp|
- The Emacs page at the GNU Project
|Lisp 15||Lisp 15|
|ZetaLisp||Lisp Machine Lisp|
|Common Lisp||Common Lisp|
|Emacs Lisp||Emacs Lisp|
- Free software portal
emacs lisp, emacs lisp book, emacs lisp comment, emacs lisp define, emacs lisp evaluate buffer, emacs lisp interpreter, emacs lisp reference manual, emacs lisp scheme, emacs lisp strings, emacs lisp tutorial
Emacs Lisp Information about
Emacs Lisp viewing the topic.
There are excerpts from wikipedia on this article and video
Our site has a system which serves search engine function.
You can search all data in our system with above button which written "What did you look for? "
Welcome to our simple, stylish and fast search engine system.
We have prepared this method why you can reach most accurate and most up to date knowladge. The search engine that developed for you transmits you to the latest and exact information with its basic and quick system.
You can find nearly everything data which found from internet with this system.