1 \input texinfo @c -*- mode: texinfo; coding: utf-8 -*-
2 @comment %**start of header
3 @setfilename ../../info/eintr.info
4 @c setfilename emacs-lisp-intro.info
5 @c sethtmlfilename emacs-lisp-intro.html
6 @settitle Programming in Emacs Lisp
12 @include emacsver.texi
14 @c ================ How to Print a Book in Various Sizes ================
16 @c This book can be printed in any of three different sizes.
17 @c Set the following @-commands appropriately.
27 @c European A4 size paper:
32 @c (Note: if you edit the book so as to change the length of the
33 @c table of contents, you may have to change the value of 'pageno' below.)
35 @c <<<< For hard copy printing, this file is now
36 @c set for smallbook, which works for all sizes
37 @c of paper, and with PostScript figures >>>>
45 @c ================ Included Figures ================
47 @c If you clear this, the figures will be printed as ASCII diagrams
48 @c rather than PostScript/PDF.
49 @c (This is not relevant to Info, since Info only handles ASCII.)
50 @set print-postscript-figures
51 @c clear print-postscript-figures
53 @comment %**end of header
55 @c per rms and peterb, use 10pt fonts for the main text, mostly to
56 @c save on paper cost.
57 @c Do this inside @tex for now, so current makeinfo does not complain.
63 \global\hbadness=6666 % don't worry about not-too-underfull boxes
66 @c These refer to the printed book sold by the FSF.
67 @set edition-number 3.10
68 @set update-date 28 October 2009
70 @c For next or subsequent edition:
71 @c create function using with-output-to-temp-buffer
72 @c create a major mode, with keymaps
73 @c run an asynchronous process, like grep or diff
75 @c For 8.5 by 11 inch format: do not use such a small amount of
76 @c whitespace between paragraphs as smallbook format
79 \global\parskip 6pt plus 1pt
83 @c For all sized formats: print within-book cross
84 @c reference with ``...'' rather than [...]
86 @c This works with the texinfo.tex file, version 2003-05-04.08,
87 @c in the Texinfo version 4.6 of the 2003 Jun 13 distribution.
90 \if \xrefprintnodename
91 \global\def\xrefprintnodename#1{\unskip, ``#1''}
93 \global\def\xrefprintnodename#1{ ``#1''}
95 % \global\def\xrefprintnodename#1{, ``#1''}
98 @c ----------------------------------------------------
100 @dircategory Emacs lisp
102 * Emacs Lisp Intro: (eintr). A simple introduction to Emacs Lisp programming.
106 This is an @cite{Introduction to Programming in Emacs Lisp}, for
107 people who are not programmers.
110 Edition @value{edition-number}, @value{update-date}
113 Distributed with Emacs version @value{EMACSVER}.
116 Copyright @copyright{} 1990--1995, 1997, 2001--2016 Free Software
123 GNU Press, @hfill @uref{http://www.fsf.org/licensing/gnu-press/}@*
124 a division of the @hfill email: @email{sales@@fsf.org}@*
125 Free Software Foundation, Inc. @hfill Tel: +1 (617) 542-5942@*
126 51 Franklin Street, Fifth Floor @hfill Fax: +1 (617) 542-2652@*
127 Boston, MA 02110-1301 USA
131 Printed copies available from @uref{http://shop.fsf.org/}. Published by:
134 GNU Press, http://www.fsf.org/licensing/gnu-press/
135 a division of the email: sales@@fsf.org
136 Free Software Foundation, Inc. Tel: +1 (617) 542-5942
137 51 Franklin Street, Fifth Floor Fax: +1 (617) 542-2652
138 Boston, MA 02110-1301 USA
146 Permission is granted to copy, distribute and/or modify this document
147 under the terms of the GNU Free Documentation License, Version 1.3 or
148 any later version published by the Free Software Foundation; there
149 being no Invariant Section, with the Front-Cover Texts being ``A GNU
150 Manual'', and with the Back-Cover Texts as in (a) below. A copy of
151 the license is included in the section entitled ``GNU Free
152 Documentation License''.
154 (a) The FSF's Back-Cover Text is: ``You have the freedom to
155 copy and modify this GNU manual. Buying copies from the FSF
156 supports it in developing GNU and promoting software freedom.''
160 @c half title; two lines here, so do not use 'shorttitlepage'
163 \hbox{}\vskip 1.5in \chaprm \centerline{An Introduction to}%
165 {\begingroup\hbox{}\vskip 0.25in \chaprm%
166 \centerline{Programming in Emacs Lisp}%
167 \endgroup\page\hbox{}\page}
172 @center @titlefont{An Introduction to}
174 @center @titlefont{Programming in Emacs Lisp}
176 @center Revised Third Edition
178 @center by Robert J. Chassell
181 @vskip 0pt plus 1filll
187 @evenheading @thispage @| @| @thischapter
188 @oddheading @thissection @| @| @thispage
192 @c Keep T.O.C. short by tightening up for largebook
195 \global\parskip 2pt plus 1pt
196 \global\advance\baselineskip by -1pt
206 @top An Introduction to Programming in Emacs Lisp
210 <p>The homepage for GNU Emacs is at
211 <a href="/software/emacs/">http://www.gnu.org/software/emacs/</a>.<br>
212 To view this manual in other formats, click
213 <a href="/software/emacs/manual/eintr.html">here</a>.
219 This master menu first lists each chapter and index; then it lists
220 every node in every chapter.
223 @c >>>> Set pageno appropriately <<<<
225 @c The first page of the Preface is a roman numeral; it is the first
226 @c right handed page after the Table of Contents; hence the following
227 @c setting must be for an odd negative number.
230 @c global@pageno = -11
233 @set COUNT-WORDS count-words-example
234 @c Length of variable name chosen so that things still line up when expanded.
237 * Preface:: What to look for.
238 * List Processing:: What is Lisp?
239 * Practicing Evaluation:: Running several programs.
240 * Writing Defuns:: How to write function definitions.
241 * Buffer Walk Through:: Exploring a few buffer-related functions.
242 * More Complex:: A few, even more complex functions.
243 * Narrowing & Widening:: Restricting your and Emacs attention to
245 * car cdr & cons:: Fundamental functions in Lisp.
246 * Cutting & Storing Text:: Removing text and saving it.
247 * List Implementation:: How lists are implemented in the computer.
248 * Yanking:: Pasting stored text.
249 * Loops & Recursion:: How to repeat a process.
250 * Regexp Search:: Regular expression searches.
251 * Counting Words:: A review of repetition and regexps.
252 * Words in a defun:: Counting words in a @code{defun}.
253 * Readying a Graph:: A prototype graph printing function.
254 * Emacs Initialization:: How to write a @file{.emacs} file.
255 * Debugging:: How to run the Emacs Lisp debuggers.
256 * Conclusion:: Now you have the basics.
257 * the-the:: An appendix: how to find reduplicated words.
258 * Kill Ring:: An appendix: how the kill ring works.
259 * Full Graph:: How to create a graph with labeled axes.
260 * Free Software and Free Manuals::
261 * GNU Free Documentation License::
266 --- The Detailed Node Listing ---
270 * Why:: Why learn Emacs Lisp?
271 * On Reading this Text:: Read, gain familiarity, pick up habits....
272 * Who You Are:: For whom this is written.
274 * Note for Novices:: You can read this as a novice.
279 * Lisp Lists:: What are lists?
280 * Run a Program:: Any list in Lisp is a program ready to run.
281 * Making Errors:: Generating an error message.
282 * Names & Definitions:: Names of symbols and function definitions.
283 * Lisp Interpreter:: What the Lisp interpreter does.
284 * Evaluation:: Running a program.
285 * Variables:: Returning a value from a variable.
286 * Arguments:: Passing information to a function.
287 * set & setq:: Setting the value of a variable.
288 * Summary:: The major points.
289 * Error Message Exercises::
293 * Numbers Lists:: List have numbers, other lists, in them.
294 * Lisp Atoms:: Elemental entities.
295 * Whitespace in Lists:: Formatting lists to be readable.
296 * Typing Lists:: How GNU Emacs helps you type lists.
300 * Complications:: Variables, Special forms, Lists within.
301 * Byte Compiling:: Specially processing code for speed.
305 * How the Interpreter Acts:: Returns and Side Effects...
306 * Evaluating Inner Lists:: Lists within lists...
310 * fill-column Example::
311 * Void Function:: The error message for a symbol
313 * Void Variable:: The error message for a symbol without a value.
317 * Data types:: Types of data passed to a function.
318 * Args as Variable or List:: An argument can be the value
319 of a variable or list.
320 * Variable Number of Arguments:: Some functions may take a
321 variable number of arguments.
322 * Wrong Type of Argument:: Passing an argument of the wrong type
324 * message:: A useful function for sending messages.
326 Setting the Value of a Variable
328 * Using set:: Setting values.
329 * Using setq:: Setting a quoted value.
330 * Counting:: Using @code{setq} to count.
332 Practicing Evaluation
334 * How to Evaluate:: Typing editing commands or @kbd{C-x C-e}
336 * Buffer Names:: Buffers and files are different.
337 * Getting Buffers:: Getting a buffer itself, not merely its name.
338 * Switching Buffers:: How to change to another buffer.
339 * Buffer Size & Locations:: Where point is located and the size of
341 * Evaluation Exercise::
343 How To Write Function Definitions
345 * Primitive Functions::
346 * defun:: The @code{defun} macro.
347 * Install:: Install a function definition.
348 * Interactive:: Making a function interactive.
349 * Interactive Options:: Different options for @code{interactive}.
350 * Permanent Installation:: Installing code permanently.
351 * let:: Creating and initializing local variables.
353 * else:: If--then--else expressions.
354 * Truth & Falsehood:: What Lisp considers false and true.
355 * save-excursion:: Keeping track of point and buffer.
359 Install a Function Definition
361 * Effect of installation::
362 * Change a defun:: How to change a function definition.
364 Make a Function Interactive
366 * Interactive multiply-by-seven:: An overview.
367 * multiply-by-seven in detail:: The interactive version.
371 * Prevent confusion::
372 * Parts of let Expression::
373 * Sample let Expression::
374 * Uninitialized let Variables::
376 The @code{if} Special Form
378 * if in more detail::
379 * type-of-animal in detail:: An example of an @code{if} expression.
381 Truth and Falsehood in Emacs Lisp
383 * nil explained:: @code{nil} has two meanings.
385 @code{save-excursion}
387 * Point and mark:: A review of various locations.
388 * Template for save-excursion::
390 A Few Buffer-Related Functions
392 * Finding More:: How to find more information.
393 * simplified-beginning-of-buffer:: Shows @code{goto-char},
394 @code{point-min}, and @code{push-mark}.
395 * mark-whole-buffer:: Almost the same as @code{beginning-of-buffer}.
396 * append-to-buffer:: Uses @code{save-excursion} and
397 @code{insert-buffer-substring}.
398 * Buffer Related Review:: Review.
401 The Definition of @code{mark-whole-buffer}
403 * mark-whole-buffer overview::
404 * Body of mark-whole-buffer:: Only three lines of code.
406 The Definition of @code{append-to-buffer}
408 * append-to-buffer overview::
409 * append interactive:: A two part interactive expression.
410 * append-to-buffer body:: Incorporates a @code{let} expression.
411 * append save-excursion:: How the @code{save-excursion} works.
413 A Few More Complex Functions
415 * copy-to-buffer:: With @code{set-buffer}, @code{get-buffer-create}.
416 * insert-buffer:: Read-only, and with @code{or}.
417 * beginning-of-buffer:: Shows @code{goto-char},
418 @code{point-min}, and @code{push-mark}.
419 * Second Buffer Related Review::
420 * optional Exercise::
422 The Definition of @code{insert-buffer}
424 * insert-buffer code::
425 * insert-buffer interactive:: When you can read, but not write.
426 * insert-buffer body:: The body has an @code{or} and a @code{let}.
427 * if & or:: Using an @code{if} instead of an @code{or}.
428 * Insert or:: How the @code{or} expression works.
429 * Insert let:: Two @code{save-excursion} expressions.
430 * New insert-buffer::
432 The Interactive Expression in @code{insert-buffer}
434 * Read-only buffer:: When a buffer cannot be modified.
435 * b for interactive:: An existing buffer or else its name.
437 Complete Definition of @code{beginning-of-buffer}
439 * Optional Arguments::
440 * beginning-of-buffer opt arg:: Example with optional argument.
441 * beginning-of-buffer complete::
443 @code{beginning-of-buffer} with an Argument
445 * Disentangle beginning-of-buffer::
446 * Large buffer case::
447 * Small buffer case::
449 Narrowing and Widening
451 * Narrowing advantages:: The advantages of narrowing
452 * save-restriction:: The @code{save-restriction} special form.
453 * what-line:: The number of the line that point is on.
456 @code{car}, @code{cdr}, @code{cons}: Fundamental Functions
458 * Strange Names:: An historical aside: why the strange names?
459 * car & cdr:: Functions for extracting part of a list.
460 * cons:: Constructing a list.
461 * nthcdr:: Calling @code{cdr} repeatedly.
463 * setcar:: Changing the first element of a list.
464 * setcdr:: Changing the rest of a list.
470 * length:: How to find the length of a list.
472 Cutting and Storing Text
474 * Storing Text:: Text is stored in a list.
475 * zap-to-char:: Cutting out text up to a character.
476 * kill-region:: Cutting text out of a region.
477 * copy-region-as-kill:: A definition for copying text.
478 * Digression into C:: Minor note on C programming language macros.
479 * defvar:: How to give a variable an initial value.
480 * cons & search-fwd Review::
485 * Complete zap-to-char:: The complete implementation.
486 * zap-to-char interactive:: A three part interactive expression.
487 * zap-to-char body:: A short overview.
488 * search-forward:: How to search for a string.
489 * progn:: The @code{progn} special form.
490 * Summing up zap-to-char:: Using @code{point} and @code{search-forward}.
494 * Complete kill-region:: The function definition.
495 * condition-case:: Dealing with a problem.
498 @code{copy-region-as-kill}
500 * Complete copy-region-as-kill:: The complete function definition.
501 * copy-region-as-kill body:: The body of @code{copy-region-as-kill}.
503 The Body of @code{copy-region-as-kill}
505 * last-command & this-command::
506 * kill-append function::
507 * kill-new function::
509 Initializing a Variable with @code{defvar}
511 * See variable current value::
512 * defvar and asterisk::
514 How Lists are Implemented
517 * Symbols as Chest:: Exploring a powerful metaphor.
522 * Kill Ring Overview::
523 * kill-ring-yank-pointer:: The kill ring is a list.
524 * yank nthcdr Exercises:: The @code{kill-ring-yank-pointer} variable.
528 * while:: Causing a stretch of code to repeat.
530 * Recursion:: Causing a function to call itself.
535 * Looping with while:: Repeat so long as test returns true.
536 * Loop Example:: A @code{while} loop that uses a list.
537 * print-elements-of-list:: Uses @code{while}, @code{car}, @code{cdr}.
538 * Incrementing Loop:: A loop with an incrementing counter.
539 * Incrementing Loop Details::
540 * Decrementing Loop:: A loop with a decrementing counter.
542 Details of an Incrementing Loop
544 * Incrementing Example:: Counting pebbles in a triangle.
545 * Inc Example parts:: The parts of the function definition.
546 * Inc Example altogether:: Putting the function definition together.
548 Loop with a Decrementing Counter
550 * Decrementing Example:: More pebbles on the beach.
551 * Dec Example parts:: The parts of the function definition.
552 * Dec Example altogether:: Putting the function definition together.
554 Save your time: @code{dolist} and @code{dotimes}
561 * Building Robots:: Same model, different serial number ...
562 * Recursive Definition Parts:: Walk until you stop ...
563 * Recursion with list:: Using a list as the test whether to recurse.
564 * Recursive triangle function::
565 * Recursion with cond::
566 * Recursive Patterns:: Often used templates.
567 * No Deferment:: Don't store up work ...
568 * No deferment solution::
570 Recursion in Place of a Counter
572 * Recursive Example arg of 1 or 2::
573 * Recursive Example arg of 3 or 4::
581 Regular Expression Searches
583 * sentence-end:: The regular expression for @code{sentence-end}.
584 * re-search-forward:: Very similar to @code{search-forward}.
585 * forward-sentence:: A straightforward example of regexp search.
586 * forward-paragraph:: A somewhat complex example.
587 * etags:: How to create your own @file{TAGS} table.
589 * re-search Exercises::
591 @code{forward-sentence}
593 * Complete forward-sentence::
594 * fwd-sentence while loops:: Two @code{while} loops.
595 * fwd-sentence re-search:: A regular expression search.
597 @code{forward-paragraph}: a Goldmine of Functions
599 * forward-paragraph in brief:: Key parts of the function definition.
600 * fwd-para let:: The @code{let*} expression.
601 * fwd-para while:: The forward motion @code{while} loop.
603 Counting: Repetition and Regexps
606 * @value{COUNT-WORDS}:: Use a regexp, but find a problem.
607 * recursive-count-words:: Start with case of no words in region.
608 * Counting Exercise::
610 The @code{@value{COUNT-WORDS}} Function
612 * Design @value{COUNT-WORDS}:: The definition using a @code{while} loop.
613 * Whitespace Bug:: The Whitespace Bug in @code{@value{COUNT-WORDS}}.
615 Counting Words in a @code{defun}
617 * Divide and Conquer::
618 * Words and Symbols:: What to count?
619 * Syntax:: What constitutes a word or symbol?
620 * count-words-in-defun:: Very like @code{@value{COUNT-WORDS}}.
621 * Several defuns:: Counting several defuns in a file.
622 * Find a File:: Do you want to look at a file?
623 * lengths-list-file:: A list of the lengths of many definitions.
624 * Several files:: Counting in definitions in different files.
625 * Several files recursively:: Recursively counting in different files.
626 * Prepare the data:: Prepare the data for display in a graph.
628 Count Words in @code{defuns} in Different Files
630 * lengths-list-many-files:: Return a list of the lengths of defuns.
631 * append:: Attach one list to another.
633 Prepare the Data for Display in a Graph
635 * Data for Display in Detail::
636 * Sorting:: Sorting lists.
637 * Files List:: Making a list of files.
638 * Counting function definitions::
642 * Columns of a graph::
643 * graph-body-print:: How to print the body of a graph.
644 * recursive-graph-body-print::
646 * Line Graph Exercise::
648 Your @file{.emacs} File
650 * Default Configuration::
651 * Site-wide Init:: You can write site-wide init files.
652 * defcustom:: Emacs will write code for you.
653 * Beginning init File:: How to write a @file{.emacs} init file.
654 * Text and Auto-fill:: Automatically wrap lines.
655 * Mail Aliases:: Use abbreviations for email addresses.
656 * Indent Tabs Mode:: Don't use tabs with @TeX{}
657 * Keybindings:: Create some personal keybindings.
658 * Keymaps:: More about key binding.
659 * Loading Files:: Load (i.e., evaluate) files automatically.
660 * Autoload:: Make functions available.
661 * Simple Extension:: Define a function; bind it to a key.
662 * X11 Colors:: Colors in X.
664 * Mode Line:: How to customize your mode line.
668 * debug:: How to use the built-in debugger.
669 * debug-on-entry:: Start debugging when you call a function.
670 * debug-on-quit:: Start debugging when you quit with @kbd{C-g}.
671 * edebug:: How to use Edebug, a source level debugger.
672 * Debugging Exercises::
674 Handling the Kill Ring
676 * What the Kill Ring Does::
678 * yank:: Paste a copy of a clipped element.
679 * yank-pop:: Insert element pointed to.
682 The @code{current-kill} Function
684 * Code for current-kill::
685 * Understanding current-kill::
687 @code{current-kill} in Outline
689 * Body of current-kill::
690 * Digression concerning error:: How to mislead humans, but not computers.
691 * Determining the Element::
693 A Graph with Labeled Axes
696 * print-graph Varlist:: @code{let} expression in @code{print-graph}.
697 * print-Y-axis:: Print a label for the vertical axis.
698 * print-X-axis:: Print a horizontal label.
699 * Print Whole Graph:: The function to print a complete graph.
701 The @code{print-Y-axis} Function
703 * print-Y-axis in Detail::
704 * Height of label:: What height for the Y axis?
705 * Compute a Remainder:: How to compute the remainder of a division.
706 * Y Axis Element:: Construct a line for the Y axis.
707 * Y-axis-column:: Generate a list of Y axis labels.
708 * print-Y-axis Penultimate:: A not quite final version.
710 The @code{print-X-axis} Function
712 * Similarities differences:: Much like @code{print-Y-axis}, but not exactly.
713 * X Axis Tic Marks:: Create tic marks for the horizontal axis.
715 Printing the Whole Graph
717 * The final version:: A few changes.
718 * Test print-graph:: Run a short test.
719 * Graphing words in defuns:: Executing the final code.
720 * lambda:: How to write an anonymous function.
721 * mapcar:: Apply a function to elements of a list.
722 * Another Bug:: Yet another bug @dots{} most insidious.
723 * Final printed graph:: The graph itself!
731 Most of the GNU Emacs integrated environment is written in the programming
732 language called Emacs Lisp. The code written in this programming
733 language is the software---the sets of instructions---that tell the
734 computer what to do when you give it commands. Emacs is designed so
735 that you can write new code in Emacs Lisp and easily install it as an
736 extension to the editor.
738 (GNU Emacs is sometimes called an ``extensible editor'', but it does
739 much more than provide editing capabilities. It is better to refer to
740 Emacs as an ``extensible computing environment''. However, that
741 phrase is quite a mouthful. It is easier to refer to Emacs simply as
742 an editor. Moreover, everything you do in Emacs---find the Mayan date
743 and phases of the moon, simplify polynomials, debug code, manage
744 files, read letters, write books---all these activities are kinds of
745 editing in the most general sense of the word.)
748 * Why:: Why learn Emacs Lisp?
749 * On Reading this Text:: Read, gain familiarity, pick up habits....
750 * Who You Are:: For whom this is written.
752 * Note for Novices:: You can read this as a novice.
758 @unnumberedsec Why Study Emacs Lisp?
761 Although Emacs Lisp is usually thought of in association only with Emacs,
762 it is a full computer programming language. You can use Emacs Lisp as
763 you would any other programming language.
765 Perhaps you want to understand programming; perhaps you want to extend
766 Emacs; or perhaps you want to become a programmer. This introduction to
767 Emacs Lisp is designed to get you started: to guide you in learning the
768 fundamentals of programming, and more importantly, to show you how you
769 can teach yourself to go further.
771 @node On Reading this Text
772 @unnumberedsec On Reading this Text
774 All through this document, you will see little sample programs you can
775 run inside of Emacs. If you read this document in Info inside of GNU
776 Emacs, you can run the programs as they appear. (This is easy to do and
777 is explained when the examples are presented.) Alternatively, you can
778 read this introduction as a printed book while sitting beside a computer
779 running Emacs. (This is what I like to do; I like printed books.) If
780 you don't have a running Emacs beside you, you can still read this book,
781 but in this case, it is best to treat it as a novel or as a travel guide
782 to a country not yet visited: interesting, but not the same as being
785 Much of this introduction is dedicated to walkthroughs or guided tours
786 of code used in GNU Emacs. These tours are designed for two purposes:
787 first, to give you familiarity with real, working code (code you use
788 every day); and, second, to give you familiarity with the way Emacs
789 works. It is interesting to see how a working environment is
792 hope that you will pick up the habit of browsing through source code.
793 You can learn from it and mine it for ideas. Having GNU Emacs is like
794 having a dragon's cave of treasures.
796 In addition to learning about Emacs as an editor and Emacs Lisp as a
797 programming language, the examples and guided tours will give you an
798 opportunity to get acquainted with Emacs as a Lisp programming
799 environment. GNU Emacs supports programming and provides tools that
800 you will want to become comfortable using, such as @kbd{M-.} (the key
801 which invokes the @code{find-tag} command). You will also learn about
802 buffers and other objects that are part of the environment.
803 Learning about these features of Emacs is like learning new routes
804 around your home town.
807 In addition, I have written several programs as extended examples.
808 Although these are examples, the programs are real. I use them.
809 Other people use them. You may use them. Beyond the fragments of
810 programs used for illustrations, there is very little in here that is
811 just for teaching purposes; what you see is used. This is a great
812 advantage of Emacs Lisp: it is easy to learn to use it for work.
815 Finally, I hope to convey some of the skills for using Emacs to
816 learn aspects of programming that you don't know. You can often use
817 Emacs to help you understand what puzzles you or to find out how to do
818 something new. This self-reliance is not only a pleasure, but an
822 @unnumberedsec For Whom This is Written
824 This text is written as an elementary introduction for people who are
825 not programmers. If you are a programmer, you may not be satisfied with
826 this primer. The reason is that you may have become expert at reading
827 reference manuals and be put off by the way this text is organized.
829 An expert programmer who reviewed this text said to me:
832 @i{I prefer to learn from reference manuals. I ``dive into'' each
833 paragraph, and ``come up for air'' between paragraphs.}
835 @i{When I get to the end of a paragraph, I assume that that subject is
836 done, finished, that I know everything I need (with the
837 possible exception of the case when the next paragraph starts talking
838 about it in more detail). I expect that a well written reference manual
839 will not have a lot of redundancy, and that it will have excellent
840 pointers to the (one) place where the information I want is.}
843 This introduction is not written for this person!
845 Firstly, I try to say everything at least three times: first, to
846 introduce it; second, to show it in context; and third, to show it in a
847 different context, or to review it.
849 Secondly, I hardly ever put all the information about a subject in one
850 place, much less in one paragraph. To my way of thinking, that imposes
851 too heavy a burden on the reader. Instead I try to explain only what
852 you need to know at the time. (Sometimes I include a little extra
853 information so you won't be surprised later when the additional
854 information is formally introduced.)
856 When you read this text, you are not expected to learn everything the
857 first time. Frequently, you need make only a nodding
858 acquaintance with some of the items mentioned. My hope is that I have
859 structured the text and given you enough hints that you will be alert to
860 what is important, and concentrate on it.
862 You will need to dive into some paragraphs; there is no other way
863 to read them. But I have tried to keep down the number of such
864 paragraphs. This book is intended as an approachable hill, rather than
865 as a daunting mountain.
867 This introduction to @cite{Programming in Emacs Lisp} has a companion
870 @cite{The GNU Emacs Lisp Reference Manual}.
873 @ref{Top, , The GNU Emacs Lisp Reference Manual, elisp, The GNU
874 Emacs Lisp Reference Manual}.
876 The reference manual has more detail than this introduction. In the
877 reference manual, all the information about one topic is concentrated
878 in one place. You should turn to it if you are like the programmer
879 quoted above. And, of course, after you have read this
880 @cite{Introduction}, you will find the @cite{Reference Manual} useful
881 when you are writing your own programs.
884 @unnumberedsec Lisp History
887 Lisp was first developed in the late 1950s at the Massachusetts
888 Institute of Technology for research in artificial intelligence. The
889 great power of the Lisp language makes it superior for other purposes as
890 well, such as writing editor commands and integrated environments.
894 GNU Emacs Lisp is largely inspired by Maclisp, which was written at MIT
895 in the 1960s. It is somewhat inspired by Common Lisp, which became a
896 standard in the 1980s. However, Emacs Lisp is much simpler than Common
897 Lisp. (The standard Emacs distribution contains an optional extensions
898 file, @file{cl.el}, that adds many Common Lisp features to Emacs Lisp.)
900 @node Note for Novices
901 @unnumberedsec A Note for Novices
903 If you don't know GNU Emacs, you can still read this document
904 profitably. However, I recommend you learn Emacs, if only to learn to
905 move around your computer screen. You can teach yourself how to use
906 Emacs with the built-in tutorial. To use it, type @kbd{C-h t}. (This
907 means you press and release the @key{CTRL} key and the @kbd{h} at the
908 same time, and then press and release @kbd{t}.)
910 Also, I often refer to one of Emacs's standard commands by listing the
911 keys which you press to invoke the command and then giving the name of
912 the command in parentheses, like this: @kbd{M-C-\}
913 (@code{indent-region}). What this means is that the
914 @code{indent-region} command is customarily invoked by typing
915 @kbd{M-C-\}. (You can, if you wish, change the keys that are typed to
916 invoke the command; this is called @dfn{rebinding}. @xref{Keymaps, ,
917 Keymaps}.) The abbreviation @kbd{M-C-\} means that you type your
918 @key{META} key, @key{CTRL} key and @key{\} key all at the same time.
919 (On many modern keyboards the @key{META} key is labeled
921 Sometimes a combination like this is called a keychord, since it is
922 similar to the way you play a chord on a piano. If your keyboard does
923 not have a @key{META} key, the @key{ESC} key prefix is used in place
924 of it. In this case, @kbd{M-C-\} means that you press and release your
925 @key{ESC} key and then type the @key{CTRL} key and the @key{\} key at
926 the same time. But usually @kbd{M-C-\} means press the @key{CTRL} key
927 along with the key that is labeled @key{ALT} and, at the same time,
928 press the @key{\} key.
930 In addition to typing a lone keychord, you can prefix what you type
931 with @kbd{C-u}, which is called the @dfn{universal argument}. The
932 @kbd{C-u} keychord passes an argument to the subsequent command.
933 Thus, to indent a region of plain text by 6 spaces, mark the region,
934 and then type @w{@kbd{C-u 6 M-C-\}}. (If you do not specify a number,
935 Emacs either passes the number 4 to the command or otherwise runs the
936 command differently than it would otherwise.) @xref{Arguments, ,
937 Numeric Arguments, emacs, The GNU Emacs Manual}.
939 If you are reading this in Info using GNU Emacs, you can read through
940 this whole document just by pressing the space bar, @key{SPC}.
941 (To learn about Info, type @kbd{C-h i} and then select Info.)
943 A note on terminology: when I use the word Lisp alone, I often am
944 referring to the various dialects of Lisp in general, but when I speak
945 of Emacs Lisp, I am referring to GNU Emacs Lisp in particular.
948 @unnumberedsec Thank You
950 My thanks to all who helped me with this book. My especial thanks to
951 @r{Jim Blandy}, @r{Noah Friedman}, @w{Jim Kingdon}, @r{Roland
952 McGrath}, @w{Frank Ritter}, @w{Randy Smith}, @w{Richard M.
953 Stallman}, and @w{Melissa Weisshaus}. My thanks also go to both
954 @w{Philip Johnson} and @w{David Stampe} for their patient
955 encouragement. My mistakes are my own.
967 @c ================ Beginning of main text ================
969 @c Start main text on right-hand (verso) page
972 \par\vfill\supereject
975 \par\vfill\supereject
977 \par\vfill\supereject
979 \par\vfill\supereject
983 @c Note: this resetting of the page number back to 1 causes TeX to gripe
984 @c about already having seen page numbers 1-4 before (in the preface):
985 @c pdfTeX warning (ext4): destination with the same identifier (name{1})
986 @c has been already used, duplicate ignored
987 @c I guess that is harmless (what happens if a later part of the text
988 @c makes a link to something in the first 4 pages though?).
989 @c E.g., note that the Emacs manual has a preface, but does not bother
990 @c resetting the page numbers back to 1 after that.
993 @evenheading @thispage @| @| @thischapter
994 @oddheading @thissection @| @| @thispage
998 @node List Processing
999 @chapter List Processing
1001 To the untutored eye, Lisp is a strange programming language. In Lisp
1002 code there are parentheses everywhere. Some people even claim that
1003 the name stands for ``Lots of Isolated Silly Parentheses''. But the
1004 claim is unwarranted. Lisp stands for LISt Processing, and the
1005 programming language handles @emph{lists} (and lists of lists) by
1006 putting them between parentheses. The parentheses mark the boundaries
1007 of the list. Sometimes a list is preceded by a single apostrophe or
1008 quotation mark, @samp{'}@footnote{The single apostrophe or quotation
1009 mark is an abbreviation for the function @code{quote}; you need not
1010 think about functions now; functions are defined in @ref{Making
1011 Errors, , Generate an Error Message}.} Lists are the basis of Lisp.
1014 * Lisp Lists:: What are lists?
1015 * Run a Program:: Any list in Lisp is a program ready to run.
1016 * Making Errors:: Generating an error message.
1017 * Names & Definitions:: Names of symbols and function definitions.
1018 * Lisp Interpreter:: What the Lisp interpreter does.
1019 * Evaluation:: Running a program.
1020 * Variables:: Returning a value from a variable.
1021 * Arguments:: Passing information to a function.
1022 * set & setq:: Setting the value of a variable.
1023 * Summary:: The major points.
1024 * Error Message Exercises::
1031 In Lisp, a list looks like this: @code{'(rose violet daisy buttercup)}.
1032 This list is preceded by a single apostrophe. It could just as well be
1033 written as follows, which looks more like the kind of list you are likely
1034 to be familiar with:
1046 The elements of this list are the names of the four different flowers,
1047 separated from each other by whitespace and surrounded by parentheses,
1048 like flowers in a field with a stone wall around them.
1049 @cindex Flowers in a field
1052 * Numbers Lists:: List have numbers, other lists, in them.
1053 * Lisp Atoms:: Elemental entities.
1054 * Whitespace in Lists:: Formatting lists to be readable.
1055 * Typing Lists:: How GNU Emacs helps you type lists.
1060 @unnumberedsubsec Numbers, Lists inside of Lists
1063 Lists can also have numbers in them, as in this list: @code{(+ 2 2)}.
1064 This list has a plus-sign, @samp{+}, followed by two @samp{2}s, each
1065 separated by whitespace.
1067 In Lisp, both data and programs are represented the same way; that is,
1068 they are both lists of words, numbers, or other lists, separated by
1069 whitespace and surrounded by parentheses. (Since a program looks like
1070 data, one program may easily serve as data for another; this is a very
1071 powerful feature of Lisp.) (Incidentally, these two parenthetical
1072 remarks are @emph{not} Lisp lists, because they contain @samp{;} and
1073 @samp{.} as punctuation marks.)
1076 Here is another list, this time with a list inside of it:
1079 '(this list has (a list inside of it))
1082 The components of this list are the words @samp{this}, @samp{list},
1083 @samp{has}, and the list @samp{(a list inside of it)}. The interior
1084 list is made up of the words @samp{a}, @samp{list}, @samp{inside},
1085 @samp{of}, @samp{it}.
1088 @subsection Lisp Atoms
1091 In Lisp, what we have been calling words are called @dfn{atoms}. This
1092 term comes from the historical meaning of the word atom, which means
1093 ``indivisible''. As far as Lisp is concerned, the words we have been
1094 using in the lists cannot be divided into any smaller parts and still
1095 mean the same thing as part of a program; likewise with numbers and
1096 single character symbols like @samp{+}. On the other hand, unlike an
1097 ancient atom, a list can be split into parts. (@xref{car cdr & cons,
1098 , @code{car} @code{cdr} & @code{cons} Fundamental Functions}.)
1100 In a list, atoms are separated from each other by whitespace. They can be
1101 right next to a parenthesis.
1103 @cindex @samp{empty list} defined
1104 Technically speaking, a list in Lisp consists of parentheses surrounding
1105 atoms separated by whitespace or surrounding other lists or surrounding
1106 both atoms and other lists. A list can have just one atom in it or
1107 have nothing in it at all. A list with nothing in it looks like this:
1108 @code{()}, and is called the @dfn{empty list}. Unlike anything else, an
1109 empty list is considered both an atom and a list at the same time.
1111 @cindex Symbolic expressions, introduced
1112 @cindex @samp{expression} defined
1113 @cindex @samp{form} defined
1114 The printed representation of both atoms and lists are called
1115 @dfn{symbolic expressions} or, more concisely, @dfn{s-expressions}.
1116 The word @dfn{expression} by itself can refer to either the printed
1117 representation, or to the atom or list as it is held internally in the
1118 computer. Often, people use the term @dfn{expression}
1119 indiscriminately. (Also, in many texts, the word @dfn{form} is used
1120 as a synonym for expression.)
1122 Incidentally, the atoms that make up our universe were named such when
1123 they were thought to be indivisible; but it has been found that physical
1124 atoms are not indivisible. Parts can split off an atom or it can
1125 fission into two parts of roughly equal size. Physical atoms were named
1126 prematurely, before their truer nature was found. In Lisp, certain
1127 kinds of atom, such as an array, can be separated into parts; but the
1128 mechanism for doing this is different from the mechanism for splitting a
1129 list. As far as list operations are concerned, the atoms of a list are
1132 As in English, the meanings of the component letters of a Lisp atom
1133 are different from the meaning the letters make as a word. For
1134 example, the word for the South American sloth, the @samp{ai}, is
1135 completely different from the two words, @samp{a}, and @samp{i}.
1137 There are many kinds of atom in nature but only a few in Lisp: for
1138 example, @dfn{numbers}, such as 37, 511, or 1729, and @dfn{symbols}, such
1139 as @samp{+}, @samp{foo}, or @samp{forward-line}. The words we have
1140 listed in the examples above are all symbols. In everyday Lisp
1141 conversation, the word ``atom'' is not often used, because programmers
1142 usually try to be more specific about what kind of atom they are dealing
1143 with. Lisp programming is mostly about symbols (and sometimes numbers)
1144 within lists. (Incidentally, the preceding three word parenthetical
1145 remark is a proper list in Lisp, since it consists of atoms, which in
1146 this case are symbols, separated by whitespace and enclosed by
1147 parentheses, without any non-Lisp punctuation.)
1150 Text between double quotation marks---even sentences or
1151 paragraphs---is also an atom. Here is an example:
1152 @cindex Text between double quotation marks
1155 '(this list includes "text between quotation marks.")
1158 @cindex @samp{string} defined
1160 In Lisp, all of the quoted text including the punctuation mark and the
1161 blank spaces is a single atom. This kind of atom is called a
1162 @dfn{string} (for ``string of characters'') and is the sort of thing that
1163 is used for messages that a computer can print for a human to read.
1164 Strings are a different kind of atom than numbers or symbols and are
1167 @node Whitespace in Lists
1168 @subsection Whitespace in Lists
1169 @cindex Whitespace in lists
1172 The amount of whitespace in a list does not matter. From the point of view
1173 of the Lisp language,
1184 is exactly the same as this:
1187 '(this list looks like this)
1190 Both examples show what to Lisp is the same list, the list made up of
1191 the symbols @samp{this}, @samp{list}, @samp{looks}, @samp{like}, and
1192 @samp{this} in that order.
1194 Extra whitespace and newlines are designed to make a list more readable
1195 by humans. When Lisp reads the expression, it gets rid of all the extra
1196 whitespace (but it needs to have at least one space between atoms in
1197 order to tell them apart.)
1199 Odd as it seems, the examples we have seen cover almost all of what Lisp
1200 lists look like! Every other list in Lisp looks more or less like one
1201 of these examples, except that the list may be longer and more complex.
1202 In brief, a list is between parentheses, a string is between quotation
1203 marks, a symbol looks like a word, and a number looks like a number.
1204 (For certain situations, square brackets, dots and a few other special
1205 characters may be used; however, we will go quite far without them.)
1208 @subsection GNU Emacs Helps You Type Lists
1209 @cindex Help typing lists
1210 @cindex Formatting help
1212 When you type a Lisp expression in GNU Emacs using either Lisp
1213 Interaction mode or Emacs Lisp mode, you have available to you several
1214 commands to format the Lisp expression so it is easy to read. For
1215 example, pressing the @key{TAB} key automatically indents the line the
1216 cursor is on by the right amount. A command to properly indent the
1217 code in a region is customarily bound to @kbd{M-C-\}. Indentation is
1218 designed so that you can see which elements of a list belong to which
1219 list---elements of a sub-list are indented more than the elements of
1222 In addition, when you type a closing parenthesis, Emacs momentarily
1223 jumps the cursor back to the matching opening parenthesis, so you can
1224 see which one it is. This is very useful, since every list you type
1225 in Lisp must have its closing parenthesis match its opening
1226 parenthesis. (@xref{Major Modes, , Major Modes, emacs, The GNU Emacs
1227 Manual}, for more information about Emacs's modes.)
1230 @section Run a Program
1231 @cindex Run a program
1232 @cindex Program, running one
1234 @cindex @samp{evaluate} defined
1235 A list in Lisp---any list---is a program ready to run. If you run it
1236 (for which the Lisp jargon is @dfn{evaluate}), the computer will do one
1237 of three things: do nothing except return to you the list itself; send
1238 you an error message; or, treat the first symbol in the list as a
1239 command to do something. (Usually, of course, it is the last of these
1240 three things that you really want!)
1242 @c use code for the single apostrophe, not samp.
1244 @cindex @code{'} for quoting
1245 @cindex quoting using apostrophe
1246 @cindex apostrophe for quoting
1247 The single apostrophe, @code{'}, that I put in front of some of the
1248 example lists in preceding sections is called a @dfn{quote}; when it
1249 precedes a list, it tells Lisp to do nothing with the list, other than
1250 take it as it is written. But if there is no quote preceding a list,
1251 the first item of the list is special: it is a command for the computer
1252 to obey. (In Lisp, these commands are called @emph{functions}.) The list
1253 @code{(+ 2 2)} shown above did not have a quote in front of it, so Lisp
1254 understands that the @code{+} is an instruction to do something with the
1255 rest of the list: add the numbers that follow.
1258 If you are reading this inside of GNU Emacs in Info, here is how you can
1259 evaluate such a list: place your cursor immediately after the right
1260 hand parenthesis of the following list and then type @kbd{C-x C-e}:
1266 @c use code for the number four, not samp.
1268 You will see the number @code{4} appear in the echo area. (What
1269 you have just done is evaluate the list. The echo area
1270 is the line at the bottom of the screen that displays or echoes
1271 text.) Now try the same thing with a quoted list: place the cursor
1272 right after the following list and type @kbd{C-x C-e}:
1275 '(this is a quoted list)
1279 You will see @code{(this is a quoted list)} appear in the echo area.
1281 @cindex Lisp interpreter, explained
1282 @cindex Interpreter, Lisp, explained
1283 In both cases, what you are doing is giving a command to the program
1284 inside of GNU Emacs called the @dfn{Lisp interpreter}---giving the
1285 interpreter a command to evaluate the expression. The name of the Lisp
1286 interpreter comes from the word for the task done by a human who comes
1287 up with the meaning of an expression---who interprets it.
1289 You can also evaluate an atom that is not part of a list---one that is
1290 not surrounded by parentheses; again, the Lisp interpreter translates
1291 from the humanly readable expression to the language of the computer.
1292 But before discussing this (@pxref{Variables}), we will discuss what the
1293 Lisp interpreter does when you make an error.
1296 @section Generate an Error Message
1297 @cindex Generate an error message
1298 @cindex Error message generation
1300 Partly so you won't worry if you do it accidentally, we will now give
1301 a command to the Lisp interpreter that generates an error message.
1302 This is a harmless activity; and indeed, we will often try to generate
1303 error messages intentionally. Once you understand the jargon, error
1304 messages can be informative. Instead of being called ``error''
1305 messages, they should be called ``help'' messages. They are like
1306 signposts to a traveler in a strange country; deciphering them can be
1307 hard, but once understood, they can point the way.
1309 The error message is generated by a built-in GNU Emacs debugger. We
1310 will enter the debugger. You get out of the debugger by typing @code{q}.
1312 What we will do is evaluate a list that is not quoted and does not
1313 have a meaningful command as its first element. Here is a list almost
1314 exactly the same as the one we just used, but without the single-quote
1315 in front of it. Position the cursor right after it and type @kbd{C-x
1319 (this is an unquoted list)
1324 What you see depends on which version of Emacs you are running. GNU
1325 Emacs version 22 provides more information than version 20 and before.
1326 First, the more recent result of generating an error; then the
1327 earlier, version 20 result.
1331 In GNU Emacs version 22, a @file{*Backtrace*} window will open up and
1332 you will see the following in it:
1335 A @file{*Backtrace*} window will open up and you should see the
1340 ---------- Buffer: *Backtrace* ----------
1341 Debugger entered--Lisp error: (void-function this)
1342 (this is an unquoted list)
1343 eval((this is an unquoted list))
1344 eval-last-sexp-1(nil)
1346 call-interactively(eval-last-sexp)
1347 ---------- Buffer: *Backtrace* ----------
1353 Your cursor will be in this window (you may have to wait a few seconds
1354 before it becomes visible). To quit the debugger and make the
1355 debugger window go away, type:
1362 Please type @kbd{q} right now, so you become confident that you can
1363 get out of the debugger. Then, type @kbd{C-x C-e} again to re-enter
1366 @cindex @samp{function} defined
1367 Based on what we already know, we can almost read this error message.
1369 You read the @file{*Backtrace*} buffer from the bottom up; it tells
1370 you what Emacs did. When you typed @kbd{C-x C-e}, you made an
1371 interactive call to the command @code{eval-last-sexp}. @code{eval} is
1372 an abbreviation for ``evaluate'' and @code{sexp} is an abbreviation for
1373 ``symbolic expression''. The command means ``evaluate last symbolic
1374 expression'', which is the expression just before your cursor.
1376 Each line above tells you what the Lisp interpreter evaluated next.
1377 The most recent action is at the top. The buffer is called the
1378 @file{*Backtrace*} buffer because it enables you to track Emacs
1382 At the top of the @file{*Backtrace*} buffer, you see the line:
1385 Debugger entered--Lisp error: (void-function this)
1389 The Lisp interpreter tried to evaluate the first atom of the list, the
1390 word @samp{this}. It is this action that generated the error message
1391 @samp{void-function this}.
1393 The message contains the words @samp{void-function} and @samp{this}.
1395 @cindex @samp{function} defined
1396 The word @samp{function} was mentioned once before. It is a very
1397 important word. For our purposes, we can define it by saying that a
1398 @dfn{function} is a set of instructions to the computer that tell the
1399 computer to do something.
1401 Now we can begin to understand the error message: @samp{void-function
1402 this}. The function (that is, the word @samp{this}) does not have a
1403 definition of any set of instructions for the computer to carry out.
1405 The slightly odd word, @samp{void-function}, is designed to cover the
1406 way Emacs Lisp is implemented, which is that when a symbol does not
1407 have a function definition attached to it, the place that should
1408 contain the instructions is void.
1410 On the other hand, since we were able to add 2 plus 2 successfully, by
1411 evaluating @code{(+ 2 2)}, we can infer that the symbol @code{+} must
1412 have a set of instructions for the computer to obey and those
1413 instructions must be to add the numbers that follow the @code{+}.
1415 It is possible to prevent Emacs entering the debugger in cases like
1416 this. We do not explain how to do that here, but we will mention what
1417 the result looks like, because you may encounter a similar situation
1418 if there is a bug in some Emacs code that you are using. In such
1419 cases, you will see only one line of error message; it will appear in
1420 the echo area and look like this:
1423 Symbol's function definition is void:@: this
1428 (Also, your terminal may beep at you---some do, some don't; and others
1429 blink. This is just a device to get your attention.)
1431 The message goes away as soon as you type a key, even just to
1434 We know the meaning of the word @samp{Symbol}. It refers to the first
1435 atom of the list, the word @samp{this}. The word @samp{function}
1436 refers to the instructions that tell the computer what to do.
1437 (Technically, the symbol tells the computer where to find the
1438 instructions, but this is a complication we can ignore for the
1441 The error message can be understood: @samp{Symbol's function
1442 definition is void:@: this}. The symbol (that is, the word
1443 @samp{this}) lacks instructions for the computer to carry out.
1445 @node Names & Definitions
1446 @section Symbol Names and Function Definitions
1447 @cindex Symbol names
1449 We can articulate another characteristic of Lisp based on what we have
1450 discussed so far---an important characteristic: a symbol, like
1451 @code{+}, is not itself the set of instructions for the computer to
1452 carry out. Instead, the symbol is used, perhaps temporarily, as a way
1453 of locating the definition or set of instructions. What we see is the
1454 name through which the instructions can be found. Names of people
1455 work the same way. I can be referred to as @samp{Bob}; however, I am
1456 not the letters @samp{B}, @samp{o}, @samp{b} but am, or was, the
1457 consciousness consistently associated with a particular life-form.
1458 The name is not me, but it can be used to refer to me.
1460 In Lisp, one set of instructions can be attached to several names.
1461 For example, the computer instructions for adding numbers can be
1462 linked to the symbol @code{plus} as well as to the symbol @code{+}
1463 (and are in some dialects of Lisp). Among humans, I can be referred
1464 to as @samp{Robert} as well as @samp{Bob} and by other words as well.
1466 On the other hand, a symbol can have only one function definition
1467 attached to it at a time. Otherwise, the computer would be confused as
1468 to which definition to use. If this were the case among people, only
1469 one person in the world could be named @samp{Bob}. However, the function
1470 definition to which the name refers can be changed readily.
1471 (@xref{Install, , Install a Function Definition}.)
1473 Since Emacs Lisp is large, it is customary to name symbols in a way
1474 that identifies the part of Emacs to which the function belongs.
1475 Thus, all the names for functions that deal with Texinfo start with
1476 @samp{texinfo-} and those for functions that deal with reading mail
1477 start with @samp{rmail-}.
1479 @node Lisp Interpreter
1480 @section The Lisp Interpreter
1481 @cindex Lisp interpreter, what it does
1482 @cindex Interpreter, what it does
1484 Based on what we have seen, we can now start to figure out what the
1485 Lisp interpreter does when we command it to evaluate a list.
1486 First, it looks to see whether there is a quote before the list; if
1487 there is, the interpreter just gives us the list. On the other
1488 hand, if there is no quote, the interpreter looks at the first element
1489 in the list and sees whether it has a function definition. If it does,
1490 the interpreter carries out the instructions in the function definition.
1491 Otherwise, the interpreter prints an error message.
1493 This is how Lisp works. Simple. There are added complications which we
1494 will get to in a minute, but these are the fundamentals. Of course, to
1495 write Lisp programs, you need to know how to write function definitions
1496 and attach them to names, and how to do this without confusing either
1497 yourself or the computer.
1500 * Complications:: Variables, Special forms, Lists within.
1501 * Byte Compiling:: Specially processing code for speed.
1506 @unnumberedsubsec Complications
1509 Now, for the first complication. In addition to lists, the Lisp
1510 interpreter can evaluate a symbol that is not quoted and does not have
1511 parentheses around it. The Lisp interpreter will attempt to determine
1512 the symbol's value as a @dfn{variable}. This situation is described
1513 in the section on variables. (@xref{Variables}.)
1515 @cindex Special form
1516 The second complication occurs because some functions are unusual and
1517 do not work in the usual manner. Those that don't are called
1518 @dfn{special forms}. They are used for special jobs, like defining a
1519 function, and there are not many of them. In the next few chapters,
1520 you will be introduced to several of the more important special forms.
1522 As well as special forms, there are also @dfn{macros}. A macro
1523 is a construct defined in Lisp, which differs from a function in that it
1524 translates a Lisp expression into another expression that is to be
1525 evaluated in place of the original expression. (@xref{Lisp macro}.)
1527 For the purposes of this introduction, you do not need to worry too much
1528 about whether something is a special form, macro, or ordinary function.
1529 For example, @code{if} is a special form (@pxref{if}), but @code{when}
1530 is a macro (@pxref{Lisp macro}). In earlier versions of Emacs,
1531 @code{defun} was a special form, but now it is a macro (@pxref{defun}).
1532 It still behaves in the same way.
1534 The final complication is this: if the function that the
1535 Lisp interpreter is looking at is not a special form, and if it is part
1536 of a list, the Lisp interpreter looks to see whether the list has a list
1537 inside of it. If there is an inner list, the Lisp interpreter first
1538 figures out what it should do with the inside list, and then it works on
1539 the outside list. If there is yet another list embedded inside the
1540 inner list, it works on that one first, and so on. It always works on
1541 the innermost list first. The interpreter works on the innermost list
1542 first, to evaluate the result of that list. The result may be
1543 used by the enclosing expression.
1545 Otherwise, the interpreter works left to right, from one expression to
1548 @node Byte Compiling
1549 @subsection Byte Compiling
1550 @cindex Byte compiling
1552 One other aspect of interpreting: the Lisp interpreter is able to
1553 interpret two kinds of entity: humanly readable code, on which we will
1554 focus exclusively, and specially processed code, called @dfn{byte
1555 compiled} code, which is not humanly readable. Byte compiled code
1556 runs faster than humanly readable code.
1558 You can transform humanly readable code into byte compiled code by
1559 running one of the compile commands such as @code{byte-compile-file}.
1560 Byte compiled code is usually stored in a file that ends with a
1561 @file{.elc} extension rather than a @file{.el} extension. You will
1562 see both kinds of file in the @file{emacs/lisp} directory; the files
1563 to read are those with @file{.el} extensions.
1565 As a practical matter, for most things you might do to customize or
1566 extend Emacs, you do not need to byte compile; and I will not discuss
1567 the topic here. @xref{Byte Compilation, , Byte Compilation, elisp,
1568 The GNU Emacs Lisp Reference Manual}, for a full description of byte
1575 When the Lisp interpreter works on an expression, the term for the
1576 activity is called @dfn{evaluation}. We say that the interpreter
1577 ``evaluates the expression''. I've used this term several times before.
1578 The word comes from its use in everyday language, ``to ascertain the
1579 value or amount of; to appraise'', according to @cite{Webster's New
1580 Collegiate Dictionary}.
1583 * How the Interpreter Acts:: Returns and Side Effects...
1584 * Evaluating Inner Lists:: Lists within lists...
1588 @node How the Interpreter Acts
1589 @unnumberedsubsec How the Lisp Interpreter Acts
1592 @cindex @samp{returned value} explained
1593 After evaluating an expression, the Lisp interpreter will most likely
1594 @dfn{return} the value that the computer produces by carrying out the
1595 instructions it found in the function definition, or perhaps it will
1596 give up on that function and produce an error message. (The interpreter
1597 may also find itself tossed, so to speak, to a different function or it
1598 may attempt to repeat continually what it is doing for ever and ever in
1599 an infinite loop. These actions are less common; and
1600 we can ignore them.) Most frequently, the interpreter returns a value.
1602 @cindex @samp{side effect} defined
1603 At the same time the interpreter returns a value, it may do something
1604 else as well, such as move a cursor or copy a file; this other kind of
1605 action is called a @dfn{side effect}. Actions that we humans think are
1606 important, such as printing results, are often side effects to the
1607 Lisp interpreter. It is fairly easy to learn to use side effects.
1609 In summary, evaluating a symbolic expression most commonly causes the
1610 Lisp interpreter to return a value and perhaps carry out a side effect;
1611 or else produce an error.
1613 @node Evaluating Inner Lists
1614 @subsection Evaluating Inner Lists
1615 @cindex Inner list evaluation
1616 @cindex Evaluating inner lists
1618 If evaluation applies to a list that is inside another list, the outer
1619 list may use the value returned by the first evaluation as information
1620 when the outer list is evaluated. This explains why inner expressions
1621 are evaluated first: the values they return are used by the outer
1625 We can investigate this process by evaluating another addition example.
1626 Place your cursor after the following expression and type @kbd{C-x C-e}:
1633 The number 8 will appear in the echo area.
1635 What happens is that the Lisp interpreter first evaluates the inner
1636 expression, @code{(+ 3 3)}, for which the value 6 is returned; then it
1637 evaluates the outer expression as if it were written @code{(+ 2 6)}, which
1638 returns the value 8. Since there are no more enclosing expressions to
1639 evaluate, the interpreter prints that value in the echo area.
1641 Now it is easy to understand the name of the command invoked by the
1642 keystrokes @kbd{C-x C-e}: the name is @code{eval-last-sexp}. The
1643 letters @code{sexp} are an abbreviation for ``symbolic expression'', and
1644 @code{eval} is an abbreviation for ``evaluate''. The command
1645 evaluates the last symbolic expression.
1647 As an experiment, you can try evaluating the expression by putting the
1648 cursor at the beginning of the next line immediately following the
1649 expression, or inside the expression.
1652 Here is another copy of the expression:
1659 If you place the cursor at the beginning of the blank line that
1660 immediately follows the expression and type @kbd{C-x C-e}, you will
1661 still get the value 8 printed in the echo area. Now try putting the
1662 cursor inside the expression. If you put it right after the next to
1663 last parenthesis (so it appears to sit on top of the last parenthesis),
1664 you will get a 6 printed in the echo area! This is because the command
1665 evaluates the expression @code{(+ 3 3)}.
1667 Now put the cursor immediately after a number. Type @kbd{C-x C-e} and
1668 you will get the number itself. In Lisp, if you evaluate a number, you
1669 get the number itself---this is how numbers differ from symbols. If you
1670 evaluate a list starting with a symbol like @code{+}, you will get a
1671 value returned that is the result of the computer carrying out the
1672 instructions in the function definition attached to that name. If a
1673 symbol by itself is evaluated, something different happens, as we will
1674 see in the next section.
1680 In Emacs Lisp, a symbol can have a value attached to it just as it can
1681 have a function definition attached to it. The two are different.
1682 The function definition is a set of instructions that a computer will
1683 obey. A value, on the other hand, is something, such as number or a
1684 name, that can vary (which is why such a symbol is called a variable).
1685 The value of a symbol can be any expression in Lisp, such as a symbol,
1686 number, list, or string. A symbol that has a value is often called a
1689 A symbol can have both a function definition and a value attached to
1690 it at the same time. Or it can have just one or the other.
1691 The two are separate. This is somewhat similar
1692 to the way the name Cambridge can refer to the city in Massachusetts
1693 and have some information attached to the name as well, such as
1694 ``great programming center''.
1697 (Incidentally, in Emacs Lisp, a symbol can have two
1698 other things attached to it, too: a property list and a documentation
1699 string; these are discussed later.)
1702 Another way to think about this is to imagine a symbol as being a chest
1703 of drawers. The function definition is put in one drawer, the value in
1704 another, and so on. What is put in the drawer holding the value can be
1705 changed without affecting the contents of the drawer holding the
1706 function definition, and vice versa.
1709 * fill-column Example::
1710 * Void Function:: The error message for a symbol
1712 * Void Variable:: The error message for a symbol without a value.
1716 @node fill-column Example
1717 @unnumberedsubsec @code{fill-column}, an Example Variable
1720 @findex fill-column, @r{an example variable}
1721 @cindex Example variable, @code{fill-column}
1722 @cindex Variable, example of, @code{fill-column}
1723 The variable @code{fill-column} illustrates a symbol with a value
1724 attached to it: in every GNU Emacs buffer, this symbol is set to some
1725 value, usually 72 or 70, but sometimes to some other value. To find the
1726 value of this symbol, evaluate it by itself. If you are reading this in
1727 Info inside of GNU Emacs, you can do this by putting the cursor after
1728 the symbol and typing @kbd{C-x C-e}:
1735 After I typed @kbd{C-x C-e}, Emacs printed the number 72 in my echo
1736 area. This is the value for which @code{fill-column} is set for me as I
1737 write this. It may be different for you in your Info buffer. Notice
1738 that the value returned as a variable is printed in exactly the same way
1739 as the value returned by a function carrying out its instructions. From
1740 the point of view of the Lisp interpreter, a value returned is a value
1741 returned. What kind of expression it came from ceases to matter once
1744 A symbol can have any value attached to it or, to use the jargon, we can
1745 @dfn{bind} the variable to a value: to a number, such as 72; to a
1746 string, @code{"such as this"}; to a list, such as @code{(spruce pine
1747 oak)}; we can even bind a variable to a function definition.
1749 A symbol can be bound to a value in several ways. @xref{set & setq, ,
1750 Setting the Value of a Variable}, for information about one way to do
1754 @subsection Error Message for a Symbol Without a Function
1755 @cindex Symbol without function error
1756 @cindex Error for symbol without function
1758 When we evaluated @code{fill-column} to find its value as a variable,
1759 we did not place parentheses around the word. This is because we did
1760 not intend to use it as a function name.
1762 If @code{fill-column} were the first or only element of a list, the
1763 Lisp interpreter would attempt to find the function definition
1764 attached to it. But @code{fill-column} has no function definition.
1765 Try evaluating this:
1773 You will create a @file{*Backtrace*} buffer that says:
1777 ---------- Buffer: *Backtrace* ----------
1778 Debugger entered--Lisp error: (void-function fill-column)
1781 eval-last-sexp-1(nil)
1783 call-interactively(eval-last-sexp)
1784 ---------- Buffer: *Backtrace* ----------
1789 (Remember, to quit the debugger and make the debugger window go away,
1790 type @kbd{q} in the @file{*Backtrace*} buffer.)
1794 In GNU Emacs 20 and before, you will produce an error message that says:
1797 Symbol's function definition is void:@: fill-column
1801 (The message will go away as soon as you move the cursor or type
1806 @subsection Error Message for a Symbol Without a Value
1807 @cindex Symbol without value error
1808 @cindex Error for symbol without value
1810 If you attempt to evaluate a symbol that does not have a value bound to
1811 it, you will receive an error message. You can see this by
1812 experimenting with our 2 plus 2 addition. In the following expression,
1813 put your cursor right after the @code{+}, before the first number 2,
1822 In GNU Emacs 22, you will create a @file{*Backtrace*} buffer that
1827 ---------- Buffer: *Backtrace* ----------
1828 Debugger entered--Lisp error: (void-variable +)
1830 eval-last-sexp-1(nil)
1832 call-interactively(eval-last-sexp)
1833 ---------- Buffer: *Backtrace* ----------
1838 (Again, you can quit the debugger by
1839 typing @kbd{q} in the @file{*Backtrace*} buffer.)
1841 This backtrace is different from the very first error message we saw,
1842 which said, @samp{Debugger entered--Lisp error: (void-function this)}.
1843 In this case, the function does not have a value as a variable; while
1844 in the other error message, the function (the word @samp{this}) did not
1847 In this experiment with the @code{+}, what we did was cause the Lisp
1848 interpreter to evaluate the @code{+} and look for the value of the
1849 variable instead of the function definition. We did this by placing the
1850 cursor right after the symbol rather than after the parenthesis of the
1851 enclosing list as we did before. As a consequence, the Lisp interpreter
1852 evaluated the preceding s-expression, which in this case was
1855 Since @code{+} does not have a value bound to it, just the function
1856 definition, the error message reported that the symbol's value as a
1861 In GNU Emacs version 20 and before, your error message will say:
1864 Symbol's value as variable is void:@: +
1868 The meaning is the same as in GNU Emacs 22.
1874 @cindex Passing information to functions
1876 To see how information is passed to functions, let's look again at
1877 our old standby, the addition of two plus two. In Lisp, this is written
1884 If you evaluate this expression, the number 4 will appear in your echo
1885 area. What the Lisp interpreter does is add the numbers that follow
1888 @cindex @samp{argument} defined
1889 The numbers added by @code{+} are called the @dfn{arguments} of the
1890 function @code{+}. These numbers are the information that is given to
1891 or @dfn{passed} to the function.
1893 The word ``argument'' comes from the way it is used in mathematics and
1894 does not refer to a disputation between two people; instead it refers to
1895 the information presented to the function, in this case, to the
1896 @code{+}. In Lisp, the arguments to a function are the atoms or lists
1897 that follow the function. The values returned by the evaluation of
1898 these atoms or lists are passed to the function. Different functions
1899 require different numbers of arguments; some functions require none at
1900 all.@footnote{It is curious to track the path by which the word ``argument''
1901 came to have two different meanings, one in mathematics and the other in
1902 everyday English. According to the @cite{Oxford English Dictionary},
1903 the word derives from the Latin for @samp{to make clear, prove}; thus it
1904 came to mean, by one thread of derivation, ``the evidence offered as
1905 proof'', which is to say, ``the information offered'', which led to its
1906 meaning in Lisp. But in the other thread of derivation, it came to mean
1907 ``to assert in a manner against which others may make counter
1908 assertions'', which led to the meaning of the word as a disputation.
1909 (Note here that the English word has two different definitions attached
1910 to it at the same time. By contrast, in Emacs Lisp, a symbol cannot
1911 have two different function definitions at the same time.)}
1914 * Data types:: Types of data passed to a function.
1915 * Args as Variable or List:: An argument can be the value
1916 of a variable or list.
1917 * Variable Number of Arguments:: Some functions may take a
1918 variable number of arguments.
1919 * Wrong Type of Argument:: Passing an argument of the wrong type
1921 * message:: A useful function for sending messages.
1925 @subsection Arguments' Data Types
1927 @cindex Types of data
1928 @cindex Arguments' data types
1930 The type of data that should be passed to a function depends on what
1931 kind of information it uses. The arguments to a function such as
1932 @code{+} must have values that are numbers, since @code{+} adds numbers.
1933 Other functions use different kinds of data for their arguments.
1937 For example, the @code{concat} function links together or unites two or
1938 more strings of text to produce a string. The arguments are strings.
1939 Concatenating the two character strings @code{abc}, @code{def} produces
1940 the single string @code{abcdef}. This can be seen by evaluating the
1944 (concat "abc" "def")
1948 The value produced by evaluating this expression is @code{"abcdef"}.
1951 A function such as @code{substring} uses both a string and numbers as
1952 arguments. The function returns a part of the string, a @dfn{substring} of
1953 the first argument. This function takes three arguments. Its first
1954 argument is the string of characters, the second and third arguments
1955 are numbers that indicate the beginning (inclusive) and end
1956 (exclusive) of the substring. The numbers are a count of the number
1957 of characters (including spaces and punctuation) from the beginning of
1958 the string. Note that the characters in a string are numbered from
1962 For example, if you evaluate the following:
1965 (substring "The quick brown fox jumped." 16 19)
1969 you will see @code{"fox"} appear in the echo area. The arguments are the
1970 string and the two numbers.
1972 Note that the string passed to @code{substring} is a single atom even
1973 though it is made up of several words separated by spaces. Lisp counts
1974 everything between the two quotation marks as part of the string,
1975 including the spaces. You can think of the @code{substring} function as
1976 a kind of atom smasher since it takes an otherwise indivisible atom
1977 and extracts a part. However, @code{substring} is only able to extract
1978 a substring from an argument that is a string, not from another type of
1979 atom such as a number or symbol.
1981 @node Args as Variable or List
1982 @subsection An Argument as the Value of a Variable or List
1984 An argument can be a symbol that returns a value when it is evaluated.
1985 For example, when the symbol @code{fill-column} by itself is evaluated,
1986 it returns a number. This number can be used in an addition.
1989 Position the cursor after the following expression and type @kbd{C-x
1997 The value will be a number two more than what you get by evaluating
1998 @code{fill-column} alone. For me, this is 74, because my value of
1999 @code{fill-column} is 72.
2001 As we have just seen, an argument can be a symbol that returns a value
2002 when evaluated. In addition, an argument can be a list that returns a
2003 value when it is evaluated. For example, in the following expression,
2004 the arguments to the function @code{concat} are the strings
2005 @w{@code{"The "}} and @w{@code{" red foxes."}} and the list
2006 @code{(number-to-string (+ 2 fill-column))}.
2008 @c For GNU Emacs 22, need number-to-string
2010 (concat "The " (number-to-string (+ 2 fill-column)) " red foxes.")
2014 If you evaluate this expression---and if, as with my Emacs,
2015 @code{fill-column} evaluates to 72---@code{"The 74 red foxes."} will
2016 appear in the echo area. (Note that you must put spaces after the
2017 word @samp{The} and before the word @samp{red} so they will appear in
2018 the final string. The function @code{number-to-string} converts the
2019 integer that the addition function returns to a string.
2020 @code{number-to-string} is also known as @code{int-to-string}.)
2022 @node Variable Number of Arguments
2023 @subsection Variable Number of Arguments
2024 @cindex Variable number of arguments
2025 @cindex Arguments, variable number of
2027 Some functions, such as @code{concat}, @code{+} or @code{*}, take any
2028 number of arguments. (The @code{*} is the symbol for multiplication.)
2029 This can be seen by evaluating each of the following expressions in
2030 the usual way. What you will see in the echo area is printed in this
2031 text after @samp{@result{}}, which you may read as ``evaluates to''.
2034 In the first set, the functions have no arguments:
2045 In this set, the functions have one argument each:
2056 In this set, the functions have three arguments each:
2060 (+ 3 4 5) @result{} 12
2062 (* 3 4 5) @result{} 60
2066 @node Wrong Type of Argument
2067 @subsection Using the Wrong Type Object as an Argument
2068 @cindex Wrong type of argument
2069 @cindex Argument, wrong type of
2071 When a function is passed an argument of the wrong type, the Lisp
2072 interpreter produces an error message. For example, the @code{+}
2073 function expects the values of its arguments to be numbers. As an
2074 experiment we can pass it the quoted symbol @code{hello} instead of a
2075 number. Position the cursor after the following expression and type
2083 When you do this you will generate an error message. What has happened
2084 is that @code{+} has tried to add the 2 to the value returned by
2085 @code{'hello}, but the value returned by @code{'hello} is the symbol
2086 @code{hello}, not a number. Only numbers can be added. So @code{+}
2087 could not carry out its addition.
2090 You will create and enter a @file{*Backtrace*} buffer that says:
2095 ---------- Buffer: *Backtrace* ----------
2096 Debugger entered--Lisp error:
2097 (wrong-type-argument number-or-marker-p hello)
2099 eval((+ 2 (quote hello)))
2100 eval-last-sexp-1(nil)
2102 call-interactively(eval-last-sexp)
2103 ---------- Buffer: *Backtrace* ----------
2108 As usual, the error message tries to be helpful and makes sense after you
2109 learn how to read it.@footnote{@code{(quote hello)} is an expansion of
2110 the abbreviation @code{'hello}.}
2112 The first part of the error message is straightforward; it says
2113 @samp{wrong type argument}. Next comes the mysterious jargon word
2114 @w{@samp{number-or-marker-p}}. This word is trying to tell you what
2115 kind of argument the @code{+} expected.
2117 The symbol @code{number-or-marker-p} says that the Lisp interpreter is
2118 trying to determine whether the information presented it (the value of
2119 the argument) is a number or a marker (a special object representing a
2120 buffer position). What it does is test to see whether the @code{+} is
2121 being given numbers to add. It also tests to see whether the
2122 argument is something called a marker, which is a specific feature of
2123 Emacs Lisp. (In Emacs, locations in a buffer are recorded as markers.
2124 When the mark is set with the @kbd{C-@@} or @kbd{C-@key{SPC}} command,
2125 its position is kept as a marker. The mark can be considered a
2126 number---the number of characters the location is from the beginning
2127 of the buffer.) In Emacs Lisp, @code{+} can be used to add the
2128 numeric value of marker positions as numbers.
2130 The @samp{p} of @code{number-or-marker-p} is the embodiment of a
2131 practice started in the early days of Lisp programming. The @samp{p}
2132 stands for ``predicate''. In the jargon used by the early Lisp
2133 researchers, a predicate refers to a function to determine whether some
2134 property is true or false. So the @samp{p} tells us that
2135 @code{number-or-marker-p} is the name of a function that determines
2136 whether it is true or false that the argument supplied is a number or
2137 a marker. Other Lisp symbols that end in @samp{p} include @code{zerop},
2138 a function that tests whether its argument has the value of zero, and
2139 @code{listp}, a function that tests whether its argument is a list.
2141 Finally, the last part of the error message is the symbol @code{hello}.
2142 This is the value of the argument that was passed to @code{+}. If the
2143 addition had been passed the correct type of object, the value passed
2144 would have been a number, such as 37, rather than a symbol like
2145 @code{hello}. But then you would not have got the error message.
2149 In GNU Emacs version 20 and before, the echo area displays an error
2153 Wrong type argument:@: number-or-marker-p, hello
2156 This says, in different words, the same as the top line of the
2157 @file{*Backtrace*} buffer.
2161 @subsection The @code{message} Function
2164 Like @code{+}, the @code{message} function takes a variable number of
2165 arguments. It is used to send messages to the user and is so useful
2166 that we will describe it here.
2169 A message is printed in the echo area. For example, you can print a
2170 message in your echo area by evaluating the following list:
2173 (message "This message appears in the echo area!")
2176 The whole string between double quotation marks is a single argument
2177 and is printed @i{in toto}. (Note that in this example, the message
2178 itself will appear in the echo area within double quotes; that is
2179 because you see the value returned by the @code{message} function. In
2180 most uses of @code{message} in programs that you write, the text will
2181 be printed in the echo area as a side-effect, without the quotes.
2182 @xref{multiply-by-seven in detail, , @code{multiply-by-seven} in
2183 detail}, for an example of this.)
2185 However, if there is a @samp{%s} in the quoted string of characters, the
2186 @code{message} function does not print the @samp{%s} as such, but looks
2187 to the argument that follows the string. It evaluates the second
2188 argument and prints the value at the location in the string where the
2192 You can see this by positioning the cursor after the following
2193 expression and typing @kbd{C-x C-e}:
2196 (message "The name of this buffer is: %s." (buffer-name))
2200 In Info, @code{"The name of this buffer is: *info*."} will appear in the
2201 echo area. The function @code{buffer-name} returns the name of the
2202 buffer as a string, which the @code{message} function inserts in place
2205 To print a value as an integer, use @samp{%d} in the same way as
2206 @samp{%s}. For example, to print a message in the echo area that
2207 states the value of the @code{fill-column}, evaluate the following:
2210 (message "The value of fill-column is %d." fill-column)
2214 On my system, when I evaluate this list, @code{"The value of
2215 fill-column is 72."} appears in my echo area@footnote{Actually, you
2216 can use @code{%s} to print a number. It is non-specific. @code{%d}
2217 prints only the part of a number left of a decimal point, and not
2218 anything that is not a number.}.
2220 If there is more than one @samp{%s} in the quoted string, the value of
2221 the first argument following the quoted string is printed at the
2222 location of the first @samp{%s} and the value of the second argument is
2223 printed at the location of the second @samp{%s}, and so on.
2226 For example, if you evaluate the following,
2230 (message "There are %d %s in the office!"
2231 (- fill-column 14) "pink elephants")
2236 a rather whimsical message will appear in your echo area. On my system
2237 it says, @code{"There are 58 pink elephants in the office!"}.
2239 The expression @code{(- fill-column 14)} is evaluated and the resulting
2240 number is inserted in place of the @samp{%d}; and the string in double
2241 quotes, @code{"pink elephants"}, is treated as a single argument and
2242 inserted in place of the @samp{%s}. (That is to say, a string between
2243 double quotes evaluates to itself, like a number.)
2245 Finally, here is a somewhat complex example that not only illustrates
2246 the computation of a number, but also shows how you can use an
2247 expression within an expression to generate the text that is substituted
2252 (message "He saw %d %s"
2256 "The quick brown foxes jumped." 16 21)
2261 In this example, @code{message} has three arguments: the string,
2262 @code{"He saw %d %s"}, the expression, @code{(- fill-column 32)}, and
2263 the expression beginning with the function @code{concat}. The value
2264 resulting from the evaluation of @code{(- fill-column 32)} is inserted
2265 in place of the @samp{%d}; and the value returned by the expression
2266 beginning with @code{concat} is inserted in place of the @samp{%s}.
2268 When your fill column is 70 and you evaluate the expression, the
2269 message @code{"He saw 38 red foxes leaping."} appears in your echo
2273 @section Setting the Value of a Variable
2274 @cindex Variable, setting value
2275 @cindex Setting value of variable
2277 @cindex @samp{bind} defined
2278 There are several ways by which a variable can be given a value. One of
2279 the ways is to use either the function @code{set} or the function
2280 @code{setq}. Another way is to use @code{let} (@pxref{let}). (The
2281 jargon for this process is to @dfn{bind} a variable to a value.)
2283 The following sections not only describe how @code{set} and @code{setq}
2284 work but also illustrate how arguments are passed.
2287 * Using set:: Setting values.
2288 * Using setq:: Setting a quoted value.
2289 * Counting:: Using @code{setq} to count.
2293 @subsection Using @code{set}
2296 To set the value of the symbol @code{flowers} to the list @code{'(rose
2297 violet daisy buttercup)}, evaluate the following expression by
2298 positioning the cursor after the expression and typing @kbd{C-x C-e}.
2301 (set 'flowers '(rose violet daisy buttercup))
2305 The list @code{(rose violet daisy buttercup)} will appear in the echo
2306 area. This is what is @emph{returned} by the @code{set} function. As a
2307 side effect, the symbol @code{flowers} is bound to the list; that is,
2308 the symbol @code{flowers}, which can be viewed as a variable, is given
2309 the list as its value. (This process, by the way, illustrates how a
2310 side effect to the Lisp interpreter, setting the value, can be the
2311 primary effect that we humans are interested in. This is because every
2312 Lisp function must return a value if it does not get an error, but it
2313 will only have a side effect if it is designed to have one.)
2315 After evaluating the @code{set} expression, you can evaluate the symbol
2316 @code{flowers} and it will return the value you just set. Here is the
2317 symbol. Place your cursor after it and type @kbd{C-x C-e}.
2324 When you evaluate @code{flowers}, the list
2325 @code{(rose violet daisy buttercup)} appears in the echo area.
2327 Incidentally, if you evaluate @code{'flowers}, the variable with a quote
2328 in front of it, what you will see in the echo area is the symbol itself,
2329 @code{flowers}. Here is the quoted symbol, so you can try this:
2335 Note also, that when you use @code{set}, you need to quote both
2336 arguments to @code{set}, unless you want them evaluated. Since we do
2337 not want either argument evaluated, neither the variable
2338 @code{flowers} nor the list @code{(rose violet daisy buttercup)}, both
2339 are quoted. (When you use @code{set} without quoting its first
2340 argument, the first argument is evaluated before anything else is
2341 done. If you did this and @code{flowers} did not have a value
2342 already, you would get an error message that the @samp{Symbol's value
2343 as variable is void}; on the other hand, if @code{flowers} did return
2344 a value after it was evaluated, the @code{set} would attempt to set
2345 the value that was returned. There are situations where this is the
2346 right thing for the function to do; but such situations are rare.)
2349 @subsection Using @code{setq}
2352 As a practical matter, you almost always quote the first argument to
2353 @code{set}. The combination of @code{set} and a quoted first argument
2354 is so common that it has its own name: the special form @code{setq}.
2355 This special form is just like @code{set} except that the first argument
2356 is quoted automatically, so you don't need to type the quote mark
2357 yourself. Also, as an added convenience, @code{setq} permits you to set
2358 several different variables to different values, all in one expression.
2360 To set the value of the variable @code{carnivores} to the list
2361 @code{'(lion tiger leopard)} using @code{setq}, the following expression
2365 (setq carnivores '(lion tiger leopard))
2369 This is exactly the same as using @code{set} except the first argument
2370 is automatically quoted by @code{setq}. (The @samp{q} in @code{setq}
2371 means @code{quote}.)
2374 With @code{set}, the expression would look like this:
2377 (set 'carnivores '(lion tiger leopard))
2380 Also, @code{setq} can be used to assign different values to
2381 different variables. The first argument is bound to the value
2382 of the second argument, the third argument is bound to the value of the
2383 fourth argument, and so on. For example, you could use the following to
2384 assign a list of trees to the symbol @code{trees} and a list of herbivores
2385 to the symbol @code{herbivores}:
2389 (setq trees '(pine fir oak maple)
2390 herbivores '(gazelle antelope zebra))
2395 (The expression could just as well have been on one line, but it might
2396 not have fit on a page; and humans find it easier to read nicely
2399 Although I have been using the term ``assign'', there is another way of
2400 thinking about the workings of @code{set} and @code{setq}; and that is to
2401 say that @code{set} and @code{setq} make the symbol @emph{point} to the
2402 list. This latter way of thinking is very common and in forthcoming
2403 chapters we shall come upon at least one symbol that has ``pointer'' as
2404 part of its name. The name is chosen because the symbol has a value,
2405 specifically a list, attached to it; or, expressed another way,
2406 the symbol is set to point to the list.
2409 @subsection Counting
2412 Here is an example that shows how to use @code{setq} in a counter. You
2413 might use this to count how many times a part of your program repeats
2414 itself. First set a variable to zero; then add one to the number each
2415 time the program repeats itself. To do this, you need a variable that
2416 serves as a counter, and two expressions: an initial @code{setq}
2417 expression that sets the counter variable to zero; and a second
2418 @code{setq} expression that increments the counter each time it is
2423 (setq counter 0) ; @r{Let's call this the initializer.}
2425 (setq counter (+ counter 1)) ; @r{This is the incrementer.}
2427 counter ; @r{This is the counter.}
2432 (The text following the @samp{;} are comments. @xref{Change a
2433 defun, , Change a Function Definition}.)
2435 If you evaluate the first of these expressions, the initializer,
2436 @code{(setq counter 0)}, and then evaluate the third expression,
2437 @code{counter}, the number @code{0} will appear in the echo area. If
2438 you then evaluate the second expression, the incrementer, @code{(setq
2439 counter (+ counter 1))}, the counter will get the value 1. So if you
2440 again evaluate @code{counter}, the number @code{1} will appear in the
2441 echo area. Each time you evaluate the second expression, the value of
2442 the counter will be incremented.
2444 When you evaluate the incrementer, @code{(setq counter (+ counter 1))},
2445 the Lisp interpreter first evaluates the innermost list; this is the
2446 addition. In order to evaluate this list, it must evaluate the variable
2447 @code{counter} and the number @code{1}. When it evaluates the variable
2448 @code{counter}, it receives its current value. It passes this value and
2449 the number @code{1} to the @code{+} which adds them together. The sum
2450 is then returned as the value of the inner list and passed to the
2451 @code{setq} which sets the variable @code{counter} to this new value.
2452 Thus, the value of the variable, @code{counter}, is changed.
2457 Learning Lisp is like climbing a hill in which the first part is the
2458 steepest. You have now climbed the most difficult part; what remains
2459 becomes easier as you progress onwards.
2467 Lisp programs are made up of expressions, which are lists or single atoms.
2470 Lists are made up of zero or more atoms or inner lists, separated by whitespace and
2471 surrounded by parentheses. A list can be empty.
2474 Atoms are multi-character symbols, like @code{forward-paragraph}, single
2475 character symbols like @code{+}, strings of characters between double
2476 quotation marks, or numbers.
2479 A number evaluates to itself.
2482 A string between double quotes also evaluates to itself.
2485 When you evaluate a symbol by itself, its value is returned.
2488 When you evaluate a list, the Lisp interpreter looks at the first symbol
2489 in the list and then at the function definition bound to that symbol.
2490 Then the instructions in the function definition are carried out.
2493 A single quotation mark,
2500 , tells the Lisp interpreter that it should
2501 return the following expression as written, and not evaluate it as it
2502 would if the quote were not there.
2505 Arguments are the information passed to a function. The arguments to a
2506 function are computed by evaluating the rest of the elements of the list
2507 of which the function is the first element.
2510 A function always returns a value when it is evaluated (unless it gets
2511 an error); in addition, it may also carry out some action that is a
2512 side effect. In many cases, a function's primary purpose is to
2513 create a side effect.
2516 @node Error Message Exercises
2519 A few simple exercises:
2523 Generate an error message by evaluating an appropriate symbol that is
2524 not within parentheses.
2527 Generate an error message by evaluating an appropriate symbol that is
2528 between parentheses.
2531 Create a counter that increments by two rather than one.
2534 Write an expression that prints a message in the echo area when
2538 @node Practicing Evaluation
2539 @chapter Practicing Evaluation
2540 @cindex Practicing evaluation
2541 @cindex Evaluation practice
2543 Before learning how to write a function definition in Emacs Lisp, it is
2544 useful to spend a little time evaluating various expressions that have
2545 already been written. These expressions will be lists with the
2546 functions as their first (and often only) element. Since some of the
2547 functions associated with buffers are both simple and interesting, we
2548 will start with those. In this section, we will evaluate a few of
2549 these. In another section, we will study the code of several other
2550 buffer-related functions, to see how they were written.
2553 * How to Evaluate:: Typing editing commands or @kbd{C-x C-e}
2555 * Buffer Names:: Buffers and files are different.
2556 * Getting Buffers:: Getting a buffer itself, not merely its name.
2557 * Switching Buffers:: How to change to another buffer.
2558 * Buffer Size & Locations:: Where point is located and the size of
2560 * Evaluation Exercise::
2564 @node How to Evaluate
2565 @unnumberedsec How to Evaluate
2568 @i{Whenever you give an editing command} to Emacs Lisp, such as the
2569 command to move the cursor or to scroll the screen, @i{you are evaluating
2570 an expression,} the first element of which is a function. @i{This is
2573 @cindex @samp{interactive function} defined
2574 @cindex @samp{command} defined
2575 When you type keys, you cause the Lisp interpreter to evaluate an
2576 expression and that is how you get your results. Even typing plain text
2577 involves evaluating an Emacs Lisp function, in this case, one that uses
2578 @code{self-insert-command}, which simply inserts the character you
2579 typed. The functions you evaluate by typing keystrokes are called
2580 @dfn{interactive} functions, or @dfn{commands}; how you make a function
2581 interactive will be illustrated in the chapter on how to write function
2582 definitions. @xref{Interactive, , Making a Function Interactive}.
2584 In addition to typing keyboard commands, we have seen a second way to
2585 evaluate an expression: by positioning the cursor after a list and
2586 typing @kbd{C-x C-e}. This is what we will do in the rest of this
2587 section. There are other ways to evaluate an expression as well; these
2588 will be described as we come to them.
2590 Besides being used for practicing evaluation, the functions shown in the
2591 next few sections are important in their own right. A study of these
2592 functions makes clear the distinction between buffers and files, how to
2593 switch to a buffer, and how to determine a location within it.
2596 @section Buffer Names
2598 @findex buffer-file-name
2600 The two functions, @code{buffer-name} and @code{buffer-file-name}, show
2601 the difference between a file and a buffer. When you evaluate the
2602 following expression, @code{(buffer-name)}, the name of the buffer
2603 appears in the echo area. When you evaluate @code{(buffer-file-name)},
2604 the name of the file to which the buffer refers appears in the echo
2605 area. Usually, the name returned by @code{(buffer-name)} is the same as
2606 the name of the file to which it refers, and the name returned by
2607 @code{(buffer-file-name)} is the full path-name of the file.
2609 A file and a buffer are two different entities. A file is information
2610 recorded permanently in the computer (unless you delete it). A buffer,
2611 on the other hand, is information inside of Emacs that will vanish at
2612 the end of the editing session (or when you kill the buffer). Usually,
2613 a buffer contains information that you have copied from a file; we say
2614 the buffer is @dfn{visiting} that file. This copy is what you work on
2615 and modify. Changes to the buffer do not change the file, until you
2616 save the buffer. When you save the buffer, the buffer is copied to the file
2617 and is thus saved permanently.
2620 If you are reading this in Info inside of GNU Emacs, you can evaluate
2621 each of the following expressions by positioning the cursor after it and
2622 typing @kbd{C-x C-e}.
2633 When I do this in Info, the value returned by evaluating
2634 @code{(buffer-name)} is @file{"*info*"}, and the value returned by
2635 evaluating @code{(buffer-file-name)} is @file{nil}.
2637 On the other hand, while I am writing this document, the value
2638 returned by evaluating @code{(buffer-name)} is
2639 @file{"introduction.texinfo"}, and the value returned by evaluating
2640 @code{(buffer-file-name)} is
2641 @file{"/gnu/work/intro/introduction.texinfo"}.
2643 @cindex @code{nil}, history of word
2644 The former is the name of the buffer and the latter is the name of the
2645 file. In Info, the buffer name is @file{"*info*"}. Info does not
2646 point to any file, so the result of evaluating
2647 @code{(buffer-file-name)} is @file{nil}. The symbol @code{nil} is
2648 from the Latin word for ``nothing''; in this case, it means that the
2649 buffer is not associated with any file. (In Lisp, @code{nil} is also
2650 used to mean ``false'' and is a synonym for the empty list, @code{()}.)
2652 When I am writing, the name of my buffer is
2653 @file{"introduction.texinfo"}. The name of the file to which it
2654 points is @file{"/gnu/work/intro/introduction.texinfo"}.
2656 (In the expressions, the parentheses tell the Lisp interpreter to
2657 treat @w{@code{buffer-name}} and @w{@code{buffer-file-name}} as
2658 functions; without the parentheses, the interpreter would attempt to
2659 evaluate the symbols as variables. @xref{Variables}.)
2661 In spite of the distinction between files and buffers, you will often
2662 find that people refer to a file when they mean a buffer and vice versa.
2663 Indeed, most people say, ``I am editing a file,'' rather than saying,
2664 ``I am editing a buffer which I will soon save to a file.'' It is
2665 almost always clear from context what people mean. When dealing with
2666 computer programs, however, it is important to keep the distinction in mind,
2667 since the computer is not as smart as a person.
2669 @cindex Buffer, history of word
2670 The word ``buffer'', by the way, comes from the meaning of the word as a
2671 cushion that deadens the force of a collision. In early computers, a
2672 buffer cushioned the interaction between files and the computer's
2673 central processing unit. The drums or tapes that held a file and the
2674 central processing unit were pieces of equipment that were very
2675 different from each other, working at their own speeds, in spurts. The
2676 buffer made it possible for them to work together effectively.
2677 Eventually, the buffer grew from being an intermediary, a temporary
2678 holding place, to being the place where work is done. This
2679 transformation is rather like that of a small seaport that grew into a
2680 great city: once it was merely the place where cargo was warehoused
2681 temporarily before being loaded onto ships; then it became a business
2682 and cultural center in its own right.
2684 Not all buffers are associated with files. For example, a
2685 @file{*scratch*} buffer does not visit any file. Similarly, a
2686 @file{*Help*} buffer is not associated with any file.
2688 In the old days, when you lacked a @file{~/.emacs} file and started an
2689 Emacs session by typing the command @code{emacs} alone, without naming
2690 any files, Emacs started with the @file{*scratch*} buffer visible.
2691 Nowadays, you will see a splash screen. You can follow one of the
2692 commands suggested on the splash screen, visit a file, or press the
2693 spacebar to reach the @file{*scratch*} buffer.
2695 If you switch to the @file{*scratch*} buffer, type
2696 @code{(buffer-name)}, position the cursor after it, and then type
2697 @kbd{C-x C-e} to evaluate the expression. The name @code{"*scratch*"}
2698 will be returned and will appear in the echo area. @code{"*scratch*"}
2699 is the name of the buffer. When you type @code{(buffer-file-name)} in
2700 the @file{*scratch*} buffer and evaluate that, @code{nil} will appear
2701 in the echo area, just as it does when you evaluate
2702 @code{(buffer-file-name)} in Info.
2704 Incidentally, if you are in the @file{*scratch*} buffer and want the
2705 value returned by an expression to appear in the @file{*scratch*}
2706 buffer itself rather than in the echo area, type @kbd{C-u C-x C-e}
2707 instead of @kbd{C-x C-e}. This causes the value returned to appear
2708 after the expression. The buffer will look like this:
2711 (buffer-name)"*scratch*"
2715 You cannot do this in Info since Info is read-only and it will not allow
2716 you to change the contents of the buffer. But you can do this in any
2717 buffer you can edit; and when you write code or documentation (such as
2718 this book), this feature is very useful.
2720 @node Getting Buffers
2721 @section Getting Buffers
2722 @findex current-buffer
2723 @findex other-buffer
2724 @cindex Getting a buffer
2726 The @code{buffer-name} function returns the @emph{name} of the buffer;
2727 to get the buffer @emph{itself}, a different function is needed: the
2728 @code{current-buffer} function. If you use this function in code, what
2729 you get is the buffer itself.
2731 A name and the object or entity to which the name refers are different
2732 from each other. You are not your name. You are a person to whom
2733 others refer by name. If you ask to speak to George and someone hands you
2734 a card with the letters @samp{G}, @samp{e}, @samp{o}, @samp{r},
2735 @samp{g}, and @samp{e} written on it, you might be amused, but you would
2736 not be satisfied. You do not want to speak to the name, but to the
2737 person to whom the name refers. A buffer is similar: the name of the
2738 scratch buffer is @file{*scratch*}, but the name is not the buffer. To
2739 get a buffer itself, you need to use a function such as
2740 @code{current-buffer}.
2742 However, there is a slight complication: if you evaluate
2743 @code{current-buffer} in an expression on its own, as we will do here,
2744 what you see is a printed representation of the name of the buffer
2745 without the contents of the buffer. Emacs works this way for two
2746 reasons: the buffer may be thousands of lines long---too long to be
2747 conveniently displayed; and, another buffer may have the same contents
2748 but a different name, and it is important to distinguish between them.
2751 Here is an expression containing the function:
2758 If you evaluate this expression in Info in Emacs in the usual way,
2759 @file{#<buffer *info*>} will appear in the echo area. The special
2760 format indicates that the buffer itself is being returned, rather than
2763 Incidentally, while you can type a number or symbol into a program, you
2764 cannot do that with the printed representation of a buffer: the only way
2765 to get a buffer itself is with a function such as @code{current-buffer}.
2767 A related function is @code{other-buffer}. This returns the most
2768 recently selected buffer other than the one you are in currently, not
2769 a printed representation of its name. If you have recently switched
2770 back and forth from the @file{*scratch*} buffer, @code{other-buffer}
2771 will return that buffer.
2774 You can see this by evaluating the expression:
2781 You should see @file{#<buffer *scratch*>} appear in the echo area, or
2782 the name of whatever other buffer you switched back from most
2783 recently@footnote{Actually, by default, if the buffer from which you
2784 just switched is visible to you in another window, @code{other-buffer}
2785 will choose the most recent buffer that you cannot see; this is a
2786 subtlety that I often forget.}.
2788 @node Switching Buffers
2789 @section Switching Buffers
2790 @findex switch-to-buffer
2792 @cindex Switching to a buffer
2794 The @code{other-buffer} function actually provides a buffer when it is
2795 used as an argument to a function that requires one. We can see this
2796 by using @code{other-buffer} and @code{switch-to-buffer} to switch to a
2799 But first, a brief introduction to the @code{switch-to-buffer}
2800 function. When you switched back and forth from Info to the
2801 @file{*scratch*} buffer to evaluate @code{(buffer-name)}, you most
2802 likely typed @kbd{C-x b} and then typed @file{*scratch*}@footnote{Or
2803 rather, to save typing, you probably only typed @kbd{RET} if the
2804 default buffer was @file{*scratch*}, or if it was different, then you
2805 typed just part of the name, such as @code{*sc}, pressed your
2806 @kbd{TAB} key to cause it to expand to the full name, and then typed
2807 @kbd{RET}.} when prompted in the minibuffer for the name of
2808 the buffer to which you wanted to switch. The keystrokes, @kbd{C-x
2809 b}, cause the Lisp interpreter to evaluate the interactive function
2810 @code{switch-to-buffer}. As we said before, this is how Emacs works:
2811 different keystrokes call or run different functions. For example,
2812 @kbd{C-f} calls @code{forward-char}, @kbd{M-e} calls
2813 @code{forward-sentence}, and so on.
2815 By writing @code{switch-to-buffer} in an expression, and giving it a
2816 buffer to switch to, we can switch buffers just the way @kbd{C-x b}
2820 (switch-to-buffer (other-buffer))
2824 The symbol @code{switch-to-buffer} is the first element of the list,
2825 so the Lisp interpreter will treat it as a function and carry out the
2826 instructions that are attached to it. But before doing that, the
2827 interpreter will note that @code{other-buffer} is inside parentheses
2828 and work on that symbol first. @code{other-buffer} is the first (and
2829 in this case, the only) element of this list, so the Lisp interpreter
2830 calls or runs the function. It returns another buffer. Next, the
2831 interpreter runs @code{switch-to-buffer}, passing to it, as an
2832 argument, the other buffer, which is what Emacs will switch to. If
2833 you are reading this in Info, try this now. Evaluate the expression.
2834 (To get back, type @kbd{C-x b @key{RET}}.)@footnote{Remember, this
2835 expression will move you to your most recent other buffer that you
2836 cannot see. If you really want to go to your most recently selected
2837 buffer, even if you can still see it, you need to evaluate the
2838 following more complex expression:
2841 (switch-to-buffer (other-buffer (current-buffer) t))
2845 In this case, the first argument to @code{other-buffer} tells it which
2846 buffer to skip---the current one---and the second argument tells
2847 @code{other-buffer} it is OK to switch to a visible buffer. In
2848 regular use, @code{switch-to-buffer} takes you to a buffer not visible
2849 in windows since you would most likely use @kbd{C-x o}
2850 (@code{other-window}) to go to another visible buffer.}
2852 In the programming examples in later sections of this document, you will
2853 see the function @code{set-buffer} more often than
2854 @code{switch-to-buffer}. This is because of a difference between
2855 computer programs and humans: humans have eyes and expect to see the
2856 buffer on which they are working on their computer terminals. This is
2857 so obvious, it almost goes without saying. However, programs do not
2858 have eyes. When a computer program works on a buffer, that buffer does
2859 not need to be visible on the screen.
2861 @code{switch-to-buffer} is designed for humans and does two different
2862 things: it switches the buffer to which Emacs's attention is directed; and
2863 it switches the buffer displayed in the window to the new buffer.
2864 @code{set-buffer}, on the other hand, does only one thing: it switches
2865 the attention of the computer program to a different buffer. The buffer
2866 on the screen remains unchanged (of course, normally nothing happens
2867 there until the command finishes running).
2869 @cindex @samp{call} defined
2870 Also, we have just introduced another jargon term, the word @dfn{call}.
2871 When you evaluate a list in which the first symbol is a function, you
2872 are calling that function. The use of the term comes from the notion of
2873 the function as an entity that can do something for you if you call
2874 it---just as a plumber is an entity who can fix a leak if you call him
2877 @node Buffer Size & Locations
2878 @section Buffer Size and the Location of Point
2879 @cindex Size of buffer
2881 @cindex Point location
2882 @cindex Location of point
2884 Finally, let's look at several rather simple functions,
2885 @code{buffer-size}, @code{point}, @code{point-min}, and
2886 @code{point-max}. These give information about the size of a buffer and
2887 the location of point within it.
2889 The function @code{buffer-size} tells you the size of the current
2890 buffer; that is, the function returns a count of the number of
2891 characters in the buffer.
2898 You can evaluate this in the usual way, by positioning the
2899 cursor after the expression and typing @kbd{C-x C-e}.
2901 @cindex @samp{point} defined
2902 In Emacs, the current position of the cursor is called @dfn{point}.
2903 The expression @code{(point)} returns a number that tells you where the
2904 cursor is located as a count of the number of characters from the
2905 beginning of the buffer up to point.
2908 You can see the character count for point in this buffer by evaluating
2909 the following expression in the usual way:
2916 As I write this, the value of point is 65724. The @code{point}
2917 function is frequently used in some of the examples later in this
2921 The value of point depends, of course, on its location within the
2922 buffer. If you evaluate point in this spot, the number will be larger:
2929 For me, the value of point in this location is 66043, which means that
2930 there are 319 characters (including spaces) between the two
2931 expressions. (Doubtless, you will see different numbers, since I will
2932 have edited this since I first evaluated point.)
2934 @cindex @samp{narrowing} defined
2935 The function @code{point-min} is somewhat similar to @code{point}, but
2936 it returns the value of the minimum permissible value of point in the
2937 current buffer. This is the number 1 unless @dfn{narrowing} is in
2938 effect. (Narrowing is a mechanism whereby you can restrict yourself,
2939 or a program, to operations on just a part of a buffer.
2940 @xref{Narrowing & Widening, , Narrowing and Widening}.) Likewise, the
2941 function @code{point-max} returns the value of the maximum permissible
2942 value of point in the current buffer.
2944 @node Evaluation Exercise
2947 Find a file with which you are working and move towards its middle.
2948 Find its buffer name, file name, length, and your position in the file.
2950 @node Writing Defuns
2951 @chapter How To Write Function Definitions
2952 @cindex Definition writing
2953 @cindex Function definition writing
2954 @cindex Writing a function definition
2956 When the Lisp interpreter evaluates a list, it looks to see whether the
2957 first symbol on the list has a function definition attached to it; or,
2958 put another way, whether the symbol points to a function definition. If
2959 it does, the computer carries out the instructions in the definition. A
2960 symbol that has a function definition is called, simply, a function
2961 (although, properly speaking, the definition is the function and the
2962 symbol refers to it.)
2965 * Primitive Functions::
2966 * defun:: The @code{defun} macro.
2967 * Install:: Install a function definition.
2968 * Interactive:: Making a function interactive.
2969 * Interactive Options:: Different options for @code{interactive}.
2970 * Permanent Installation:: Installing code permanently.
2971 * let:: Creating and initializing local variables.
2973 * else:: If--then--else expressions.
2974 * Truth & Falsehood:: What Lisp considers false and true.
2975 * save-excursion:: Keeping track of point and buffer.
2981 @node Primitive Functions
2982 @unnumberedsec An Aside about Primitive Functions
2984 @cindex Primitive functions
2985 @cindex Functions, primitive
2987 @cindex C language primitives
2988 @cindex Primitives written in C
2989 All functions are defined in terms of other functions, except for a few
2990 @dfn{primitive} functions that are written in the C programming
2991 language. When you write functions' definitions, you will write them in
2992 Emacs Lisp and use other functions as your building blocks. Some of the
2993 functions you will use will themselves be written in Emacs Lisp (perhaps
2994 by you) and some will be primitives written in C@. The primitive
2995 functions are used exactly like those written in Emacs Lisp and behave
2996 like them. They are written in C so we can easily run GNU Emacs on any
2997 computer that has sufficient power and can run C.
2999 Let me re-emphasize this: when you write code in Emacs Lisp, you do not
3000 distinguish between the use of functions written in C and the use of
3001 functions written in Emacs Lisp. The difference is irrelevant. I
3002 mention the distinction only because it is interesting to know. Indeed,
3003 unless you investigate, you won't know whether an already-written
3004 function is written in Emacs Lisp or C.
3007 @section The @code{defun} Macro
3010 @cindex @samp{function definition} defined
3011 In Lisp, a symbol such as @code{mark-whole-buffer} has code attached to
3012 it that tells the computer what to do when the function is called.
3013 This code is called the @dfn{function definition} and is created by
3014 evaluating a Lisp expression that starts with the symbol @code{defun}
3015 (which is an abbreviation for @emph{define function}).
3017 In subsequent sections, we will look at function definitions from the
3018 Emacs source code, such as @code{mark-whole-buffer}. In this section,
3019 we will describe a simple function definition so you can see how it
3020 looks. This function definition uses arithmetic because it makes for a
3021 simple example. Some people dislike examples using arithmetic; however,
3022 if you are such a person, do not despair. Hardly any of the code we
3023 will study in the remainder of this introduction involves arithmetic or
3024 mathematics. The examples mostly involve text in one way or another.
3026 A function definition has up to five parts following the word
3031 The name of the symbol to which the function definition should be
3035 A list of the arguments that will be passed to the function. If no
3036 arguments will be passed to the function, this is an empty list,
3040 Documentation describing the function. (Technically optional, but
3041 strongly recommended.)
3044 Optionally, an expression to make the function interactive so you can
3045 use it by typing @kbd{M-x} and then the name of the function; or by
3046 typing an appropriate key or keychord.
3048 @cindex @samp{body} defined
3050 The code that instructs the computer what to do: the @dfn{body} of the
3051 function definition.
3054 It is helpful to think of the five parts of a function definition as
3055 being organized in a template, with slots for each part:
3059 (defun @var{function-name} (@var{arguments}@dots{})
3060 "@var{optional-documentation}@dots{}"
3061 (interactive @var{argument-passing-info}) ; @r{optional}
3066 As an example, here is the code for a function that multiplies its
3067 argument by 7. (This example is not interactive. @xref{Interactive,
3068 , Making a Function Interactive}, for that information.)
3072 (defun multiply-by-seven (number)
3073 "Multiply NUMBER by seven."
3078 This definition begins with a parenthesis and the symbol @code{defun},
3079 followed by the name of the function.
3081 @cindex @samp{argument list} defined
3082 The name of the function is followed by a list that contains the
3083 arguments that will be passed to the function. This list is called
3084 the @dfn{argument list}. In this example, the list has only one
3085 element, the symbol, @code{number}. When the function is used, the
3086 symbol will be bound to the value that is used as the argument to the
3089 Instead of choosing the word @code{number} for the name of the argument,
3090 I could have picked any other name. For example, I could have chosen
3091 the word @code{multiplicand}. I picked the word ``number'' because it
3092 tells what kind of value is intended for this slot; but I could just as
3093 well have chosen the word ``multiplicand'' to indicate the role that the
3094 value placed in this slot will play in the workings of the function. I
3095 could have called it @code{foogle}, but that would have been a bad
3096 choice because it would not tell humans what it means. The choice of
3097 name is up to the programmer and should be chosen to make the meaning of
3100 Indeed, you can choose any name you wish for a symbol in an argument
3101 list, even the name of a symbol used in some other function: the name
3102 you use in an argument list is private to that particular definition.
3103 In that definition, the name refers to a different entity than any use
3104 of the same name outside the function definition. Suppose you have a
3105 nick-name ``Shorty'' in your family; when your family members refer to
3106 ``Shorty'', they mean you. But outside your family, in a movie, for
3107 example, the name ``Shorty'' refers to someone else. Because a name in an
3108 argument list is private to the function definition, you can change the
3109 value of such a symbol inside the body of a function without changing
3110 its value outside the function. The effect is similar to that produced
3111 by a @code{let} expression. (@xref{let, , @code{let}}.)
3114 Note also that we discuss the word ``number'' in two different ways: as a
3115 symbol that appears in the code, and as the name of something that will
3116 be replaced by a something else during the evaluation of the function.
3117 In the first case, @code{number} is a symbol, not a number; it happens
3118 that within the function, it is a variable who value is the number in
3119 question, but our primary interest in it is as a symbol. On the other
3120 hand, when we are talking about the function, our interest is that we
3121 will substitute a number for the word @var{number}. To keep this
3122 distinction clear, we use different typography for the two
3123 circumstances. When we talk about this function, or about how it works,
3124 we refer to this number by writing @var{number}. In the function
3125 itself, we refer to it by writing @code{number}.
3128 The argument list is followed by the documentation string that
3129 describes the function. This is what you see when you type
3130 @w{@kbd{C-h f}} and the name of a function. Incidentally, when you
3131 write a documentation string like this, you should make the first line
3132 a complete sentence since some commands, such as @code{apropos}, print
3133 only the first line of a multi-line documentation string. Also, you
3134 should not indent the second line of a documentation string, if you
3135 have one, because that looks odd when you use @kbd{C-h f}
3136 (@code{describe-function}). The documentation string is optional, but
3137 it is so useful, it should be included in almost every function you
3140 @findex * @r{(multiplication)}
3141 The third line of the example consists of the body of the function
3142 definition. (Most functions' definitions, of course, are longer than
3143 this.) In this function, the body is the list, @code{(* 7 number)}, which
3144 says to multiply the value of @var{number} by 7. (In Emacs Lisp,
3145 @code{*} is the function for multiplication, just as @code{+} is the
3146 function for addition.)
3148 When you use the @code{multiply-by-seven} function, the argument
3149 @code{number} evaluates to the actual number you want used. Here is an
3150 example that shows how @code{multiply-by-seven} is used; but don't try
3151 to evaluate this yet!
3154 (multiply-by-seven 3)
3158 The symbol @code{number}, specified in the function definition in the
3159 next section, is bound to the value 3 in the actual use of
3160 the function. Note that although @code{number} was inside parentheses
3161 in the function definition, the argument passed to the
3162 @code{multiply-by-seven} function is not in parentheses. The
3163 parentheses are written in the function definition so the computer can
3164 figure out where the argument list ends and the rest of the function
3167 If you evaluate this example, you are likely to get an error message.
3168 (Go ahead, try it!) This is because we have written the function
3169 definition, but not yet told the computer about the definition---we have
3170 not yet loaded the function definition in Emacs.
3171 Installing a function is the process that tells the Lisp interpreter the
3172 definition of the function. Installation is described in the next
3176 @section Install a Function Definition
3177 @cindex Install a Function Definition
3178 @cindex Definition installation
3179 @cindex Function definition installation
3181 If you are reading this inside of Info in Emacs, you can try out the
3182 @code{multiply-by-seven} function by first evaluating the function
3183 definition and then evaluating @code{(multiply-by-seven 3)}. A copy of
3184 the function definition follows. Place the cursor after the last
3185 parenthesis of the function definition and type @kbd{C-x C-e}. When you
3186 do this, @code{multiply-by-seven} will appear in the echo area. (What
3187 this means is that when a function definition is evaluated, the value it
3188 returns is the name of the defined function.) At the same time, this
3189 action installs the function definition.
3193 (defun multiply-by-seven (number)
3194 "Multiply NUMBER by seven."
3200 By evaluating this @code{defun}, you have just installed
3201 @code{multiply-by-seven} in Emacs. The function is now just as much a
3202 part of Emacs as @code{forward-word} or any other editing function you
3203 use. (@code{multiply-by-seven} will stay installed until you quit
3204 Emacs. To reload code automatically whenever you start Emacs, see
3205 @ref{Permanent Installation, , Installing Code Permanently}.)
3208 * Effect of installation::
3209 * Change a defun:: How to change a function definition.
3213 @node Effect of installation
3214 @unnumberedsubsec The effect of installation
3217 You can see the effect of installing @code{multiply-by-seven} by
3218 evaluating the following sample. Place the cursor after the following
3219 expression and type @kbd{C-x C-e}. The number 21 will appear in the
3223 (multiply-by-seven 3)
3226 If you wish, you can read the documentation for the function by typing
3227 @kbd{C-h f} (@code{describe-function}) and then the name of the
3228 function, @code{multiply-by-seven}. When you do this, a
3229 @file{*Help*} window will appear on your screen that says:
3233 multiply-by-seven is a Lisp function.
3235 (multiply-by-seven NUMBER)
3237 Multiply NUMBER by seven.
3242 (To return to a single window on your screen, type @kbd{C-x 1}.)
3244 @node Change a defun
3245 @subsection Change a Function Definition
3246 @cindex Changing a function definition
3247 @cindex Function definition, how to change
3248 @cindex Definition, how to change
3250 If you want to change the code in @code{multiply-by-seven}, just rewrite
3251 it. To install the new version in place of the old one, evaluate the
3252 function definition again. This is how you modify code in Emacs. It is
3255 As an example, you can change the @code{multiply-by-seven} function to
3256 add the number to itself seven times instead of multiplying the number
3257 by seven. It produces the same answer, but by a different path. At
3258 the same time, we will add a comment to the code; a comment is text
3259 that the Lisp interpreter ignores, but that a human reader may find
3260 useful or enlightening. The comment is that this is the second
3265 (defun multiply-by-seven (number) ; @r{Second version.}
3266 "Multiply NUMBER by seven."
3267 (+ number number number number number number number))
3271 @cindex Comments in Lisp code
3272 The comment follows a semicolon, @samp{;}. In Lisp, everything on a
3273 line that follows a semicolon is a comment. The end of the line is the
3274 end of the comment. To stretch a comment over two or more lines, begin
3275 each line with a semicolon.
3277 @xref{Beginning init File, , Beginning a @file{.emacs}
3278 File}, and @ref{Comments, , Comments, elisp, The GNU Emacs Lisp
3279 Reference Manual}, for more about comments.
3281 You can install this version of the @code{multiply-by-seven} function by
3282 evaluating it in the same way you evaluated the first function: place
3283 the cursor after the last parenthesis and type @kbd{C-x C-e}.
3285 In summary, this is how you write code in Emacs Lisp: you write a
3286 function; install it; test it; and then make fixes or enhancements and
3290 @section Make a Function Interactive
3291 @cindex Interactive functions
3294 You make a function interactive by placing a list that begins with
3295 the special form @code{interactive} immediately after the
3296 documentation. A user can invoke an interactive function by typing
3297 @kbd{M-x} and then the name of the function; or by typing the keys to
3298 which it is bound, for example, by typing @kbd{C-n} for
3299 @code{next-line} or @kbd{C-x h} for @code{mark-whole-buffer}.
3301 Interestingly, when you call an interactive function interactively,
3302 the value returned is not automatically displayed in the echo area.
3303 This is because you often call an interactive function for its side
3304 effects, such as moving forward by a word or line, and not for the
3305 value returned. If the returned value were displayed in the echo area
3306 each time you typed a key, it would be very distracting.
3309 * Interactive multiply-by-seven:: An overview.
3310 * multiply-by-seven in detail:: The interactive version.
3314 @node Interactive multiply-by-seven
3315 @unnumberedsubsec An Interactive @code{multiply-by-seven}, An Overview
3318 Both the use of the special form @code{interactive} and one way to
3319 display a value in the echo area can be illustrated by creating an
3320 interactive version of @code{multiply-by-seven}.
3327 (defun multiply-by-seven (number) ; @r{Interactive version.}
3328 "Multiply NUMBER by seven."
3330 (message "The result is %d" (* 7 number)))
3335 You can install this code by placing your cursor after it and typing
3336 @kbd{C-x C-e}. The name of the function will appear in your echo area.
3337 Then, you can use this code by typing @kbd{C-u} and a number and then
3338 typing @kbd{M-x multiply-by-seven} and pressing @key{RET}. The phrase
3339 @samp{The result is @dots{}} followed by the product will appear in the
3342 Speaking more generally, you invoke a function like this in either of two
3347 By typing a prefix argument that contains the number to be passed, and
3348 then typing @kbd{M-x} and the name of the function, as with
3349 @kbd{C-u 3 M-x forward-sentence}; or,
3352 By typing whatever key or keychord the function is bound to, as with
3357 Both the examples just mentioned work identically to move point forward
3358 three sentences. (Since @code{multiply-by-seven} is not bound to a key,
3359 it could not be used as an example of key binding.)
3361 (@xref{Keybindings, , Some Keybindings}, to learn how to bind a command
3364 A @dfn{prefix argument} is passed to an interactive function by typing the
3365 @key{META} key followed by a number, for example, @kbd{M-3 M-e}, or by
3366 typing @kbd{C-u} and then a number, for example, @kbd{C-u 3 M-e} (if you
3367 type @kbd{C-u} without a number, it defaults to 4).
3369 @node multiply-by-seven in detail
3370 @subsection An Interactive @code{multiply-by-seven}
3372 Let's look at the use of the special form @code{interactive} and then at
3373 the function @code{message} in the interactive version of
3374 @code{multiply-by-seven}. You will recall that the function definition
3379 (defun multiply-by-seven (number) ; @r{Interactive version.}
3380 "Multiply NUMBER by seven."
3382 (message "The result is %d" (* 7 number)))
3386 In this function, the expression, @code{(interactive "p")}, is a list of
3387 two elements. The @code{"p"} tells Emacs to pass the prefix argument to
3388 the function and use its value for the argument of the function.
3391 The argument will be a number. This means that the symbol
3392 @code{number} will be bound to a number in the line:
3395 (message "The result is %d" (* 7 number))
3400 For example, if your prefix argument is 5, the Lisp interpreter will
3401 evaluate the line as if it were:
3404 (message "The result is %d" (* 7 5))
3408 (If you are reading this in GNU Emacs, you can evaluate this expression
3409 yourself.) First, the interpreter will evaluate the inner list, which
3410 is @code{(* 7 5)}. This returns a value of 35. Next, it
3411 will evaluate the outer list, passing the values of the second and
3412 subsequent elements of the list to the function @code{message}.
3414 As we have seen, @code{message} is an Emacs Lisp function especially
3415 designed for sending a one line message to a user. (@xref{message, ,
3416 The @code{message} function}.) In summary, the @code{message}
3417 function prints its first argument in the echo area as is, except for
3418 occurrences of @samp{%d} or @samp{%s} (and various other %-sequences
3419 which we have not mentioned). When it sees a control sequence, the
3420 function looks to the second or subsequent arguments and prints the
3421 value of the argument in the location in the string where the control
3422 sequence is located.
3424 In the interactive @code{multiply-by-seven} function, the control string
3425 is @samp{%d}, which requires a number, and the value returned by
3426 evaluating @code{(* 7 5)} is the number 35. Consequently, the number 35
3427 is printed in place of the @samp{%d} and the message is @samp{The result
3430 (Note that when you call the function @code{multiply-by-seven}, the
3431 message is printed without quotes, but when you call @code{message}, the
3432 text is printed in double quotes. This is because the value returned by
3433 @code{message} is what appears in the echo area when you evaluate an
3434 expression whose first element is @code{message}; but when embedded in a
3435 function, @code{message} prints the text as a side effect without
3438 @node Interactive Options
3439 @section Different Options for @code{interactive}
3440 @cindex Options for @code{interactive}
3441 @cindex Interactive options
3443 In the example, @code{multiply-by-seven} used @code{"p"} as the
3444 argument to @code{interactive}. This argument told Emacs to interpret
3445 your typing either @kbd{C-u} followed by a number or @key{META}
3446 followed by a number as a command to pass that number to the function
3447 as its argument. Emacs has more than twenty characters predefined for
3448 use with @code{interactive}. In almost every case, one of these
3449 options will enable you to pass the right information interactively to
3450 a function. (@xref{Interactive Codes, , Code Characters for
3451 @code{interactive}, elisp, The GNU Emacs Lisp Reference Manual}.)
3454 Consider the function @code{zap-to-char}. Its interactive expression
3457 @c FIXME: the interactive expression of zap-to-char has been changed
3461 (interactive "p\ncZap to char: ")
3464 The first part of the argument to @code{interactive} is @samp{p}, with
3465 which you are already familiar. This argument tells Emacs to
3466 interpret a prefix, as a number to be passed to the function. You
3467 can specify a prefix either by typing @kbd{C-u} followed by a number
3468 or by typing @key{META} followed by a number. The prefix is the
3469 number of specified characters. Thus, if your prefix is three and the
3470 specified character is @samp{x}, then you will delete all the text up
3471 to and including the third next @samp{x}. If you do not set a prefix,
3472 then you delete all the text up to and including the specified
3473 character, but no more.
3475 The @samp{c} tells the function the name of the character to which to delete.
3477 More formally, a function with two or more arguments can have
3478 information passed to each argument by adding parts to the string that
3479 follows @code{interactive}. When you do this, the information is
3480 passed to each argument in the same order it is specified in the
3481 @code{interactive} list. In the string, each part is separated from
3482 the next part by a @samp{\n}, which is a newline. For example, you
3483 can follow @samp{p} with a @samp{\n} and an @samp{cZap to char:@: }.
3484 This causes Emacs to pass the value of the prefix argument (if there
3485 is one) and the character.
3487 In this case, the function definition looks like the following, where
3488 @code{arg} and @code{char} are the symbols to which @code{interactive}
3489 binds the prefix argument and the specified character:
3493 (defun @var{name-of-function} (arg char)
3494 "@var{documentation}@dots{}"
3495 (interactive "p\ncZap to char: ")
3496 @var{body-of-function}@dots{})
3501 (The space after the colon in the prompt makes it look better when you
3502 are prompted. @xref{copy-to-buffer, , The Definition of
3503 @code{copy-to-buffer}}, for an example.)
3505 When a function does not take arguments, @code{interactive} does not
3506 require any. Such a function contains the simple expression
3507 @code{(interactive)}. The @code{mark-whole-buffer} function is like
3510 Alternatively, if the special letter-codes are not right for your
3511 application, you can pass your own arguments to @code{interactive} as
3514 @xref{append-to-buffer, , The Definition of @code{append-to-buffer}},
3515 for an example. @xref{Using Interactive, , Using @code{Interactive},
3516 elisp, The GNU Emacs Lisp Reference Manual}, for a more complete
3517 explanation about this technique.
3519 @node Permanent Installation
3520 @section Install Code Permanently
3521 @cindex Install code permanently
3522 @cindex Permanent code installation
3523 @cindex Code installation
3525 When you install a function definition by evaluating it, it will stay
3526 installed until you quit Emacs. The next time you start a new session
3527 of Emacs, the function will not be installed unless you evaluate the
3528 function definition again.
3530 At some point, you may want to have code installed automatically
3531 whenever you start a new session of Emacs. There are several ways of
3536 If you have code that is just for yourself, you can put the code for the
3537 function definition in your @file{.emacs} initialization file. When you
3538 start Emacs, your @file{.emacs} file is automatically evaluated and all
3539 the function definitions within it are installed.
3540 @xref{Emacs Initialization, , Your @file{.emacs} File}.
3543 Alternatively, you can put the function definitions that you want
3544 installed in one or more files of their own and use the @code{load}
3545 function to cause Emacs to evaluate and thereby install each of the
3546 functions in the files.
3547 @xref{Loading Files, , Loading Files}.
3550 Thirdly, if you have code that your whole site will use, it is usual
3551 to put it in a file called @file{site-init.el} that is loaded when
3552 Emacs is built. This makes the code available to everyone who uses
3553 your machine. (See the @file{INSTALL} file that is part of the Emacs
3557 Finally, if you have code that everyone who uses Emacs may want, you
3558 can post it on a computer network or send a copy to the Free Software
3559 Foundation. (When you do this, please license the code and its
3560 documentation under a license that permits other people to run, copy,
3561 study, modify, and redistribute the code and which protects you from
3562 having your work taken from you.) If you send a copy of your code to
3563 the Free Software Foundation, and properly protect yourself and
3564 others, it may be included in the next release of Emacs. In large
3565 part, this is how Emacs has grown over the past years, by donations.
3571 The @code{let} expression is a special form in Lisp that you will need
3572 to use in most function definitions.
3574 @code{let} is used to attach or bind a symbol to a value in such a way
3575 that the Lisp interpreter will not confuse the variable with a
3576 variable of the same name that is not part of the function.
3578 To understand why the @code{let} special form is necessary, consider
3579 the situation in which you own a home that you generally refer to as
3580 ``the house'', as in the sentence, ``The house needs painting.'' If you
3581 are visiting a friend and your host refers to ``the house'', he is
3582 likely to be referring to @emph{his} house, not yours, that is, to a
3585 If your friend is referring to his house and you think he is referring
3586 to your house, you may be in for some confusion. The same thing could
3587 happen in Lisp if a variable that is used inside of one function has
3588 the same name as a variable that is used inside of another function,
3589 and the two are not intended to refer to the same value. The
3590 @code{let} special form prevents this kind of confusion.
3593 * Prevent confusion::
3594 * Parts of let Expression::
3595 * Sample let Expression::
3596 * Uninitialized let Variables::
3600 @node Prevent confusion
3601 @unnumberedsubsec @code{let} Prevents Confusion
3604 @cindex @samp{local variable} defined
3605 @cindex @samp{variable, local}, defined
3606 The @code{let} special form prevents confusion. @code{let} creates a
3607 name for a @dfn{local variable} that overshadows any use of the same
3608 name outside the @code{let} expression. This is like understanding
3609 that whenever your host refers to ``the house'', he means his house, not
3610 yours. (Symbols used in argument lists work the same way.
3611 @xref{defun, , The @code{defun} Macro}.)
3613 Local variables created by a @code{let} expression retain their value
3614 @emph{only} within the @code{let} expression itself (and within
3615 expressions called within the @code{let} expression); the local
3616 variables have no effect outside the @code{let} expression.
3618 Another way to think about @code{let} is that it is like a @code{setq}
3619 that is temporary and local. The values set by @code{let} are
3620 automatically undone when the @code{let} is finished. The setting
3621 only affects expressions that are inside the bounds of the @code{let}
3622 expression. In computer science jargon, we would say the binding of
3623 a symbol is visible only in functions called in the @code{let} form;
3624 in Emacs Lisp, scoping is dynamic, not lexical.
3626 @code{let} can create more than one variable at once. Also,
3627 @code{let} gives each variable it creates an initial value, either a
3628 value specified by you, or @code{nil}. (In the jargon, this is
3629 binding the variable to the value.) After @code{let} has created
3630 and bound the variables, it executes the code in the body of the
3631 @code{let}, and returns the value of the last expression in the body,
3632 as the value of the whole @code{let} expression. (``Execute'' is a jargon
3633 term that means to evaluate a list; it comes from the use of the word
3634 meaning ``to give practical effect to'' (@cite{Oxford English
3635 Dictionary}). Since you evaluate an expression to perform an action,
3636 ``execute'' has evolved as a synonym to ``evaluate''.)
3638 @node Parts of let Expression
3639 @subsection The Parts of a @code{let} Expression
3640 @cindex @code{let} expression, parts of
3641 @cindex Parts of @code{let} expression
3643 @cindex @samp{varlist} defined
3644 A @code{let} expression is a list of three parts. The first part is
3645 the symbol @code{let}. The second part is a list, called a
3646 @dfn{varlist}, each element of which is either a symbol by itself or a
3647 two-element list, the first element of which is a symbol. The third
3648 part of the @code{let} expression is the body of the @code{let}. The
3649 body usually consists of one or more lists.
3652 A template for a @code{let} expression looks like this:
3655 (let @var{varlist} @var{body}@dots{})
3659 The symbols in the varlist are the variables that are given initial
3660 values by the @code{let} special form. Symbols by themselves are given
3661 the initial value of @code{nil}; and each symbol that is the first
3662 element of a two-element list is bound to the value that is returned
3663 when the Lisp interpreter evaluates the second element.
3665 Thus, a varlist might look like this: @code{(thread (needles 3))}. In
3666 this case, in a @code{let} expression, Emacs binds the symbol
3667 @code{thread} to an initial value of @code{nil}, and binds the symbol
3668 @code{needles} to an initial value of 3.
3670 When you write a @code{let} expression, what you do is put the
3671 appropriate expressions in the slots of the @code{let} expression
3674 If the varlist is composed of two-element lists, as is often the case,
3675 the template for the @code{let} expression looks like this:
3679 (let ((@var{variable} @var{value})
3680 (@var{variable} @var{value})
3686 @node Sample let Expression
3687 @subsection Sample @code{let} Expression
3688 @cindex Sample @code{let} expression
3689 @cindex @code{let} expression sample
3691 The following expression creates and gives initial values
3692 to the two variables @code{zebra} and @code{tiger}. The body of the
3693 @code{let} expression is a list which calls the @code{message} function.
3697 (let ((zebra "stripes")
3699 (message "One kind of animal has %s and another is %s."
3704 Here, the varlist is @code{((zebra "stripes") (tiger "fierce"))}.
3706 The two variables are @code{zebra} and @code{tiger}. Each variable is
3707 the first element of a two-element list and each value is the second
3708 element of its two-element list. In the varlist, Emacs binds the
3709 variable @code{zebra} to the value @code{"stripes"}@footnote{According
3710 to Jared Diamond in @cite{Guns, Germs, and Steel}, ``@dots{} zebras
3711 become impossibly dangerous as they grow older'' but the claim here is
3712 that they do not become fierce like a tiger. (1997, W. W. Norton and
3713 Co., ISBN 0-393-03894-2, page 171)}, and binds the
3714 variable @code{tiger} to the value @code{"fierce"}. In this example,
3715 both values are strings. The values could just as well have been
3716 another list or a symbol. The body of the @code{let}
3717 follows after the list holding the variables. In this example, the
3718 body is a list that uses the @code{message} function to print a string
3722 You may evaluate the example in the usual fashion, by placing the
3723 cursor after the last parenthesis and typing @kbd{C-x C-e}. When you do
3724 this, the following will appear in the echo area:
3727 "One kind of animal has stripes and another is fierce."
3730 As we have seen before, the @code{message} function prints its first
3731 argument, except for @samp{%s}. In this example, the value of the variable
3732 @code{zebra} is printed at the location of the first @samp{%s} and the
3733 value of the variable @code{tiger} is printed at the location of the
3736 @node Uninitialized let Variables
3737 @subsection Uninitialized Variables in a @code{let} Statement
3738 @cindex Uninitialized @code{let} variables
3739 @cindex @code{let} variables uninitialized
3741 If you do not bind the variables in a @code{let} statement to specific
3742 initial values, they will automatically be bound to an initial value of
3743 @code{nil}, as in the following expression:
3752 "Here are %d variables with %s, %s, and %s value."
3753 birch pine fir oak))
3758 Here, the varlist is @code{((birch 3) pine fir (oak 'some))}.
3761 If you evaluate this expression in the usual way, the following will
3762 appear in your echo area:
3765 "Here are 3 variables with nil, nil, and some value."
3769 In this example, Emacs binds the symbol @code{birch} to the number 3,
3770 binds the symbols @code{pine} and @code{fir} to @code{nil}, and binds
3771 the symbol @code{oak} to the value @code{some}.
3773 Note that in the first part of the @code{let}, the variables @code{pine}
3774 and @code{fir} stand alone as atoms that are not surrounded by
3775 parentheses; this is because they are being bound to @code{nil}, the
3776 empty list. But @code{oak} is bound to @code{some} and so is a part of
3777 the list @code{(oak 'some)}. Similarly, @code{birch} is bound to the
3778 number 3 and so is in a list with that number. (Since a number
3779 evaluates to itself, the number does not need to be quoted. Also, the
3780 number is printed in the message using a @samp{%d} rather than a
3781 @samp{%s}.) The four variables as a group are put into a list to
3782 delimit them from the body of the @code{let}.
3785 @section The @code{if} Special Form
3787 @cindex Conditional with @code{if}
3789 A third special form, in addition to @code{defun} and @code{let}, is the
3790 conditional @code{if}. This form is used to instruct the computer to
3791 make decisions. You can write function definitions without using
3792 @code{if}, but it is used often enough, and is important enough, to be
3793 included here. It is used, for example, in the code for the
3794 function @code{beginning-of-buffer}.
3796 The basic idea behind an @code{if}, is that @emph{if} a test is true,
3797 @emph{then} an expression is evaluated. If the test is not true, the
3798 expression is not evaluated. For example, you might make a decision
3799 such as, ``if it is warm and sunny, then go to the beach!''
3802 * if in more detail::
3803 * type-of-animal in detail:: An example of an @code{if} expression.
3807 @node if in more detail
3808 @unnumberedsubsec @code{if} in more detail
3811 @cindex @samp{if-part} defined
3812 @cindex @samp{then-part} defined
3813 An @code{if} expression written in Lisp does not use the word ``then'';
3814 the test and the action are the second and third elements of the list
3815 whose first element is @code{if}. Nonetheless, the test part of an
3816 @code{if} expression is often called the @dfn{if-part} and the second
3817 argument is often called the @dfn{then-part}.
3819 Also, when an @code{if} expression is written, the true-or-false-test
3820 is usually written on the same line as the symbol @code{if}, but the
3821 action to carry out if the test is true, the then-part, is written
3822 on the second and subsequent lines. This makes the @code{if}
3823 expression easier to read.
3827 (if @var{true-or-false-test}
3828 @var{action-to-carry-out-if-test-is-true})
3833 The true-or-false-test will be an expression that
3834 is evaluated by the Lisp interpreter.
3836 Here is an example that you can evaluate in the usual manner. The test
3837 is whether the number 5 is greater than the number 4. Since it is, the
3838 message @samp{5 is greater than 4!} will be printed.
3842 (if (> 5 4) ; @r{if-part}
3843 (message "5 is greater than 4!")) ; @r{then-part}
3848 (The function @code{>} tests whether its first argument is greater than
3849 its second argument and returns true if it is.)
3850 @findex > (greater than)
3852 Of course, in actual use, the test in an @code{if} expression will not
3853 be fixed for all time as it is by the expression @code{(> 5 4)}.
3854 Instead, at least one of the variables used in the test will be bound to
3855 a value that is not known ahead of time. (If the value were known ahead
3856 of time, we would not need to run the test!)
3858 For example, the value may be bound to an argument of a function
3859 definition. In the following function definition, the character of the
3860 animal is a value that is passed to the function. If the value bound to
3861 @code{characteristic} is @code{"fierce"}, then the message, @samp{It is a
3862 tiger!} will be printed; otherwise, @code{nil} will be returned.
3866 (defun type-of-animal (characteristic)
3867 "Print message in echo area depending on CHARACTERISTIC.
3868 If the CHARACTERISTIC is the string \"fierce\",
3869 then warn of a tiger."
3870 (if (equal characteristic "fierce")
3871 (message "It is a tiger!")))
3877 If you are reading this inside of GNU Emacs, you can evaluate the
3878 function definition in the usual way to install it in Emacs, and then you
3879 can evaluate the following two expressions to see the results:
3883 (type-of-animal "fierce")
3885 (type-of-animal "striped")
3890 @c Following sentences rewritten to prevent overfull hbox.
3892 When you evaluate @code{(type-of-animal "fierce")}, you will see the
3893 following message printed in the echo area: @code{"It is a tiger!"}; and
3894 when you evaluate @code{(type-of-animal "striped")} you will see @code{nil}
3895 printed in the echo area.
3897 @node type-of-animal in detail
3898 @subsection The @code{type-of-animal} Function in Detail
3900 Let's look at the @code{type-of-animal} function in detail.
3902 The function definition for @code{type-of-animal} was written by filling
3903 the slots of two templates, one for a function definition as a whole, and
3904 a second for an @code{if} expression.
3907 The template for every function that is not interactive is:
3911 (defun @var{name-of-function} (@var{argument-list})
3912 "@var{documentation}@dots{}"
3918 The parts of the function that match this template look like this:
3922 (defun type-of-animal (characteristic)
3923 "Print message in echo area depending on CHARACTERISTIC.
3924 If the CHARACTERISTIC is the string \"fierce\",
3925 then warn of a tiger."
3926 @var{body: the} @code{if} @var{expression})
3930 The name of function is @code{type-of-animal}; it is passed the value
3931 of one argument. The argument list is followed by a multi-line
3932 documentation string. The documentation string is included in the
3933 example because it is a good habit to write documentation string for
3934 every function definition. The body of the function definition
3935 consists of the @code{if} expression.
3938 The template for an @code{if} expression looks like this:
3942 (if @var{true-or-false-test}
3943 @var{action-to-carry-out-if-the-test-returns-true})
3948 In the @code{type-of-animal} function, the code for the @code{if}
3953 (if (equal characteristic "fierce")
3954 (message "It is a tiger!")))
3959 Here, the true-or-false-test is the expression:
3962 (equal characteristic "fierce")
3966 In Lisp, @code{equal} is a function that determines whether its first
3967 argument is equal to its second argument. The second argument is the
3968 string @code{"fierce"} and the first argument is the value of the
3969 symbol @code{characteristic}---in other words, the argument passed to
3972 In the first exercise of @code{type-of-animal}, the argument
3973 @code{"fierce"} is passed to @code{type-of-animal}. Since @code{"fierce"}
3974 is equal to @code{"fierce"}, the expression, @code{(equal characteristic
3975 "fierce")}, returns a value of true. When this happens, the @code{if}
3976 evaluates the second argument or then-part of the @code{if}:
3977 @code{(message "It is a tiger!")}.
3979 On the other hand, in the second exercise of @code{type-of-animal}, the
3980 argument @code{"striped"} is passed to @code{type-of-animal}. @code{"striped"}
3981 is not equal to @code{"fierce"}, so the then-part is not evaluated and
3982 @code{nil} is returned by the @code{if} expression.
3985 @section If--then--else Expressions
3988 An @code{if} expression may have an optional third argument, called
3989 the @dfn{else-part}, for the case when the true-or-false-test returns
3990 false. When this happens, the second argument or then-part of the
3991 overall @code{if} expression is @emph{not} evaluated, but the third or
3992 else-part @emph{is} evaluated. You might think of this as the cloudy
3993 day alternative for the decision ``if it is warm and sunny, then go to
3994 the beach, else read a book!''.
3996 The word ``else'' is not written in the Lisp code; the else-part of an
3997 @code{if} expression comes after the then-part. In the written Lisp, the
3998 else-part is usually written to start on a line of its own and is
3999 indented less than the then-part:
4003 (if @var{true-or-false-test}
4004 @var{action-to-carry-out-if-the-test-returns-true}
4005 @var{action-to-carry-out-if-the-test-returns-false})
4009 For example, the following @code{if} expression prints the message @samp{4
4010 is not greater than 5!} when you evaluate it in the usual way:
4014 (if (> 4 5) ; @r{if-part}
4015 (message "4 falsely greater than 5!") ; @r{then-part}
4016 (message "4 is not greater than 5!")) ; @r{else-part}
4021 Note that the different levels of indentation make it easy to
4022 distinguish the then-part from the else-part. (GNU Emacs has several
4023 commands that automatically indent @code{if} expressions correctly.
4024 @xref{Typing Lists, , GNU Emacs Helps You Type Lists}.)
4026 We can extend the @code{type-of-animal} function to include an
4027 else-part by simply incorporating an additional part to the @code{if}
4031 You can see the consequences of doing this if you evaluate the following
4032 version of the @code{type-of-animal} function definition to install it
4033 and then evaluate the two subsequent expressions to pass different
4034 arguments to the function.
4038 (defun type-of-animal (characteristic) ; @r{Second version.}
4039 "Print message in echo area depending on CHARACTERISTIC.
4040 If the CHARACTERISTIC is the string \"fierce\",
4041 then warn of a tiger; else say it is not fierce."
4042 (if (equal characteristic "fierce")
4043 (message "It is a tiger!")
4044 (message "It is not fierce!")))
4051 (type-of-animal "fierce")
4053 (type-of-animal "striped")
4058 @c Following sentence rewritten to prevent overfull hbox.
4060 When you evaluate @code{(type-of-animal "fierce")}, you will see the
4061 following message printed in the echo area: @code{"It is a tiger!"}; but
4062 when you evaluate @code{(type-of-animal "striped")}, you will see
4063 @code{"It is not fierce!"}.
4065 (Of course, if the @var{characteristic} were @code{"ferocious"}, the
4066 message @code{"It is not fierce!"} would be printed; and it would be
4067 misleading! When you write code, you need to take into account the
4068 possibility that some such argument will be tested by the @code{if}
4069 and write your program accordingly.)
4071 @node Truth & Falsehood
4072 @section Truth and Falsehood in Emacs Lisp
4073 @cindex Truth and falsehood in Emacs Lisp
4074 @cindex Falsehood and truth in Emacs Lisp
4077 There is an important aspect to the truth test in an @code{if}
4078 expression. So far, we have spoken of ``true'' and ``false'' as values of
4079 predicates as if they were new kinds of Emacs Lisp objects. In fact,
4080 ``false'' is just our old friend @code{nil}. Anything else---anything
4081 at all---is ``true''.
4083 The expression that tests for truth is interpreted as @dfn{true}
4084 if the result of evaluating it is a value that is not @code{nil}. In
4085 other words, the result of the test is considered true if the value
4086 returned is a number such as 47, a string such as @code{"hello"}, or a
4087 symbol (other than @code{nil}) such as @code{flowers}, or a list (so
4088 long as it is not empty), or even a buffer!
4091 * nil explained:: @code{nil} has two meanings.
4096 @unnumberedsubsec An explanation of @code{nil}
4099 Before illustrating a test for truth, we need an explanation of @code{nil}.
4101 In Emacs Lisp, the symbol @code{nil} has two meanings. First, it means the
4102 empty list. Second, it means false and is the value returned when a
4103 true-or-false-test tests false. @code{nil} can be written as an empty
4104 list, @code{()}, or as @code{nil}. As far as the Lisp interpreter is
4105 concerned, @code{()} and @code{nil} are the same. Humans, however, tend
4106 to use @code{nil} for false and @code{()} for the empty list.
4108 In Emacs Lisp, any value that is not @code{nil}---is not the empty
4109 list---is considered true. This means that if an evaluation returns
4110 something that is not an empty list, an @code{if} expression will test
4111 true. For example, if a number is put in the slot for the test, it
4112 will be evaluated and will return itself, since that is what numbers
4113 do when evaluated. In this conditional, the @code{if} expression will
4114 test true. The expression tests false only when @code{nil}, an empty
4115 list, is returned by evaluating the expression.
4117 You can see this by evaluating the two expressions in the following examples.
4119 In the first example, the number 4 is evaluated as the test in the
4120 @code{if} expression and returns itself; consequently, the then-part
4121 of the expression is evaluated and returned: @samp{true} appears in
4122 the echo area. In the second example, the @code{nil} indicates false;
4123 consequently, the else-part of the expression is evaluated and
4124 returned: @samp{false} appears in the echo area.
4141 Incidentally, if some other useful value is not available for a test that
4142 returns true, then the Lisp interpreter will return the symbol @code{t}
4143 for true. For example, the expression @code{(> 5 4)} returns @code{t}
4144 when evaluated, as you can see by evaluating it in the usual way:
4152 On the other hand, this function returns @code{nil} if the test is false.
4158 @node save-excursion
4159 @section @code{save-excursion}
4160 @findex save-excursion
4161 @cindex Region, what it is
4162 @cindex Preserving point and buffer
4163 @cindex Point and buffer preservation
4167 The @code{save-excursion} function is the third and final special form
4168 that we will discuss in this chapter.
4170 In Emacs Lisp programs used for editing, the @code{save-excursion}
4171 function is very common. It saves the location of point,
4172 executes the body of the function, and then restores point to
4173 its previous position if its location was changed. Its primary
4174 purpose is to keep the user from being surprised and disturbed by
4175 unexpected movement of point.
4178 * Point and mark:: A review of various locations.
4179 * Template for save-excursion::
4183 @node Point and mark
4184 @unnumberedsubsec Point and Mark
4187 Before discussing @code{save-excursion}, however, it may be useful
4188 first to review what point and mark are in GNU Emacs. @dfn{Point} is
4189 the current location of the cursor. Wherever the cursor
4190 is, that is point. More precisely, on terminals where the cursor
4191 appears to be on top of a character, point is immediately before the
4192 character. In Emacs Lisp, point is an integer. The first character in
4193 a buffer is number one, the second is number two, and so on. The
4194 function @code{point} returns the current position of the cursor as a
4195 number. Each buffer has its own value for point.
4197 The @dfn{mark} is another position in the buffer; its value can be set
4198 with a command such as @kbd{C-@key{SPC}} (@code{set-mark-command}). If
4199 a mark has been set, you can use the command @kbd{C-x C-x}
4200 (@code{exchange-point-and-mark}) to cause the cursor to jump to the mark
4201 and set the mark to be the previous position of point. In addition, if
4202 you set another mark, the position of the previous mark is saved in the
4203 mark ring. Many mark positions can be saved this way. You can jump the
4204 cursor to a saved mark by typing @kbd{C-u C-@key{SPC}} one or more
4207 The part of the buffer between point and mark is called @dfn{the
4208 region}. Numerous commands work on the region, including
4209 @code{center-region}, @code{count-lines-region}, @code{kill-region}, and
4210 @code{print-region}.
4212 The @code{save-excursion} special form saves the location of point and
4213 restores this position after the code within the body of the
4214 special form is evaluated by the Lisp interpreter. Thus, if point were
4215 in the beginning of a piece of text and some code moved point to the end
4216 of the buffer, the @code{save-excursion} would put point back to where
4217 it was before, after the expressions in the body of the function were
4220 In Emacs, a function frequently moves point as part of its internal
4221 workings even though a user would not expect this. For example,
4222 @code{count-lines-region} moves point. To prevent the user from being
4223 bothered by jumps that are both unexpected and (from the user's point of
4224 view) unnecessary, @code{save-excursion} is often used to keep point in
4225 the location expected by the user. The use of
4226 @code{save-excursion} is good housekeeping.
4228 To make sure the house stays clean, @code{save-excursion} restores the
4229 value of point even if something goes wrong in the code inside
4230 of it (or, to be more precise and to use the proper jargon, ``in case of
4231 abnormal exit''). This feature is very helpful.
4233 In addition to recording the value of point,
4234 @code{save-excursion} keeps track of the current buffer, and restores
4235 it, too. This means you can write code that will change the buffer and
4236 have @code{save-excursion} switch you back to the original buffer.
4237 This is how @code{save-excursion} is used in @code{append-to-buffer}.
4238 (@xref{append-to-buffer, , The Definition of @code{append-to-buffer}}.)
4240 @node Template for save-excursion
4241 @subsection Template for a @code{save-excursion} Expression
4244 The template for code using @code{save-excursion} is simple:
4254 The body of the function is one or more expressions that will be
4255 evaluated in sequence by the Lisp interpreter. If there is more than
4256 one expression in the body, the value of the last one will be returned
4257 as the value of the @code{save-excursion} function. The other
4258 expressions in the body are evaluated only for their side effects; and
4259 @code{save-excursion} itself is used only for its side effect (which
4260 is restoring the position of point).
4263 In more detail, the template for a @code{save-excursion} expression
4269 @var{first-expression-in-body}
4270 @var{second-expression-in-body}
4271 @var{third-expression-in-body}
4273 @var{last-expression-in-body})
4278 An expression, of course, may be a symbol on its own or a list.
4280 In Emacs Lisp code, a @code{save-excursion} expression often occurs
4281 within the body of a @code{let} expression. It looks like this:
4294 In the last few chapters we have introduced a macro and a fair number
4295 of functions and special forms. Here they are described in brief,
4296 along with a few similar functions that have not been mentioned yet.
4299 @item eval-last-sexp
4300 Evaluate the last symbolic expression before the current location of
4301 point. The value is printed in the echo area unless the function is
4302 invoked with an argument; in that case, the output is printed in the
4303 current buffer. This command is normally bound to @kbd{C-x C-e}.
4306 Define function. This macro has up to five parts: the name, a
4307 template for the arguments that will be passed to the function,
4308 documentation, an optional interactive declaration, and the body of
4312 For example, in Emacs the function definition of
4313 @code{dired-unmark-all-marks} is as follows.
4317 (defun dired-unmark-all-marks ()
4318 "Remove all marks from all files in the Dired buffer."
4320 (dired-unmark-all-files ?\r))
4325 Declare to the interpreter that the function can be used
4326 interactively. This special form may be followed by a string with one
4327 or more parts that pass the information to the arguments of the
4328 function, in sequence. These parts may also tell the interpreter to
4329 prompt for information. Parts of the string are separated by
4330 newlines, @samp{\n}.
4333 Common code characters are:
4337 The name of an existing buffer.
4340 The name of an existing file.
4343 The numeric prefix argument. (Note that this @code{p} is lower case.)
4346 Point and the mark, as two numeric arguments, smallest first. This
4347 is the only code letter that specifies two successive arguments
4351 @xref{Interactive Codes, , Code Characters for @samp{interactive},
4352 elisp, The GNU Emacs Lisp Reference Manual}, for a complete list of
4356 Declare that a list of variables is for use within the body of the
4357 @code{let} and give them an initial value, either @code{nil} or a
4358 specified value; then evaluate the rest of the expressions in the body
4359 of the @code{let} and return the value of the last one. Inside the
4360 body of the @code{let}, the Lisp interpreter does not see the values of
4361 the variables of the same names that are bound outside of the
4369 (let ((foo (buffer-name))
4370 (bar (buffer-size)))
4372 "This buffer is %s and has %d characters."
4377 @item save-excursion
4378 Record the values of point and the current buffer before
4379 evaluating the body of this special form. Restore the value of point and
4387 (message "We are %d characters into this buffer."
4390 (goto-char (point-min)) (point))))
4395 Evaluate the first argument to the function; if it is true, evaluate
4396 the second argument; else evaluate the third argument, if there is one.
4398 The @code{if} special form is called a @dfn{conditional}. There are
4399 other conditionals in Emacs Lisp, but @code{if} is perhaps the most
4407 (if (= 22 emacs-major-version)
4408 (message "This is version 22 Emacs")
4409 (message "This is not version 22 Emacs"))
4418 The @code{<} function tests whether its first argument is smaller than
4419 its second argument. A corresponding function, @code{>}, tests whether
4420 the first argument is greater than the second. Likewise, @code{<=}
4421 tests whether the first argument is less than or equal to the second and
4422 @code{>=} tests whether the first argument is greater than or equal to
4423 the second. In all cases, both arguments must be numbers or markers
4424 (markers indicate positions in buffers).
4428 The @code{=} function tests whether two arguments, both numbers or
4434 Test whether two objects are the same. @code{equal} uses one meaning
4435 of the word ``same'' and @code{eq} uses another: @code{equal} returns
4436 true if the two objects have a similar structure and contents, such as
4437 two copies of the same book. On the other hand, @code{eq}, returns
4438 true if both arguments are actually the same object.
4447 The @code{string-lessp} function tests whether its first argument is
4448 smaller than the second argument. A shorter, alternative name for the
4449 same function (a @code{defalias}) is @code{string<}.
4451 The arguments to @code{string-lessp} must be strings or symbols; the
4452 ordering is lexicographic, so case is significant. The print names of
4453 symbols are used instead of the symbols themselves.
4455 @cindex @samp{empty string} defined
4456 An empty string, @samp{""}, a string with no characters in it, is
4457 smaller than any string of characters.
4459 @code{string-equal} provides the corresponding test for equality. Its
4460 shorter, alternative name is @code{string=}. There are no string test
4461 functions that correspond to @var{>}, @code{>=}, or @code{<=}.
4464 Print a message in the echo area. The first argument is a string that
4465 can contain @samp{%s}, @samp{%d}, or @samp{%c} to print the value of
4466 arguments that follow the string. The argument used by @samp{%s} must
4467 be a string or a symbol; the argument used by @samp{%d} must be a
4468 number. The argument used by @samp{%c} must be an @sc{ascii} code
4469 number; it will be printed as the character with that @sc{ascii} code.
4470 (Various other %-sequences have not been mentioned.)
4474 The @code{setq} function sets the value of its first argument to the
4475 value of the second argument. The first argument is automatically
4476 quoted by @code{setq}. It does the same for succeeding pairs of
4477 arguments. Another function, @code{set}, takes only two arguments and
4478 evaluates both of them before setting the value returned by its first
4479 argument to the value returned by its second argument.
4482 Without an argument, return the name of the buffer, as a string.
4484 @item buffer-file-name
4485 Without an argument, return the name of the file the buffer is
4488 @item current-buffer
4489 Return the buffer in which Emacs is active; it may not be
4490 the buffer that is visible on the screen.
4493 Return the most recently selected buffer (other than the buffer passed
4494 to @code{other-buffer} as an argument and other than the current
4497 @item switch-to-buffer
4498 Select a buffer for Emacs to be active in and display it in the current
4499 window so users can look at it. Usually bound to @kbd{C-x b}.
4502 Switch Emacs's attention to a buffer on which programs will run. Don't
4503 alter what the window is showing.
4506 Return the number of characters in the current buffer.
4509 Return the value of the current position of the cursor, as an
4510 integer counting the number of characters from the beginning of the
4514 Return the minimum permissible value of point in
4515 the current buffer. This is 1, unless narrowing is in effect.
4518 Return the value of the maximum permissible value of point in the
4519 current buffer. This is the end of the buffer, unless narrowing is in
4524 @node defun Exercises
4529 Write a non-interactive function that doubles the value of its
4530 argument, a number. Make that function interactive.
4533 Write a function that tests whether the current value of
4534 @code{fill-column} is greater than the argument passed to the function,
4535 and if so, prints an appropriate message.
4538 @node Buffer Walk Through
4539 @chapter A Few Buffer-Related Functions
4541 In this chapter we study in detail several of the functions used in GNU
4542 Emacs. This is called a ``walk-through''. These functions are used as
4543 examples of Lisp code, but are not imaginary examples; with the
4544 exception of the first, simplified function definition, these functions
4545 show the actual code used in GNU Emacs. You can learn a great deal from
4546 these definitions. The functions described here are all related to
4547 buffers. Later, we will study other functions.
4550 * Finding More:: How to find more information.
4551 * simplified-beginning-of-buffer:: Shows @code{goto-char},
4552 @code{point-min}, and @code{push-mark}.
4553 * mark-whole-buffer:: Almost the same as @code{beginning-of-buffer}.
4554 * append-to-buffer:: Uses @code{save-excursion} and
4555 @code{insert-buffer-substring}.
4556 * Buffer Related Review:: Review.
4557 * Buffer Exercises::
4561 @section Finding More Information
4563 @findex describe-function, @r{introduced}
4564 @cindex Find function documentation
4565 In this walk-through, I will describe each new function as we come to
4566 it, sometimes in detail and sometimes briefly. If you are interested,
4567 you can get the full documentation of any Emacs Lisp function at any
4568 time by typing @kbd{C-h f} and then the name of the function (and then
4569 @key{RET}). Similarly, you can get the full documentation for a
4570 variable by typing @kbd{C-h v} and then the name of the variable (and
4573 @cindex Find source of function
4574 @c In version 22, tells location both of C and of Emacs Lisp
4575 Also, @code{describe-function} will tell you the location of the
4576 function definition.
4578 Put point into the name of the file that contains the function and
4579 press the @key{RET} key. In this case, @key{RET} means
4580 @code{push-button} rather than ``return'' or ``enter''. Emacs will take
4581 you directly to the function definition.
4586 If you move point over the file name and press
4587 the @key{RET} key, which in this case means @code{help-follow} rather
4588 than ``return'' or ``enter'', Emacs will take you directly to the function
4592 More generally, if you want to see a function in its original source
4593 file, you can use the @code{find-tag} function to jump to it.
4594 @code{find-tag} works with a wide variety of languages, not just
4595 Lisp, and C, and it works with non-programming text as well. For
4596 example, @code{find-tag} will jump to the various nodes in the
4597 Texinfo source file of this document.
4598 The @code{find-tag} function depends on @dfn{tags tables} that record
4599 the locations of the functions, variables, and other items to which
4600 @code{find-tag} jumps.
4602 To use the @code{find-tag} command, type @kbd{M-.} (i.e., press the
4603 period key while holding down the @key{META} key, or else type the
4604 @key{ESC} key and then type the period key), and then, at the prompt,
4605 type in the name of the function whose source code you want to see,
4606 such as @code{mark-whole-buffer}, and then type @key{RET}. Emacs will
4607 switch buffers and display the source code for the function on your
4608 screen. To switch back to your current buffer, type @kbd{C-x b
4609 @key{RET}}. (On some keyboards, the @key{META} key is labeled
4612 @c !!! 22.1.1 tags table location in this paragraph
4613 @cindex TAGS table, specifying
4615 Depending on how the initial default values of your copy of Emacs are
4616 set, you may also need to specify the location of your tags table,
4617 which is a file called @file{TAGS}. For example, if you are
4618 interested in Emacs sources, the tags table you will most likely want,
4619 if it has already been created for you, will be in a subdirectory of
4620 the @file{/usr/local/share/emacs/} directory; thus you would use the
4621 @code{M-x visit-tags-table} command and specify a pathname such as
4622 @file{/usr/local/share/emacs/22.1.1/lisp/TAGS}. If the tags table
4623 has not already been created, you will have to create it yourself. It
4624 will be in a file such as @file{/usr/local/src/emacs/src/TAGS}.
4627 To create a @file{TAGS} file in a specific directory, switch to that
4628 directory in Emacs using @kbd{M-x cd} command, or list the directory
4629 with @kbd{C-x d} (@code{dired}). Then run the compile command, with
4630 @w{@code{etags *.el}} as the command to execute:
4633 M-x compile RET etags *.el RET
4636 For more information, see @ref{etags, , Create Your Own @file{TAGS} File}.
4638 After you become more familiar with Emacs Lisp, you will find that you will
4639 frequently use @code{find-tag} to navigate your way around source code;
4640 and you will create your own @file{TAGS} tables.
4642 @cindex Library, as term for ``file''
4643 Incidentally, the files that contain Lisp code are conventionally
4644 called @dfn{libraries}. The metaphor is derived from that of a
4645 specialized library, such as a law library or an engineering library,
4646 rather than a general library. Each library, or file, contains
4647 functions that relate to a particular topic or activity, such as
4648 @file{abbrev.el} for handling abbreviations and other typing
4649 shortcuts, and @file{help.el} for help. (Sometimes several
4650 libraries provide code for a single activity, as the various
4651 @file{rmail@dots{}} files provide code for reading electronic mail.)
4652 In @cite{The GNU Emacs Manual}, you will see sentences such as ``The
4653 @kbd{C-h p} command lets you search the standard Emacs Lisp libraries
4654 by topic keywords.''
4656 @node simplified-beginning-of-buffer
4657 @section A Simplified @code{beginning-of-buffer} Definition
4658 @findex simplified-beginning-of-buffer
4660 The @code{beginning-of-buffer} command is a good function to start with
4661 since you are likely to be familiar with it and it is easy to
4662 understand. Used as an interactive command, @code{beginning-of-buffer}
4663 moves the cursor to the beginning of the buffer, leaving the mark at the
4664 previous position. It is generally bound to @kbd{M-<}.
4666 In this section, we will discuss a shortened version of the function
4667 that shows how it is most frequently used. This shortened function
4668 works as written, but it does not contain the code for a complex option.
4669 In another section, we will describe the entire function.
4670 (@xref{beginning-of-buffer, , Complete Definition of
4671 @code{beginning-of-buffer}}.)
4673 Before looking at the code, let's consider what the function
4674 definition has to contain: it must include an expression that makes
4675 the function interactive so it can be called by typing @kbd{M-x
4676 beginning-of-buffer} or by typing a keychord such as @kbd{M-<}; it
4677 must include code to leave a mark at the original position in the
4678 buffer; and it must include code to move the cursor to the beginning
4682 Here is the complete text of the shortened version of the function:
4686 (defun simplified-beginning-of-buffer ()
4687 "Move point to the beginning of the buffer;
4688 leave mark at previous position."
4691 (goto-char (point-min)))
4695 Like all function definitions, this definition has five parts following
4696 the macro @code{defun}:
4700 The name: in this example, @code{simplified-beginning-of-buffer}.
4703 A list of the arguments: in this example, an empty list, @code{()},
4706 The documentation string.
4709 The interactive expression.
4716 In this function definition, the argument list is empty; this means that
4717 this function does not require any arguments. (When we look at the
4718 definition for the complete function, we will see that it may be passed
4719 an optional argument.)
4721 The interactive expression tells Emacs that the function is intended to
4722 be used interactively. In this example, @code{interactive} does not have
4723 an argument because @code{simplified-beginning-of-buffer} does not
4727 The body of the function consists of the two lines:
4732 (goto-char (point-min))
4736 The first of these lines is the expression, @code{(push-mark)}. When
4737 this expression is evaluated by the Lisp interpreter, it sets a mark at
4738 the current position of the cursor, wherever that may be. The position
4739 of this mark is saved in the mark ring.
4741 The next line is @code{(goto-char (point-min))}. This expression
4742 jumps the cursor to the minimum point in the buffer, that is, to the
4743 beginning of the buffer (or to the beginning of the accessible portion
4744 of the buffer if it is narrowed. @xref{Narrowing & Widening, ,
4745 Narrowing and Widening}.)
4747 The @code{push-mark} command sets a mark at the place where the cursor
4748 was located before it was moved to the beginning of the buffer by the
4749 @code{(goto-char (point-min))} expression. Consequently, you can, if
4750 you wish, go back to where you were originally by typing @kbd{C-x C-x}.
4752 That is all there is to the function definition!
4754 @findex describe-function
4755 When you are reading code such as this and come upon an unfamiliar
4756 function, such as @code{goto-char}, you can find out what it does by
4757 using the @code{describe-function} command. To use this command, type
4758 @kbd{C-h f} and then type in the name of the function and press
4759 @key{RET}. The @code{describe-function} command will print the
4760 function's documentation string in a @file{*Help*} window. For
4761 example, the documentation for @code{goto-char} is:
4765 Set point to POSITION, a number or marker.
4766 Beginning of buffer is position (point-min), end is (point-max).
4771 The function's one argument is the desired position.
4774 (The prompt for @code{describe-function} will offer you the symbol
4775 under or preceding the cursor, so you can save typing by positioning
4776 the cursor right over or after the function and then typing @kbd{C-h f
4779 The @code{end-of-buffer} function definition is written in the same way as
4780 the @code{beginning-of-buffer} definition except that the body of the
4781 function contains the expression @code{(goto-char (point-max))} in place
4782 of @code{(goto-char (point-min))}.
4784 @node mark-whole-buffer
4785 @section The Definition of @code{mark-whole-buffer}
4786 @findex mark-whole-buffer
4788 The @code{mark-whole-buffer} function is no harder to understand than the
4789 @code{simplified-beginning-of-buffer} function. In this case, however,
4790 we will look at the complete function, not a shortened version.
4792 The @code{mark-whole-buffer} function is not as commonly used as the
4793 @code{beginning-of-buffer} function, but is useful nonetheless: it
4794 marks a whole buffer as a region by putting point at the beginning and
4795 a mark at the end of the buffer. It is generally bound to @kbd{C-x
4799 * mark-whole-buffer overview::
4800 * Body of mark-whole-buffer:: Only three lines of code.
4804 @node mark-whole-buffer overview
4805 @unnumberedsubsec An overview of @code{mark-whole-buffer}
4809 In GNU Emacs 22, the code for the complete function looks like this:
4813 (defun mark-whole-buffer ()
4814 "Put point at beginning and mark at end of buffer.
4815 You probably should not use this function in Lisp programs;
4816 it is usually a mistake for a Lisp function to use any subroutine
4817 that uses or sets the mark."
4820 (push-mark (point-max) nil t)
4821 (goto-char (point-min)))
4826 Like all other functions, the @code{mark-whole-buffer} function fits
4827 into the template for a function definition. The template looks like
4832 (defun @var{name-of-function} (@var{argument-list})
4833 "@var{documentation}@dots{}"
4834 (@var{interactive-expression}@dots{})
4839 Here is how the function works: the name of the function is
4840 @code{mark-whole-buffer}; it is followed by an empty argument list,
4841 @samp{()}, which means that the function does not require arguments.
4842 The documentation comes next.
4844 The next line is an @code{(interactive)} expression that tells Emacs
4845 that the function will be used interactively. These details are similar
4846 to the @code{simplified-beginning-of-buffer} function described in the
4850 @node Body of mark-whole-buffer
4851 @subsection Body of @code{mark-whole-buffer}
4853 The body of the @code{mark-whole-buffer} function consists of three
4860 (push-mark (point-max) nil t)
4861 (goto-char (point-min))
4865 The first of these lines is the expression, @code{(push-mark (point))}.
4867 This line does exactly the same job as the first line of the body of
4868 the @code{simplified-beginning-of-buffer} function, which is written
4869 @code{(push-mark)}. In both cases, the Lisp interpreter sets a mark
4870 at the current position of the cursor.
4872 I don't know why the expression in @code{mark-whole-buffer} is written
4873 @code{(push-mark (point))} and the expression in
4874 @code{beginning-of-buffer} is written @code{(push-mark)}. Perhaps
4875 whoever wrote the code did not know that the arguments for
4876 @code{push-mark} are optional and that if @code{push-mark} is not
4877 passed an argument, the function automatically sets mark at the
4878 location of point by default. Or perhaps the expression was written
4879 so as to parallel the structure of the next line. In any case, the
4880 line causes Emacs to determine the position of point and set a mark
4883 In earlier versions of GNU Emacs, the next line of
4884 @code{mark-whole-buffer} was @code{(push-mark (point-max))}. This
4885 expression sets a mark at the point in the buffer that has the highest
4886 number. This will be the end of the buffer (or, if the buffer is
4887 narrowed, the end of the accessible portion of the buffer.
4888 @xref{Narrowing & Widening, , Narrowing and Widening}, for more about
4889 narrowing.) After this mark has been set, the previous mark, the one
4890 set at point, is no longer set, but Emacs remembers its position, just
4891 as all other recent marks are always remembered. This means that you
4892 can, if you wish, go back to that position by typing @kbd{C-u
4896 In GNU Emacs 22, the @code{(point-max)} is slightly more complicated.
4900 (push-mark (point-max) nil t)
4904 The expression works nearly the same as before. It sets a mark at the
4905 highest numbered place in the buffer that it can. However, in this
4906 version, @code{push-mark} has two additional arguments. The second
4907 argument to @code{push-mark} is @code{nil}. This tells the function
4908 it @emph{should} display a message that says ``Mark set'' when it pushes
4909 the mark. The third argument is @code{t}. This tells
4910 @code{push-mark} to activate the mark when Transient Mark mode is
4911 turned on. Transient Mark mode highlights the currently active
4912 region. It is often turned off.
4914 Finally, the last line of the function is @code{(goto-char
4915 (point-min)))}. This is written exactly the same way as it is written
4916 in @code{beginning-of-buffer}. The expression moves the cursor to
4917 the minimum point in the buffer, that is, to the beginning of the buffer
4918 (or to the beginning of the accessible portion of the buffer). As a
4919 result of this, point is placed at the beginning of the buffer and mark
4920 is set at the end of the buffer. The whole buffer is, therefore, the
4923 @c FIXME: the definition of append-to-buffer has been changed (in
4925 @node append-to-buffer
4926 @section The Definition of @code{append-to-buffer}
4927 @findex append-to-buffer
4929 The @code{append-to-buffer} command is more complex than the
4930 @code{mark-whole-buffer} command. What it does is copy the region
4931 (that is, the part of the buffer between point and mark) from the
4932 current buffer to a specified buffer.
4935 * append-to-buffer overview::
4936 * append interactive:: A two part interactive expression.
4937 * append-to-buffer body:: Incorporates a @code{let} expression.
4938 * append save-excursion:: How the @code{save-excursion} works.
4942 @node append-to-buffer overview
4943 @unnumberedsubsec An Overview of @code{append-to-buffer}
4946 @findex insert-buffer-substring
4947 The @code{append-to-buffer} command uses the
4948 @code{insert-buffer-substring} function to copy the region.
4949 @code{insert-buffer-substring} is described by its name: it takes a
4950 substring from a buffer, and inserts it into another buffer.
4952 Most of @code{append-to-buffer} is
4953 concerned with setting up the conditions for
4954 @code{insert-buffer-substring} to work: the code must specify both the
4955 buffer to which the text will go, the window it comes from and goes
4956 to, and the region that will be copied.
4959 Here is the complete text of the function:
4963 (defun append-to-buffer (buffer start end)
4964 "Append to specified buffer the text of the region.
4965 It is inserted into that buffer before its point.
4969 When calling from a program, give three arguments:
4970 BUFFER (or buffer name), START and END.
4971 START and END specify the portion of the current buffer to be copied."
4973 (list (read-buffer "Append to buffer: " (other-buffer
4974 (current-buffer) t))
4975 (region-beginning) (region-end)))
4978 (let ((oldbuf (current-buffer)))
4980 (let* ((append-to (get-buffer-create buffer))
4981 (windows (get-buffer-window-list append-to t t))
4983 (set-buffer append-to)
4984 (setq point (point))
4985 (barf-if-buffer-read-only)
4986 (insert-buffer-substring oldbuf start end)
4987 (dolist (window windows)
4988 (when (= (window-point window) point)
4989 (set-window-point window (point))))))))
4993 The function can be understood by looking at it as a series of
4994 filled-in templates.
4996 The outermost template is for the function definition. In this
4997 function, it looks like this (with several slots filled in):
5001 (defun append-to-buffer (buffer start end)
5002 "@var{documentation}@dots{}"
5003 (interactive @dots{})
5008 The first line of the function includes its name and three arguments.
5009 The arguments are the @code{buffer} to which the text will be copied, and
5010 the @code{start} and @code{end} of the region in the current buffer that
5013 The next part of the function is the documentation, which is clear and
5014 complete. As is conventional, the three arguments are written in
5015 upper case so you will notice them easily. Even better, they are
5016 described in the same order as in the argument list.
5018 Note that the documentation distinguishes between a buffer and its
5019 name. (The function can handle either.)
5021 @node append interactive
5022 @subsection The @code{append-to-buffer} Interactive Expression
5024 Since the @code{append-to-buffer} function will be used interactively,
5025 the function must have an @code{interactive} expression. (For a
5026 review of @code{interactive}, see @ref{Interactive, , Making a
5027 Function Interactive}.) The expression reads as follows:
5033 "Append to buffer: "
5034 (other-buffer (current-buffer) t))
5041 This expression is not one with letters standing for parts, as
5042 described earlier. Instead, it starts a list with these parts:
5044 The first part of the list is an expression to read the name of a
5045 buffer and return it as a string. That is @code{read-buffer}. The
5046 function requires a prompt as its first argument, @samp{"Append to
5047 buffer: "}. Its second argument tells the command what value to
5048 provide if you don't specify anything.
5050 In this case that second argument is an expression containing the
5051 function @code{other-buffer}, an exception, and a @samp{t}, standing
5054 The first argument to @code{other-buffer}, the exception, is yet
5055 another function, @code{current-buffer}. That is not going to be
5056 returned. The second argument is the symbol for true, @code{t}. that
5057 tells @code{other-buffer} that it may show visible buffers (except in
5058 this case, it will not show the current buffer, which makes sense).
5061 The expression looks like this:
5064 (other-buffer (current-buffer) t)
5067 The second and third arguments to the @code{list} expression are
5068 @code{(region-beginning)} and @code{(region-end)}. These two
5069 functions specify the beginning and end of the text to be appended.
5072 Originally, the command used the letters @samp{B} and @samp{r}.
5073 The whole @code{interactive} expression looked like this:
5076 (interactive "BAppend to buffer:@: \nr")
5080 But when that was done, the default value of the buffer switched to
5081 was invisible. That was not wanted.
5083 (The prompt was separated from the second argument with a newline,
5084 @samp{\n}. It was followed by an @samp{r} that told Emacs to bind the
5085 two arguments that follow the symbol @code{buffer} in the function's
5086 argument list (that is, @code{start} and @code{end}) to the values of
5087 point and mark. That argument worked fine.)
5089 @node append-to-buffer body
5090 @subsection The Body of @code{append-to-buffer}
5093 in GNU Emacs 22 in /usr/local/src/emacs/lisp/simple.el
5095 (defun append-to-buffer (buffer start end)
5096 "Append to specified buffer the text of the region.
5097 It is inserted into that buffer before its point.
5099 When calling from a program, give three arguments:
5100 BUFFER (or buffer name), START and END.
5101 START and END specify the portion of the current buffer to be copied."
5103 (list (read-buffer "Append to buffer: " (other-buffer (current-buffer) t))
5104 (region-beginning) (region-end)))
5105 (let ((oldbuf (current-buffer)))
5107 (let* ((append-to (get-buffer-create buffer))
5108 (windows (get-buffer-window-list append-to t t))
5110 (set-buffer append-to)
5111 (setq point (point))
5112 (barf-if-buffer-read-only)
5113 (insert-buffer-substring oldbuf start end)
5114 (dolist (window windows)
5115 (when (= (window-point window) point)
5116 (set-window-point window (point))))))))
5119 The body of the @code{append-to-buffer} function begins with @code{let}.
5121 As we have seen before (@pxref{let, , @code{let}}), the purpose of a
5122 @code{let} expression is to create and give initial values to one or
5123 more variables that will only be used within the body of the
5124 @code{let}. This means that such a variable will not be confused with
5125 any variable of the same name outside the @code{let} expression.
5127 We can see how the @code{let} expression fits into the function as a
5128 whole by showing a template for @code{append-to-buffer} with the
5129 @code{let} expression in outline:
5133 (defun append-to-buffer (buffer start end)
5134 "@var{documentation}@dots{}"
5135 (interactive @dots{})
5136 (let ((@var{variable} @var{value}))
5141 The @code{let} expression has three elements:
5145 The symbol @code{let};
5148 A varlist containing, in this case, a single two-element list,
5149 @code{(@var{variable} @var{value})};
5152 The body of the @code{let} expression.
5156 In the @code{append-to-buffer} function, the varlist looks like this:
5159 (oldbuf (current-buffer))
5163 In this part of the @code{let} expression, the one variable,
5164 @code{oldbuf}, is bound to the value returned by the
5165 @code{(current-buffer)} expression. The variable, @code{oldbuf}, is
5166 used to keep track of the buffer in which you are working and from
5167 which you will copy.
5169 The element or elements of a varlist are surrounded by a set of
5170 parentheses so the Lisp interpreter can distinguish the varlist from
5171 the body of the @code{let}. As a consequence, the two-element list
5172 within the varlist is surrounded by a circumscribing set of parentheses.
5173 The line looks like this:
5177 (let ((oldbuf (current-buffer)))
5183 The two parentheses before @code{oldbuf} might surprise you if you did
5184 not realize that the first parenthesis before @code{oldbuf} marks the
5185 boundary of the varlist and the second parenthesis marks the beginning
5186 of the two-element list, @code{(oldbuf (current-buffer))}.
5188 @node append save-excursion
5189 @subsection @code{save-excursion} in @code{append-to-buffer}
5191 The body of the @code{let} expression in @code{append-to-buffer}
5192 consists of a @code{save-excursion} expression.
5194 The @code{save-excursion} function saves the location of point, and restores it
5195 to that position after the expressions in the
5196 body of the @code{save-excursion} complete execution. In addition,
5197 @code{save-excursion} keeps track of the original buffer, and
5198 restores it. This is how @code{save-excursion} is used in
5199 @code{append-to-buffer}.
5202 @cindex Indentation for formatting
5203 @cindex Formatting convention
5204 Incidentally, it is worth noting here that a Lisp function is normally
5205 formatted so that everything that is enclosed in a multi-line spread is
5206 indented more to the right than the first symbol. In this function
5207 definition, the @code{let} is indented more than the @code{defun}, and
5208 the @code{save-excursion} is indented more than the @code{let}, like
5224 This formatting convention makes it easy to see that the lines in
5225 the body of the @code{save-excursion} are enclosed by the parentheses
5226 associated with @code{save-excursion}, just as the
5227 @code{save-excursion} itself is enclosed by the parentheses associated
5228 with the @code{let}:
5232 (let ((oldbuf (current-buffer)))
5235 (set-buffer @dots{})
5236 (insert-buffer-substring oldbuf start end)
5242 The use of the @code{save-excursion} function can be viewed as a process
5243 of filling in the slots of a template:
5248 @var{first-expression-in-body}
5249 @var{second-expression-in-body}
5251 @var{last-expression-in-body})
5257 In this function, the body of the @code{save-excursion} contains only
5258 one expression, the @code{let*} expression. You know about a
5259 @code{let} function. The @code{let*} function is different. It has a
5260 @samp{*} in its name. It enables Emacs to set each variable in its
5261 varlist in sequence, one after another.
5263 Its critical feature is that variables later in the varlist can make
5264 use of the values to which Emacs set variables earlier in the varlist.
5265 @xref{fwd-para let, , The @code{let*} expression}.
5267 We will skip functions like @code{let*} and focus on two: the
5268 @code{set-buffer} function and the @code{insert-buffer-substring}
5272 In the old days, the @code{set-buffer} expression was simply
5275 (set-buffer (get-buffer-create buffer))
5283 (set-buffer append-to)
5287 @code{append-to} is bound to @code{(get-buffer-create buffer)} earlier
5288 on in the @code{let*} expression. That extra binding would not be
5289 necessary except for that @code{append-to} is used later in the
5290 varlist as an argument to @code{get-buffer-window-list}.
5295 (let ((oldbuf (current-buffer)))
5297 (let* ((append-to (get-buffer-create buffer))
5298 (windows (get-buffer-window-list append-to t t))
5300 (set-buffer append-to)
5301 (setq point (point))
5302 (barf-if-buffer-read-only)
5303 (insert-buffer-substring oldbuf start end)
5304 (dolist (window windows)
5305 (when (= (window-point window) point)
5306 (set-window-point window (point))))))))
5309 The @code{append-to-buffer} function definition inserts text from the
5310 buffer in which you are currently to a named buffer. It happens that
5311 @code{insert-buffer-substring} copies text from another buffer to the
5312 current buffer, just the reverse---that is why the
5313 @code{append-to-buffer} definition starts out with a @code{let} that
5314 binds the local symbol @code{oldbuf} to the value returned by
5315 @code{current-buffer}.
5318 The @code{insert-buffer-substring} expression looks like this:
5321 (insert-buffer-substring oldbuf start end)
5325 The @code{insert-buffer-substring} function copies a string
5326 @emph{from} the buffer specified as its first argument and inserts the
5327 string into the present buffer. In this case, the argument to
5328 @code{insert-buffer-substring} is the value of the variable created
5329 and bound by the @code{let}, namely the value of @code{oldbuf}, which
5330 was the current buffer when you gave the @code{append-to-buffer}
5333 After @code{insert-buffer-substring} has done its work,
5334 @code{save-excursion} will restore the action to the original buffer
5335 and @code{append-to-buffer} will have done its job.
5338 Written in skeletal form, the workings of the body look like this:
5342 (let (@var{bind-}@code{oldbuf}@var{-to-value-of-}@code{current-buffer})
5343 (save-excursion ; @r{Keep track of buffer.}
5345 @var{insert-substring-from-}@code{oldbuf}@var{-into-buffer})
5347 @var{change-back-to-original-buffer-when-finished}
5348 @var{let-the-local-meaning-of-}@code{oldbuf}@var{-disappear-when-finished}
5352 In summary, @code{append-to-buffer} works as follows: it saves the
5353 value of the current buffer in the variable called @code{oldbuf}. It
5354 gets the new buffer (creating one if need be) and switches Emacs's
5355 attention to it. Using the value of @code{oldbuf}, it inserts the
5356 region of text from the old buffer into the new buffer; and then using
5357 @code{save-excursion}, it brings you back to your original buffer.
5359 In looking at @code{append-to-buffer}, you have explored a fairly
5360 complex function. It shows how to use @code{let} and
5361 @code{save-excursion}, and how to change to and come back from another
5362 buffer. Many function definitions use @code{let},
5363 @code{save-excursion}, and @code{set-buffer} this way.
5365 @node Buffer Related Review
5368 Here is a brief summary of the various functions discussed in this chapter.
5371 @item describe-function
5372 @itemx describe-variable
5373 Print the documentation for a function or variable.
5374 Conventionally bound to @kbd{C-h f} and @kbd{C-h v}.
5377 Find the file containing the source for a function or variable and
5378 switch buffers to it, positioning point at the beginning of the item.
5379 Conventionally bound to @kbd{M-.} (that's a period following the
5382 @item save-excursion
5383 Save the location of point and restore its value after the
5384 arguments to @code{save-excursion} have been evaluated. Also, remember
5385 the current buffer and return to it.
5388 Set mark at a location and record the value of the previous mark on the
5389 mark ring. The mark is a location in the buffer that will keep its
5390 relative position even if text is added to or removed from the buffer.
5393 Set point to the location specified by the value of the argument, which
5394 can be a number, a marker, or an expression that returns the number of
5395 a position, such as @code{(point-min)}.
5397 @item insert-buffer-substring
5398 Copy a region of text from a buffer that is passed to the function as
5399 an argument and insert the region into the current buffer.
5401 @item mark-whole-buffer
5402 Mark the whole buffer as a region. Normally bound to @kbd{C-x h}.
5405 Switch the attention of Emacs to another buffer, but do not change the
5406 window being displayed. Used when the program rather than a human is
5407 to work on a different buffer.
5409 @item get-buffer-create
5411 Find a named buffer or create one if a buffer of that name does not
5412 exist. The @code{get-buffer} function returns @code{nil} if the named
5413 buffer does not exist.
5417 @node Buffer Exercises
5422 Write your own @code{simplified-end-of-buffer} function definition;
5423 then test it to see whether it works.
5426 Use @code{if} and @code{get-buffer} to write a function that prints a
5427 message telling you whether a buffer exists.
5430 Using @code{find-tag}, find the source for the @code{copy-to-buffer}
5435 @chapter A Few More Complex Functions
5437 In this chapter, we build on what we have learned in previous chapters
5438 by looking at more complex functions. The @code{copy-to-buffer}
5439 function illustrates use of two @code{save-excursion} expressions in
5440 one definition, while the @code{insert-buffer} function illustrates
5441 use of an asterisk in an @code{interactive} expression, use of
5442 @code{or}, and the important distinction between a name and the object
5443 to which the name refers.
5446 * copy-to-buffer:: With @code{set-buffer}, @code{get-buffer-create}.
5447 * insert-buffer:: Read-only, and with @code{or}.
5448 * beginning-of-buffer:: Shows @code{goto-char},
5449 @code{point-min}, and @code{push-mark}.
5450 * Second Buffer Related Review::
5451 * optional Exercise::
5454 @node copy-to-buffer
5455 @section The Definition of @code{copy-to-buffer}
5456 @findex copy-to-buffer
5458 After understanding how @code{append-to-buffer} works, it is easy to
5459 understand @code{copy-to-buffer}. This function copies text into a
5460 buffer, but instead of adding to the second buffer, it replaces all the
5461 previous text in the second buffer.
5464 The body of @code{copy-to-buffer} looks like this,
5469 (interactive "BCopy to buffer: \nr")
5470 (let ((oldbuf (current-buffer)))
5471 (with-current-buffer (get-buffer-create buffer)
5472 (barf-if-buffer-read-only)
5475 (insert-buffer-substring oldbuf start end)))))
5479 The @code{copy-to-buffer} function has a simpler @code{interactive}
5480 expression than @code{append-to-buffer}.
5483 The definition then says
5486 (with-current-buffer (get-buffer-create buffer) @dots{}
5489 First, look at the earliest inner expression; that is evaluated first.
5490 That expression starts with @code{get-buffer-create buffer}. The
5491 function tells the computer to use the buffer with the name specified
5492 as the one to which you are copying, or if such a buffer does not
5493 exist, to create it. Then, the @code{with-current-buffer} function
5494 evaluates its body with that buffer temporarily current.
5496 (This demonstrates another way to shift the computer's attention but
5497 not the user's. The @code{append-to-buffer} function showed how to do
5498 the same with @code{save-excursion} and @code{set-buffer}.
5499 @code{with-current-buffer} is a newer, and arguably easier,
5502 The @code{barf-if-buffer-read-only} function sends you an error
5503 message saying the buffer is read-only if you cannot modify it.
5505 The next line has the @code{erase-buffer} function as its sole
5506 contents. That function erases the buffer.
5508 Finally, the last two lines contain the @code{save-excursion}
5509 expression with @code{insert-buffer-substring} as its body.
5510 The @code{insert-buffer-substring} expression copies the text from
5511 the buffer you are in (and you have not seen the computer shift its
5512 attention, so you don't know that that buffer is now called
5515 Incidentally, this is what is meant by ``replacement''. To replace text,
5516 Emacs erases the previous text and then inserts new text.
5519 In outline, the body of @code{copy-to-buffer} looks like this:
5523 (let (@var{bind-}@code{oldbuf}@var{-to-value-of-}@code{current-buffer})
5524 (@var{with-the-buffer-you-are-copying-to}
5525 (@var{but-do-not-erase-or-copy-to-a-read-only-buffer})
5528 @var{insert-substring-from-}@code{oldbuf}@var{-into-buffer})))
5533 @section The Definition of @code{insert-buffer}
5534 @findex insert-buffer
5536 @code{insert-buffer} is yet another buffer-related function. This
5537 command copies another buffer @emph{into} the current buffer. It is the
5538 reverse of @code{append-to-buffer} or @code{copy-to-buffer}, since they
5539 copy a region of text @emph{from} the current buffer to another buffer.
5541 Here is a discussion based on the original code. The code was
5542 simplified in 2003 and is harder to understand.
5544 (@xref{New insert-buffer, , New Body for @code{insert-buffer}}, to see
5545 a discussion of the new body.)
5547 In addition, this code illustrates the use of @code{interactive} with a
5548 buffer that might be @dfn{read-only} and the important distinction
5549 between the name of an object and the object actually referred to.
5552 * insert-buffer code::
5553 * insert-buffer interactive:: When you can read, but not write.
5554 * insert-buffer body:: The body has an @code{or} and a @code{let}.
5555 * if & or:: Using an @code{if} instead of an @code{or}.
5556 * Insert or:: How the @code{or} expression works.
5557 * Insert let:: Two @code{save-excursion} expressions.
5558 * New insert-buffer::
5562 @node insert-buffer code
5563 @unnumberedsubsec The Code for @code{insert-buffer}
5567 Here is the earlier code:
5571 (defun insert-buffer (buffer)
5572 "Insert after point the contents of BUFFER.
5573 Puts mark after the inserted text.
5574 BUFFER may be a buffer or a buffer name."
5575 (interactive "*bInsert buffer:@: ")
5578 (or (bufferp buffer)
5579 (setq buffer (get-buffer buffer)))
5580 (let (start end newmark)
5584 (setq start (point-min) end (point-max)))
5587 (insert-buffer-substring buffer start end)
5588 (setq newmark (point)))
5589 (push-mark newmark)))
5594 As with other function definitions, you can use a template to see an
5595 outline of the function:
5599 (defun insert-buffer (buffer)
5600 "@var{documentation}@dots{}"
5601 (interactive "*bInsert buffer:@: ")
5606 @node insert-buffer interactive
5607 @subsection The Interactive Expression in @code{insert-buffer}
5608 @findex interactive, @r{example use of}
5610 In @code{insert-buffer}, the argument to the @code{interactive}
5611 declaration has two parts, an asterisk, @samp{*}, and @samp{bInsert
5615 * Read-only buffer:: When a buffer cannot be modified.
5616 * b for interactive:: An existing buffer or else its name.
5619 @node Read-only buffer
5620 @unnumberedsubsubsec A Read-only Buffer
5621 @cindex Read-only buffer
5622 @cindex Asterisk for read-only buffer
5623 @findex * @r{for read-only buffer}
5625 The asterisk is for the situation when the current buffer is a
5626 read-only buffer---a buffer that cannot be modified. If
5627 @code{insert-buffer} is called when the current buffer is read-only, a
5628 message to this effect is printed in the echo area and the terminal
5629 may beep or blink at you; you will not be permitted to insert anything
5630 into current buffer. The asterisk does not need to be followed by a
5631 newline to separate it from the next argument.
5633 @node b for interactive
5634 @unnumberedsubsubsec @samp{b} in an Interactive Expression
5636 The next argument in the interactive expression starts with a lower
5637 case @samp{b}. (This is different from the code for
5638 @code{append-to-buffer}, which uses an upper-case @samp{B}.
5639 @xref{append-to-buffer, , The Definition of @code{append-to-buffer}}.)
5640 The lower-case @samp{b} tells the Lisp interpreter that the argument
5641 for @code{insert-buffer} should be an existing buffer or else its
5642 name. (The upper-case @samp{B} option provides for the possibility
5643 that the buffer does not exist.) Emacs will prompt you for the name
5644 of the buffer, offering you a default buffer, with name completion
5645 enabled. If the buffer does not exist, you receive a message that
5646 says ``No match''; your terminal may beep at you as well.
5648 The new and simplified code generates a list for @code{interactive}.
5649 It uses the @code{barf-if-buffer-read-only} and @code{read-buffer}
5650 functions with which we are already familiar and the @code{progn}
5651 special form with which we are not. (It will be described later.)
5653 @node insert-buffer body
5654 @subsection The Body of the @code{insert-buffer} Function
5656 The body of the @code{insert-buffer} function has two major parts: an
5657 @code{or} expression and a @code{let} expression. The purpose of the
5658 @code{or} expression is to ensure that the argument @code{buffer} is
5659 bound to a buffer and not just the name of a buffer. The body of the
5660 @code{let} expression contains the code which copies the other buffer
5661 into the current buffer.
5664 In outline, the two expressions fit into the @code{insert-buffer}
5669 (defun insert-buffer (buffer)
5670 "@var{documentation}@dots{}"
5671 (interactive "*bInsert buffer:@: ")
5676 (let (@var{varlist})
5677 @var{body-of-}@code{let}@dots{} )
5681 To understand how the @code{or} expression ensures that the argument
5682 @code{buffer} is bound to a buffer and not to the name of a buffer, it
5683 is first necessary to understand the @code{or} function.
5685 Before doing this, let me rewrite this part of the function using
5686 @code{if} so that you can see what is done in a manner that will be familiar.
5689 @subsection @code{insert-buffer} With an @code{if} Instead of an @code{or}
5691 The job to be done is to make sure the value of @code{buffer} is a
5692 buffer itself and not the name of a buffer. If the value is the name,
5693 then the buffer itself must be got.
5695 You can imagine yourself at a conference where an usher is wandering
5696 around holding a list with your name on it and looking for you: the
5697 usher is bound to your name, not to you; but when the usher finds
5698 you and takes your arm, the usher becomes bound to you.
5701 In Lisp, you might describe this situation like this:
5705 (if (not (holding-on-to-guest))
5706 (find-and-take-arm-of-guest))
5710 We want to do the same thing with a buffer---if we do not have the
5711 buffer itself, we want to get it.
5714 Using a predicate called @code{bufferp} that tells us whether we have a
5715 buffer (rather than its name), we can write the code like this:
5719 (if (not (bufferp buffer)) ; @r{if-part}
5720 (setq buffer (get-buffer buffer))) ; @r{then-part}
5725 Here, the true-or-false-test of the @code{if} expression is
5726 @w{@code{(not (bufferp buffer))}}; and the then-part is the expression
5727 @w{@code{(setq buffer (get-buffer buffer))}}.
5729 In the test, the function @code{bufferp} returns true if its argument is
5730 a buffer---but false if its argument is the name of the buffer. (The
5731 last character of the function name @code{bufferp} is the character
5732 @samp{p}; as we saw earlier, such use of @samp{p} is a convention that
5733 indicates that the function is a predicate, which is a term that means
5734 that the function will determine whether some property is true or false.
5735 @xref{Wrong Type of Argument, , Using the Wrong Type Object as an
5739 The function @code{not} precedes the expression @code{(bufferp buffer)},
5740 so the true-or-false-test looks like this:
5743 (not (bufferp buffer))
5747 @code{not} is a function that returns true if its argument is false
5748 and false if its argument is true. So if @code{(bufferp buffer)}
5749 returns true, the @code{not} expression returns false and vice versa.
5751 Using this test, the @code{if} expression works as follows: when the
5752 value of the variable @code{buffer} is actually a buffer rather than
5753 its name, the true-or-false-test returns false and the @code{if}
5754 expression does not evaluate the then-part. This is fine, since we do
5755 not need to do anything to the variable @code{buffer} if it really is
5758 On the other hand, when the value of @code{buffer} is not a buffer
5759 itself, but the name of a buffer, the true-or-false-test returns true
5760 and the then-part of the expression is evaluated. In this case, the
5761 then-part is @code{(setq buffer (get-buffer buffer))}. This
5762 expression uses the @code{get-buffer} function to return an actual
5763 buffer itself, given its name. The @code{setq} then sets the variable
5764 @code{buffer} to the value of the buffer itself, replacing its previous
5765 value (which was the name of the buffer).
5768 @subsection The @code{or} in the Body
5770 The purpose of the @code{or} expression in the @code{insert-buffer}
5771 function is to ensure that the argument @code{buffer} is bound to a
5772 buffer and not just to the name of a buffer. The previous section shows
5773 how the job could have been done using an @code{if} expression.
5774 However, the @code{insert-buffer} function actually uses @code{or}.
5775 To understand this, it is necessary to understand how @code{or} works.
5778 An @code{or} function can have any number of arguments. It evaluates
5779 each argument in turn and returns the value of the first of its
5780 arguments that is not @code{nil}. Also, and this is a crucial feature
5781 of @code{or}, it does not evaluate any subsequent arguments after
5782 returning the first non-@code{nil} value.
5785 The @code{or} expression looks like this:
5789 (or (bufferp buffer)
5790 (setq buffer (get-buffer buffer)))
5795 The first argument to @code{or} is the expression @code{(bufferp buffer)}.
5796 This expression returns true (a non-@code{nil} value) if the buffer is
5797 actually a buffer, and not just the name of a buffer. In the @code{or}
5798 expression, if this is the case, the @code{or} expression returns this
5799 true value and does not evaluate the next expression---and this is fine
5800 with us, since we do not want to do anything to the value of
5801 @code{buffer} if it really is a buffer.
5803 On the other hand, if the value of @code{(bufferp buffer)} is @code{nil},
5804 which it will be if the value of @code{buffer} is the name of a buffer,
5805 the Lisp interpreter evaluates the next element of the @code{or}
5806 expression. This is the expression @code{(setq buffer (get-buffer
5807 buffer))}. This expression returns a non-@code{nil} value, which
5808 is the value to which it sets the variable @code{buffer}---and this
5809 value is a buffer itself, not the name of a buffer.
5811 The result of all this is that the symbol @code{buffer} is always
5812 bound to a buffer itself rather than to the name of a buffer. All
5813 this is necessary because the @code{set-buffer} function in a
5814 following line only works with a buffer itself, not with the name to a
5818 Incidentally, using @code{or}, the situation with the usher would be
5822 (or (holding-on-to-guest) (find-and-take-arm-of-guest))
5826 @subsection The @code{let} Expression in @code{insert-buffer}
5828 After ensuring that the variable @code{buffer} refers to a buffer itself
5829 and not just to the name of a buffer, the @code{insert-buffer function}
5830 continues with a @code{let} expression. This specifies three local
5831 variables, @code{start}, @code{end}, and @code{newmark} and binds them
5832 to the initial value @code{nil}. These variables are used inside the
5833 remainder of the @code{let} and temporarily hide any other occurrence of
5834 variables of the same name in Emacs until the end of the @code{let}.
5837 The body of the @code{let} contains two @code{save-excursion}
5838 expressions. First, we will look at the inner @code{save-excursion}
5839 expression in detail. The expression looks like this:
5845 (setq start (point-min) end (point-max)))
5850 The expression @code{(set-buffer buffer)} changes Emacs's attention
5851 from the current buffer to the one from which the text will copied.
5852 In that buffer, the variables @code{start} and @code{end} are set to
5853 the beginning and end of the buffer, using the commands
5854 @code{point-min} and @code{point-max}. Note that we have here an
5855 illustration of how @code{setq} is able to set two variables in the
5856 same expression. The first argument of @code{setq} is set to the
5857 value of its second, and its third argument is set to the value of its
5860 After the body of the inner @code{save-excursion} is evaluated, the
5861 @code{save-excursion} restores the original buffer, but @code{start} and
5862 @code{end} remain set to the values of the beginning and end of the
5863 buffer from which the text will be copied.
5866 The outer @code{save-excursion} expression looks like this:
5871 (@var{inner-}@code{save-excursion}@var{-expression}
5872 (@var{go-to-new-buffer-and-set-}@code{start}@var{-and-}@code{end})
5873 (insert-buffer-substring buffer start end)
5874 (setq newmark (point)))
5879 The @code{insert-buffer-substring} function copies the text
5880 @emph{into} the current buffer @emph{from} the region indicated by
5881 @code{start} and @code{end} in @code{buffer}. Since the whole of the
5882 second buffer lies between @code{start} and @code{end}, the whole of
5883 the second buffer is copied into the buffer you are editing. Next,
5884 the value of point, which will be at the end of the inserted text, is
5885 recorded in the variable @code{newmark}.
5887 After the body of the outer @code{save-excursion} is evaluated, point
5888 is relocated to its original place.
5890 However, it is convenient to locate a mark at the end of the newly
5891 inserted text and locate point at its beginning. The @code{newmark}
5892 variable records the end of the inserted text. In the last line of
5893 the @code{let} expression, the @code{(push-mark newmark)} expression
5894 function sets a mark to this location. (The previous location of the
5895 mark is still accessible; it is recorded on the mark ring and you can
5896 go back to it with @kbd{C-u C-@key{SPC}}.) Meanwhile, point is
5897 located at the beginning of the inserted text, which is where it was
5898 before you called the insert function, the position of which was saved
5899 by the first @code{save-excursion}.
5902 The whole @code{let} expression looks like this:
5906 (let (start end newmark)
5910 (setq start (point-min) end (point-max)))
5911 (insert-buffer-substring buffer start end)
5912 (setq newmark (point)))
5913 (push-mark newmark))
5917 Like the @code{append-to-buffer} function, the @code{insert-buffer}
5918 function uses @code{let}, @code{save-excursion}, and
5919 @code{set-buffer}. In addition, the function illustrates one way to
5920 use @code{or}. All these functions are building blocks that we will
5921 find and use again and again.
5923 @node New insert-buffer
5924 @subsection New Body for @code{insert-buffer}
5925 @findex insert-buffer, new version body
5926 @findex new version body for insert-buffer
5928 The body in the GNU Emacs 22 version is more confusing than the original.
5931 It consists of two expressions,
5937 (insert-buffer-substring (get-buffer buffer))
5945 except, and this is what confuses novices, very important work is done
5946 inside the @code{push-mark} expression.
5948 The @code{get-buffer} function returns a buffer with the name
5949 provided. You will note that the function is @emph{not} called
5950 @code{get-buffer-create}; it does not create a buffer if one does not
5951 already exist. The buffer returned by @code{get-buffer}, an existing
5952 buffer, is passed to @code{insert-buffer-substring}, which inserts the
5953 whole of the buffer (since you did not specify anything else).
5955 The location into which the buffer is inserted is recorded by
5956 @code{push-mark}. Then the function returns @code{nil}, the value of
5957 its last command. Put another way, the @code{insert-buffer} function
5958 exists only to produce a side effect, inserting another buffer, not to
5961 @node beginning-of-buffer
5962 @section Complete Definition of @code{beginning-of-buffer}
5963 @findex beginning-of-buffer
5965 The basic structure of the @code{beginning-of-buffer} function has
5966 already been discussed. (@xref{simplified-beginning-of-buffer, , A
5967 Simplified @code{beginning-of-buffer} Definition}.)
5968 This section describes the complex part of the definition.
5970 As previously described, when invoked without an argument,
5971 @code{beginning-of-buffer} moves the cursor to the beginning of the
5972 buffer (in truth, the beginning of the accessible portion of the
5973 buffer), leaving the mark at the previous position. However, when the
5974 command is invoked with a number between one and ten, the function
5975 considers that number to be a fraction of the length of the buffer,
5976 measured in tenths, and Emacs moves the cursor that fraction of the
5977 way from the beginning of the buffer. Thus, you can either call this
5978 function with the key command @kbd{M-<}, which will move the cursor to
5979 the beginning of the buffer, or with a key command such as @kbd{C-u 7
5980 M-<} which will move the cursor to a point 70% of the way through the
5981 buffer. If a number bigger than ten is used for the argument, it
5982 moves to the end of the buffer.
5984 The @code{beginning-of-buffer} function can be called with or without an
5985 argument. The use of the argument is optional.
5988 * Optional Arguments::
5989 * beginning-of-buffer opt arg:: Example with optional argument.
5990 * beginning-of-buffer complete::
5993 @node Optional Arguments
5994 @subsection Optional Arguments
5996 Unless told otherwise, Lisp expects that a function with an argument in
5997 its function definition will be called with a value for that argument.
5998 If that does not happen, you get an error and a message that says
5999 @samp{Wrong number of arguments}.
6001 @cindex Optional arguments
6004 However, optional arguments are a feature of Lisp: a particular
6005 @dfn{keyword} is used to tell the Lisp interpreter that an argument is
6006 optional. The keyword is @code{&optional}. (The @samp{&} in front of
6007 @samp{optional} is part of the keyword.) In a function definition, if
6008 an argument follows the keyword @code{&optional}, no value need be
6009 passed to that argument when the function is called.
6012 The first line of the function definition of @code{beginning-of-buffer}
6013 therefore looks like this:
6016 (defun beginning-of-buffer (&optional arg)
6020 In outline, the whole function looks like this:
6024 (defun beginning-of-buffer (&optional arg)
6025 "@var{documentation}@dots{}"
6027 (or (@var{is-the-argument-a-cons-cell} arg)
6028 (and @var{are-both-transient-mark-mode-and-mark-active-true})
6030 (let (@var{determine-size-and-set-it})
6032 (@var{if-there-is-an-argument}
6033 @var{figure-out-where-to-go}
6040 The function is similar to the @code{simplified-beginning-of-buffer}
6041 function except that the @code{interactive} expression has @code{"P"}
6042 as an argument and the @code{goto-char} function is followed by an
6043 if-then-else expression that figures out where to put the cursor if
6044 there is an argument that is not a cons cell.
6046 (Since I do not explain a cons cell for many more chapters, please
6047 consider ignoring the function @code{consp}. @xref{List
6048 Implementation, , How Lists are Implemented}, and @ref{Cons Cell Type,
6049 , Cons Cell and List Types, elisp, The GNU Emacs Lisp Reference
6052 The @code{"P"} in the @code{interactive} expression tells Emacs to
6053 pass a prefix argument, if there is one, to the function in raw form.
6054 A prefix argument is made by typing the @key{META} key followed by a
6055 number, or by typing @kbd{C-u} and then a number. (If you don't type
6056 a number, @kbd{C-u} defaults to a cons cell with a 4. A lowercase
6057 @code{"p"} in the @code{interactive} expression causes the function to
6058 convert a prefix arg to a number.)
6060 The true-or-false-test of the @code{if} expression looks complex, but
6061 it is not: it checks whether @code{arg} has a value that is not
6062 @code{nil} and whether it is a cons cell. (That is what @code{consp}
6063 does; it checks whether its argument is a cons cell.) If @code{arg}
6064 has a value that is not @code{nil} (and is not a cons cell), which
6065 will be the case if @code{beginning-of-buffer} is called with a
6066 numeric argument, then this true-or-false-test will return true and
6067 the then-part of the @code{if} expression will be evaluated. On the
6068 other hand, if @code{beginning-of-buffer} is not called with an
6069 argument, the value of @code{arg} will be @code{nil} and the else-part
6070 of the @code{if} expression will be evaluated. The else-part is
6071 simply @code{point-min}, and when this is the outcome, the whole
6072 @code{goto-char} expression is @code{(goto-char (point-min))}, which
6073 is how we saw the @code{beginning-of-buffer} function in its
6076 @node beginning-of-buffer opt arg
6077 @subsection @code{beginning-of-buffer} with an Argument
6079 When @code{beginning-of-buffer} is called with an argument, an
6080 expression is evaluated which calculates what value to pass to
6081 @code{goto-char}. This expression is rather complicated at first sight.
6082 It includes an inner @code{if} expression and much arithmetic. It looks
6087 (if (> (buffer-size) 10000)
6088 ;; @r{Avoid overflow for large buffer sizes!}
6089 (* (prefix-numeric-value arg)
6094 size (prefix-numeric-value arg))) 10)))
6099 * Disentangle beginning-of-buffer::
6100 * Large buffer case::
6101 * Small buffer case::
6105 @node Disentangle beginning-of-buffer
6106 @unnumberedsubsubsec Disentangle @code{beginning-of-buffer}
6109 Like other complex-looking expressions, the conditional expression
6110 within @code{beginning-of-buffer} can be disentangled by looking at it
6111 as parts of a template, in this case, the template for an if-then-else
6112 expression. In skeletal form, the expression looks like this:
6116 (if (@var{buffer-is-large}
6117 @var{divide-buffer-size-by-10-and-multiply-by-arg}
6118 @var{else-use-alternate-calculation}
6122 The true-or-false-test of this inner @code{if} expression checks the
6123 size of the buffer. The reason for this is that the old version 18
6124 Emacs used numbers that are no bigger than eight million or so and in
6125 the computation that followed, the programmer feared that Emacs might
6126 try to use over-large numbers if the buffer were large. The term
6127 ``overflow'', mentioned in the comment, means numbers that are over
6128 large. More recent versions of Emacs use larger numbers, but this
6129 code has not been touched, if only because people now look at buffers
6130 that are far, far larger than ever before.
6132 There are two cases: if the buffer is large and if it is not.
6134 @node Large buffer case
6135 @unnumberedsubsubsec What happens in a large buffer
6137 In @code{beginning-of-buffer}, the inner @code{if} expression tests
6138 whether the size of the buffer is greater than 10,000 characters. To do
6139 this, it uses the @code{>} function and the computation of @code{size}
6140 that comes from the let expression.
6142 In the old days, the function @code{buffer-size} was used. Not only
6143 was that function called several times, it gave the size of the whole
6144 buffer, not the accessible part. The computation makes much more
6145 sense when it handles just the accessible part. (@xref{Narrowing &
6146 Widening, , Narrowing and Widening}, for more information on focusing
6147 attention to an accessible part.)
6150 The line looks like this:
6158 When the buffer is large, the then-part of the @code{if} expression is
6159 evaluated. It reads like this (after formatting for easy reading):
6164 (prefix-numeric-value arg)
6170 This expression is a multiplication, with two arguments to the function
6173 The first argument is @code{(prefix-numeric-value arg)}. When
6174 @code{"P"} is used as the argument for @code{interactive}, the value
6175 passed to the function as its argument is passed a @dfn{raw prefix
6176 argument}, and not a number. (It is a number in a list.) To perform
6177 the arithmetic, a conversion is necessary, and
6178 @code{prefix-numeric-value} does the job.
6180 @findex / @r{(division)}
6182 The second argument is @code{(/ size 10)}. This expression divides
6183 the numeric value by ten---the numeric value of the size of the
6184 accessible portion of the buffer. This produces a number that tells
6185 how many characters make up one tenth of the buffer size. (In Lisp,
6186 @code{/} is used for division, just as @code{*} is used for
6190 In the multiplication expression as a whole, this amount is multiplied
6191 by the value of the prefix argument---the multiplication looks like this:
6195 (* @var{numeric-value-of-prefix-arg}
6196 @var{number-of-characters-in-one-tenth-of-the-accessible-buffer})
6201 If, for example, the prefix argument is @samp{7}, the one-tenth value
6202 will be multiplied by 7 to give a position 70% of the way through.
6205 The result of all this is that if the accessible portion of the buffer
6206 is large, the @code{goto-char} expression reads like this:
6210 (goto-char (* (prefix-numeric-value arg)
6215 This puts the cursor where we want it.
6217 @node Small buffer case
6218 @unnumberedsubsubsec What happens in a small buffer
6220 If the buffer contains fewer than 10,000 characters, a slightly
6221 different computation is performed. You might think this is not
6222 necessary, since the first computation could do the job. However, in
6223 a small buffer, the first method may not put the cursor on exactly the
6224 desired line; the second method does a better job.
6227 The code looks like this:
6229 @c Keep this on one line.
6231 (/ (+ 10 (* size (prefix-numeric-value arg))) 10))
6236 This is code in which you figure out what happens by discovering how the
6237 functions are embedded in parentheses. It is easier to read if you
6238 reformat it with each expression indented more deeply than its
6239 enclosing expression:
6247 (prefix-numeric-value arg)))
6254 Looking at parentheses, we see that the innermost operation is
6255 @code{(prefix-numeric-value arg)}, which converts the raw argument to
6256 a number. In the following expression, this number is multiplied by
6257 the size of the accessible portion of the buffer:
6260 (* size (prefix-numeric-value arg))
6264 This multiplication creates a number that may be larger than the size of
6265 the buffer---seven times larger if the argument is 7, for example. Ten
6266 is then added to this number and finally the large number is divided by
6267 ten to provide a value that is one character larger than the percentage
6268 position in the buffer.
6270 The number that results from all this is passed to @code{goto-char} and
6271 the cursor is moved to that point.
6274 @node beginning-of-buffer complete
6275 @subsection The Complete @code{beginning-of-buffer}
6278 Here is the complete text of the @code{beginning-of-buffer} function:
6284 (defun beginning-of-buffer (&optional arg)
6285 "Move point to the beginning of the buffer;
6286 leave mark at previous position.
6287 With \\[universal-argument] prefix,
6288 do not set mark at previous position.
6290 put point N/10 of the way from the beginning.
6292 If the buffer is narrowed,
6293 this command uses the beginning and size
6294 of the accessible part of the buffer.
6298 Don't use this command in Lisp programs!
6299 \(goto-char (point-min)) is faster
6300 and avoids clobbering the mark."
6303 (and transient-mark-mode mark-active)
6307 (let ((size (- (point-max) (point-min))))
6308 (goto-char (if (and arg (not (consp arg)))
6311 ;; Avoid overflow for large buffer sizes!
6312 (* (prefix-numeric-value arg)
6314 (/ (+ 10 (* size (prefix-numeric-value arg)))
6317 (if (and arg (not (consp arg))) (forward-line 1)))
6322 From before GNU Emacs 22
6325 (defun beginning-of-buffer (&optional arg)
6326 "Move point to the beginning of the buffer;
6327 leave mark at previous position.
6328 With arg N, put point N/10 of the way
6329 from the true beginning.
6332 Don't use this in Lisp programs!
6333 \(goto-char (point-min)) is faster
6334 and does not set the mark."
6341 (if (> (buffer-size) 10000)
6342 ;; @r{Avoid overflow for large buffer sizes!}
6343 (* (prefix-numeric-value arg)
6344 (/ (buffer-size) 10))
6347 (/ (+ 10 (* (buffer-size)
6348 (prefix-numeric-value arg)))
6351 (if arg (forward-line 1)))
6357 Except for two small points, the previous discussion shows how this
6358 function works. The first point deals with a detail in the
6359 documentation string, and the second point concerns the last line of
6363 In the documentation string, there is reference to an expression:
6366 \\[universal-argument]
6370 A @samp{\\} is used before the first square bracket of this
6371 expression. This @samp{\\} tells the Lisp interpreter to substitute
6372 whatever key is currently bound to the @samp{[@dots{}]}. In the case
6373 of @code{universal-argument}, that is usually @kbd{C-u}, but it might
6374 be different. (@xref{Documentation Tips, , Tips for Documentation
6375 Strings, elisp, The GNU Emacs Lisp Reference Manual}, for more
6379 Finally, the last line of the @code{beginning-of-buffer} command says
6380 to move point to the beginning of the next line if the command is
6381 invoked with an argument:
6384 (if (and arg (not (consp arg))) (forward-line 1))
6388 This puts the cursor at the beginning of the first line after the
6389 appropriate tenths position in the buffer. This is a flourish that
6390 means that the cursor is always located @emph{at least} the requested
6391 tenths of the way through the buffer, which is a nicety that is,
6392 perhaps, not necessary, but which, if it did not occur, would be sure
6393 to draw complaints. (The @code{(not (consp arg))} portion is so that
6394 if you specify the command with a @kbd{C-u}, but without a number,
6395 that is to say, if the raw prefix argument is simply a cons cell,
6396 the command does not put you at the beginning of the second line.)
6398 @node Second Buffer Related Review
6401 Here is a brief summary of some of the topics covered in this chapter.
6405 Evaluate each argument in sequence, and return the value of the first
6406 argument that is not @code{nil}; if none return a value that is not
6407 @code{nil}, return @code{nil}. In brief, return the first true value
6408 of the arguments; return a true value if one @emph{or} any of the
6412 Evaluate each argument in sequence, and if any are @code{nil}, return
6413 @code{nil}; if none are @code{nil}, return the value of the last
6414 argument. In brief, return a true value only if all the arguments are
6415 true; return a true value if one @emph{and} each of the others is
6419 A keyword used to indicate that an argument to a function definition
6420 is optional; this means that the function can be evaluated without the
6421 argument, if desired.
6423 @item prefix-numeric-value
6424 Convert the raw prefix argument produced by @code{(interactive
6425 "P")} to a numeric value.
6428 Move point forward to the beginning of the next line, or if the argument
6429 is greater than one, forward that many lines. If it can't move as far
6430 forward as it is supposed to, @code{forward-line} goes forward as far as
6431 it can and then returns a count of the number of additional lines it was
6432 supposed to move but couldn't.
6435 Delete the entire contents of the current buffer.
6438 Return @code{t} if its argument is a buffer; otherwise return @code{nil}.
6441 @node optional Exercise
6442 @section @code{optional} Argument Exercise
6444 Write an interactive function with an optional argument that tests
6445 whether its argument, a number, is greater than or equal to, or else,
6446 less than the value of @code{fill-column}, and tells you which, in a
6447 message. However, if you do not pass an argument to the function, use
6448 56 as a default value.
6450 @node Narrowing & Widening
6451 @chapter Narrowing and Widening
6452 @cindex Focusing attention (narrowing)
6456 Narrowing is a feature of Emacs that makes it possible for you to focus
6457 on a specific part of a buffer, and work without accidentally changing
6458 other parts. Narrowing is normally disabled since it can confuse
6462 * Narrowing advantages:: The advantages of narrowing
6463 * save-restriction:: The @code{save-restriction} special form.
6464 * what-line:: The number of the line that point is on.
6469 @node Narrowing advantages
6470 @unnumberedsec The Advantages of Narrowing
6473 With narrowing, the rest of a buffer is made invisible, as if it weren't
6474 there. This is an advantage if, for example, you want to replace a word
6475 in one part of a buffer but not in another: you narrow to the part you want
6476 and the replacement is carried out only in that section, not in the rest
6477 of the buffer. Searches will only work within a narrowed region, not
6478 outside of one, so if you are fixing a part of a document, you can keep
6479 yourself from accidentally finding parts you do not need to fix by
6480 narrowing just to the region you want.
6481 (The key binding for @code{narrow-to-region} is @kbd{C-x n n}.)
6483 However, narrowing does make the rest of the buffer invisible, which
6484 can scare people who inadvertently invoke narrowing and think they
6485 have deleted a part of their file. Moreover, the @code{undo} command
6486 (which is usually bound to @kbd{C-x u}) does not turn off narrowing
6487 (nor should it), so people can become quite desperate if they do not
6488 know that they can return the rest of a buffer to visibility with the
6489 @code{widen} command.
6490 (The key binding for @code{widen} is @kbd{C-x n w}.)
6492 Narrowing is just as useful to the Lisp interpreter as to a human.
6493 Often, an Emacs Lisp function is designed to work on just part of a
6494 buffer; or conversely, an Emacs Lisp function needs to work on all of a
6495 buffer that has been narrowed. The @code{what-line} function, for
6496 example, removes the narrowing from a buffer, if it has any narrowing
6497 and when it has finished its job, restores the narrowing to what it was.
6498 On the other hand, the @code{count-lines} function
6499 uses narrowing to restrict itself to just that portion
6500 of the buffer in which it is interested and then restores the previous
6503 @node save-restriction
6504 @section The @code{save-restriction} Special Form
6505 @findex save-restriction
6507 In Emacs Lisp, you can use the @code{save-restriction} special form to
6508 keep track of whatever narrowing is in effect, if any. When the Lisp
6509 interpreter meets with @code{save-restriction}, it executes the code
6510 in the body of the @code{save-restriction} expression, and then undoes
6511 any changes to narrowing that the code caused. If, for example, the
6512 buffer is narrowed and the code that follows @code{save-restriction}
6513 gets rid of the narrowing, @code{save-restriction} returns the buffer
6514 to its narrowed region afterwards. In the @code{what-line} command,
6515 any narrowing the buffer may have is undone by the @code{widen}
6516 command that immediately follows the @code{save-restriction} command.
6517 Any original narrowing is restored just before the completion of the
6521 The template for a @code{save-restriction} expression is simple:
6531 The body of the @code{save-restriction} is one or more expressions that
6532 will be evaluated in sequence by the Lisp interpreter.
6534 Finally, a point to note: when you use both @code{save-excursion} and
6535 @code{save-restriction}, one right after the other, you should use
6536 @code{save-excursion} outermost. If you write them in reverse order,
6537 you may fail to record narrowing in the buffer to which Emacs switches
6538 after calling @code{save-excursion}. Thus, when written together,
6539 @code{save-excursion} and @code{save-restriction} should be written
6550 In other circumstances, when not written together, the
6551 @code{save-excursion} and @code{save-restriction} special forms must
6552 be written in the order appropriate to the function.
6568 /usr/local/src/emacs/lisp/simple.el
6571 "Print the current buffer line number and narrowed line number of point."
6573 (let ((start (point-min))
6574 (n (line-number-at-pos)))
6576 (message "Line %d" n)
6580 (message "line %d (narrowed line %d)"
6581 (+ n (line-number-at-pos start) -1) n))))))
6583 (defun line-number-at-pos (&optional pos)
6584 "Return (narrowed) buffer line number at position POS.
6585 If POS is nil, use current buffer location.
6586 Counting starts at (point-min), so the value refers
6587 to the contents of the accessible portion of the buffer."
6588 (let ((opoint (or pos (point))) start)
6590 (goto-char (point-min))
6591 (setq start (point))
6594 (1+ (count-lines start (point))))))
6596 (defun count-lines (start end)
6597 "Return number of lines between START and END.
6598 This is usually the number of newlines between them,
6599 but can be one more if START is not equal to END
6600 and the greater of them is not at the start of a line."
6603 (narrow-to-region start end)
6604 (goto-char (point-min))
6605 (if (eq selective-display t)
6608 (while (re-search-forward "[\n\C-m]" nil t 40)
6609 (setq done (+ 40 done)))
6610 (while (re-search-forward "[\n\C-m]" nil t 1)
6611 (setq done (+ 1 done)))
6612 (goto-char (point-max))
6613 (if (and (/= start end)
6617 (- (buffer-size) (forward-line (buffer-size)))))))
6621 @section @code{what-line}
6623 @cindex Widening, example of
6625 The @code{what-line} command tells you the number of the line in which
6626 the cursor is located. The function illustrates the use of the
6627 @code{save-restriction} and @code{save-excursion} commands. Here is the
6628 original text of the function:
6633 "Print the current line number (in the buffer) of point."
6640 (1+ (count-lines 1 (point)))))))
6644 (In recent versions of GNU Emacs, the @code{what-line} function has
6645 been expanded to tell you your line number in a narrowed buffer as
6646 well as your line number in a widened buffer. The recent version is
6647 more complex than the version shown here. If you feel adventurous,
6648 you might want to look at it after figuring out how this version
6649 works. You will probably need to use @kbd{C-h f}
6650 (@code{describe-function}). The newer version uses a conditional to
6651 determine whether the buffer has been narrowed.
6653 (Also, it uses @code{line-number-at-pos}, which among other simple
6654 expressions, such as @code{(goto-char (point-min))}, moves point to
6655 the beginning of the current line with @code{(forward-line 0)} rather
6656 than @code{beginning-of-line}.)
6658 The @code{what-line} function as shown here has a documentation line
6659 and is interactive, as you would expect. The next two lines use the
6660 functions @code{save-restriction} and @code{widen}.
6662 The @code{save-restriction} special form notes whatever narrowing is in
6663 effect, if any, in the current buffer and restores that narrowing after
6664 the code in the body of the @code{save-restriction} has been evaluated.
6666 The @code{save-restriction} special form is followed by @code{widen}.
6667 This function undoes any narrowing the current buffer may have had
6668 when @code{what-line} was called. (The narrowing that was there is
6669 the narrowing that @code{save-restriction} remembers.) This widening
6670 makes it possible for the line counting commands to count from the
6671 beginning of the buffer. Otherwise, they would have been limited to
6672 counting within the accessible region. Any original narrowing is
6673 restored just before the completion of the function by the
6674 @code{save-restriction} special form.
6676 The call to @code{widen} is followed by @code{save-excursion}, which
6677 saves the location of the cursor (i.e., of point), and
6678 restores it after the code in the body of the @code{save-excursion}
6679 uses the @code{beginning-of-line} function to move point.
6681 (Note that the @code{(widen)} expression comes between the
6682 @code{save-restriction} and @code{save-excursion} special forms. When
6683 you write the two @code{save- @dots{}} expressions in sequence, write
6684 @code{save-excursion} outermost.)
6687 The last two lines of the @code{what-line} function are functions to
6688 count the number of lines in the buffer and then print the number in the
6694 (1+ (count-lines 1 (point)))))))
6698 The @code{message} function prints a one-line message at the bottom of
6699 the Emacs screen. The first argument is inside of quotation marks and
6700 is printed as a string of characters. However, it may contain a
6701 @samp{%d} expression to print a following argument. @samp{%d} prints
6702 the argument as a decimal, so the message will say something such as
6706 The number that is printed in place of the @samp{%d} is computed by the
6707 last line of the function:
6710 (1+ (count-lines 1 (point)))
6716 (defun count-lines (start end)
6717 "Return number of lines between START and END.
6718 This is usually the number of newlines between them,
6719 but can be one more if START is not equal to END
6720 and the greater of them is not at the start of a line."
6723 (narrow-to-region start end)
6724 (goto-char (point-min))
6725 (if (eq selective-display t)
6728 (while (re-search-forward "[\n\C-m]" nil t 40)
6729 (setq done (+ 40 done)))
6730 (while (re-search-forward "[\n\C-m]" nil t 1)
6731 (setq done (+ 1 done)))
6732 (goto-char (point-max))
6733 (if (and (/= start end)
6737 (- (buffer-size) (forward-line (buffer-size)))))))
6741 What this does is count the lines from the first position of the
6742 buffer, indicated by the @code{1}, up to @code{(point)}, and then add
6743 one to that number. (The @code{1+} function adds one to its
6744 argument.) We add one to it because line 2 has only one line before
6745 it, and @code{count-lines} counts only the lines @emph{before} the
6748 After @code{count-lines} has done its job, and the message has been
6749 printed in the echo area, the @code{save-excursion} restores point to
6750 its original position; and @code{save-restriction} restores
6751 the original narrowing, if any.
6753 @node narrow Exercise
6754 @section Exercise with Narrowing
6756 Write a function that will display the first 60 characters of the
6757 current buffer, even if you have narrowed the buffer to its latter
6758 half so that the first line is inaccessible. Restore point, mark, and
6759 narrowing. For this exercise, you need to use a whole potpourri of
6760 functions, including @code{save-restriction}, @code{widen},
6761 @code{goto-char}, @code{point-min}, @code{message}, and
6762 @code{buffer-substring}.
6764 @cindex Properties, mention of @code{buffer-substring-no-properties}
6765 (@code{buffer-substring} is a previously unmentioned function you will
6766 have to investigate yourself; or perhaps you will have to use
6767 @code{buffer-substring-no-properties} or
6768 @code{filter-buffer-substring} @dots{}, yet other functions. Text
6769 properties are a feature otherwise not discussed here. @xref{Text
6770 Properties, , Text Properties, elisp, The GNU Emacs Lisp Reference
6773 Additionally, do you really need @code{goto-char} or @code{point-min}?
6774 Or can you write the function without them?
6776 @node car cdr & cons
6777 @chapter @code{car}, @code{cdr}, @code{cons}: Fundamental Functions
6778 @findex car, @r{introduced}
6779 @findex cdr, @r{introduced}
6781 In Lisp, @code{car}, @code{cdr}, and @code{cons} are fundamental
6782 functions. The @code{cons} function is used to construct lists, and
6783 the @code{car} and @code{cdr} functions are used to take them apart.
6785 In the walk through of the @code{copy-region-as-kill} function, we
6786 will see @code{cons} as well as two variants on @code{cdr},
6787 namely, @code{setcdr} and @code{nthcdr}. (@xref{copy-region-as-kill}.)
6790 * Strange Names:: An historical aside: why the strange names?
6791 * car & cdr:: Functions for extracting part of a list.
6792 * cons:: Constructing a list.
6793 * nthcdr:: Calling @code{cdr} repeatedly.
6795 * setcar:: Changing the first element of a list.
6796 * setcdr:: Changing the rest of a list.
6802 @unnumberedsec Strange Names
6805 The name of the @code{cons} function is not unreasonable: it is an
6806 abbreviation of the word ``construct''. The origins of the names for
6807 @code{car} and @code{cdr}, on the other hand, are esoteric: @code{car}
6808 is an acronym from the phrase ``Contents of the Address part of the
6809 Register''; and @code{cdr} (pronounced ``could-er'') is an acronym from
6810 the phrase ``Contents of the Decrement part of the Register''. These
6811 phrases refer to specific pieces of hardware on the very early
6812 computer on which the original Lisp was developed. Besides being
6813 obsolete, the phrases have been completely irrelevant for more than 25
6814 years to anyone thinking about Lisp. Nonetheless, although a few
6815 brave scholars have begun to use more reasonable names for these
6816 functions, the old terms are still in use. In particular, since the
6817 terms are used in the Emacs Lisp source code, we will use them in this
6821 @section @code{car} and @code{cdr}
6823 The @sc{car} of a list is, quite simply, the first item in the list.
6824 Thus the @sc{car} of the list @code{(rose violet daisy buttercup)} is
6828 If you are reading this in Info in GNU Emacs, you can see this by
6829 evaluating the following:
6832 (car '(rose violet daisy buttercup))
6836 After evaluating the expression, @code{rose} will appear in the echo
6839 Clearly, a more reasonable name for the @code{car} function would be
6840 @code{first} and this is often suggested.
6842 @code{car} does not remove the first item from the list; it only reports
6843 what it is. After @code{car} has been applied to a list, the list is
6844 still the same as it was. In the jargon, @code{car} is
6845 ``non-destructive''. This feature turns out to be important.
6847 The @sc{cdr} of a list is the rest of the list, that is, the
6848 @code{cdr} function returns the part of the list that follows the
6849 first item. Thus, while the @sc{car} of the list @code{'(rose violet
6850 daisy buttercup)} is @code{rose}, the rest of the list, the value
6851 returned by the @code{cdr} function, is @code{(violet daisy
6855 You can see this by evaluating the following in the usual way:
6858 (cdr '(rose violet daisy buttercup))
6862 When you evaluate this, @code{(violet daisy buttercup)} will appear in
6865 Like @code{car}, @code{cdr} does not remove any elements from the
6866 list---it just returns a report of what the second and subsequent
6869 Incidentally, in the example, the list of flowers is quoted. If it were
6870 not, the Lisp interpreter would try to evaluate the list by calling
6871 @code{rose} as a function. In this example, we do not want to do that.
6873 Clearly, a more reasonable name for @code{cdr} would be @code{rest}.
6875 (There is a lesson here: when you name new functions, consider very
6876 carefully what you are doing, since you may be stuck with the names
6877 for far longer than you expect. The reason this document perpetuates
6878 these names is that the Emacs Lisp source code uses them, and if I did
6879 not use them, you would have a hard time reading the code; but do,
6880 please, try to avoid using these terms yourself. The people who come
6881 after you will be grateful to you.)
6883 When @code{car} and @code{cdr} are applied to a list made up of symbols,
6884 such as the list @code{(pine fir oak maple)}, the element of the list
6885 returned by the function @code{car} is the symbol @code{pine} without
6886 any parentheses around it. @code{pine} is the first element in the
6887 list. However, the @sc{cdr} of the list is a list itself, @code{(fir
6888 oak maple)}, as you can see by evaluating the following expressions in
6893 (car '(pine fir oak maple))
6895 (cdr '(pine fir oak maple))
6899 On the other hand, in a list of lists, the first element is itself a
6900 list. @code{car} returns this first element as a list. For example,
6901 the following list contains three sub-lists, a list of carnivores, a
6902 list of herbivores and a list of sea mammals:
6906 (car '((lion tiger cheetah)
6907 (gazelle antelope zebra)
6908 (whale dolphin seal)))
6913 In this example, the first element or @sc{car} of the list is the list of
6914 carnivores, @code{(lion tiger cheetah)}, and the rest of the list is
6915 @code{((gazelle antelope zebra) (whale dolphin seal))}.
6919 (cdr '((lion tiger cheetah)
6920 (gazelle antelope zebra)
6921 (whale dolphin seal)))
6925 It is worth saying again that @code{car} and @code{cdr} are
6926 non-destructive---that is, they do not modify or change lists to which
6927 they are applied. This is very important for how they are used.
6929 Also, in the first chapter, in the discussion about atoms, I said that
6930 in Lisp, certain kinds of atom, such as an array, can be separated
6931 into parts; but the mechanism for doing this is different from the
6932 mechanism for splitting a list. As far as Lisp is concerned, the
6933 atoms of a list are unsplittable. (@xref{Lisp Atoms}.) The
6934 @code{car} and @code{cdr} functions are used for splitting lists and
6935 are considered fundamental to Lisp. Since they cannot split or gain
6936 access to the parts of an array, an array is considered an atom.
6937 Conversely, the other fundamental function, @code{cons}, can put
6938 together or construct a list, but not an array. (Arrays are handled
6939 by array-specific functions. @xref{Arrays, , Arrays, elisp, The GNU
6940 Emacs Lisp Reference Manual}.)
6943 @section @code{cons}
6944 @findex cons, @r{introduced}
6946 The @code{cons} function constructs lists; it is the inverse of
6947 @code{car} and @code{cdr}. For example, @code{cons} can be used to make
6948 a four element list from the three element list, @code{(fir oak maple)}:
6951 (cons 'pine '(fir oak maple))
6956 After evaluating this list, you will see
6959 (pine fir oak maple)
6963 appear in the echo area. @code{cons} causes the creation of a new
6964 list in which the element is followed by the elements of the original
6967 We often say that @code{cons} puts a new element at the beginning of
6968 a list, or that it attaches or pushes elements onto the list, but this
6969 phrasing can be misleading, since @code{cons} does not change an
6970 existing list, but creates a new one.
6972 Like @code{car} and @code{cdr}, @code{cons} is non-destructive.
6976 * length:: How to find the length of a list.
6981 @unnumberedsubsec Build a list
6984 @code{cons} must have a list to attach to.@footnote{Actually, you can
6985 @code{cons} an element to an atom to produce a dotted pair. Dotted
6986 pairs are not discussed here; see @ref{Dotted Pair Notation, , Dotted
6987 Pair Notation, elisp, The GNU Emacs Lisp Reference Manual}.} You
6988 cannot start from absolutely nothing. If you are building a list, you
6989 need to provide at least an empty list at the beginning. Here is a
6990 series of @code{cons} expressions that build up a list of flowers. If
6991 you are reading this in Info in GNU Emacs, you can evaluate each of
6992 the expressions in the usual way; the value is printed in this text
6993 after @samp{@result{}}, which you may read as ``evaluates to''.
6997 (cons 'buttercup ())
6998 @result{} (buttercup)
7002 (cons 'daisy '(buttercup))
7003 @result{} (daisy buttercup)
7007 (cons 'violet '(daisy buttercup))
7008 @result{} (violet daisy buttercup)
7012 (cons 'rose '(violet daisy buttercup))
7013 @result{} (rose violet daisy buttercup)
7018 In the first example, the empty list is shown as @code{()} and a list
7019 made up of @code{buttercup} followed by the empty list is constructed.
7020 As you can see, the empty list is not shown in the list that was
7021 constructed. All that you see is @code{(buttercup)}. The empty list is
7022 not counted as an element of a list because there is nothing in an empty
7023 list. Generally speaking, an empty list is invisible.
7025 The second example, @code{(cons 'daisy '(buttercup))} constructs a new,
7026 two element list by putting @code{daisy} in front of @code{buttercup};
7027 and the third example constructs a three element list by putting
7028 @code{violet} in front of @code{daisy} and @code{buttercup}.
7031 @subsection Find the Length of a List: @code{length}
7034 You can find out how many elements there are in a list by using the Lisp
7035 function @code{length}, as in the following examples:
7039 (length '(buttercup))
7044 (length '(daisy buttercup))
7049 (length (cons 'violet '(daisy buttercup)))
7055 In the third example, the @code{cons} function is used to construct a
7056 three element list which is then passed to the @code{length} function as
7060 We can also use @code{length} to count the number of elements in an
7071 As you would expect, the number of elements in an empty list is zero.
7073 An interesting experiment is to find out what happens if you try to find
7074 the length of no list at all; that is, if you try to call @code{length}
7075 without giving it an argument, not even an empty list:
7083 What you see, if you evaluate this, is the error message
7086 Lisp error: (wrong-number-of-arguments length 0)
7090 This means that the function receives the wrong number of
7091 arguments, zero, when it expects some other number of arguments. In
7092 this case, one argument is expected, the argument being a list whose
7093 length the function is measuring. (Note that @emph{one} list is
7094 @emph{one} argument, even if the list has many elements inside it.)
7096 The part of the error message that says @samp{length} is the name of
7100 @code{length} is still a subroutine, but you need C-h f to discover that.
7102 In an earlier version:
7103 This is written with a special notation, @samp{#<subr},
7104 that indicates that the function @code{length} is one of the primitive
7105 functions written in C rather than in Emacs Lisp. (@samp{subr} is an
7106 abbreviation for ``subroutine''.) @xref{What Is a Function, , What Is a
7107 Function?, elisp , The GNU Emacs Lisp Reference Manual}, for more
7112 @section @code{nthcdr}
7115 The @code{nthcdr} function is associated with the @code{cdr} function.
7116 What it does is take the @sc{cdr} of a list repeatedly.
7118 If you take the @sc{cdr} of the list @code{(pine fir
7119 oak maple)}, you will be returned the list @code{(fir oak maple)}. If you
7120 repeat this on what was returned, you will be returned the list
7121 @code{(oak maple)}. (Of course, repeated @sc{cdr}ing on the original
7122 list will just give you the original @sc{cdr} since the function does
7123 not change the list. You need to evaluate the @sc{cdr} of the
7124 @sc{cdr} and so on.) If you continue this, eventually you will be
7125 returned an empty list, which in this case, instead of being shown as
7126 @code{()} is shown as @code{nil}.
7129 For review, here is a series of repeated @sc{cdr}s, the text following
7130 the @samp{@result{}} shows what is returned.
7134 (cdr '(pine fir oak maple))
7135 @result{}(fir oak maple)
7139 (cdr '(fir oak maple))
7140 @result{} (oak maple)
7165 You can also do several @sc{cdr}s without printing the values in
7170 (cdr (cdr '(pine fir oak maple)))
7171 @result{} (oak maple)
7176 In this example, the Lisp interpreter evaluates the innermost list first.
7177 The innermost list is quoted, so it just passes the list as it is to the
7178 innermost @code{cdr}. This @code{cdr} passes a list made up of the
7179 second and subsequent elements of the list to the outermost @code{cdr},
7180 which produces a list composed of the third and subsequent elements of
7181 the original list. In this example, the @code{cdr} function is repeated
7182 and returns a list that consists of the original list without its
7185 The @code{nthcdr} function does the same as repeating the call to
7186 @code{cdr}. In the following example, the argument 2 is passed to the
7187 function @code{nthcdr}, along with the list, and the value returned is
7188 the list without its first two items, which is exactly the same
7189 as repeating @code{cdr} twice on the list:
7193 (nthcdr 2 '(pine fir oak maple))
7194 @result{} (oak maple)
7199 Using the original four element list, we can see what happens when
7200 various numeric arguments are passed to @code{nthcdr}, including 0, 1,
7205 ;; @r{Leave the list as it was.}
7206 (nthcdr 0 '(pine fir oak maple))
7207 @result{} (pine fir oak maple)
7211 ;; @r{Return a copy without the first element.}
7212 (nthcdr 1 '(pine fir oak maple))
7213 @result{} (fir oak maple)
7217 ;; @r{Return a copy of the list without three elements.}
7218 (nthcdr 3 '(pine fir oak maple))
7223 ;; @r{Return a copy lacking all four elements.}
7224 (nthcdr 4 '(pine fir oak maple))
7229 ;; @r{Return a copy lacking all elements.}
7230 (nthcdr 5 '(pine fir oak maple))
7239 The @code{nthcdr} function takes the @sc{cdr} of a list repeatedly.
7240 The @code{nth} function takes the @sc{car} of the result returned by
7241 @code{nthcdr}. It returns the Nth element of the list.
7244 Thus, if it were not defined in C for speed, the definition of
7245 @code{nth} would be:
7250 "Returns the Nth element of LIST.
7251 N counts from zero. If LIST is not that long, nil is returned."
7252 (car (nthcdr n list)))
7257 (Originally, @code{nth} was defined in Emacs Lisp in @file{subr.el},
7258 but its definition was redone in C in the 1980s.)
7260 The @code{nth} function returns a single element of a list.
7261 This can be very convenient.
7263 Note that the elements are numbered from zero, not one. That is to
7264 say, the first element of a list, its @sc{car} is the zeroth element.
7265 This zero-based counting often bothers people who
7266 are accustomed to the first element in a list being number one, which
7274 (nth 0 '("one" "two" "three"))
7277 (nth 1 '("one" "two" "three"))
7282 It is worth mentioning that @code{nth}, like @code{nthcdr} and
7283 @code{cdr}, does not change the original list---the function is
7284 non-destructive. This is in sharp contrast to the @code{setcar} and
7285 @code{setcdr} functions.
7288 @section @code{setcar}
7291 As you might guess from their names, the @code{setcar} and @code{setcdr}
7292 functions set the @sc{car} or the @sc{cdr} of a list to a new value.
7293 They actually change the original list, unlike @code{car} and @code{cdr}
7294 which leave the original list as it was. One way to find out how this
7295 works is to experiment. We will start with the @code{setcar} function.
7298 First, we can make a list and then set the value of a variable to the
7299 list, using the @code{setq} function. Here is a list of animals:
7302 (setq animals '(antelope giraffe lion tiger))
7306 If you are reading this in Info inside of GNU Emacs, you can evaluate
7307 this expression in the usual fashion, by positioning the cursor after
7308 the expression and typing @kbd{C-x C-e}. (I'm doing this right here
7309 as I write this. This is one of the advantages of having the
7310 interpreter built into the computing environment. Incidentally, when
7311 there is nothing on the line after the final parentheses, such as a
7312 comment, point can be on the next line. Thus, if your cursor is in
7313 the first column of the next line, you do not need to move it.
7314 Indeed, Emacs permits any amount of white space after the final
7318 When we evaluate the variable @code{animals}, we see that it is bound to
7319 the list @code{(antelope giraffe lion tiger)}:
7324 @result{} (antelope giraffe lion tiger)
7329 Put another way, the variable @code{animals} points to the list
7330 @code{(antelope giraffe lion tiger)}.
7332 Next, evaluate the function @code{setcar} while passing it two
7333 arguments, the variable @code{animals} and the quoted symbol
7334 @code{hippopotamus}; this is done by writing the three element list
7335 @code{(setcar animals 'hippopotamus)} and then evaluating it in the
7339 (setcar animals 'hippopotamus)
7344 After evaluating this expression, evaluate the variable @code{animals}
7345 again. You will see that the list of animals has changed:
7350 @result{} (hippopotamus giraffe lion tiger)
7355 The first element on the list, @code{antelope} is replaced by
7356 @code{hippopotamus}.
7358 So we can see that @code{setcar} did not add a new element to the list
7359 as @code{cons} would have; it replaced @code{antelope} with
7360 @code{hippopotamus}; it @emph{changed} the list.
7363 @section @code{setcdr}
7366 The @code{setcdr} function is similar to the @code{setcar} function,
7367 except that the function replaces the second and subsequent elements of
7368 a list rather than the first element.
7370 (To see how to change the last element of a list, look ahead to
7371 @ref{kill-new function, , The @code{kill-new} function}, which uses
7372 the @code{nthcdr} and @code{setcdr} functions.)
7375 To see how this works, set the value of the variable to a list of
7376 domesticated animals by evaluating the following expression:
7379 (setq domesticated-animals '(horse cow sheep goat))
7384 If you now evaluate the list, you will be returned the list
7385 @code{(horse cow sheep goat)}:
7389 domesticated-animals
7390 @result{} (horse cow sheep goat)
7395 Next, evaluate @code{setcdr} with two arguments, the name of the
7396 variable which has a list as its value, and the list to which the
7397 @sc{cdr} of the first list will be set;
7400 (setcdr domesticated-animals '(cat dog))
7404 If you evaluate this expression, the list @code{(cat dog)} will appear
7405 in the echo area. This is the value returned by the function. The
7406 result we are interested in is the side effect, which we can see by
7407 evaluating the variable @code{domesticated-animals}:
7411 domesticated-animals
7412 @result{} (horse cat dog)
7417 Indeed, the list is changed from @code{(horse cow sheep goat)} to
7418 @code{(horse cat dog)}. The @sc{cdr} of the list is changed from
7419 @code{(cow sheep goat)} to @code{(cat dog)}.
7424 Construct a list of four birds by evaluating several expressions with
7425 @code{cons}. Find out what happens when you @code{cons} a list onto
7426 itself. Replace the first element of the list of four birds with a
7427 fish. Replace the rest of that list with a list of other fish.
7429 @node Cutting & Storing Text
7430 @chapter Cutting and Storing Text
7431 @cindex Cutting and storing text
7432 @cindex Storing and cutting text
7433 @cindex Killing text
7434 @cindex Clipping text
7435 @cindex Erasing text
7436 @cindex Deleting text
7438 Whenever you cut or clip text out of a buffer with a @dfn{kill} command in
7439 GNU Emacs, it is stored in a list and you can bring it back with a
7442 (The use of the word ``kill'' in Emacs for processes which specifically
7443 @emph{do not} destroy the values of the entities is an unfortunate
7444 historical accident. A much more appropriate word would be ``clip'' since
7445 that is what the kill commands do; they clip text out of a buffer and
7446 put it into storage from which it can be brought back. I have often
7447 been tempted to replace globally all occurrences of ``kill'' in the Emacs
7448 sources with ``clip'' and all occurrences of ``killed'' with ``clipped''.)
7451 * Storing Text:: Text is stored in a list.
7452 * zap-to-char:: Cutting out text up to a character.
7453 * kill-region:: Cutting text out of a region.
7454 * copy-region-as-kill:: A definition for copying text.
7455 * Digression into C:: Minor note on C programming language macros.
7456 * defvar:: How to give a variable an initial value.
7457 * cons & search-fwd Review::
7458 * search Exercises::
7463 @unnumberedsec Storing Text in a List
7466 When text is cut out of a buffer, it is stored on a list. Successive
7467 pieces of text are stored on the list successively, so the list might
7471 ("a piece of text" "previous piece")
7476 The function @code{cons} can be used to create a new list from a piece
7477 of text (an ``atom'', to use the jargon) and an existing list, like
7482 (cons "another piece"
7483 '("a piece of text" "previous piece"))
7489 If you evaluate this expression, a list of three elements will appear in
7493 ("another piece" "a piece of text" "previous piece")
7496 With the @code{car} and @code{nthcdr} functions, you can retrieve
7497 whichever piece of text you want. For example, in the following code,
7498 @code{nthcdr 1 @dots{}} returns the list with the first item removed;
7499 and the @code{car} returns the first element of that remainder---the
7500 second element of the original list:
7504 (car (nthcdr 1 '("another piece"
7507 @result{} "a piece of text"
7511 The actual functions in Emacs are more complex than this, of course.
7512 The code for cutting and retrieving text has to be written so that
7513 Emacs can figure out which element in the list you want---the first,
7514 second, third, or whatever. In addition, when you get to the end of
7515 the list, Emacs should give you the first element of the list, rather
7516 than nothing at all.
7518 The list that holds the pieces of text is called the @dfn{kill ring}.
7519 This chapter leads up to a description of the kill ring and how it is
7520 used by first tracing how the @code{zap-to-char} function works. This
7521 function calls a function that invokes a function that
7522 manipulates the kill ring. Thus, before reaching the mountains, we
7523 climb the foothills.
7525 A subsequent chapter describes how text that is cut from the buffer is
7526 retrieved. @xref{Yanking, , Yanking Text Back}.
7529 @section @code{zap-to-char}
7532 Let us look at the interactive @code{zap-to-char} function.
7535 * Complete zap-to-char:: The complete implementation.
7536 * zap-to-char interactive:: A three part interactive expression.
7537 * zap-to-char body:: A short overview.
7538 * search-forward:: How to search for a string.
7539 * progn:: The @code{progn} special form.
7540 * Summing up zap-to-char:: Using @code{point} and @code{search-forward}.
7544 @node Complete zap-to-char
7545 @unnumberedsubsec The Complete @code{zap-to-char} Implementation
7548 The @code{zap-to-char} function removes the text in the region between
7549 the location of the cursor (i.e., of point) up to and including the
7550 next occurrence of a specified character. The text that
7551 @code{zap-to-char} removes is put in the kill ring; and it can be
7552 retrieved from the kill ring by typing @kbd{C-y} (@code{yank}). If
7553 the command is given an argument, it removes text through that number
7554 of occurrences. Thus, if the cursor were at the beginning of this
7555 sentence and the character were @samp{s}, @samp{Thus} would be
7556 removed. If the argument were two, @samp{Thus, if the curs} would be
7557 removed, up to and including the @samp{s} in @samp{cursor}.
7559 If the specified character is not found, @code{zap-to-char} will say
7560 ``Search failed'', tell you the character you typed, and not remove
7563 In order to determine how much text to remove, @code{zap-to-char} uses
7564 a search function. Searches are used extensively in code that
7565 manipulates text, and we will focus attention on them as well as on the
7569 @c GNU Emacs version 19
7570 (defun zap-to-char (arg char) ; version 19 implementation
7571 "Kill up to and including ARG'th occurrence of CHAR.
7572 Goes backward if ARG is negative; error if CHAR not found."
7573 (interactive "*p\ncZap to char: ")
7574 (kill-region (point)
7577 (char-to-string char) nil nil arg)
7582 Here is the complete text of the version 22 implementation of the function:
7587 (defun zap-to-char (arg char)
7588 "Kill up to and including ARG'th occurrence of CHAR.
7589 Case is ignored if `case-fold-search' is non-nil in the current buffer.
7590 Goes backward if ARG is negative; error if CHAR not found."
7591 (interactive "p\ncZap to char: ")
7592 (if (char-table-p translation-table-for-input)
7593 (setq char (or (aref translation-table-for-input char) char)))
7594 (kill-region (point) (progn
7595 (search-forward (char-to-string char)
7601 The documentation is thorough. You do need to know the jargon meaning
7602 of the word ``kill''.
7604 @cindex curved quotes
7605 @cindex curly quotes
7606 The version 22 documentation string for @code{zap-to-char} uses ASCII
7607 grave accent and apostrophe to quote a symbol, so it appears as
7608 @t{`case-fold-search'}. This quoting style was inspired by 1970s-era
7609 displays in which grave accent and apostrophe were often mirror images
7610 suitable for use as quotes. On most modern displays this is no longer
7611 true, and when these two ASCII characters appear in documentation
7612 strings or diagnostic message formats, Emacs typically transliterates
7613 them to curved single quotes, so that the abovequoted symbol appears
7614 as @t{‘case-fold-search’}. Source-code strings can also simply use
7615 curved quotes directly.
7617 @node zap-to-char interactive
7618 @subsection The @code{interactive} Expression
7621 The interactive expression in the @code{zap-to-char} command looks like
7625 (interactive "p\ncZap to char: ")
7628 The part within quotation marks, @code{"p\ncZap to char:@: "}, specifies
7629 two different things. First, and most simply, is the @samp{p}.
7630 This part is separated from the next part by a newline, @samp{\n}.
7631 The @samp{p} means that the first argument to the function will be
7632 passed the value of a @dfn{processed prefix}. The prefix argument is
7633 passed by typing @kbd{C-u} and a number, or @kbd{M-} and a number. If
7634 the function is called interactively without a prefix, 1 is passed to
7637 The second part of @code{"p\ncZap to char:@: "} is
7638 @samp{cZap to char:@: }. In this part, the lower case @samp{c}
7639 indicates that @code{interactive} expects a prompt and that the
7640 argument will be a character. The prompt follows the @samp{c} and is
7641 the string @samp{Zap to char:@: } (with a space after the colon to
7644 What all this does is prepare the arguments to @code{zap-to-char} so they
7645 are of the right type, and give the user a prompt.
7647 In a read-only buffer, the @code{zap-to-char} function copies the text
7648 to the kill ring, but does not remove it. The echo area displays a
7649 message saying that the buffer is read-only. Also, the terminal may
7650 beep or blink at you.
7652 @node zap-to-char body
7653 @subsection The Body of @code{zap-to-char}
7655 The body of the @code{zap-to-char} function contains the code that
7656 kills (that is, removes) the text in the region from the current
7657 position of the cursor up to and including the specified character.
7659 The first part of the code looks like this:
7662 (if (char-table-p translation-table-for-input)
7663 (setq char (or (aref translation-table-for-input char) char)))
7664 (kill-region (point) (progn
7665 (search-forward (char-to-string char) nil nil arg)
7670 @code{char-table-p} is an hitherto unseen function. It determines
7671 whether its argument is a character table. When it is, it sets the
7672 character passed to @code{zap-to-char} to one of them, if that
7673 character exists, or to the character itself. (This becomes important
7674 for certain characters in non-European languages. The @code{aref}
7675 function extracts an element from an array. It is an array-specific
7676 function that is not described in this document. @xref{Arrays, ,
7677 Arrays, elisp, The GNU Emacs Lisp Reference Manual}.)
7680 @code{(point)} is the current position of the cursor.
7682 The next part of the code is an expression using @code{progn}. The body
7683 of the @code{progn} consists of calls to @code{search-forward} and
7686 It is easier to understand how @code{progn} works after learning about
7687 @code{search-forward}, so we will look at @code{search-forward} and
7688 then at @code{progn}.
7690 @node search-forward
7691 @subsection The @code{search-forward} Function
7692 @findex search-forward
7694 The @code{search-forward} function is used to locate the
7695 zapped-for-character in @code{zap-to-char}. If the search is
7696 successful, @code{search-forward} leaves point immediately after the
7697 last character in the target string. (In @code{zap-to-char}, the
7698 target string is just one character long. @code{zap-to-char} uses the
7699 function @code{char-to-string} to ensure that the computer treats that
7700 character as a string.) If the search is backwards,
7701 @code{search-forward} leaves point just before the first character in
7702 the target. Also, @code{search-forward} returns @code{t} for true.
7703 (Moving point is therefore a side effect.)
7706 In @code{zap-to-char}, the @code{search-forward} function looks like this:
7709 (search-forward (char-to-string char) nil nil arg)
7712 The @code{search-forward} function takes four arguments:
7716 The first argument is the target, what is searched for. This must be a
7717 string, such as @samp{"z"}.
7719 As it happens, the argument passed to @code{zap-to-char} is a single
7720 character. Because of the way computers are built, the Lisp
7721 interpreter may treat a single character as being different from a
7722 string of characters. Inside the computer, a single character has a
7723 different electronic format than a string of one character. (A single
7724 character can often be recorded in the computer using exactly one
7725 byte; but a string may be longer, and the computer needs to be ready
7726 for this.) Since the @code{search-forward} function searches for a
7727 string, the character that the @code{zap-to-char} function receives as
7728 its argument must be converted inside the computer from one format to
7729 the other; otherwise the @code{search-forward} function will fail.
7730 The @code{char-to-string} function is used to make this conversion.
7733 The second argument bounds the search; it is specified as a position in
7734 the buffer. In this case, the search can go to the end of the buffer,
7735 so no bound is set and the second argument is @code{nil}.
7738 The third argument tells the function what it should do if the search
7739 fails---it can signal an error (and print a message) or it can return
7740 @code{nil}. A @code{nil} as the third argument causes the function to
7741 signal an error when the search fails.
7744 The fourth argument to @code{search-forward} is the repeat count---how
7745 many occurrences of the string to look for. This argument is optional
7746 and if the function is called without a repeat count, this argument is
7747 passed the value 1. If this argument is negative, the search goes
7752 In template form, a @code{search-forward} expression looks like this:
7756 (search-forward "@var{target-string}"
7757 @var{limit-of-search}
7758 @var{what-to-do-if-search-fails}
7763 We will look at @code{progn} next.
7766 @subsection The @code{progn} Special Form
7769 @code{progn} is a special form that causes each of its arguments to be
7770 evaluated in sequence and then returns the value of the last one. The
7771 preceding expressions are evaluated only for the side effects they
7772 perform. The values produced by them are discarded.
7775 The template for a @code{progn} expression is very simple:
7784 In @code{zap-to-char}, the @code{progn} expression has to do two things:
7785 put point in exactly the right position; and return the location of
7786 point so that @code{kill-region} will know how far to kill to.
7788 The first argument to the @code{progn} is @code{search-forward}. When
7789 @code{search-forward} finds the string, the function leaves point
7790 immediately after the last character in the target string. (In this
7791 case the target string is just one character long.) If the search is
7792 backwards, @code{search-forward} leaves point just before the first
7793 character in the target. The movement of point is a side effect.
7795 The second and last argument to @code{progn} is the expression
7796 @code{(point)}. This expression returns the value of point, which in
7797 this case will be the location to which it has been moved by
7798 @code{search-forward}. (In the source, a line that tells the function
7799 to go to the previous character, if it is going forward, was commented
7800 out in 1999; I don't remember whether that feature or mis-feature was
7801 ever a part of the distributed source.) The value of @code{point} is
7802 returned by the @code{progn} expression and is passed to
7803 @code{kill-region} as @code{kill-region}'s second argument.
7805 @node Summing up zap-to-char
7806 @subsection Summing up @code{zap-to-char}
7808 Now that we have seen how @code{search-forward} and @code{progn} work,
7809 we can see how the @code{zap-to-char} function works as a whole.
7811 The first argument to @code{kill-region} is the position of the cursor
7812 when the @code{zap-to-char} command is given---the value of point at
7813 that time. Within the @code{progn}, the search function then moves
7814 point to just after the zapped-to-character and @code{point} returns the
7815 value of this location. The @code{kill-region} function puts together
7816 these two values of point, the first one as the beginning of the region
7817 and the second one as the end of the region, and removes the region.
7819 The @code{progn} special form is necessary because the
7820 @code{kill-region} command takes two arguments; and it would fail if
7821 @code{search-forward} and @code{point} expressions were written in
7822 sequence as two additional arguments. The @code{progn} expression is
7823 a single argument to @code{kill-region} and returns the one value that
7824 @code{kill-region} needs for its second argument.
7827 @section @code{kill-region}
7830 The @code{zap-to-char} function uses the @code{kill-region} function.
7831 This function clips text from a region and copies that text to
7832 the kill ring, from which it may be retrieved.
7837 (defun kill-region (beg end &optional yank-handler)
7838 "Kill (\"cut\") text between point and mark.
7839 This deletes the text from the buffer and saves it in the kill ring.
7840 The command \\[yank] can retrieve it from there.
7841 \(If you want to kill and then yank immediately, use \\[kill-ring-save].)
7843 If you want to append the killed region to the last killed text,
7844 use \\[append-next-kill] before \\[kill-region].
7846 If the buffer is read-only, Emacs will beep and refrain from deleting
7847 the text, but put the text in the kill ring anyway. This means that
7848 you can use the killing commands to copy text from a read-only buffer.
7850 This is the primitive for programs to kill text (as opposed to deleting it).
7851 Supply two arguments, character positions indicating the stretch of text
7853 Any command that calls this function is a \"kill command\".
7854 If the previous command was also a kill command,
7855 the text killed this time appends to the text killed last time
7856 to make one entry in the kill ring.
7858 In Lisp code, optional third arg YANK-HANDLER, if non-nil,
7859 specifies the yank-handler text property to be set on the killed
7860 text. See `insert-for-yank'."
7861 ;; Pass point first, then mark, because the order matters
7862 ;; when calling kill-append.
7863 (interactive (list (point) (mark)))
7864 (unless (and beg end)
7865 (error "The mark is not set now, so there is no region"))
7867 (let ((string (filter-buffer-substring beg end t)))
7868 (when string ;STRING is nil if BEG = END
7869 ;; Add that string to the kill ring, one way or another.
7870 (if (eq last-command 'kill-region)
7871 (kill-append string (< end beg) yank-handler)
7872 (kill-new string nil yank-handler)))
7873 (when (or string (eq last-command 'kill-region))
7874 (setq this-command 'kill-region))
7876 ((buffer-read-only text-read-only)
7877 ;; The code above failed because the buffer, or some of the characters
7878 ;; in the region, are read-only.
7879 ;; We should beep, in case the user just isn't aware of this.
7880 ;; However, there's no harm in putting
7881 ;; the region's text in the kill ring, anyway.
7882 (copy-region-as-kill beg end)
7883 ;; Set this-command now, so it will be set even if we get an error.
7884 (setq this-command 'kill-region)
7885 ;; This should barf, if appropriate, and give us the correct error.
7886 (if kill-read-only-ok
7887 (progn (message "Read only text copied to kill ring") nil)
7888 ;; Signal an error if the buffer is read-only.
7889 (barf-if-buffer-read-only)
7890 ;; If the buffer isn't read-only, the text is.
7891 (signal 'text-read-only (list (current-buffer)))))))
7894 The Emacs 22 version of that function uses @code{condition-case} and
7895 @code{copy-region-as-kill}, both of which we will explain.
7896 @code{condition-case} is an important special form.
7898 In essence, the @code{kill-region} function calls
7899 @code{condition-case}, which takes three arguments. In this function,
7900 the first argument does nothing. The second argument contains the
7901 code that does the work when all goes well. The third argument
7902 contains the code that is called in the event of an error.
7905 * Complete kill-region:: The function definition.
7906 * condition-case:: Dealing with a problem.
7911 @node Complete kill-region
7912 @unnumberedsubsec The Complete @code{kill-region} Definition
7916 We will go through the @code{condition-case} code in a moment. First,
7917 let us look at the definition of @code{kill-region}, with comments
7923 (defun kill-region (beg end)
7924 "Kill (\"cut\") text between point and mark.
7925 This deletes the text from the buffer and saves it in the kill ring.
7926 The command \\[yank] can retrieve it from there. @dots{} "
7930 ;; @bullet{} Since order matters, pass point first.
7931 (interactive (list (point) (mark)))
7932 ;; @bullet{} And tell us if we cannot cut the text.
7933 ;; 'unless' is an 'if' without a then-part.
7934 (unless (and beg end)
7935 (error "The mark is not set now, so there is no region"))
7939 ;; @bullet{} 'condition-case' takes three arguments.
7940 ;; If the first argument is nil, as it is here,
7941 ;; information about the error signal is not
7942 ;; stored for use by another function.
7947 ;; @bullet{} The second argument to 'condition-case' tells the
7948 ;; Lisp interpreter what to do when all goes well.
7952 ;; It starts with a 'let' function that extracts the string
7953 ;; and tests whether it exists. If so (that is what the
7954 ;; 'when' checks), it calls an 'if' function that determines
7955 ;; whether the previous command was another call to
7956 ;; 'kill-region'; if it was, then the new text is appended to
7957 ;; the previous text; if not, then a different function,
7958 ;; 'kill-new', is called.
7962 ;; The 'kill-append' function concatenates the new string and
7963 ;; the old. The 'kill-new' function inserts text into a new
7964 ;; item in the kill ring.
7968 ;; 'when' is an 'if' without an else-part. The second 'when'
7969 ;; again checks whether the current string exists; in
7970 ;; addition, it checks whether the previous command was
7971 ;; another call to 'kill-region'. If one or the other
7972 ;; condition is true, then it sets the current command to
7973 ;; be 'kill-region'.
7976 (let ((string (filter-buffer-substring beg end t)))
7977 (when string ;STRING is nil if BEG = END
7978 ;; Add that string to the kill ring, one way or another.
7979 (if (eq last-command 'kill-region)
7982 ;; @minus{} 'yank-handler' is an optional argument to
7983 ;; 'kill-region' that tells the 'kill-append' and
7984 ;; 'kill-new' functions how deal with properties
7985 ;; added to the text, such as 'bold' or 'italics'.
7986 (kill-append string (< end beg) yank-handler)
7987 (kill-new string nil yank-handler)))
7988 (when (or string (eq last-command 'kill-region))
7989 (setq this-command 'kill-region))
7994 ;; @bullet{} The third argument to 'condition-case' tells the interpreter
7995 ;; what to do with an error.
7998 ;; The third argument has a conditions part and a body part.
7999 ;; If the conditions are met (in this case,
8000 ;; if text or buffer are read-only)
8001 ;; then the body is executed.
8004 ;; The first part of the third argument is the following:
8005 ((buffer-read-only text-read-only) ;; the if-part
8006 ;; @dots{} the then-part
8007 (copy-region-as-kill beg end)
8010 ;; Next, also as part of the then-part, set this-command, so
8011 ;; it will be set in an error
8012 (setq this-command 'kill-region)
8013 ;; Finally, in the then-part, send a message if you may copy
8014 ;; the text to the kill ring without signaling an error, but
8015 ;; don't if you may not.
8018 (if kill-read-only-ok
8019 (progn (message "Read only text copied to kill ring") nil)
8020 (barf-if-buffer-read-only)
8021 ;; If the buffer isn't read-only, the text is.
8022 (signal 'text-read-only (list (current-buffer)))))
8030 (defun kill-region (beg end)
8031 "Kill between point and mark.
8032 The text is deleted but saved in the kill ring."
8037 ;; 1. 'condition-case' takes three arguments.
8038 ;; If the first argument is nil, as it is here,
8039 ;; information about the error signal is not
8040 ;; stored for use by another function.
8045 ;; 2. The second argument to 'condition-case'
8046 ;; tells the Lisp interpreter what to do when all goes well.
8050 ;; The 'delete-and-extract-region' function usually does the
8051 ;; work. If the beginning and ending of the region are both
8052 ;; the same, then the variable 'string' will be empty, or nil
8053 (let ((string (delete-and-extract-region beg end)))
8057 ;; 'when' is an 'if' clause that cannot take an 'else-part'.
8058 ;; Emacs normally sets the value of 'last-command' to the
8059 ;; previous command.
8062 ;; 'kill-append' concatenates the new string and the old.
8063 ;; 'kill-new' inserts text into a new item in the kill ring.
8065 (if (eq last-command 'kill-region)
8066 ;; if true, prepend string
8067 (kill-append string (< end beg))
8069 (setq this-command 'kill-region))
8073 ;; 3. The third argument to 'condition-case' tells the interpreter
8074 ;; what to do with an error.
8077 ;; The third argument has a conditions part and a body part.
8078 ;; If the conditions are met (in this case,
8079 ;; if text or buffer are read-only)
8080 ;; then the body is executed.
8083 ((buffer-read-only text-read-only) ;; this is the if-part
8085 (copy-region-as-kill beg end)
8088 (if kill-read-only-ok ;; usually this variable is nil
8089 (message "Read only text copied to kill ring")
8090 ;; or else, signal an error if the buffer is read-only;
8091 (barf-if-buffer-read-only)
8092 ;; and, in any case, signal that the text is read-only.
8093 (signal 'text-read-only (list (current-buffer)))))))
8098 @node condition-case
8099 @subsection @code{condition-case}
8100 @findex condition-case
8102 As we have seen earlier (@pxref{Making Errors, , Generate an Error
8103 Message}), when the Emacs Lisp interpreter has trouble evaluating an
8104 expression, it provides you with help; in the jargon, this is called
8105 ``signaling an error''. Usually, the computer stops the program and
8106 shows you a message.
8108 However, some programs undertake complicated actions. They should not
8109 simply stop on an error. In the @code{kill-region} function, the most
8110 likely error is that you will try to kill text that is read-only and
8111 cannot be removed. So the @code{kill-region} function contains code
8112 to handle this circumstance. This code, which makes up the body of
8113 the @code{kill-region} function, is inside of a @code{condition-case}
8117 The template for @code{condition-case} looks like this:
8124 @var{error-handler}@dots{})
8128 The second argument, @var{bodyform}, is straightforward. The
8129 @code{condition-case} special form causes the Lisp interpreter to
8130 evaluate the code in @var{bodyform}. If no error occurs, the special
8131 form returns the code's value and produces the side-effects, if any.
8133 In short, the @var{bodyform} part of a @code{condition-case}
8134 expression determines what should happen when everything works
8137 However, if an error occurs, among its other actions, the function
8138 generating the error signal will define one or more error condition
8141 An error handler is the third argument to @code{condition-case}.
8142 An error handler has two parts, a @var{condition-name} and a
8143 @var{body}. If the @var{condition-name} part of an error handler
8144 matches a condition name generated by an error, then the @var{body}
8145 part of the error handler is run.
8147 As you will expect, the @var{condition-name} part of an error handler
8148 may be either a single condition name or a list of condition names.
8150 Also, a complete @code{condition-case} expression may contain more
8151 than one error handler. When an error occurs, the first applicable
8154 Lastly, the first argument to the @code{condition-case} expression,
8155 the @var{var} argument, is sometimes bound to a variable that
8156 contains information about the error. However, if that argument is
8157 nil, as is the case in @code{kill-region}, that information is
8161 In brief, in the @code{kill-region} function, the code
8162 @code{condition-case} works like this:
8166 @var{If no errors}, @var{run only this code}
8167 @var{but}, @var{if errors}, @var{run this other code}.
8174 copy-region-as-kill is short, 12 lines, and uses
8175 filter-buffer-substring, which is longer, 39 lines
8176 and has delete-and-extract-region in it.
8177 delete-and-extract-region is written in C.
8179 see Initializing a Variable with @code{defvar}
8181 Initializing a Variable with @code{defvar} includes line 8350
8185 @subsection Lisp macro
8189 The part of the @code{condition-case} expression that is evaluated in
8190 the expectation that all goes well has a @code{when}. The code uses
8191 @code{when} to determine whether the @code{string} variable points to
8194 A @code{when} expression is simply a programmers' convenience. It is
8195 an @code{if} without the possibility of an else clause. In your mind,
8196 you can replace @code{when} with @code{if} and understand what goes
8197 on. That is what the Lisp interpreter does.
8199 Technically speaking, @code{when} is a Lisp macro. A Lisp macro
8200 enables you to define new control constructs and other language
8201 features. It tells the interpreter how to compute another Lisp
8202 expression which will in turn compute the value. In this case, the
8203 other expression is an @code{if} expression.
8205 The @code{kill-region} function definition also has an @code{unless}
8206 macro; it is the converse of @code{when}. The @code{unless} macro is
8207 an @code{if} without a then clause
8209 For more about Lisp macros, see @ref{Macros, , Macros, elisp, The GNU
8210 Emacs Lisp Reference Manual}. The C programming language also
8211 provides macros. These are different, but also useful.
8214 We will briefly look at C macros in
8215 @ref{Digression into C}.
8219 Regarding the @code{when} macro, in the @code{condition-case}
8220 expression, when the string has content, then another conditional
8221 expression is executed. This is an @code{if} with both a then-part
8226 (if (eq last-command 'kill-region)
8227 (kill-append string (< end beg) yank-handler)
8228 (kill-new string nil yank-handler))
8232 The then-part is evaluated if the previous command was another call to
8233 @code{kill-region}; if not, the else-part is evaluated.
8235 @code{yank-handler} is an optional argument to @code{kill-region} that
8236 tells the @code{kill-append} and @code{kill-new} functions how deal
8237 with properties added to the text, such as bold or italics.
8239 @code{last-command} is a variable that comes with Emacs that we have
8240 not seen before. Normally, whenever a function is executed, Emacs
8241 sets the value of @code{last-command} to the previous command.
8244 In this segment of the definition, the @code{if} expression checks
8245 whether the previous command was @code{kill-region}. If it was,
8248 (kill-append string (< end beg) yank-handler)
8252 concatenates a copy of the newly clipped text to the just previously
8253 clipped text in the kill ring.
8255 @node copy-region-as-kill
8256 @section @code{copy-region-as-kill}
8257 @findex copy-region-as-kill
8260 The @code{copy-region-as-kill} function copies a region of text from a
8261 buffer and (via either @code{kill-append} or @code{kill-new}) saves it
8262 in the @code{kill-ring}.
8264 If you call @code{copy-region-as-kill} immediately after a
8265 @code{kill-region} command, Emacs appends the newly copied text to the
8266 previously copied text. This means that if you yank back the text, you
8267 get it all, from both this and the previous operation. On the other
8268 hand, if some other command precedes the @code{copy-region-as-kill},
8269 the function copies the text into a separate entry in the kill ring.
8272 * Complete copy-region-as-kill:: The complete function definition.
8273 * copy-region-as-kill body:: The body of @code{copy-region-as-kill}.
8277 @node Complete copy-region-as-kill
8278 @unnumberedsubsec The complete @code{copy-region-as-kill} function definition
8282 Here is the complete text of the version 22 @code{copy-region-as-kill}
8287 (defun copy-region-as-kill (beg end)
8288 "Save the region as if killed, but don't kill it.
8289 In Transient Mark mode, deactivate the mark.
8290 If `interprogram-cut-function' is non-nil, also save the text for a window
8291 system cut and paste."
8295 (if (eq last-command 'kill-region)
8296 (kill-append (filter-buffer-substring beg end) (< end beg))
8297 (kill-new (filter-buffer-substring beg end)))
8300 (if transient-mark-mode
8301 (setq deactivate-mark t))
8307 As usual, this function can be divided into its component parts:
8311 (defun copy-region-as-kill (@var{argument-list})
8312 "@var{documentation}@dots{}"
8318 The arguments are @code{beg} and @code{end} and the function is
8319 interactive with @code{"r"}, so the two arguments must refer to the
8320 beginning and end of the region. If you have been reading through this
8321 document from the beginning, understanding these parts of a function is
8322 almost becoming routine.
8324 The documentation is somewhat confusing unless you remember that the
8325 word ``kill'' has a meaning different from usual. The Transient Mark
8326 and @code{interprogram-cut-function} comments explain certain
8329 After you once set a mark, a buffer always contains a region. If you
8330 wish, you can use Transient Mark mode to highlight the region
8331 temporarily. (No one wants to highlight the region all the time, so
8332 Transient Mark mode highlights it only at appropriate times. Many
8333 people turn off Transient Mark mode, so the region is never
8336 Also, a windowing system allows you to copy, cut, and paste among
8337 different programs. In the X windowing system, for example, the
8338 @code{interprogram-cut-function} function is @code{x-select-text},
8339 which works with the windowing system's equivalent of the Emacs kill
8342 The body of the @code{copy-region-as-kill} function starts with an
8343 @code{if} clause. What this clause does is distinguish between two
8344 different situations: whether or not this command is executed
8345 immediately after a previous @code{kill-region} command. In the first
8346 case, the new region is appended to the previously copied text.
8347 Otherwise, it is inserted into the beginning of the kill ring as a
8348 separate piece of text from the previous piece.
8350 The last two lines of the function prevent the region from lighting up
8351 if Transient Mark mode is turned on.
8353 The body of @code{copy-region-as-kill} merits discussion in detail.
8355 @node copy-region-as-kill body
8356 @subsection The Body of @code{copy-region-as-kill}
8358 The @code{copy-region-as-kill} function works in much the same way as
8359 the @code{kill-region} function. Both are written so that two or more
8360 kills in a row combine their text into a single entry. If you yank
8361 back the text from the kill ring, you get it all in one piece.
8362 Moreover, kills that kill forward from the current position of the
8363 cursor are added to the end of the previously copied text and commands
8364 that copy text backwards add it to the beginning of the previously
8365 copied text. This way, the words in the text stay in the proper
8368 Like @code{kill-region}, the @code{copy-region-as-kill} function makes
8369 use of the @code{last-command} variable that keeps track of the
8370 previous Emacs command.
8373 * last-command & this-command::
8374 * kill-append function::
8375 * kill-new function::
8379 @node last-command & this-command
8380 @unnumberedsubsubsec @code{last-command} and @code{this-command}
8383 Normally, whenever a function is executed, Emacs sets the value of
8384 @code{this-command} to the function being executed (which in this case
8385 would be @code{copy-region-as-kill}). At the same time, Emacs sets
8386 the value of @code{last-command} to the previous value of
8387 @code{this-command}.
8389 In the first part of the body of the @code{copy-region-as-kill}
8390 function, an @code{if} expression determines whether the value of
8391 @code{last-command} is @code{kill-region}. If so, the then-part of
8392 the @code{if} expression is evaluated; it uses the @code{kill-append}
8393 function to concatenate the text copied at this call to the function
8394 with the text already in the first element (the @sc{car}) of the kill
8395 ring. On the other hand, if the value of @code{last-command} is not
8396 @code{kill-region}, then the @code{copy-region-as-kill} function
8397 attaches a new element to the kill ring using the @code{kill-new}
8401 The @code{if} expression reads as follows; it uses @code{eq}:
8405 (if (eq last-command 'kill-region)
8407 (kill-append (filter-buffer-substring beg end) (< end beg))
8409 (kill-new (filter-buffer-substring beg end)))
8413 @findex filter-buffer-substring
8414 (The @code{filter-buffer-substring} function returns a filtered
8415 substring of the buffer, if any. Optionally---the arguments are not
8416 here, so neither is done---the function may delete the initial text or
8417 return the text without its properties; this function is a replacement
8418 for the older @code{buffer-substring} function, which came before text
8419 properties were implemented.)
8421 @findex eq @r{(example of use)}
8423 The @code{eq} function tests whether its first argument is the same Lisp
8424 object as its second argument. The @code{eq} function is similar to the
8425 @code{equal} function in that it is used to test for equality, but
8426 differs in that it determines whether two representations are actually
8427 the same object inside the computer, but with different names.
8428 @code{equal} determines whether the structure and contents of two
8429 expressions are the same.
8431 If the previous command was @code{kill-region}, then the Emacs Lisp
8432 interpreter calls the @code{kill-append} function
8434 @node kill-append function
8435 @unnumberedsubsubsec The @code{kill-append} function
8439 The @code{kill-append} function looks like this:
8444 (defun kill-append (string before-p &optional yank-handler)
8445 "Append STRING to the end of the latest kill in the kill ring.
8446 If BEFORE-P is non-nil, prepend STRING to the kill.
8448 (let* ((cur (car kill-ring)))
8449 (kill-new (if before-p (concat string cur) (concat cur string))
8450 (or (= (length cur) 0)
8452 (get-text-property 0 'yank-handler cur)))
8459 (defun kill-append (string before-p)
8460 "Append STRING to the end of the latest kill in the kill ring.
8461 If BEFORE-P is non-nil, prepend STRING to the kill.
8462 If `interprogram-cut-function' is set, pass the resulting kill to
8464 (kill-new (if before-p
8465 (concat string (car kill-ring))
8466 (concat (car kill-ring) string))
8471 The @code{kill-append} function is fairly straightforward. It uses
8472 the @code{kill-new} function, which we will discuss in more detail in
8475 (Also, the function provides an optional argument called
8476 @code{yank-handler}; when invoked, this argument tells the function
8477 how to deal with properties added to the text, such as bold or
8480 @c !!! bug in GNU Emacs 22 version of kill-append ?
8481 It has a @code{let*} function to set the value of the first element of
8482 the kill ring to @code{cur}. (I do not know why the function does not
8483 use @code{let} instead; only one value is set in the expression.
8484 Perhaps this is a bug that produces no problems?)
8486 Consider the conditional that is one of the two arguments to
8487 @code{kill-new}. It uses @code{concat} to concatenate the new text to
8488 the @sc{car} of the kill ring. Whether it prepends or appends the
8489 text depends on the results of an @code{if} expression:
8493 (if before-p ; @r{if-part}
8494 (concat string cur) ; @r{then-part}
8495 (concat cur string)) ; @r{else-part}
8500 If the region being killed is before the region that was killed in the
8501 last command, then it should be prepended before the material that was
8502 saved in the previous kill; and conversely, if the killed text follows
8503 what was just killed, it should be appended after the previous text.
8504 The @code{if} expression depends on the predicate @code{before-p} to
8505 decide whether the newly saved text should be put before or after the
8506 previously saved text.
8508 The symbol @code{before-p} is the name of one of the arguments to
8509 @code{kill-append}. When the @code{kill-append} function is
8510 evaluated, it is bound to the value returned by evaluating the actual
8511 argument. In this case, this is the expression @code{(< end beg)}.
8512 This expression does not directly determine whether the killed text in
8513 this command is located before or after the kill text of the last
8514 command; what it does is determine whether the value of the variable
8515 @code{end} is less than the value of the variable @code{beg}. If it
8516 is, it means that the user is most likely heading towards the
8517 beginning of the buffer. Also, the result of evaluating the predicate
8518 expression, @code{(< end beg)}, will be true and the text will be
8519 prepended before the previous text. On the other hand, if the value of
8520 the variable @code{end} is greater than the value of the variable
8521 @code{beg}, the text will be appended after the previous text.
8524 When the newly saved text will be prepended, then the string with the new
8525 text will be concatenated before the old text:
8533 But if the text will be appended, it will be concatenated
8537 (concat cur string))
8540 To understand how this works, we first need to review the
8541 @code{concat} function. The @code{concat} function links together or
8542 unites two strings of text. The result is a string. For example:
8546 (concat "abc" "def")
8552 (car '("first element" "second element")))
8553 @result{} "new first element"
8556 '("first element" "second element")) " modified")
8557 @result{} "first element modified"
8561 We can now make sense of @code{kill-append}: it modifies the contents
8562 of the kill ring. The kill ring is a list, each element of which is
8563 saved text. The @code{kill-append} function uses the @code{kill-new}
8564 function which in turn uses the @code{setcar} function.
8566 @node kill-new function
8567 @unnumberedsubsubsec The @code{kill-new} function
8571 In version 22 the @code{kill-new} function looks like this:
8575 (defun kill-new (string &optional replace yank-handler)
8576 "Make STRING the latest kill in the kill ring.
8577 Set `kill-ring-yank-pointer' to point to it.
8579 If `interprogram-cut-function' is non-nil, apply it to STRING.
8580 Optional second argument REPLACE non-nil means that STRING will replace
8581 the front of the kill ring, rather than being added to the list.
8585 (if (> (length string) 0)
8587 (put-text-property 0 (length string)
8588 'yank-handler yank-handler string))
8590 (signal 'args-out-of-range
8591 (list string "yank-handler specified for empty string"))))
8594 (if (fboundp 'menu-bar-update-yank-menu)
8595 (menu-bar-update-yank-menu string (and replace (car kill-ring))))
8598 (if (and replace kill-ring)
8599 (setcar kill-ring string)
8600 (push string kill-ring)
8601 (if (> (length kill-ring) kill-ring-max)
8602 (setcdr (nthcdr (1- kill-ring-max) kill-ring) nil)))
8605 (setq kill-ring-yank-pointer kill-ring)
8606 (if interprogram-cut-function
8607 (funcall interprogram-cut-function string (not replace))))
8612 (defun kill-new (string &optional replace)
8613 "Make STRING the latest kill in the kill ring.
8614 Set the kill-ring-yank pointer to point to it.
8615 If `interprogram-cut-function' is non-nil, apply it to STRING.
8616 Optional second argument REPLACE non-nil means that STRING will replace
8617 the front of the kill ring, rather than being added to the list."
8618 (and (fboundp 'menu-bar-update-yank-menu)
8619 (menu-bar-update-yank-menu string (and replace (car kill-ring))))
8620 (if (and replace kill-ring)
8621 (setcar kill-ring string)
8622 (setq kill-ring (cons string kill-ring))
8623 (if (> (length kill-ring) kill-ring-max)
8624 (setcdr (nthcdr (1- kill-ring-max) kill-ring) nil)))
8625 (setq kill-ring-yank-pointer kill-ring)
8626 (if interprogram-cut-function
8627 (funcall interprogram-cut-function string (not replace))))
8630 (Notice that the function is not interactive.)
8632 As usual, we can look at this function in parts.
8634 The function definition has an optional @code{yank-handler} argument,
8635 which when invoked tells the function how to deal with properties
8636 added to the text, such as bold or italics. We will skip that.
8639 The first line of the documentation makes sense:
8642 Make STRING the latest kill in the kill ring.
8646 Let's skip over the rest of the documentation for the moment.
8649 Also, let's skip over the initial @code{if} expression and those lines
8650 of code involving @code{menu-bar-update-yank-menu}. We will explain
8654 The critical lines are these:
8658 (if (and replace kill-ring)
8660 (setcar kill-ring string)
8664 (push string kill-ring)
8667 (if (> (length kill-ring) kill-ring-max)
8668 ;; @r{avoid overly long kill ring}
8669 (setcdr (nthcdr (1- kill-ring-max) kill-ring) nil)))
8672 (setq kill-ring-yank-pointer kill-ring)
8673 (if interprogram-cut-function
8674 (funcall interprogram-cut-function string (not replace))))
8678 The conditional test is @w{@code{(and replace kill-ring)}}.
8679 This will be true when two conditions are met: the kill ring has
8680 something in it, and the @code{replace} variable is true.
8683 When the @code{kill-append} function sets @code{replace} to be true
8684 and when the kill ring has at least one item in it, the @code{setcar}
8685 expression is executed:
8688 (setcar kill-ring string)
8691 The @code{setcar} function actually changes the first element of the
8692 @code{kill-ring} list to the value of @code{string}. It replaces the
8696 On the other hand, if the kill ring is empty, or replace is false, the
8697 else-part of the condition is executed:
8700 (push string kill-ring)
8705 @code{push} puts its first argument onto the second. It is similar to
8709 (setq kill-ring (cons string kill-ring))
8717 (add-to-list kill-ring string)
8721 When it is false, the expression first constructs a new version of the
8722 kill ring by prepending @code{string} to the existing kill ring as a
8723 new element (that is what the @code{push} does). Then it executes a
8724 second @code{if} clause. This second @code{if} clause keeps the kill
8725 ring from growing too long.
8727 Let's look at these two expressions in order.
8729 The @code{push} line of the else-part sets the new value of the kill
8730 ring to what results from adding the string being killed to the old
8733 We can see how this works with an example.
8739 (setq example-list '("here is a clause" "another clause"))
8744 After evaluating this expression with @kbd{C-x C-e}, you can evaluate
8745 @code{example-list} and see what it returns:
8750 @result{} ("here is a clause" "another clause")
8756 Now, we can add a new element on to this list by evaluating the
8757 following expression:
8758 @findex push, @r{example}
8761 (push "a third clause" example-list)
8766 When we evaluate @code{example-list}, we find its value is:
8771 @result{} ("a third clause" "here is a clause" "another clause")
8776 Thus, the third clause is added to the list by @code{push}.
8779 Now for the second part of the @code{if} clause. This expression
8780 keeps the kill ring from growing too long. It looks like this:
8784 (if (> (length kill-ring) kill-ring-max)
8785 (setcdr (nthcdr (1- kill-ring-max) kill-ring) nil))
8789 The code checks whether the length of the kill ring is greater than
8790 the maximum permitted length. This is the value of
8791 @code{kill-ring-max} (which is 60, by default). If the length of the
8792 kill ring is too long, then this code sets the last element of the
8793 kill ring to @code{nil}. It does this by using two functions,
8794 @code{nthcdr} and @code{setcdr}.
8796 We looked at @code{setcdr} earlier (@pxref{setcdr, , @code{setcdr}}).
8797 It sets the @sc{cdr} of a list, just as @code{setcar} sets the
8798 @sc{car} of a list. In this case, however, @code{setcdr} will not be
8799 setting the @sc{cdr} of the whole kill ring; the @code{nthcdr}
8800 function is used to cause it to set the @sc{cdr} of the next to last
8801 element of the kill ring---this means that since the @sc{cdr} of the
8802 next to last element is the last element of the kill ring, it will set
8803 the last element of the kill ring.
8805 @findex nthcdr, @r{example}
8806 The @code{nthcdr} function works by repeatedly taking the @sc{cdr} of a
8807 list---it takes the @sc{cdr} of the @sc{cdr} of the @sc{cdr}
8808 @dots{} It does this @var{N} times and returns the results.
8809 (@xref{nthcdr, , @code{nthcdr}}.)
8811 @findex setcdr, @r{example}
8812 Thus, if we had a four element list that was supposed to be three
8813 elements long, we could set the @sc{cdr} of the next to last element
8814 to @code{nil}, and thereby shorten the list. (If you set the last
8815 element to some other value than @code{nil}, which you could do, then
8816 you would not have shortened the list. @xref{setcdr, ,
8819 You can see shortening by evaluating the following three expressions
8820 in turn. First set the value of @code{trees} to @code{(maple oak pine
8821 birch)}, then set the @sc{cdr} of its second @sc{cdr} to @code{nil}
8822 and then find the value of @code{trees}:
8826 (setq trees '(maple oak pine birch))
8827 @result{} (maple oak pine birch)
8831 (setcdr (nthcdr 2 trees) nil)
8835 @result{} (maple oak pine)
8840 (The value returned by the @code{setcdr} expression is @code{nil} since
8841 that is what the @sc{cdr} is set to.)
8843 To repeat, in @code{kill-new}, the @code{nthcdr} function takes the
8844 @sc{cdr} a number of times that is one less than the maximum permitted
8845 size of the kill ring and @code{setcdr} sets the @sc{cdr} of that
8846 element (which will be the rest of the elements in the kill ring) to
8847 @code{nil}. This prevents the kill ring from growing too long.
8850 The next to last expression in the @code{kill-new} function is
8853 (setq kill-ring-yank-pointer kill-ring)
8856 The @code{kill-ring-yank-pointer} is a global variable that is set to be
8857 the @code{kill-ring}.
8859 Even though the @code{kill-ring-yank-pointer} is called a
8860 @samp{pointer}, it is a variable just like the kill ring. However, the
8861 name has been chosen to help humans understand how the variable is used.
8864 Now, to return to an early expression in the body of the function:
8868 (if (fboundp 'menu-bar-update-yank-menu)
8869 (menu-bar-update-yank-menu string (and replace (car kill-ring))))
8874 It starts with an @code{if} expression
8876 In this case, the expression tests first to see whether
8877 @code{menu-bar-update-yank-menu} exists as a function, and if so,
8878 calls it. The @code{fboundp} function returns true if the symbol it
8879 is testing has a function definition that is not void. If the
8880 symbol's function definition were void, we would receive an error
8881 message, as we did when we created errors intentionally (@pxref{Making
8882 Errors, , Generate an Error Message}).
8885 The then-part contains an expression whose first element is the
8886 function @code{and}.
8889 The @code{and} special form evaluates each of its arguments until one
8890 of the arguments returns a value of @code{nil}, in which case the
8891 @code{and} expression returns @code{nil}; however, if none of the
8892 arguments returns a value of @code{nil}, the value resulting from
8893 evaluating the last argument is returned. (Since such a value is not
8894 @code{nil}, it is considered true in Emacs Lisp.) In other words, an
8895 @code{and} expression returns a true value only if all its arguments
8896 are true. (@xref{Second Buffer Related Review}.)
8898 The expression determines whether the second argument to
8899 @code{menu-bar-update-yank-menu} is true or not.
8901 ;; If we're supposed to be extending an existing string, and that
8902 ;; string really is at the front of the menu, then update it in place.
8905 @code{menu-bar-update-yank-menu} is one of the functions that make it
8906 possible to use the ``Select and Paste'' menu in the Edit item of a menu
8907 bar; using a mouse, you can look at the various pieces of text you
8908 have saved and select one piece to paste.
8910 The last expression in the @code{kill-new} function adds the newly
8911 copied string to whatever facility exists for copying and pasting
8912 among different programs running in a windowing system. In the X
8913 Windowing system, for example, the @code{x-select-text} function takes
8914 the string and stores it in memory operated by X@. You can paste the
8915 string in another program, such as an Xterm.
8918 The expression looks like this:
8922 (if interprogram-cut-function
8923 (funcall interprogram-cut-function string (not replace))))
8927 If an @code{interprogram-cut-function} exists, then Emacs executes
8928 @code{funcall}, which in turn calls its first argument as a function
8929 and passes the remaining arguments to it. (Incidentally, as far as I
8930 can see, this @code{if} expression could be replaced by an @code{and}
8931 expression similar to the one in the first part of the function.)
8933 We are not going to discuss windowing systems and other programs
8934 further, but merely note that this is a mechanism that enables GNU
8935 Emacs to work easily and well with other programs.
8937 This code for placing text in the kill ring, either concatenated with
8938 an existing element or as a new element, leads us to the code for
8939 bringing back text that has been cut out of the buffer---the yank
8940 commands. However, before discussing the yank commands, it is better
8941 to learn how lists are implemented in a computer. This will make
8942 clear such mysteries as the use of the term ``pointer''. But before
8943 that, we will digress into C.
8946 @c is this true in Emacs 22? Does not seems to be
8948 (If the @w{@code{(< end beg))}}
8949 expression is true, @code{kill-append} prepends the string to the just
8950 previously clipped text. For a detailed discussion, see
8951 @ref{kill-append function, , The @code{kill-append} function}.)
8953 If you then yank back the text, i.e., paste it, you get both
8954 pieces of text at once. That way, if you delete two words in a row,
8955 and then yank them back, you get both words, in their proper order,
8956 with one yank. (The @w{@code{(< end beg))}} expression makes sure the
8959 On the other hand, if the previous command is not @code{kill-region},
8960 then the @code{kill-new} function is called, which adds the text to
8961 the kill ring as the latest item, and sets the
8962 @code{kill-ring-yank-pointer} variable to point to it.
8966 @c Evidently, changed for Emacs 22. The zap-to-char command does not
8967 @c use the delete-and-extract-region function
8969 2006 Oct 26, the Digression into C is now OK but should come after
8970 copy-region-as-kill and filter-buffer-substring
8974 copy-region-as-kill is short, 12 lines, and uses
8975 filter-buffer-substring, which is longer, 39 lines
8976 and has delete-and-extract-region in it.
8977 delete-and-extract-region is written in C.
8979 see Initializing a Variable with @code{defvar}
8982 @node Digression into C
8983 @section Digression into C
8984 @findex delete-and-extract-region
8985 @cindex C, a digression into
8986 @cindex Digression into C
8988 The @code{copy-region-as-kill} function (@pxref{copy-region-as-kill, ,
8989 @code{copy-region-as-kill}}) uses the @code{filter-buffer-substring}
8990 function, which in turn uses the @code{delete-and-extract-region}
8991 function. It removes the contents of a region and you cannot get them
8994 Unlike the other code discussed here, the
8995 @code{delete-and-extract-region} function is not written in Emacs
8996 Lisp; it is written in C and is one of the primitives of the GNU Emacs
8997 system. Since it is very simple, I will digress briefly from Lisp and
9000 @c GNU Emacs 24 in src/editfns.c
9001 @c the DEFUN for delete-and-extract-region
9004 Like many of the other Emacs primitives,
9005 @code{delete-and-extract-region} is written as an instance of a C
9006 macro, a macro being a template for code. The complete macro looks
9011 DEFUN ("delete-and-extract-region", Fdelete_and_extract_region,
9012 Sdelete_and_extract_region, 2, 2, 0,
9013 doc: /* Delete the text between START and END and return it. */)
9014 (Lisp_Object start, Lisp_Object end)
9016 validate_region (&start, &end);
9017 if (XINT (start) == XINT (end))
9018 return empty_unibyte_string;
9019 return del_range_1 (XINT (start), XINT (end), 1, 1);
9024 Without going into the details of the macro writing process, let me
9025 point out that this macro starts with the word @code{DEFUN}. The word
9026 @code{DEFUN} was chosen since the code serves the same purpose as
9027 @code{defun} does in Lisp. (The @code{DEFUN} C macro is defined in
9028 @file{emacs/src/lisp.h}.)
9030 The word @code{DEFUN} is followed by seven parts inside of
9035 The first part is the name given to the function in Lisp,
9036 @code{delete-and-extract-region}.
9039 The second part is the name of the function in C,
9040 @code{Fdelete_and_extract_region}. By convention, it starts with
9041 @samp{F}. Since C does not use hyphens in names, underscores are used
9045 The third part is the name for the C constant structure that records
9046 information on this function for internal use. It is the name of the
9047 function in C but begins with an @samp{S} instead of an @samp{F}.
9050 The fourth and fifth parts specify the minimum and maximum number of
9051 arguments the function can have. This function demands exactly 2
9055 The sixth part is nearly like the argument that follows the
9056 @code{interactive} declaration in a function written in Lisp: a letter
9057 followed, perhaps, by a prompt. The only difference from Lisp is
9058 when the macro is called with no arguments. Then you write a @code{0}
9059 (which is a null string), as in this macro.
9061 If you were to specify arguments, you would place them between
9062 quotation marks. The C macro for @code{goto-char} includes
9063 @code{"NGoto char: "} in this position to indicate that the function
9064 expects a raw prefix, in this case, a numerical location in a buffer,
9065 and provides a prompt.
9068 The seventh part is a documentation string, just like the one for a
9069 function written in Emacs Lisp. This is written as a C comment. (When
9070 you build Emacs, the program @command{lib-src/make-docfile} extracts
9071 these comments and uses them to make the documentation.)
9075 In a C macro, the formal parameters come next, with a statement of
9076 what kind of object they are, followed by the body
9077 of the macro. For @code{delete-and-extract-region} the body
9078 consists of the following four lines:
9082 validate_region (&start, &end);
9083 if (XINT (start) == XINT (end))
9084 return empty_unibyte_string;
9085 return del_range_1 (XINT (start), XINT (end), 1, 1);
9089 The @code{validate_region} function checks whether the values
9090 passed as the beginning and end of the region are the proper type and
9091 are within range. If the beginning and end positions are the same,
9092 then return an empty string.
9094 The @code{del_range_1} function actually deletes the text. It is a
9095 complex function we will not look into. It updates the buffer and
9096 does other things. However, it is worth looking at the two arguments
9097 passed to @code{del_range_1}. These are @w{@code{XINT (start)}} and
9098 @w{@code{XINT (end)}}.
9100 As far as the C language is concerned, @code{start} and @code{end} are
9101 two integers that mark the beginning and end of the region to be
9102 deleted@footnote{More precisely, and requiring more expert knowledge
9103 to understand, the two integers are of type @code{Lisp_Object}, which can
9104 also be a C union instead of an integer type.}.
9106 Integer widths depend on the machine, and are typically 32 or 64 bits.
9107 A few of the bits are used to specify the type of information; the
9108 remaining bits are used as content.
9110 @samp{XINT} is a C macro that extracts the relevant number from the
9111 longer collection of bits; the type bits are discarded.
9114 The command in @code{delete-and-extract-region} looks like this:
9117 del_range_1 (XINT (start), XINT (end), 1, 1);
9121 It deletes the region between the beginning position, @code{start},
9122 and the ending position, @code{end}.
9124 From the point of view of the person writing Lisp, Emacs is all very
9125 simple; but hidden underneath is a great deal of complexity to make it
9129 @section Initializing a Variable with @code{defvar}
9131 @cindex Initializing a variable
9132 @cindex Variable initialization
9137 copy-region-as-kill is short, 12 lines, and uses
9138 filter-buffer-substring, which is longer, 39 lines
9139 and has delete-and-extract-region in it.
9140 delete-and-extract-region is written in C.
9142 see Initializing a Variable with @code{defvar}
9146 The @code{copy-region-as-kill} function is written in Emacs Lisp. Two
9147 functions within it, @code{kill-append} and @code{kill-new}, copy a
9148 region in a buffer and save it in a variable called the
9149 @code{kill-ring}. This section describes how the @code{kill-ring}
9150 variable is created and initialized using the @code{defvar} special
9153 (Again we note that the term @code{kill-ring} is a misnomer. The text
9154 that is clipped out of the buffer can be brought back; it is not a ring
9155 of corpses, but a ring of resurrectable text.)
9157 In Emacs Lisp, a variable such as the @code{kill-ring} is created and
9158 given an initial value by using the @code{defvar} special form. The
9159 name comes from ``define variable''.
9161 The @code{defvar} special form is similar to @code{setq} in that it sets
9162 the value of a variable. It is unlike @code{setq} in two ways: first,
9163 it only sets the value of the variable if the variable does not already
9164 have a value. If the variable already has a value, @code{defvar} does
9165 not override the existing value. Second, @code{defvar} has a
9166 documentation string.
9168 (There is a related macro, @code{defcustom}, designed for variables
9169 that people customize. It has more features than @code{defvar}.
9170 (@xref{defcustom, , Setting Variables with @code{defcustom}}.)
9173 * See variable current value::
9174 * defvar and asterisk::
9178 @node See variable current value
9179 @unnumberedsubsec Seeing the Current Value of a Variable
9182 You can see the current value of a variable, any variable, by using
9183 the @code{describe-variable} function, which is usually invoked by
9184 typing @kbd{C-h v}. If you type @kbd{C-h v} and then @code{kill-ring}
9185 (followed by @key{RET}) when prompted, you will see what is in your
9186 current kill ring---this may be quite a lot! Conversely, if you have
9187 been doing nothing this Emacs session except read this document, you
9188 may have nothing in it. Also, you will see the documentation for
9194 List of killed text sequences.
9195 Since the kill ring is supposed to interact nicely with cut-and-paste
9196 facilities offered by window systems, use of this variable should
9199 interact nicely with `interprogram-cut-function' and
9200 `interprogram-paste-function'. The functions `kill-new',
9201 `kill-append', and `current-kill' are supposed to implement this
9202 interaction; you may want to use them instead of manipulating the kill
9208 The kill ring is defined by a @code{defvar} in the following way:
9212 (defvar kill-ring nil
9213 "List of killed text sequences.
9219 In this variable definition, the variable is given an initial value of
9220 @code{nil}, which makes sense, since if you have saved nothing, you want
9221 nothing back if you give a @code{yank} command. The documentation
9222 string is written just like the documentation string of a @code{defun}.
9223 As with the documentation string of the @code{defun}, the first line of
9224 the documentation should be a complete sentence, since some commands,
9225 like @code{apropos}, print only the first line of documentation.
9226 Succeeding lines should not be indented; otherwise they look odd when
9227 you use @kbd{C-h v} (@code{describe-variable}).
9229 @node defvar and asterisk
9230 @subsection @code{defvar} and an asterisk
9231 @findex defvar @r{for a user customizable variable}
9232 @findex defvar @r{with an asterisk}
9234 In the past, Emacs used the @code{defvar} special form both for
9235 internal variables that you would not expect a user to change and for
9236 variables that you do expect a user to change. Although you can still
9237 use @code{defvar} for user customizable variables, please use
9238 @code{defcustom} instead, since it provides a path into
9239 the Customization commands. (@xref{defcustom, , Specifying Variables
9240 using @code{defcustom}}.)
9242 When you specified a variable using the @code{defvar} special form,
9243 you could distinguish a variable that a user might want to change from
9244 others by typing an asterisk, @samp{*}, in the first column of its
9245 documentation string. For example:
9249 (defvar shell-command-default-error-buffer nil
9250 "*Buffer name for `shell-command' @dots{} error output.
9255 @findex set-variable
9257 You could (and still can) use the @code{set-variable} command to
9258 change the value of @code{shell-command-default-error-buffer}
9259 temporarily. However, options set using @code{set-variable} are set
9260 only for the duration of your editing session. The new values are not
9261 saved between sessions. Each time Emacs starts, it reads the original
9262 value, unless you change the value within your @file{.emacs} file,
9263 either by setting it manually or by using @code{customize}.
9264 @xref{Emacs Initialization, , Your @file{.emacs} File}.
9266 For me, the major use of the @code{set-variable} command is to suggest
9267 variables that I might want to set in my @file{.emacs} file. There
9268 are now more than 700 such variables, far too many to remember
9269 readily. Fortunately, you can press @key{TAB} after calling the
9270 @code{M-x set-variable} command to see the list of variables.
9271 (@xref{Examining, , Examining and Setting Variables, emacs,
9272 The GNU Emacs Manual}.)
9275 @node cons & search-fwd Review
9278 Here is a brief summary of some recently introduced functions.
9283 @code{car} returns the first element of a list; @code{cdr} returns the
9284 second and subsequent elements of a list.
9291 (car '(1 2 3 4 5 6 7))
9293 (cdr '(1 2 3 4 5 6 7))
9294 @result{} (2 3 4 5 6 7)
9299 @code{cons} constructs a list by prepending its first argument to its
9313 @code{funcall} evaluates its first argument as a function. It passes
9314 its remaining arguments to its first argument.
9317 Return the result of taking @sc{cdr} @var{n} times on a list.
9325 The ``rest of the rest'', as it were.
9332 (nthcdr 3 '(1 2 3 4 5 6 7))
9339 @code{setcar} changes the first element of a list; @code{setcdr}
9340 changes the second and subsequent elements of a list.
9347 (setq triple '(1 2 3))
9354 (setcdr triple '("foo" "bar"))
9357 @result{} (37 "foo" "bar")
9362 Evaluate each argument in sequence and then return the value of the
9375 @item save-restriction
9376 Record whatever narrowing is in effect in the current buffer, if any,
9377 and restore that narrowing after evaluating the arguments.
9379 @item search-forward
9380 Search for a string, and if the string is found, move point. With a
9381 regular expression, use the similar @code{re-search-forward}.
9382 (@xref{Regexp Search, , Regular Expression Searches}, for an
9383 explanation of regular expression patterns and searches.)
9387 @code{search-forward} and @code{re-search-forward} take four
9392 The string or regular expression to search for.
9395 Optionally, the limit of the search.
9398 Optionally, what to do if the search fails, return @code{nil} or an
9402 Optionally, how many times to repeat the search; if negative, the
9403 search goes backwards.
9407 @itemx delete-and-extract-region
9408 @itemx copy-region-as-kill
9410 @code{kill-region} cuts the text between point and mark from the
9411 buffer and stores that text in the kill ring, so you can get it back
9414 @code{copy-region-as-kill} copies the text between point and mark into
9415 the kill ring, from which you can get it by yanking. The function
9416 does not cut or remove the text from the buffer.
9419 @code{delete-and-extract-region} removes the text between point and
9420 mark from the buffer and throws it away. You cannot get it back.
9421 (This is not an interactive command.)
9424 @node search Exercises
9425 @section Searching Exercises
9429 Write an interactive function that searches for a string. If the
9430 search finds the string, leave point after it and display a message
9431 that says ``Found!''. (Do not use @code{search-forward} for the name
9432 of this function; if you do, you will overwrite the existing version of
9433 @code{search-forward} that comes with Emacs. Use a name such as
9434 @code{test-search} instead.)
9437 Write a function that prints the third element of the kill ring in the
9438 echo area, if any; if the kill ring does not contain a third element,
9439 print an appropriate message.
9442 @node List Implementation
9443 @chapter How Lists are Implemented
9444 @cindex Lists in a computer
9446 In Lisp, atoms are recorded in a straightforward fashion; if the
9447 implementation is not straightforward in practice, it is, nonetheless,
9448 straightforward in theory. The atom @samp{rose}, for example, is
9449 recorded as the four contiguous letters @samp{r}, @samp{o}, @samp{s},
9450 @samp{e}. A list, on the other hand, is kept differently. The mechanism
9451 is equally simple, but it takes a moment to get used to the idea. A
9452 list is kept using a series of pairs of pointers. In the series, the
9453 first pointer in each pair points to an atom or to another list, and the
9454 second pointer in each pair points to the next pair, or to the symbol
9455 @code{nil}, which marks the end of the list.
9457 A pointer itself is quite simply the electronic address of what is
9458 pointed to. Hence, a list is kept as a series of electronic addresses.
9461 * Lists diagrammed::
9462 * Symbols as Chest:: Exploring a powerful metaphor.
9467 @node Lists diagrammed
9468 @unnumberedsec Lists diagrammed
9471 For example, the list @code{(rose violet buttercup)} has three elements,
9472 @samp{rose}, @samp{violet}, and @samp{buttercup}. In the computer, the
9473 electronic address of @samp{rose} is recorded in a segment of computer
9474 memory along with the address that gives the electronic address of where
9475 the atom @samp{violet} is located; and that address (the one that tells
9476 where @samp{violet} is located) is kept along with an address that tells
9477 where the address for the atom @samp{buttercup} is located.
9480 This sounds more complicated than it is and is easier seen in a diagram:
9482 @c clear print-postscript-figures
9483 @c !!! cons-cell-diagram #1
9487 ___ ___ ___ ___ ___ ___
9488 |___|___|--> |___|___|--> |___|___|--> nil
9491 --> rose --> violet --> buttercup
9495 @ifset print-postscript-figures
9498 @center @image{cons-1}
9502 @ifclear print-postscript-figures
9506 ___ ___ ___ ___ ___ ___
9507 |___|___|--> |___|___|--> |___|___|--> nil
9510 --> rose --> violet --> buttercup
9517 In the diagram, each box represents a word of computer memory that
9518 holds a Lisp object, usually in the form of a memory address. The boxes,
9519 i.e., the addresses, are in pairs. Each arrow points to what the address
9520 is the address of, either an atom or another pair of addresses. The
9521 first box is the electronic address of @samp{rose} and the arrow points
9522 to @samp{rose}; the second box is the address of the next pair of boxes,
9523 the first part of which is the address of @samp{violet} and the second
9524 part of which is the address of the next pair. The very last box
9525 points to the symbol @code{nil}, which marks the end of the list.
9528 When a variable is set to a list with a function such as @code{setq},
9529 it stores the address of the first box in the variable. Thus,
9530 evaluation of the expression
9533 (setq bouquet '(rose violet buttercup))
9538 creates a situation like this:
9540 @c cons-cell-diagram #2
9546 | ___ ___ ___ ___ ___ ___
9547 --> |___|___|--> |___|___|--> |___|___|--> nil
9550 --> rose --> violet --> buttercup
9554 @ifset print-postscript-figures
9557 @center @image{cons-2}
9561 @ifclear print-postscript-figures
9567 | ___ ___ ___ ___ ___ ___
9568 --> |___|___|--> |___|___|--> |___|___|--> nil
9571 --> rose --> violet --> buttercup
9578 In this example, the symbol @code{bouquet} holds the address of the first
9582 This same list can be illustrated in a different sort of box notation
9585 @c cons-cell-diagram #2a
9591 | -------------- --------------- ----------------
9592 | | car | cdr | | car | cdr | | car | cdr |
9593 -->| rose | o------->| violet | o------->| butter- | nil |
9594 | | | | | | | cup | |
9595 -------------- --------------- ----------------
9599 @ifset print-postscript-figures
9602 @center @image{cons-2a}
9606 @ifclear print-postscript-figures
9612 | -------------- --------------- ----------------
9613 | | car | cdr | | car | cdr | | car | cdr |
9614 -->| rose | o------->| violet | o------->| butter- | nil |
9615 | | | | | | | cup | |
9616 -------------- --------------- ----------------
9622 (Symbols consist of more than pairs of addresses, but the structure of
9623 a symbol is made up of addresses. Indeed, the symbol @code{bouquet}
9624 consists of a group of address-boxes, one of which is the address of
9625 the printed word @samp{bouquet}, a second of which is the address of a
9626 function definition attached to the symbol, if any, a third of which
9627 is the address of the first pair of address-boxes for the list
9628 @code{(rose violet buttercup)}, and so on. Here we are showing that
9629 the symbol's third address-box points to the first pair of
9630 address-boxes for the list.)
9632 If a symbol is set to the @sc{cdr} of a list, the list itself is not
9633 changed; the symbol simply has an address further down the list. (In
9634 the jargon, @sc{car} and @sc{cdr} are ``non-destructive''.) Thus,
9635 evaluation of the following expression
9638 (setq flowers (cdr bouquet))
9645 @c cons-cell-diagram #3
9652 | ___ ___ | ___ ___ ___ ___
9653 --> | | | --> | | | | | |
9654 |___|___|----> |___|___|--> |___|___|--> nil
9657 --> rose --> violet --> buttercup
9662 @ifset print-postscript-figures
9665 @center @image{cons-3}
9669 @ifclear print-postscript-figures
9676 | ___ ___ | ___ ___ ___ ___
9677 --> | | | --> | | | | | |
9678 |___|___|----> |___|___|--> |___|___|--> nil
9681 --> rose --> violet --> buttercup
9689 The value of @code{flowers} is @code{(violet buttercup)}, which is
9690 to say, the symbol @code{flowers} holds the address of the pair of
9691 address-boxes, the first of which holds the address of @code{violet},
9692 and the second of which holds the address of @code{buttercup}.
9694 A pair of address-boxes is called a @dfn{cons cell} or @dfn{dotted
9695 pair}. @xref{Cons Cell Type, , Cons Cell and List Types, elisp, The GNU Emacs Lisp
9696 Reference Manual}, and @ref{Dotted Pair Notation, , Dotted Pair
9697 Notation, elisp, The GNU Emacs Lisp Reference Manual}, for more
9698 information about cons cells and dotted pairs.
9701 The function @code{cons} adds a new pair of addresses to the front of
9702 a series of addresses like that shown above. For example, evaluating
9706 (setq bouquet (cons 'lily bouquet))
9713 @c cons-cell-diagram #4
9720 | ___ ___ ___ ___ | ___ ___ ___ ___
9721 --> | | | | | | --> | | | | | |
9722 |___|___|----> |___|___|----> |___|___|---->|___|___|--> nil
9725 --> lily --> rose --> violet --> buttercup
9730 @ifset print-postscript-figures
9733 @center @image{cons-4}
9737 @ifclear print-postscript-figures
9744 | ___ ___ ___ ___ | ___ ___ ___ ___
9745 --> | | | | | | --> | | | | | |
9746 |___|___|----> |___|___|----> |___|___|---->|___|___|--> nil
9749 --> lily --> rose --> violet --> buttercup
9758 However, this does not change the value of the symbol
9759 @code{flowers}, as you can see by evaluating the following,
9762 (eq (cdr (cdr bouquet)) flowers)
9766 which returns @code{t} for true.
9768 Until it is reset, @code{flowers} still has the value
9769 @code{(violet buttercup)}; that is, it has the address of the cons
9770 cell whose first address is of @code{violet}. Also, this does not
9771 alter any of the pre-existing cons cells; they are all still there.
9773 Thus, in Lisp, to get the @sc{cdr} of a list, you just get the address
9774 of the next cons cell in the series; to get the @sc{car} of a list,
9775 you get the address of the first element of the list; to @code{cons} a
9776 new element on a list, you add a new cons cell to the front of the list.
9777 That is all there is to it! The underlying structure of Lisp is
9780 And what does the last address in a series of cons cells refer to? It
9781 is the address of the empty list, of @code{nil}.
9783 In summary, when a Lisp variable is set to a value, it is provided with
9784 the address of the list to which the variable refers.
9786 @node Symbols as Chest
9787 @section Symbols as a Chest of Drawers
9788 @cindex Symbols as a Chest of Drawers
9789 @cindex Chest of Drawers, metaphor for a symbol
9790 @cindex Drawers, Chest of, metaphor for a symbol
9792 In an earlier section, I suggested that you might imagine a symbol as
9793 being a chest of drawers. The function definition is put in one
9794 drawer, the value in another, and so on. What is put in the drawer
9795 holding the value can be changed without affecting the contents of the
9796 drawer holding the function definition, and vice versa.
9798 Actually, what is put in each drawer is the address of the value or
9799 function definition. It is as if you found an old chest in the attic,
9800 and in one of its drawers you found a map giving you directions to
9801 where the buried treasure lies.
9803 (In addition to its name, symbol definition, and variable value, a
9804 symbol has a drawer for a @dfn{property list} which can be used to
9805 record other information. Property lists are not discussed here; see
9806 @ref{Property Lists, , Property Lists, elisp, The GNU Emacs Lisp
9810 Here is a fanciful representation:
9812 @c chest-of-drawers diagram
9817 Chest of Drawers Contents of Drawers
9821 ---------------------
9822 | directions to | [map to]
9823 | symbol name | bouquet
9825 +---------------------+
9827 | symbol definition | [none]
9829 +---------------------+
9830 | directions to | [map to]
9831 | variable value | (rose violet buttercup)
9833 +---------------------+
9835 | property list | [not described here]
9837 +---------------------+
9843 @ifset print-postscript-figures
9846 @center @image{drawers}
9850 @ifclear print-postscript-figures
9855 Chest of Drawers Contents of Drawers
9859 ---------------------
9860 | directions to | [map to]
9861 | symbol name | bouquet
9863 +---------------------+
9865 | symbol definition | [none]
9867 +---------------------+
9868 | directions to | [map to]
9869 | variable value | (rose violet buttercup)
9871 +---------------------+
9873 | property list | [not described here]
9875 +---------------------+
9886 Set @code{flowers} to @code{violet} and @code{buttercup}. Cons two
9887 more flowers on to this list and set this new list to
9888 @code{more-flowers}. Set the @sc{car} of @code{flowers} to a fish.
9889 What does the @code{more-flowers} list now contain?
9892 @chapter Yanking Text Back
9894 @cindex Text retrieval
9895 @cindex Retrieving text
9896 @cindex Pasting text
9898 Whenever you cut text out of a buffer with a kill command in GNU Emacs,
9899 you can bring it back with a yank command. The text that is cut out of
9900 the buffer is put in the kill ring and the yank commands insert the
9901 appropriate contents of the kill ring back into a buffer (not necessarily
9902 the original buffer).
9904 A simple @kbd{C-y} (@code{yank}) command inserts the first item from
9905 the kill ring into the current buffer. If the @kbd{C-y} command is
9906 followed immediately by @kbd{M-y}, the first element is replaced by
9907 the second element. Successive @kbd{M-y} commands replace the second
9908 element with the third, fourth, or fifth element, and so on. When the
9909 last element in the kill ring is reached, it is replaced by the first
9910 element and the cycle is repeated. (Thus the kill ring is called a
9911 ``ring'' rather than just a ``list''. However, the actual data structure
9912 that holds the text is a list.
9913 @xref{Kill Ring, , Handling the Kill Ring}, for the details of how the
9914 list is handled as a ring.)
9917 * Kill Ring Overview::
9918 * kill-ring-yank-pointer:: The kill ring is a list.
9919 * yank nthcdr Exercises:: The @code{kill-ring-yank-pointer} variable.
9922 @node Kill Ring Overview
9923 @section Kill Ring Overview
9924 @cindex Kill ring overview
9926 The kill ring is a list of textual strings. This is what it looks like:
9929 ("some text" "a different piece of text" "yet more text")
9932 If this were the contents of my kill ring and I pressed @kbd{C-y}, the
9933 string of characters saying @samp{some text} would be inserted in this
9934 buffer where my cursor is located.
9936 The @code{yank} command is also used for duplicating text by copying it.
9937 The copied text is not cut from the buffer, but a copy of it is put on the
9938 kill ring and is inserted by yanking it back.
9940 Three functions are used for bringing text back from the kill ring:
9941 @code{yank}, which is usually bound to @kbd{C-y}; @code{yank-pop},
9942 which is usually bound to @kbd{M-y}; and @code{rotate-yank-pointer},
9943 which is used by the two other functions.
9945 These functions refer to the kill ring through a variable called the
9946 @code{kill-ring-yank-pointer}. Indeed, the insertion code for both the
9947 @code{yank} and @code{yank-pop} functions is:
9950 (insert (car kill-ring-yank-pointer))
9954 (Well, no more. In GNU Emacs 22, the function has been replaced by
9955 @code{insert-for-yank} which calls @code{insert-for-yank-1}
9956 repetitively for each @code{yank-handler} segment. In turn,
9957 @code{insert-for-yank-1} strips text properties from the inserted text
9958 according to @code{yank-excluded-properties}. Otherwise, it is just
9959 like @code{insert}. We will stick with plain @code{insert} since it
9960 is easier to understand.)
9962 To begin to understand how @code{yank} and @code{yank-pop} work, it is
9963 first necessary to look at the @code{kill-ring-yank-pointer} variable.
9965 @node kill-ring-yank-pointer
9966 @section The @code{kill-ring-yank-pointer} Variable
9968 @code{kill-ring-yank-pointer} is a variable, just as @code{kill-ring} is
9969 a variable. It points to something by being bound to the value of what
9970 it points to, like any other Lisp variable.
9973 Thus, if the value of the kill ring is:
9976 ("some text" "a different piece of text" "yet more text")
9981 and the @code{kill-ring-yank-pointer} points to the second clause, the
9982 value of @code{kill-ring-yank-pointer} is:
9985 ("a different piece of text" "yet more text")
9988 As explained in the previous chapter (@pxref{List Implementation}), the
9989 computer does not keep two different copies of the text being pointed to
9990 by both the @code{kill-ring} and the @code{kill-ring-yank-pointer}. The
9991 words ``a different piece of text'' and ``yet more text'' are not
9992 duplicated. Instead, the two Lisp variables point to the same pieces of
9993 text. Here is a diagram:
9995 @c cons-cell-diagram #5
9999 kill-ring kill-ring-yank-pointer
10001 | ___ ___ | ___ ___ ___ ___
10002 ---> | | | --> | | | | | |
10003 |___|___|----> |___|___|--> |___|___|--> nil
10006 | | --> "yet more text"
10008 | --> "a different piece of text"
10015 @ifset print-postscript-figures
10018 @center @image{cons-5}
10022 @ifclear print-postscript-figures
10026 kill-ring kill-ring-yank-pointer
10028 | ___ ___ | ___ ___ ___ ___
10029 ---> | | | --> | | | | | |
10030 |___|___|----> |___|___|--> |___|___|--> nil
10033 | | --> "yet more text"
10035 | --> "a different piece of text
10044 Both the variable @code{kill-ring} and the variable
10045 @code{kill-ring-yank-pointer} are pointers. But the kill ring itself is
10046 usually described as if it were actually what it is composed of. The
10047 @code{kill-ring} is spoken of as if it were the list rather than that it
10048 points to the list. Conversely, the @code{kill-ring-yank-pointer} is
10049 spoken of as pointing to a list.
10051 These two ways of talking about the same thing sound confusing at first but
10052 make sense on reflection. The kill ring is generally thought of as the
10053 complete structure of data that holds the information of what has recently
10054 been cut out of the Emacs buffers. The @code{kill-ring-yank-pointer}
10055 on the other hand, serves to indicate---that is, to point to---that part
10056 of the kill ring of which the first element (the @sc{car}) will be
10060 In GNU Emacs 22, the @code{kill-new} function calls
10062 @code{(setq kill-ring-yank-pointer kill-ring)}
10064 (defun rotate-yank-pointer (arg)
10065 "Rotate the yanking point in the kill ring.
10066 With argument, rotate that many kills forward (or backward, if negative)."
10068 (current-kill arg))
10070 (defun current-kill (n &optional do-not-move)
10071 "Rotate the yanking point by N places, and then return that kill.
10072 If N is zero, `interprogram-paste-function' is set, and calling it
10073 returns a string, then that string is added to the front of the
10074 kill ring and returned as the latest kill.
10075 If optional arg DO-NOT-MOVE is non-nil, then don't actually move the
10076 yanking point; just return the Nth kill forward."
10077 (let ((interprogram-paste (and (= n 0)
10078 interprogram-paste-function
10079 (funcall interprogram-paste-function))))
10080 (if interprogram-paste
10082 ;; Disable the interprogram cut function when we add the new
10083 ;; text to the kill ring, so Emacs doesn't try to own the
10084 ;; selection, with identical text.
10085 (let ((interprogram-cut-function nil))
10086 (kill-new interprogram-paste))
10087 interprogram-paste)
10088 (or kill-ring (error "Kill ring is empty"))
10089 (let ((ARGth-kill-element
10090 (nthcdr (mod (- n (length kill-ring-yank-pointer))
10091 (length kill-ring))
10094 (setq kill-ring-yank-pointer ARGth-kill-element))
10095 (car ARGth-kill-element)))))
10100 @node yank nthcdr Exercises
10101 @section Exercises with @code{yank} and @code{nthcdr}
10105 Using @kbd{C-h v} (@code{describe-variable}), look at the value of
10106 your kill ring. Add several items to your kill ring; look at its
10107 value again. Using @kbd{M-y} (@code{yank-pop)}, move all the way
10108 around the kill ring. How many items were in your kill ring? Find
10109 the value of @code{kill-ring-max}. Was your kill ring full, or could
10110 you have kept more blocks of text within it?
10113 Using @code{nthcdr} and @code{car}, construct a series of expressions
10114 to return the first, second, third, and fourth elements of a list.
10117 @node Loops & Recursion
10118 @chapter Loops and Recursion
10119 @cindex Loops and recursion
10120 @cindex Recursion and loops
10121 @cindex Repetition (loops)
10123 Emacs Lisp has two primary ways to cause an expression, or a series of
10124 expressions, to be evaluated repeatedly: one uses a @code{while}
10125 loop, and the other uses @dfn{recursion}.
10127 Repetition can be very valuable. For example, to move forward four
10128 sentences, you need only write a program that will move forward one
10129 sentence and then repeat the process four times. Since a computer does
10130 not get bored or tired, such repetitive action does not have the
10131 deleterious effects that excessive or the wrong kinds of repetition can
10134 People mostly write Emacs Lisp functions using @code{while} loops and
10135 their kin; but you can use recursion, which provides a very powerful
10136 way to think about and then to solve problems@footnote{You can write
10137 recursive functions to be frugal or wasteful of mental or computer
10138 resources; as it happens, methods that people find easy---that are
10139 frugal of mental resources---sometimes use considerable computer
10140 resources. Emacs was designed to run on machines that we now consider
10141 limited and its default settings are conservative. You may want to
10142 increase the values of @code{max-specpdl-size} and
10143 @code{max-lisp-eval-depth}. In my @file{.emacs} file, I set them to
10144 15 and 30 times their default value.}.
10147 * while:: Causing a stretch of code to repeat.
10149 * Recursion:: Causing a function to call itself.
10150 * Looping exercise::
10154 @section @code{while}
10158 The @code{while} special form tests whether the value returned by
10159 evaluating its first argument is true or false. This is similar to what
10160 the Lisp interpreter does with an @code{if}; what the interpreter does
10161 next, however, is different.
10163 In a @code{while} expression, if the value returned by evaluating the
10164 first argument is false, the Lisp interpreter skips the rest of the
10165 expression (the @dfn{body} of the expression) and does not evaluate it.
10166 However, if the value is true, the Lisp interpreter evaluates the body
10167 of the expression and then again tests whether the first argument to
10168 @code{while} is true or false. If the value returned by evaluating the
10169 first argument is again true, the Lisp interpreter again evaluates the
10170 body of the expression.
10173 The template for a @code{while} expression looks like this:
10177 (while @var{true-or-false-test}
10183 * Looping with while:: Repeat so long as test returns true.
10184 * Loop Example:: A @code{while} loop that uses a list.
10185 * print-elements-of-list:: Uses @code{while}, @code{car}, @code{cdr}.
10186 * Incrementing Loop:: A loop with an incrementing counter.
10187 * Incrementing Loop Details::
10188 * Decrementing Loop:: A loop with a decrementing counter.
10192 @node Looping with while
10193 @unnumberedsubsec Looping with @code{while}
10196 So long as the true-or-false-test of the @code{while} expression
10197 returns a true value when it is evaluated, the body is repeatedly
10198 evaluated. This process is called a loop since the Lisp interpreter
10199 repeats the same thing again and again, like an airplane doing a loop.
10200 When the result of evaluating the true-or-false-test is false, the
10201 Lisp interpreter does not evaluate the rest of the @code{while}
10202 expression and exits the loop.
10204 Clearly, if the value returned by evaluating the first argument to
10205 @code{while} is always true, the body following will be evaluated
10206 again and again @dots{} and again @dots{} forever. Conversely, if the
10207 value returned is never true, the expressions in the body will never
10208 be evaluated. The craft of writing a @code{while} loop consists of
10209 choosing a mechanism such that the true-or-false-test returns true
10210 just the number of times that you want the subsequent expressions to
10211 be evaluated, and then have the test return false.
10213 The value returned by evaluating a @code{while} is the value of the
10214 true-or-false-test. An interesting consequence of this is that a
10215 @code{while} loop that evaluates without error will return @code{nil}
10216 or false regardless of whether it has looped 1 or 100 times or none at
10217 all. A @code{while} expression that evaluates successfully never
10218 returns a true value! What this means is that @code{while} is always
10219 evaluated for its side effects, which is to say, the consequences of
10220 evaluating the expressions within the body of the @code{while} loop.
10221 This makes sense. It is not the mere act of looping that is desired,
10222 but the consequences of what happens when the expressions in the loop
10223 are repeatedly evaluated.
10226 @subsection A @code{while} Loop and a List
10228 A common way to control a @code{while} loop is to test whether a list
10229 has any elements. If it does, the loop is repeated; but if it does not,
10230 the repetition is ended. Since this is an important technique, we will
10231 create a short example to illustrate it.
10233 A simple way to test whether a list has elements is to evaluate the
10234 list: if it has no elements, it is an empty list and will return the
10235 empty list, @code{()}, which is a synonym for @code{nil} or false. On
10236 the other hand, a list with elements will return those elements when it
10237 is evaluated. Since Emacs Lisp considers as true any value that is not
10238 @code{nil}, a list that returns elements will test true in a
10242 For example, you can set the variable @code{empty-list} to @code{nil} by
10243 evaluating the following @code{setq} expression:
10246 (setq empty-list ())
10250 After evaluating the @code{setq} expression, you can evaluate the
10251 variable @code{empty-list} in the usual way, by placing the cursor after
10252 the symbol and typing @kbd{C-x C-e}; @code{nil} will appear in your
10259 On the other hand, if you set a variable to be a list with elements, the
10260 list will appear when you evaluate the variable, as you can see by
10261 evaluating the following two expressions:
10265 (setq animals '(gazelle giraffe lion tiger))
10271 Thus, to create a @code{while} loop that tests whether there are any
10272 items in the list @code{animals}, the first part of the loop will be
10283 When the @code{while} tests its first argument, the variable
10284 @code{animals} is evaluated. It returns a list. So long as the list
10285 has elements, the @code{while} considers the results of the test to be
10286 true; but when the list is empty, it considers the results of the test
10289 To prevent the @code{while} loop from running forever, some mechanism
10290 needs to be provided to empty the list eventually. An oft-used
10291 technique is to have one of the subsequent forms in the @code{while}
10292 expression set the value of the list to be the @sc{cdr} of the list.
10293 Each time the @code{cdr} function is evaluated, the list will be made
10294 shorter, until eventually only the empty list will be left. At this
10295 point, the test of the @code{while} loop will return false, and the
10296 arguments to the @code{while} will no longer be evaluated.
10298 For example, the list of animals bound to the variable @code{animals}
10299 can be set to be the @sc{cdr} of the original list with the
10300 following expression:
10303 (setq animals (cdr animals))
10307 If you have evaluated the previous expressions and then evaluate this
10308 expression, you will see @code{(giraffe lion tiger)} appear in the echo
10309 area. If you evaluate the expression again, @code{(lion tiger)} will
10310 appear in the echo area. If you evaluate it again and yet again,
10311 @code{(tiger)} appears and then the empty list, shown by @code{nil}.
10313 A template for a @code{while} loop that uses the @code{cdr} function
10314 repeatedly to cause the true-or-false-test eventually to test false
10319 (while @var{test-whether-list-is-empty}
10321 @var{set-list-to-cdr-of-list})
10325 This test and use of @code{cdr} can be put together in a function that
10326 goes through a list and prints each element of the list on a line of its
10329 @node print-elements-of-list
10330 @subsection An Example: @code{print-elements-of-list}
10331 @findex print-elements-of-list
10333 The @code{print-elements-of-list} function illustrates a @code{while}
10336 @cindex @file{*scratch*} buffer
10337 The function requires several lines for its output. If you are
10338 reading this in a recent instance of GNU Emacs,
10339 @c GNU Emacs 21, GNU Emacs 22, or a later version,
10340 you can evaluate the following expression inside of Info, as usual.
10342 If you are using an earlier version of Emacs, you need to copy the
10343 necessary expressions to your @file{*scratch*} buffer and evaluate
10344 them there. This is because the echo area had only one line in the
10347 You can copy the expressions by marking the beginning of the region
10348 with @kbd{C-@key{SPC}} (@code{set-mark-command}), moving the cursor to
10349 the end of the region and then copying the region using @kbd{M-w}
10350 (@code{kill-ring-save}, which calls @code{copy-region-as-kill} and
10351 then provides visual feedback). In the @file{*scratch*}
10352 buffer, you can yank the expressions back by typing @kbd{C-y}
10355 After you have copied the expressions to the @file{*scratch*} buffer,
10356 evaluate each expression in turn. Be sure to evaluate the last
10357 expression, @code{(print-elements-of-list animals)}, by typing
10358 @kbd{C-u C-x C-e}, that is, by giving an argument to
10359 @code{eval-last-sexp}. This will cause the result of the evaluation
10360 to be printed in the @file{*scratch*} buffer instead of being printed
10361 in the echo area. (Otherwise you will see something like this in your
10362 echo area: @code{^Jgazelle^J^Jgiraffe^J^Jlion^J^Jtiger^Jnil}, in which
10363 each @samp{^J} stands for a newline.)
10366 In a recent instance of GNU Emacs, you can evaluate these expressions
10367 directly in the Info buffer, and the echo area will grow to show the
10372 (setq animals '(gazelle giraffe lion tiger))
10374 (defun print-elements-of-list (list)
10375 "Print each element of LIST on a line of its own."
10378 (setq list (cdr list))))
10380 (print-elements-of-list animals)
10386 When you evaluate the three expressions in sequence, you will see
10402 Each element of the list is printed on a line of its own (that is what
10403 the function @code{print} does) and then the value returned by the
10404 function is printed. Since the last expression in the function is the
10405 @code{while} loop, and since @code{while} loops always return
10406 @code{nil}, a @code{nil} is printed after the last element of the list.
10408 @node Incrementing Loop
10409 @subsection A Loop with an Incrementing Counter
10411 A loop is not useful unless it stops when it ought. Besides
10412 controlling a loop with a list, a common way of stopping a loop is to
10413 write the first argument as a test that returns false when the correct
10414 number of repetitions are complete. This means that the loop must
10415 have a counter---an expression that counts how many times the loop
10419 @node Incrementing Loop Details
10420 @unnumberedsubsec Details of an Incrementing Loop
10423 The test for a loop with an incrementing counter can be an expression
10424 such as @code{(< count desired-number)} which returns @code{t} for
10425 true if the value of @code{count} is less than the
10426 @code{desired-number} of repetitions and @code{nil} for false if the
10427 value of @code{count} is equal to or is greater than the
10428 @code{desired-number}. The expression that increments the count can
10429 be a simple @code{setq} such as @code{(setq count (1+ count))}, where
10430 @code{1+} is a built-in function in Emacs Lisp that adds 1 to its
10431 argument. (The expression @w{@code{(1+ count)}} has the same result
10432 as @w{@code{(+ count 1)}}, but is easier for a human to read.)
10435 The template for a @code{while} loop controlled by an incrementing
10436 counter looks like this:
10440 @var{set-count-to-initial-value}
10441 (while (< count desired-number) ; @r{true-or-false-test}
10443 (setq count (1+ count))) ; @r{incrementer}
10448 Note that you need to set the initial value of @code{count}; usually it
10452 * Incrementing Example:: Counting pebbles in a triangle.
10453 * Inc Example parts:: The parts of the function definition.
10454 * Inc Example altogether:: Putting the function definition together.
10457 @node Incrementing Example
10458 @unnumberedsubsubsec Example with incrementing counter
10460 Suppose you are playing on the beach and decide to make a triangle of
10461 pebbles, putting one pebble in the first row, two in the second row,
10462 three in the third row and so on, like this:
10480 @bullet{} @bullet{}
10481 @bullet{} @bullet{} @bullet{}
10482 @bullet{} @bullet{} @bullet{} @bullet{}
10489 (About 2500 years ago, Pythagoras and others developed the beginnings of
10490 number theory by considering questions such as this.)
10492 Suppose you want to know how many pebbles you will need to make a
10493 triangle with 7 rows?
10495 Clearly, what you need to do is add up the numbers from 1 to 7. There
10496 are two ways to do this; start with the smallest number, one, and add up
10497 the list in sequence, 1, 2, 3, 4 and so on; or start with the largest
10498 number and add the list going down: 7, 6, 5, 4 and so on. Because both
10499 mechanisms illustrate common ways of writing @code{while} loops, we will
10500 create two examples, one counting up and the other counting down. In
10501 this first example, we will start with 1 and add 2, 3, 4 and so on.
10503 If you are just adding up a short list of numbers, the easiest way to do
10504 it is to add up all the numbers at once. However, if you do not know
10505 ahead of time how many numbers your list will have, or if you want to be
10506 prepared for a very long list, then you need to design your addition so
10507 that what you do is repeat a simple process many times instead of doing
10508 a more complex process once.
10510 For example, instead of adding up all the pebbles all at once, what you
10511 can do is add the number of pebbles in the first row, 1, to the number
10512 in the second row, 2, and then add the total of those two rows to the
10513 third row, 3. Then you can add the number in the fourth row, 4, to the
10514 total of the first three rows; and so on.
10516 The critical characteristic of the process is that each repetitive
10517 action is simple. In this case, at each step we add only two numbers,
10518 the number of pebbles in the row and the total already found. This
10519 process of adding two numbers is repeated again and again until the last
10520 row has been added to the total of all the preceding rows. In a more
10521 complex loop the repetitive action might not be so simple, but it will
10522 be simpler than doing everything all at once.
10524 @node Inc Example parts
10525 @unnumberedsubsubsec The parts of the function definition
10527 The preceding analysis gives us the bones of our function definition:
10528 first, we will need a variable that we can call @code{total} that will
10529 be the total number of pebbles. This will be the value returned by
10532 Second, we know that the function will require an argument: this
10533 argument will be the total number of rows in the triangle. It can be
10534 called @code{number-of-rows}.
10536 Finally, we need a variable to use as a counter. We could call this
10537 variable @code{counter}, but a better name is @code{row-number}. That
10538 is because what the counter does in this function is count rows, and a
10539 program should be written to be as understandable as possible.
10541 When the Lisp interpreter first starts evaluating the expressions in the
10542 function, the value of @code{total} should be set to zero, since we have
10543 not added anything to it. Then the function should add the number of
10544 pebbles in the first row to the total, and then add the number of
10545 pebbles in the second to the total, and then add the number of
10546 pebbles in the third row to the total, and so on, until there are no
10547 more rows left to add.
10549 Both @code{total} and @code{row-number} are used only inside the
10550 function, so they can be declared as local variables with @code{let}
10551 and given initial values. Clearly, the initial value for @code{total}
10552 should be 0. The initial value of @code{row-number} should be 1,
10553 since we start with the first row. This means that the @code{let}
10554 statement will look like this:
10564 After the internal variables are declared and bound to their initial
10565 values, we can begin the @code{while} loop. The expression that serves
10566 as the test should return a value of @code{t} for true so long as the
10567 @code{row-number} is less than or equal to the @code{number-of-rows}.
10568 (If the expression tests true only so long as the row number is less
10569 than the number of rows in the triangle, the last row will never be
10570 added to the total; hence the row number has to be either less than or
10571 equal to the number of rows.)
10574 @findex <= @r{(less than or equal)}
10575 Lisp provides the @code{<=} function that returns true if the value of
10576 its first argument is less than or equal to the value of its second
10577 argument and false otherwise. So the expression that the @code{while}
10578 will evaluate as its test should look like this:
10581 (<= row-number number-of-rows)
10584 The total number of pebbles can be found by repeatedly adding the number
10585 of pebbles in a row to the total already found. Since the number of
10586 pebbles in the row is equal to the row number, the total can be found by
10587 adding the row number to the total. (Clearly, in a more complex
10588 situation, the number of pebbles in the row might be related to the row
10589 number in a more complicated way; if this were the case, the row number
10590 would be replaced by the appropriate expression.)
10593 (setq total (+ total row-number))
10597 What this does is set the new value of @code{total} to be equal to the
10598 sum of adding the number of pebbles in the row to the previous total.
10600 After setting the value of @code{total}, the conditions need to be
10601 established for the next repetition of the loop, if there is one. This
10602 is done by incrementing the value of the @code{row-number} variable,
10603 which serves as a counter. After the @code{row-number} variable has
10604 been incremented, the true-or-false-test at the beginning of the
10605 @code{while} loop tests whether its value is still less than or equal to
10606 the value of the @code{number-of-rows} and if it is, adds the new value
10607 of the @code{row-number} variable to the @code{total} of the previous
10608 repetition of the loop.
10611 The built-in Emacs Lisp function @code{1+} adds 1 to a number, so the
10612 @code{row-number} variable can be incremented with this expression:
10615 (setq row-number (1+ row-number))
10618 @node Inc Example altogether
10619 @unnumberedsubsubsec Putting the function definition together
10621 We have created the parts for the function definition; now we need to
10625 First, the contents of the @code{while} expression:
10629 (while (<= row-number number-of-rows) ; @r{true-or-false-test}
10630 (setq total (+ total row-number))
10631 (setq row-number (1+ row-number))) ; @r{incrementer}
10635 Along with the @code{let} expression varlist, this very nearly
10636 completes the body of the function definition. However, it requires
10637 one final element, the need for which is somewhat subtle.
10639 The final touch is to place the variable @code{total} on a line by
10640 itself after the @code{while} expression. Otherwise, the value returned
10641 by the whole function is the value of the last expression that is
10642 evaluated in the body of the @code{let}, and this is the value
10643 returned by the @code{while}, which is always @code{nil}.
10645 This may not be evident at first sight. It almost looks as if the
10646 incrementing expression is the last expression of the whole function.
10647 But that expression is part of the body of the @code{while}; it is the
10648 last element of the list that starts with the symbol @code{while}.
10649 Moreover, the whole of the @code{while} loop is a list within the body
10653 In outline, the function will look like this:
10657 (defun @var{name-of-function} (@var{argument-list})
10658 "@var{documentation}@dots{}"
10659 (let (@var{varlist})
10660 (while (@var{true-or-false-test})
10661 @var{body-of-while}@dots{} )
10662 @dots{} )) ; @r{Need final expression here.}
10666 The result of evaluating the @code{let} is what is going to be returned
10667 by the @code{defun} since the @code{let} is not embedded within any
10668 containing list, except for the @code{defun} as a whole. However, if
10669 the @code{while} is the last element of the @code{let} expression, the
10670 function will always return @code{nil}. This is not what we want!
10671 Instead, what we want is the value of the variable @code{total}. This
10672 is returned by simply placing the symbol as the last element of the list
10673 starting with @code{let}. It gets evaluated after the preceding
10674 elements of the list are evaluated, which means it gets evaluated after
10675 it has been assigned the correct value for the total.
10677 It may be easier to see this by printing the list starting with
10678 @code{let} all on one line. This format makes it evident that the
10679 @var{varlist} and @code{while} expressions are the second and third
10680 elements of the list starting with @code{let}, and the @code{total} is
10685 (let (@var{varlist}) (while (@var{true-or-false-test}) @var{body-of-while}@dots{} ) total)
10690 Putting everything together, the @code{triangle} function definition
10695 (defun triangle (number-of-rows) ; @r{Version with}
10696 ; @r{ incrementing counter.}
10697 "Add up the number of pebbles in a triangle.
10698 The first row has one pebble, the second row two pebbles,
10699 the third row three pebbles, and so on.
10700 The argument is NUMBER-OF-ROWS."
10705 (while (<= row-number number-of-rows)
10706 (setq total (+ total row-number))
10707 (setq row-number (1+ row-number)))
10713 After you have installed @code{triangle} by evaluating the function, you
10714 can try it out. Here are two examples:
10725 The sum of the first four numbers is 10 and the sum of the first seven
10728 @node Decrementing Loop
10729 @subsection Loop with a Decrementing Counter
10731 Another common way to write a @code{while} loop is to write the test
10732 so that it determines whether a counter is greater than zero. So long
10733 as the counter is greater than zero, the loop is repeated. But when
10734 the counter is equal to or less than zero, the loop is stopped. For
10735 this to work, the counter has to start out greater than zero and then
10736 be made smaller and smaller by a form that is evaluated
10739 The test will be an expression such as @code{(> counter 0)} which
10740 returns @code{t} for true if the value of @code{counter} is greater
10741 than zero, and @code{nil} for false if the value of @code{counter} is
10742 equal to or less than zero. The expression that makes the number
10743 smaller and smaller can be a simple @code{setq} such as @code{(setq
10744 counter (1- counter))}, where @code{1-} is a built-in function in
10745 Emacs Lisp that subtracts 1 from its argument.
10748 The template for a decrementing @code{while} loop looks like this:
10752 (while (> counter 0) ; @r{true-or-false-test}
10754 (setq counter (1- counter))) ; @r{decrementer}
10759 * Decrementing Example:: More pebbles on the beach.
10760 * Dec Example parts:: The parts of the function definition.
10761 * Dec Example altogether:: Putting the function definition together.
10764 @node Decrementing Example
10765 @unnumberedsubsubsec Example with decrementing counter
10767 To illustrate a loop with a decrementing counter, we will rewrite the
10768 @code{triangle} function so the counter decreases to zero.
10770 This is the reverse of the earlier version of the function. In this
10771 case, to find out how many pebbles are needed to make a triangle with
10772 3 rows, add the number of pebbles in the third row, 3, to the number
10773 in the preceding row, 2, and then add the total of those two rows to
10774 the row that precedes them, which is 1.
10776 Likewise, to find the number of pebbles in a triangle with 7 rows, add
10777 the number of pebbles in the seventh row, 7, to the number in the
10778 preceding row, which is 6, and then add the total of those two rows to
10779 the row that precedes them, which is 5, and so on. As in the previous
10780 example, each addition only involves adding two numbers, the total of
10781 the rows already added up and the number of pebbles in the row that is
10782 being added to the total. This process of adding two numbers is
10783 repeated again and again until there are no more pebbles to add.
10785 We know how many pebbles to start with: the number of pebbles in the
10786 last row is equal to the number of rows. If the triangle has seven
10787 rows, the number of pebbles in the last row is 7. Likewise, we know how
10788 many pebbles are in the preceding row: it is one less than the number in
10791 @node Dec Example parts
10792 @unnumberedsubsubsec The parts of the function definition
10794 We start with three variables: the total number of rows in the
10795 triangle; the number of pebbles in a row; and the total number of
10796 pebbles, which is what we want to calculate. These variables can be
10797 named @code{number-of-rows}, @code{number-of-pebbles-in-row}, and
10798 @code{total}, respectively.
10800 Both @code{total} and @code{number-of-pebbles-in-row} are used only
10801 inside the function and are declared with @code{let}. The initial
10802 value of @code{total} should, of course, be zero. However, the
10803 initial value of @code{number-of-pebbles-in-row} should be equal to
10804 the number of rows in the triangle, since the addition will start with
10808 This means that the beginning of the @code{let} expression will look
10814 (number-of-pebbles-in-row number-of-rows))
10819 The total number of pebbles can be found by repeatedly adding the number
10820 of pebbles in a row to the total already found, that is, by repeatedly
10821 evaluating the following expression:
10824 (setq total (+ total number-of-pebbles-in-row))
10828 After the @code{number-of-pebbles-in-row} is added to the @code{total},
10829 the @code{number-of-pebbles-in-row} should be decremented by one, since
10830 the next time the loop repeats, the preceding row will be
10831 added to the total.
10833 The number of pebbles in a preceding row is one less than the number of
10834 pebbles in a row, so the built-in Emacs Lisp function @code{1-} can be
10835 used to compute the number of pebbles in the preceding row. This can be
10836 done with the following expression:
10840 (setq number-of-pebbles-in-row
10841 (1- number-of-pebbles-in-row))
10845 Finally, we know that the @code{while} loop should stop making repeated
10846 additions when there are no pebbles in a row. So the test for
10847 the @code{while} loop is simply:
10850 (while (> number-of-pebbles-in-row 0)
10853 @node Dec Example altogether
10854 @unnumberedsubsubsec Putting the function definition together
10856 We can put these expressions together to create a function definition
10857 that works. However, on examination, we find that one of the local
10858 variables is unneeded!
10861 The function definition looks like this:
10865 ;;; @r{First subtractive version.}
10866 (defun triangle (number-of-rows)
10867 "Add up the number of pebbles in a triangle."
10869 (number-of-pebbles-in-row number-of-rows))
10870 (while (> number-of-pebbles-in-row 0)
10871 (setq total (+ total number-of-pebbles-in-row))
10872 (setq number-of-pebbles-in-row
10873 (1- number-of-pebbles-in-row)))
10878 As written, this function works.
10880 However, we do not need @code{number-of-pebbles-in-row}.
10882 @cindex Argument as local variable
10883 When the @code{triangle} function is evaluated, the symbol
10884 @code{number-of-rows} will be bound to a number, giving it an initial
10885 value. That number can be changed in the body of the function as if
10886 it were a local variable, without any fear that such a change will
10887 effect the value of the variable outside of the function. This is a
10888 very useful characteristic of Lisp; it means that the variable
10889 @code{number-of-rows} can be used anywhere in the function where
10890 @code{number-of-pebbles-in-row} is used.
10893 Here is a second version of the function written a bit more cleanly:
10897 (defun triangle (number) ; @r{Second version.}
10898 "Return sum of numbers 1 through NUMBER inclusive."
10900 (while (> number 0)
10901 (setq total (+ total number))
10902 (setq number (1- number)))
10907 In brief, a properly written @code{while} loop will consist of three parts:
10911 A test that will return false after the loop has repeated itself the
10912 correct number of times.
10915 An expression the evaluation of which will return the value desired
10916 after being repeatedly evaluated.
10919 An expression to change the value passed to the true-or-false-test so
10920 that the test returns false after the loop has repeated itself the right
10924 @node dolist dotimes
10925 @section Save your time: @code{dolist} and @code{dotimes}
10927 In addition to @code{while}, both @code{dolist} and @code{dotimes}
10928 provide for looping. Sometimes these are quicker to write than the
10929 equivalent @code{while} loop. Both are Lisp macros. (@xref{Macros, ,
10930 Macros, elisp, The GNU Emacs Lisp Reference Manual}. )
10932 @code{dolist} works like a @code{while} loop that @sc{cdr}s down a
10933 list: @code{dolist} automatically shortens the list each time it
10934 loops---takes the @sc{cdr} of the list---and binds the @sc{car} of
10935 each shorter version of the list to the first of its arguments.
10937 @code{dotimes} loops a specific number of times: you specify the number.
10945 @unnumberedsubsec The @code{dolist} Macro
10948 Suppose, for example, you want to reverse a list, so that
10949 ``first'' ``second'' ``third'' becomes ``third'' ``second'' ``first''.
10952 In practice, you would use the @code{reverse} function, like this:
10956 (setq animals '(gazelle giraffe lion tiger))
10964 Here is how you could reverse the list using a @code{while} loop:
10968 (setq animals '(gazelle giraffe lion tiger))
10970 (defun reverse-list-with-while (list)
10971 "Using while, reverse the order of LIST."
10972 (let (value) ; make sure list starts empty
10974 (setq value (cons (car list) value))
10975 (setq list (cdr list)))
10978 (reverse-list-with-while animals)
10984 And here is how you could use the @code{dolist} macro:
10988 (setq animals '(gazelle giraffe lion tiger))
10990 (defun reverse-list-with-dolist (list)
10991 "Using dolist, reverse the order of LIST."
10992 (let (value) ; make sure list starts empty
10993 (dolist (element list value)
10994 (setq value (cons element value)))))
10996 (reverse-list-with-dolist animals)
11002 In Info, you can place your cursor after the closing parenthesis of
11003 each expression and type @kbd{C-x C-e}; in each case, you should see
11006 (tiger lion giraffe gazelle)
11012 For this example, the existing @code{reverse} function is obviously best.
11013 The @code{while} loop is just like our first example (@pxref{Loop
11014 Example, , A @code{while} Loop and a List}). The @code{while} first
11015 checks whether the list has elements; if so, it constructs a new list
11016 by adding the first element of the list to the existing list (which in
11017 the first iteration of the loop is @code{nil}). Since the second
11018 element is prepended in front of the first element, and the third
11019 element is prepended in front of the second element, the list is reversed.
11021 In the expression using a @code{while} loop,
11022 the @w{@code{(setq list (cdr list))}}
11023 expression shortens the list, so the @code{while} loop eventually
11024 stops. In addition, it provides the @code{cons} expression with a new
11025 first element by creating a new and shorter list at each repetition of
11028 The @code{dolist} expression does very much the same as the
11029 @code{while} expression, except that the @code{dolist} macro does some
11030 of the work you have to do when writing a @code{while} expression.
11032 Like a @code{while} loop, a @code{dolist} loops. What is different is
11033 that it automatically shortens the list each time it loops---it
11034 @sc{cdr}s down the list on its own---and it automatically binds
11035 the @sc{car} of each shorter version of the list to the first of its
11038 In the example, the @sc{car} of each shorter version of the list is
11039 referred to using the symbol @samp{element}, the list itself is called
11040 @samp{list}, and the value returned is called @samp{value}. The
11041 remainder of the @code{dolist} expression is the body.
11043 The @code{dolist} expression binds the @sc{car} of each shorter
11044 version of the list to @code{element} and then evaluates the body of
11045 the expression; and repeats the loop. The result is returned in
11049 @unnumberedsubsec The @code{dotimes} Macro
11052 The @code{dotimes} macro is similar to @code{dolist}, except that it
11053 loops a specific number of times.
11055 The first argument to @code{dotimes} is assigned the numbers 0, 1, 2
11056 and so forth each time around the loop, and the value of the third
11057 argument is returned. You need to provide the value of the second
11058 argument, which is how many times the macro loops.
11061 For example, the following binds the numbers from 0 up to, but not
11062 including, the number 3 to the first argument, @var{number}, and then
11063 constructs a list of the three numbers. (The first number is 0, the
11064 second number is 1, and the third number is 2; this makes a total of
11065 three numbers in all, starting with zero as the first number.)
11069 (let (value) ; otherwise a value is a void variable
11070 (dotimes (number 3 value)
11071 (setq value (cons number value))))
11078 @code{dotimes} returns @code{value}, so the way to use
11079 @code{dotimes} is to operate on some expression @var{number} number of
11080 times and then return the result, either as a list or an atom.
11083 Here is an example of a @code{defun} that uses @code{dotimes} to add
11084 up the number of pebbles in a triangle.
11088 (defun triangle-using-dotimes (number-of-rows)
11089 "Using `dotimes', add up the number of pebbles in a triangle."
11090 (let ((total 0)) ; otherwise a total is a void variable
11091 (dotimes (number number-of-rows total)
11092 (setq total (+ total (1+ number))))))
11094 (triangle-using-dotimes 4)
11102 A recursive function contains code that tells the Lisp interpreter to
11103 call a program that runs exactly like itself, but with slightly
11104 different arguments. The code runs exactly the same because it has
11105 the same name. However, even though the program has the same name, it
11106 is not the same entity. It is different. In the jargon, it is a
11107 different ``instance''.
11109 Eventually, if the program is written correctly, the slightly
11110 different arguments will become sufficiently different from the first
11111 arguments that the final instance will stop.
11114 * Building Robots:: Same model, different serial number ...
11115 * Recursive Definition Parts:: Walk until you stop ...
11116 * Recursion with list:: Using a list as the test whether to recurse.
11117 * Recursive triangle function::
11118 * Recursion with cond::
11119 * Recursive Patterns:: Often used templates.
11120 * No Deferment:: Don't store up work ...
11121 * No deferment solution::
11124 @node Building Robots
11125 @subsection Building Robots: Extending the Metaphor
11126 @cindex Building robots
11127 @cindex Robots, building
11129 It is sometimes helpful to think of a running program as a robot that
11130 does a job. In doing its job, a recursive function calls on a second
11131 robot to help it. The second robot is identical to the first in every
11132 way, except that the second robot helps the first and has been
11133 passed different arguments than the first.
11135 In a recursive function, the second robot may call a third; and the
11136 third may call a fourth, and so on. Each of these is a different
11137 entity; but all are clones.
11139 Since each robot has slightly different instructions---the arguments
11140 will differ from one robot to the next---the last robot should know
11143 Let's expand on the metaphor in which a computer program is a robot.
11145 A function definition provides the blueprints for a robot. When you
11146 install a function definition, that is, when you evaluate a
11147 @code{defun} macro, you install the necessary equipment to build
11148 robots. It is as if you were in a factory, setting up an assembly
11149 line. Robots with the same name are built according to the same
11150 blueprints. So they have the same model number, but a
11151 different serial number.
11153 We often say that a recursive function ``calls itself''. What we mean
11154 is that the instructions in a recursive function cause the Lisp
11155 interpreter to run a different function that has the same name and
11156 does the same job as the first, but with different arguments.
11158 It is important that the arguments differ from one instance to the
11159 next; otherwise, the process will never stop.
11161 @node Recursive Definition Parts
11162 @subsection The Parts of a Recursive Definition
11163 @cindex Parts of a Recursive Definition
11164 @cindex Recursive Definition Parts
11166 A recursive function typically contains a conditional expression which
11171 A true-or-false-test that determines whether the function is called
11172 again, here called the @dfn{do-again-test}.
11175 The name of the function. When this name is called, a new instance of
11176 the function---a new robot, as it were---is created and told what to do.
11179 An expression that returns a different value each time the function is
11180 called, here called the @dfn{next-step-expression}. Consequently, the
11181 argument (or arguments) passed to the new instance of the function
11182 will be different from that passed to the previous instance. This
11183 causes the conditional expression, the @dfn{do-again-test}, to test
11184 false after the correct number of repetitions.
11187 Recursive functions can be much simpler than any other kind of
11188 function. Indeed, when people first start to use them, they often look
11189 so mysteriously simple as to be incomprehensible. Like riding a
11190 bicycle, reading a recursive function definition takes a certain knack
11191 which is hard at first but then seems simple.
11194 There are several different common recursive patterns. A very simple
11195 pattern looks like this:
11199 (defun @var{name-of-recursive-function} (@var{argument-list})
11200 "@var{documentation}@dots{}"
11201 (if @var{do-again-test}
11203 (@var{name-of-recursive-function}
11204 @var{next-step-expression})))
11208 Each time a recursive function is evaluated, a new instance of it is
11209 created and told what to do. The arguments tell the instance what to do.
11211 An argument is bound to the value of the next-step-expression. Each
11212 instance runs with a different value of the next-step-expression.
11214 The value in the next-step-expression is used in the do-again-test.
11216 The value returned by the next-step-expression is passed to the new
11217 instance of the function, which evaluates it (or some
11218 transmogrification of it) to determine whether to continue or stop.
11219 The next-step-expression is designed so that the do-again-test returns
11220 false when the function should no longer be repeated.
11222 The do-again-test is sometimes called the @dfn{stop condition},
11223 since it stops the repetitions when it tests false.
11225 @node Recursion with list
11226 @subsection Recursion with a List
11228 The example of a @code{while} loop that printed the elements of a list
11229 of numbers can be written recursively. Here is the code, including
11230 an expression to set the value of the variable @code{animals} to a list.
11232 If you are reading this in Info in Emacs, you can evaluate this
11233 expression directly in Info. Otherwise, you must copy the example
11234 to the @file{*scratch*} buffer and evaluate each expression there.
11235 Use @kbd{C-u C-x C-e} to evaluate the
11236 @code{(print-elements-recursively animals)} expression so that the
11237 results are printed in the buffer; otherwise the Lisp interpreter will
11238 try to squeeze the results into the one line of the echo area.
11240 Also, place your cursor immediately after the last closing parenthesis
11241 of the @code{print-elements-recursively} function, before the comment.
11242 Otherwise, the Lisp interpreter will try to evaluate the comment.
11244 @findex print-elements-recursively
11247 (setq animals '(gazelle giraffe lion tiger))
11249 (defun print-elements-recursively (list)
11250 "Print each element of LIST on a line of its own.
11252 (when list ; @r{do-again-test}
11253 (print (car list)) ; @r{body}
11254 (print-elements-recursively ; @r{recursive call}
11255 (cdr list)))) ; @r{next-step-expression}
11257 (print-elements-recursively animals)
11261 The @code{print-elements-recursively} function first tests whether
11262 there is any content in the list; if there is, the function prints the
11263 first element of the list, the @sc{car} of the list. Then the
11264 function invokes itself, but gives itself as its argument, not the
11265 whole list, but the second and subsequent elements of the list, the
11266 @sc{cdr} of the list.
11268 Put another way, if the list is not empty, the function invokes
11269 another instance of code that is similar to the initial code, but is a
11270 different thread of execution, with different arguments than the first
11273 Put in yet another way, if the list is not empty, the first robot
11274 assembles a second robot and tells it what to do; the second robot is
11275 a different individual from the first, but is the same model.
11277 When the second evaluation occurs, the @code{when} expression is
11278 evaluated and if true, prints the first element of the list it
11279 receives as its argument (which is the second element of the original
11280 list). Then the function calls itself with the @sc{cdr} of the list
11281 it is invoked with, which (the second time around) is the @sc{cdr} of
11282 the @sc{cdr} of the original list.
11284 Note that although we say that the function ``calls itself'', what we
11285 mean is that the Lisp interpreter assembles and instructs a new
11286 instance of the program. The new instance is a clone of the first,
11287 but is a separate individual.
11289 Each time the function invokes itself, it does so on a
11290 shorter version of the original list. It creates a new instance that
11291 works on a shorter list.
11293 Eventually, the function invokes itself on an empty list. It creates
11294 a new instance whose argument is @code{nil}. The conditional expression
11295 tests the value of @code{list}. Since the value of @code{list} is
11296 @code{nil}, the @code{when} expression tests false so the then-part is
11297 not evaluated. The function as a whole then returns @code{nil}.
11300 When you evaluate the expression @code{(print-elements-recursively
11301 animals)} in the @file{*scratch*} buffer, you see this result:
11317 @node Recursive triangle function
11318 @subsection Recursion in Place of a Counter
11319 @findex triangle-recursively
11322 The @code{triangle} function described in a previous section can also
11323 be written recursively. It looks like this:
11327 (defun triangle-recursively (number)
11328 "Return the sum of the numbers 1 through NUMBER inclusive.
11330 (if (= number 1) ; @r{do-again-test}
11332 (+ number ; @r{else-part}
11333 (triangle-recursively ; @r{recursive call}
11334 (1- number))))) ; @r{next-step-expression}
11336 (triangle-recursively 7)
11341 You can install this function by evaluating it and then try it by
11342 evaluating @code{(triangle-recursively 7)}. (Remember to put your
11343 cursor immediately after the last parenthesis of the function
11344 definition, before the comment.) The function evaluates to 28.
11346 To understand how this function works, let's consider what happens in the
11347 various cases when the function is passed 1, 2, 3, or 4 as the value of
11351 * Recursive Example arg of 1 or 2::
11352 * Recursive Example arg of 3 or 4::
11356 @node Recursive Example arg of 1 or 2
11357 @unnumberedsubsubsec An argument of 1 or 2
11360 First, what happens if the value of the argument is 1?
11362 The function has an @code{if} expression after the documentation
11363 string. It tests whether the value of @code{number} is equal to 1; if
11364 so, Emacs evaluates the then-part of the @code{if} expression, which
11365 returns the number 1 as the value of the function. (A triangle with
11366 one row has one pebble in it.)
11368 Suppose, however, that the value of the argument is 2. In this case,
11369 Emacs evaluates the else-part of the @code{if} expression.
11372 The else-part consists of an addition, the recursive call to
11373 @code{triangle-recursively} and a decrementing action; and it looks like
11377 (+ number (triangle-recursively (1- number)))
11380 When Emacs evaluates this expression, the innermost expression is
11381 evaluated first; then the other parts in sequence. Here are the steps
11385 @item Step 1 @w{ } Evaluate the innermost expression.
11387 The innermost expression is @code{(1- number)} so Emacs decrements the
11388 value of @code{number} from 2 to 1.
11390 @item Step 2 @w{ } Evaluate the @code{triangle-recursively} function.
11392 The Lisp interpreter creates an individual instance of
11393 @code{triangle-recursively}. It does not matter that this function is
11394 contained within itself. Emacs passes the result Step 1 as the
11395 argument used by this instance of the @code{triangle-recursively}
11398 In this case, Emacs evaluates @code{triangle-recursively} with an
11399 argument of 1. This means that this evaluation of
11400 @code{triangle-recursively} returns 1.
11402 @item Step 3 @w{ } Evaluate the value of @code{number}.
11404 The variable @code{number} is the second element of the list that
11405 starts with @code{+}; its value is 2.
11407 @item Step 4 @w{ } Evaluate the @code{+} expression.
11409 The @code{+} expression receives two arguments, the first
11410 from the evaluation of @code{number} (Step 3) and the second from the
11411 evaluation of @code{triangle-recursively} (Step 2).
11413 The result of the addition is the sum of 2 plus 1, and the number 3 is
11414 returned, which is correct. A triangle with two rows has three
11418 @node Recursive Example arg of 3 or 4
11419 @unnumberedsubsubsec An argument of 3 or 4
11421 Suppose that @code{triangle-recursively} is called with an argument of
11425 @item Step 1 @w{ } Evaluate the do-again-test.
11427 The @code{if} expression is evaluated first. This is the do-again
11428 test and returns false, so the else-part of the @code{if} expression
11429 is evaluated. (Note that in this example, the do-again-test causes
11430 the function to call itself when it tests false, not when it tests
11433 @item Step 2 @w{ } Evaluate the innermost expression of the else-part.
11435 The innermost expression of the else-part is evaluated, which decrements
11436 3 to 2. This is the next-step-expression.
11438 @item Step 3 @w{ } Evaluate the @code{triangle-recursively} function.
11440 The number 2 is passed to the @code{triangle-recursively} function.
11442 We already know what happens when Emacs evaluates @code{triangle-recursively} with
11443 an argument of 2. After going through the sequence of actions described
11444 earlier, it returns a value of 3. So that is what will happen here.
11446 @item Step 4 @w{ } Evaluate the addition.
11448 3 will be passed as an argument to the addition and will be added to the
11449 number with which the function was called, which is 3.
11453 The value returned by the function as a whole will be 6.
11455 Now that we know what will happen when @code{triangle-recursively} is
11456 called with an argument of 3, it is evident what will happen if it is
11457 called with an argument of 4:
11461 In the recursive call, the evaluation of
11464 (triangle-recursively (1- 4))
11469 will return the value of evaluating
11472 (triangle-recursively 3)
11476 which is 6 and this value will be added to 4 by the addition in the
11481 The value returned by the function as a whole will be 10.
11483 Each time @code{triangle-recursively} is evaluated, it evaluates a
11484 version of itself---a different instance of itself---with a smaller
11485 argument, until the argument is small enough so that it does not
11488 Note that this particular design for a recursive function
11489 requires that operations be deferred.
11491 Before @code{(triangle-recursively 7)} can calculate its answer, it
11492 must call @code{(triangle-recursively 6)}; and before
11493 @code{(triangle-recursively 6)} can calculate its answer, it must call
11494 @code{(triangle-recursively 5)}; and so on. That is to say, the
11495 calculation that @code{(triangle-recursively 7)} makes must be
11496 deferred until @code{(triangle-recursively 6)} makes its calculation;
11497 and @code{(triangle-recursively 6)} must defer until
11498 @code{(triangle-recursively 5)} completes; and so on.
11500 If each of these instances of @code{triangle-recursively} are thought
11501 of as different robots, the first robot must wait for the second to
11502 complete its job, which must wait until the third completes, and so
11505 There is a way around this kind of waiting, which we will discuss in
11506 @ref{No Deferment, , Recursion without Deferments}.
11508 @node Recursion with cond
11509 @subsection Recursion Example Using @code{cond}
11512 The version of @code{triangle-recursively} described earlier is written
11513 with the @code{if} special form. It can also be written using another
11514 special form called @code{cond}. The name of the special form
11515 @code{cond} is an abbreviation of the word @samp{conditional}.
11517 Although the @code{cond} special form is not used as often in the
11518 Emacs Lisp sources as @code{if}, it is used often enough to justify
11522 The template for a @code{cond} expression looks like this:
11532 where the @var{body} is a series of lists.
11535 Written out more fully, the template looks like this:
11540 (@var{first-true-or-false-test} @var{first-consequent})
11541 (@var{second-true-or-false-test} @var{second-consequent})
11542 (@var{third-true-or-false-test} @var{third-consequent})
11547 When the Lisp interpreter evaluates the @code{cond} expression, it
11548 evaluates the first element (the @sc{car} or true-or-false-test) of
11549 the first expression in a series of expressions within the body of the
11552 If the true-or-false-test returns @code{nil} the rest of that
11553 expression, the consequent, is skipped and the true-or-false-test of the
11554 next expression is evaluated. When an expression is found whose
11555 true-or-false-test returns a value that is not @code{nil}, the
11556 consequent of that expression is evaluated. The consequent can be one
11557 or more expressions. If the consequent consists of more than one
11558 expression, the expressions are evaluated in sequence and the value of
11559 the last one is returned. If the expression does not have a consequent,
11560 the value of the true-or-false-test is returned.
11562 If none of the true-or-false-tests test true, the @code{cond} expression
11563 returns @code{nil}.
11566 Written using @code{cond}, the @code{triangle} function looks like this:
11570 (defun triangle-using-cond (number)
11571 (cond ((<= number 0) 0)
11574 (+ number (triangle-using-cond (1- number))))))
11579 In this example, the @code{cond} returns 0 if the number is less than or
11580 equal to 0, it returns 1 if the number is 1 and it evaluates @code{(+
11581 number (triangle-using-cond (1- number)))} if the number is greater than
11584 @node Recursive Patterns
11585 @subsection Recursive Patterns
11586 @cindex Recursive Patterns
11588 Here are three common recursive patterns. Each involves a list.
11589 Recursion does not need to involve lists, but Lisp is designed for lists
11590 and this provides a sense of its primal capabilities.
11599 @unnumberedsubsubsec Recursive Pattern: @emph{every}
11600 @cindex Every, type of recursive pattern
11601 @cindex Recursive pattern - every
11603 In the @code{every} recursive pattern, an action is performed on every
11607 The basic pattern is:
11611 If a list be empty, return @code{nil}.
11613 Else, act on the beginning of the list (the @sc{car} of the list)
11616 through a recursive call by the function on the rest (the
11617 @sc{cdr}) of the list,
11619 and, optionally, combine the acted-on element, using @code{cons},
11620 with the results of acting on the rest.
11625 Here is an example:
11629 (defun square-each (numbers-list)
11630 "Square each of a NUMBERS LIST, recursively."
11631 (if (not numbers-list) ; do-again-test
11634 (* (car numbers-list) (car numbers-list))
11635 (square-each (cdr numbers-list))))) ; next-step-expression
11639 (square-each '(1 2 3))
11646 If @code{numbers-list} is empty, do nothing. But if it has content,
11647 construct a list combining the square of the first number in the list
11648 with the result of the recursive call.
11650 (The example follows the pattern exactly: @code{nil} is returned if
11651 the numbers' list is empty. In practice, you would write the
11652 conditional so it carries out the action when the numbers' list is not
11655 The @code{print-elements-recursively} function (@pxref{Recursion with
11656 list, , Recursion with a List}) is another example of an @code{every}
11657 pattern, except in this case, rather than bring the results together
11658 using @code{cons}, we print each element of output.
11661 The @code{print-elements-recursively} function looks like this:
11665 (setq animals '(gazelle giraffe lion tiger))
11669 (defun print-elements-recursively (list)
11670 "Print each element of LIST on a line of its own.
11672 (when list ; @r{do-again-test}
11673 (print (car list)) ; @r{body}
11674 (print-elements-recursively ; @r{recursive call}
11675 (cdr list)))) ; @r{next-step-expression}
11677 (print-elements-recursively animals)
11682 The pattern for @code{print-elements-recursively} is:
11686 When the list is empty, do nothing.
11688 But when the list has at least one element,
11691 act on the beginning of the list (the @sc{car} of the list),
11693 and make a recursive call on the rest (the @sc{cdr}) of the list.
11698 @unnumberedsubsubsec Recursive Pattern: @emph{accumulate}
11699 @cindex Accumulate, type of recursive pattern
11700 @cindex Recursive pattern - accumulate
11702 Another recursive pattern is called the @code{accumulate} pattern. In
11703 the @code{accumulate} recursive pattern, an action is performed on
11704 every element of a list and the result of that action is accumulated
11705 with the results of performing the action on the other elements.
11707 This is very like the @code{every} pattern using @code{cons}, except that
11708 @code{cons} is not used, but some other combiner.
11715 If a list be empty, return zero or some other constant.
11717 Else, act on the beginning of the list (the @sc{car} of the list),
11720 and combine that acted-on element, using @code{+} or
11721 some other combining function, with
11723 a recursive call by the function on the rest (the @sc{cdr}) of the list.
11728 Here is an example:
11732 (defun add-elements (numbers-list)
11733 "Add the elements of NUMBERS-LIST together."
11734 (if (not numbers-list)
11736 (+ (car numbers-list) (add-elements (cdr numbers-list)))))
11740 (add-elements '(1 2 3 4))
11745 @xref{Files List, , Making a List of Files}, for an example of the
11746 accumulate pattern.
11749 @unnumberedsubsubsec Recursive Pattern: @emph{keep}
11750 @cindex Keep, type of recursive pattern
11751 @cindex Recursive pattern - keep
11753 A third recursive pattern is called the @code{keep} pattern.
11754 In the @code{keep} recursive pattern, each element of a list is tested;
11755 the element is acted on and the results are kept only if the element
11758 Again, this is very like the @code{every} pattern, except the element is
11759 skipped unless it meets a criterion.
11762 The pattern has three parts:
11766 If a list be empty, return @code{nil}.
11768 Else, if the beginning of the list (the @sc{car} of the list) passes
11772 act on that element and combine it, using @code{cons} with
11774 a recursive call by the function on the rest (the @sc{cdr}) of the list.
11777 Otherwise, if the beginning of the list (the @sc{car} of the list) fails
11781 skip on that element,
11783 and, recursively call the function on the rest (the @sc{cdr}) of the list.
11788 Here is an example that uses @code{cond}:
11792 (defun keep-three-letter-words (word-list)
11793 "Keep three letter words in WORD-LIST."
11795 ;; First do-again-test: stop-condition
11796 ((not word-list) nil)
11798 ;; Second do-again-test: when to act
11799 ((eq 3 (length (symbol-name (car word-list))))
11800 ;; combine acted-on element with recursive call on shorter list
11801 (cons (car word-list) (keep-three-letter-words (cdr word-list))))
11803 ;; Third do-again-test: when to skip element;
11804 ;; recursively call shorter list with next-step expression
11805 (t (keep-three-letter-words (cdr word-list)))))
11809 (keep-three-letter-words '(one two three four five six))
11810 @result{} (one two six)
11814 It goes without saying that you need not use @code{nil} as the test for
11815 when to stop; and you can, of course, combine these patterns.
11818 @subsection Recursion without Deferments
11819 @cindex Deferment in recursion
11820 @cindex Recursion without Deferments
11822 Let's consider again what happens with the @code{triangle-recursively}
11823 function. We will find that the intermediate calculations are
11824 deferred until all can be done.
11827 Here is the function definition:
11831 (defun triangle-recursively (number)
11832 "Return the sum of the numbers 1 through NUMBER inclusive.
11834 (if (= number 1) ; @r{do-again-test}
11836 (+ number ; @r{else-part}
11837 (triangle-recursively ; @r{recursive call}
11838 (1- number))))) ; @r{next-step-expression}
11842 What happens when we call this function with a argument of 7?
11844 The first instance of the @code{triangle-recursively} function adds
11845 the number 7 to the value returned by a second instance of
11846 @code{triangle-recursively}, an instance that has been passed an
11847 argument of 6. That is to say, the first calculation is:
11850 (+ 7 (triangle-recursively 6))
11854 The first instance of @code{triangle-recursively}---you may want to
11855 think of it as a little robot---cannot complete its job. It must hand
11856 off the calculation for @code{(triangle-recursively 6)} to a second
11857 instance of the program, to a second robot. This second individual is
11858 completely different from the first one; it is, in the jargon, a
11859 ``different instantiation''. Or, put another way, it is a different
11860 robot. It is the same model as the first; it calculates triangle
11861 numbers recursively; but it has a different serial number.
11863 And what does @code{(triangle-recursively 6)} return? It returns the
11864 number 6 added to the value returned by evaluating
11865 @code{triangle-recursively} with an argument of 5. Using the robot
11866 metaphor, it asks yet another robot to help it.
11872 (+ 7 6 (triangle-recursively 5))
11876 And what happens next?
11879 (+ 7 6 5 (triangle-recursively 4))
11882 Each time @code{triangle-recursively} is called, except for the last
11883 time, it creates another instance of the program---another robot---and
11884 asks it to make a calculation.
11887 Eventually, the full addition is set up and performed:
11893 This design for the function defers the calculation of the first step
11894 until the second can be done, and defers that until the third can be
11895 done, and so on. Each deferment means the computer must remember what
11896 is being waited on. This is not a problem when there are only a few
11897 steps, as in this example. But it can be a problem when there are
11900 @node No deferment solution
11901 @subsection No Deferment Solution
11902 @cindex No deferment solution
11903 @cindex Solution without deferment
11905 The solution to the problem of deferred operations is to write in a
11906 manner that does not defer operations@footnote{The phrase @dfn{tail
11907 recursive} is used to describe such a process, one that uses
11908 constant space.}. This requires
11909 writing to a different pattern, often one that involves writing two
11910 function definitions, an initialization function and a helper
11913 The initialization function sets up the job; the helper function
11917 Here are the two function definitions for adding up numbers. They are
11918 so simple, I find them hard to understand.
11922 (defun triangle-initialization (number)
11923 "Return the sum of the numbers 1 through NUMBER inclusive.
11924 This is the initialization component of a two function
11925 duo that uses recursion."
11926 (triangle-recursive-helper 0 0 number))
11932 (defun triangle-recursive-helper (sum counter number)
11933 "Return SUM, using COUNTER, through NUMBER inclusive.
11934 This is the helper component of a two function duo
11935 that uses recursion."
11936 (if (> counter number)
11938 (triangle-recursive-helper (+ sum counter) ; @r{sum}
11939 (1+ counter) ; @r{counter}
11940 number))) ; @r{number}
11945 Install both function definitions by evaluating them, then call
11946 @code{triangle-initialization} with 2 rows:
11950 (triangle-initialization 2)
11955 The initialization function calls the first instance of the helper
11956 function with three arguments: zero, zero, and a number which is the
11957 number of rows in the triangle.
11959 The first two arguments passed to the helper function are
11960 initialization values. These values are changed when
11961 @code{triangle-recursive-helper} invokes new instances.@footnote{The
11962 jargon is mildly confusing: @code{triangle-recursive-helper} uses a
11963 process that is iterative in a procedure that is recursive. The
11964 process is called iterative because the computer need only record the
11965 three values, @code{sum}, @code{counter}, and @code{number}; the
11966 procedure is recursive because the function calls itself. On the
11967 other hand, both the process and the procedure used by
11968 @code{triangle-recursively} are called recursive. The word
11969 ``recursive'' has different meanings in the two contexts.}
11971 Let's see what happens when we have a triangle that has one row. (This
11972 triangle will have one pebble in it!)
11975 @code{triangle-initialization} will call its helper with
11976 the arguments @w{@code{0 0 1}}. That function will run the conditional
11977 test whether @code{(> counter number)}:
11985 and find that the result is false, so it will invoke
11986 the else-part of the @code{if} clause:
11990 (triangle-recursive-helper
11991 (+ sum counter) ; @r{sum plus counter} @result{} @r{sum}
11992 (1+ counter) ; @r{increment counter} @result{} @r{counter}
11993 number) ; @r{number stays the same}
11999 which will first compute:
12003 (triangle-recursive-helper (+ 0 0) ; @r{sum}
12004 (1+ 0) ; @r{counter}
12008 (triangle-recursive-helper 0 1 1)
12012 Again, @code{(> counter number)} will be false, so again, the Lisp
12013 interpreter will evaluate @code{triangle-recursive-helper}, creating a
12014 new instance with new arguments.
12017 This new instance will be;
12021 (triangle-recursive-helper
12022 (+ sum counter) ; @r{sum plus counter} @result{} @r{sum}
12023 (1+ counter) ; @r{increment counter} @result{} @r{counter}
12024 number) ; @r{number stays the same}
12028 (triangle-recursive-helper 1 2 1)
12032 In this case, the @code{(> counter number)} test will be true! So the
12033 instance will return the value of the sum, which will be 1, as
12036 Now, let's pass @code{triangle-initialization} an argument
12037 of 2, to find out how many pebbles there are in a triangle with two rows.
12039 That function calls @code{(triangle-recursive-helper 0 0 2)}.
12042 In stages, the instances called will be:
12046 @r{sum counter number}
12047 (triangle-recursive-helper 0 1 2)
12049 (triangle-recursive-helper 1 2 2)
12051 (triangle-recursive-helper 3 3 2)
12055 When the last instance is called, the @code{(> counter number)} test
12056 will be true, so the instance will return the value of @code{sum},
12059 This kind of pattern helps when you are writing functions that can use
12060 many resources in a computer.
12063 @node Looping exercise
12064 @section Looping Exercise
12068 Write a function similar to @code{triangle} in which each row has a
12069 value which is the square of the row number. Use a @code{while} loop.
12072 Write a function similar to @code{triangle} that multiplies instead of
12076 Rewrite these two functions recursively. Rewrite these functions
12079 @c comma in printed title causes problem in Info cross reference
12081 Write a function for Texinfo mode that creates an index entry at the
12082 beginning of a paragraph for every @samp{@@dfn} within the paragraph.
12083 (In a Texinfo file, @samp{@@dfn} marks a definition. This book is
12084 written in Texinfo.)
12086 Many of the functions you will need are described in two of the
12087 previous chapters, @ref{Cutting & Storing Text, , Cutting and Storing
12088 Text}, and @ref{Yanking, , Yanking Text Back}. If you use
12089 @code{forward-paragraph} to put the index entry at the beginning of
12090 the paragraph, you will have to use @w{@kbd{C-h f}}
12091 (@code{describe-function}) to find out how to make the command go
12094 For more information, see
12096 @ref{Indicating, , Indicating Definitions, texinfo}.
12099 @ref{Indicating, , Indicating, texinfo, Texinfo Manual}, which goes to
12100 a Texinfo manual in the current directory. Or, if you are on the
12102 @uref{http://www.gnu.org/software/texinfo/manual/texinfo/}
12105 ``Indicating Definitions, Commands, etc.''@: in @cite{Texinfo, The GNU
12106 Documentation Format}.
12110 @node Regexp Search
12111 @chapter Regular Expression Searches
12112 @cindex Searches, illustrating
12113 @cindex Regular expression searches
12114 @cindex Patterns, searching for
12115 @cindex Motion by sentence and paragraph
12116 @cindex Sentences, movement by
12117 @cindex Paragraphs, movement by
12119 Regular expression searches are used extensively in GNU Emacs. The
12120 two functions, @code{forward-sentence} and @code{forward-paragraph},
12121 illustrate these searches well. They use regular expressions to find
12122 where to move point. The phrase ``regular expression'' is often written
12125 Regular expression searches are described in @ref{Regexp Search, ,
12126 Regular Expression Search, emacs, The GNU Emacs Manual}, as well as in
12127 @ref{Regular Expressions, , , elisp, The GNU Emacs Lisp Reference
12128 Manual}. In writing this chapter, I am presuming that you have at
12129 least a mild acquaintance with them. The major point to remember is
12130 that regular expressions permit you to search for patterns as well as
12131 for literal strings of characters. For example, the code in
12132 @code{forward-sentence} searches for the pattern of possible
12133 characters that could mark the end of a sentence, and moves point to
12136 Before looking at the code for the @code{forward-sentence} function, it
12137 is worth considering what the pattern that marks the end of a sentence
12138 must be. The pattern is discussed in the next section; following that
12139 is a description of the regular expression search function,
12140 @code{re-search-forward}. The @code{forward-sentence} function
12141 is described in the section following. Finally, the
12142 @code{forward-paragraph} function is described in the last section of
12143 this chapter. @code{forward-paragraph} is a complex function that
12144 introduces several new features.
12147 * sentence-end:: The regular expression for @code{sentence-end}.
12148 * re-search-forward:: Very similar to @code{search-forward}.
12149 * forward-sentence:: A straightforward example of regexp search.
12150 * forward-paragraph:: A somewhat complex example.
12151 * etags:: How to create your own @file{TAGS} table.
12153 * re-search Exercises::
12157 @section The Regular Expression for @code{sentence-end}
12158 @findex sentence-end
12160 The symbol @code{sentence-end} is bound to the pattern that marks the
12161 end of a sentence. What should this regular expression be?
12163 Clearly, a sentence may be ended by a period, a question mark, or an
12164 exclamation mark. Indeed, in English, only clauses that end with one
12165 of those three characters should be considered the end of a sentence.
12166 This means that the pattern should include the character set:
12172 However, we do not want @code{forward-sentence} merely to jump to a
12173 period, a question mark, or an exclamation mark, because such a character
12174 might be used in the middle of a sentence. A period, for example, is
12175 used after abbreviations. So other information is needed.
12177 According to convention, you type two spaces after every sentence, but
12178 only one space after a period, a question mark, or an exclamation mark in
12179 the body of a sentence. So a period, a question mark, or an exclamation
12180 mark followed by two spaces is a good indicator of an end of sentence.
12181 However, in a file, the two spaces may instead be a tab or the end of a
12182 line. This means that the regular expression should include these three
12183 items as alternatives.
12186 This group of alternatives will look like this:
12197 Here, @samp{$} indicates the end of the line, and I have pointed out
12198 where the tab and two spaces are inserted in the expression. Both are
12199 inserted by putting the actual characters into the expression.
12201 Two backslashes, @samp{\\}, are required before the parentheses and
12202 vertical bars: the first backslash quotes the following backslash in
12203 Emacs; and the second indicates that the following character, the
12204 parenthesis or the vertical bar, is special.
12207 Also, a sentence may be followed by one or more carriage returns, like
12218 Like tabs and spaces, a carriage return is inserted into a regular
12219 expression by inserting it literally. The asterisk indicates that the
12220 @key{RET} is repeated zero or more times.
12222 But a sentence end does not consist only of a period, a question mark or
12223 an exclamation mark followed by appropriate space: a closing quotation
12224 mark or a closing brace of some kind may precede the space. Indeed more
12225 than one such mark or brace may precede the space. These require a
12226 expression that looks like this:
12232 In this expression, the first @samp{]} is the first character in the
12233 expression; the second character is @samp{"}, which is preceded by a
12234 @samp{\} to tell Emacs the @samp{"} is @emph{not} special. The last
12235 three characters are @samp{'}, @samp{)}, and @samp{@}}.
12237 All this suggests what the regular expression pattern for matching the
12238 end of a sentence should be; and, indeed, if we evaluate
12239 @code{sentence-end} we find that it returns the following value:
12244 @result{} "[.?!][]\"')@}]*\\($\\| \\| \\)[
12250 (Well, not in GNU Emacs 22; that is because of an effort to make the
12251 process simpler and to handle more glyphs and languages. When the
12252 value of @code{sentence-end} is @code{nil}, then use the value defined
12253 by the function @code{sentence-end}. (Here is a use of the difference
12254 between a value and a function in Emacs Lisp.) The function returns a
12255 value constructed from the variables @code{sentence-end-base},
12256 @code{sentence-end-double-space}, @code{sentence-end-without-period},
12257 and @code{sentence-end-without-space}. The critical variable is
12258 @code{sentence-end-base}; its global value is similar to the one
12259 described above but it also contains two additional quotation marks.
12260 These have differing degrees of curliness. The
12261 @code{sentence-end-without-period} variable, when true, tells Emacs
12262 that a sentence may end without a period, such as text in Thai.)
12266 (Note that here the @key{TAB}, two spaces, and @key{RET} are shown
12267 literally in the pattern.)
12269 This regular expression can be deciphered as follows:
12273 The first part of the pattern is the three characters, a period, a question
12274 mark and an exclamation mark, within square brackets. The pattern must
12275 begin with one or other of these characters.
12278 The second part of the pattern is the group of closing braces and
12279 quotation marks, which can appear zero or more times. These may follow
12280 the period, question mark or exclamation mark. In a regular expression,
12281 the backslash, @samp{\}, followed by the double quotation mark,
12282 @samp{"}, indicates the class of string-quote characters. Usually, the
12283 double quotation mark is the only character in this class. The
12284 asterisk, @samp{*}, indicates that the items in the previous group (the
12285 group surrounded by square brackets, @samp{[]}) may be repeated zero or
12288 @item \\($\\| \\| \\)
12289 The third part of the pattern is one or other of: either the end of a
12290 line, or two blank spaces, or a tab. The double back-slashes are used
12291 to prevent Emacs from reading the parentheses and vertical bars as part
12292 of the search pattern; the parentheses are used to mark the group and
12293 the vertical bars are used to indicated that the patterns to either side
12294 of them are alternatives. The dollar sign is used to indicate the end
12295 of a line and both the two spaces and the tab are each inserted as is to
12296 indicate what they are.
12299 Finally, the last part of the pattern indicates that the end of the line
12300 or the whitespace following the period, question mark or exclamation
12301 mark may, but need not, be followed by one or more carriage returns. In
12302 the pattern, the carriage return is inserted as an actual carriage
12303 return between square brackets but here it is shown as @key{RET}.
12307 @node re-search-forward
12308 @section The @code{re-search-forward} Function
12309 @findex re-search-forward
12311 The @code{re-search-forward} function is very like the
12312 @code{search-forward} function. (@xref{search-forward, , The
12313 @code{search-forward} Function}.)
12315 @code{re-search-forward} searches for a regular expression. If the
12316 search is successful, it leaves point immediately after the last
12317 character in the target. If the search is backwards, it leaves point
12318 just before the first character in the target. You may tell
12319 @code{re-search-forward} to return @code{t} for true. (Moving point
12320 is therefore a side effect.)
12322 Like @code{search-forward}, the @code{re-search-forward} function takes
12327 The first argument is the regular expression that the function searches
12328 for. The regular expression will be a string between quotation marks.
12331 The optional second argument limits how far the function will search; it is a
12332 bound, which is specified as a position in the buffer.
12335 The optional third argument specifies how the function responds to
12336 failure: @code{nil} as the third argument causes the function to
12337 signal an error (and print a message) when the search fails; any other
12338 value causes it to return @code{nil} if the search fails and @code{t}
12339 if the search succeeds.
12342 The optional fourth argument is the repeat count. A negative repeat
12343 count causes @code{re-search-forward} to search backwards.
12347 The template for @code{re-search-forward} looks like this:
12351 (re-search-forward "@var{regular-expression}"
12352 @var{limit-of-search}
12353 @var{what-to-do-if-search-fails}
12354 @var{repeat-count})
12358 The second, third, and fourth arguments are optional. However, if you
12359 want to pass a value to either or both of the last two arguments, you
12360 must also pass a value to all the preceding arguments. Otherwise, the
12361 Lisp interpreter will mistake which argument you are passing the value
12365 In the @code{forward-sentence} function, the regular expression will be
12366 the value of the variable @code{sentence-end}. In simple form, that is:
12370 "[.?!][]\"')@}]*\\($\\| \\| \\)[
12376 The limit of the search will be the end of the paragraph (since a
12377 sentence cannot go beyond a paragraph). If the search fails, the
12378 function will return @code{nil}; and the repeat count will be provided
12379 by the argument to the @code{forward-sentence} function.
12381 @node forward-sentence
12382 @section @code{forward-sentence}
12383 @findex forward-sentence
12385 The command to move the cursor forward a sentence is a straightforward
12386 illustration of how to use regular expression searches in Emacs Lisp.
12387 Indeed, the function looks longer and more complicated than it is; this
12388 is because the function is designed to go backwards as well as forwards;
12389 and, optionally, over more than one sentence. The function is usually
12390 bound to the key command @kbd{M-e}.
12393 * Complete forward-sentence::
12394 * fwd-sentence while loops:: Two @code{while} loops.
12395 * fwd-sentence re-search:: A regular expression search.
12399 @node Complete forward-sentence
12400 @unnumberedsubsec Complete @code{forward-sentence} function definition
12404 Here is the code for @code{forward-sentence}:
12409 (defun forward-sentence (&optional arg)
12410 "Move forward to next end of sentence. With argument, repeat.
12411 With negative argument, move backward repeatedly to start of sentence.
12413 The variable `sentence-end' is a regular expression that matches ends of
12414 sentences. Also, every paragraph boundary terminates sentences as well."
12418 (or arg (setq arg 1))
12419 (let ((opoint (point))
12420 (sentence-end (sentence-end)))
12422 (let ((pos (point))
12423 (par-beg (save-excursion (start-of-paragraph-text) (point))))
12424 (if (and (re-search-backward sentence-end par-beg t)
12425 (or (< (match-end 0) pos)
12426 (re-search-backward sentence-end par-beg t)))
12427 (goto-char (match-end 0))
12428 (goto-char par-beg)))
12429 (setq arg (1+ arg)))
12433 (let ((par-end (save-excursion (end-of-paragraph-text) (point))))
12434 (if (re-search-forward sentence-end par-end t)
12435 (skip-chars-backward " \t\n")
12436 (goto-char par-end)))
12437 (setq arg (1- arg)))
12438 (constrain-to-field nil opoint t)))
12446 (defun forward-sentence (&optional arg)
12447 "Move forward to next sentence-end. With argument, repeat.
12448 With negative argument, move backward repeatedly to sentence-beginning.
12449 Sentence ends are identified by the value of sentence-end
12450 treated as a regular expression. Also, every paragraph boundary
12451 terminates sentences as well."
12455 (or arg (setq arg 1))
12458 (save-excursion (start-of-paragraph-text) (point))))
12459 (if (re-search-backward
12460 (concat sentence-end "[^ \t\n]") par-beg t)
12461 (goto-char (1- (match-end 0)))
12462 (goto-char par-beg)))
12463 (setq arg (1+ arg)))
12466 (save-excursion (end-of-paragraph-text) (point))))
12467 (if (re-search-forward sentence-end par-end t)
12468 (skip-chars-backward " \t\n")
12469 (goto-char par-end)))
12470 (setq arg (1- arg))))
12475 The function looks long at first sight and it is best to look at its
12476 skeleton first, and then its muscle. The way to see the skeleton is to
12477 look at the expressions that start in the left-most columns:
12481 (defun forward-sentence (&optional arg)
12482 "@var{documentation}@dots{}"
12484 (or arg (setq arg 1))
12485 (let ((opoint (point)) (sentence-end (sentence-end)))
12487 (let ((pos (point))
12488 (par-beg (save-excursion (start-of-paragraph-text) (point))))
12489 @var{rest-of-body-of-while-loop-when-going-backwards}
12491 (let ((par-end (save-excursion (end-of-paragraph-text) (point))))
12492 @var{rest-of-body-of-while-loop-when-going-forwards}
12493 @var{handle-forms-and-equivalent}
12497 This looks much simpler! The function definition consists of
12498 documentation, an @code{interactive} expression, an @code{or}
12499 expression, a @code{let} expression, and @code{while} loops.
12501 Let's look at each of these parts in turn.
12503 We note that the documentation is thorough and understandable.
12505 The function has an @code{interactive "p"} declaration. This means
12506 that the processed prefix argument, if any, is passed to the
12507 function as its argument. (This will be a number.) If the function
12508 is not passed an argument (it is optional) then the argument
12509 @code{arg} will be bound to 1.
12511 When @code{forward-sentence} is called non-interactively without an
12512 argument, @code{arg} is bound to @code{nil}. The @code{or} expression
12513 handles this. What it does is either leave the value of @code{arg} as
12514 it is, but only if @code{arg} is bound to a value; or it sets the
12515 value of @code{arg} to 1, in the case when @code{arg} is bound to
12518 Next is a @code{let}. That specifies the values of two local
12519 variables, @code{opoint} and @code{sentence-end}. The local value of
12520 point, from before the search, is used in the
12521 @code{constrain-to-field} function which handles forms and
12522 equivalents. The @code{sentence-end} variable is set by the
12523 @code{sentence-end} function.
12525 @node fwd-sentence while loops
12526 @unnumberedsubsec The @code{while} loops
12528 Two @code{while} loops follow. The first @code{while} has a
12529 true-or-false-test that tests true if the prefix argument for
12530 @code{forward-sentence} is a negative number. This is for going
12531 backwards. The body of this loop is similar to the body of the second
12532 @code{while} clause, but it is not exactly the same. We will skip
12533 this @code{while} loop and concentrate on the second @code{while}
12537 The second @code{while} loop is for moving point forward. Its skeleton
12542 (while (> arg 0) ; @r{true-or-false-test}
12544 (if (@var{true-or-false-test})
12547 (setq arg (1- arg)))) ; @code{while} @r{loop decrementer}
12551 The @code{while} loop is of the decrementing kind.
12552 (@xref{Decrementing Loop, , A Loop with a Decrementing Counter}.) It
12553 has a true-or-false-test that tests true so long as the counter (in
12554 this case, the variable @code{arg}) is greater than zero; and it has a
12555 decrementer that subtracts 1 from the value of the counter every time
12558 If no prefix argument is given to @code{forward-sentence}, which is
12559 the most common way the command is used, this @code{while} loop will
12560 run once, since the value of @code{arg} will be 1.
12562 The body of the @code{while} loop consists of a @code{let} expression,
12563 which creates and binds a local variable, and has, as its body, an
12564 @code{if} expression.
12567 The body of the @code{while} loop looks like this:
12572 (save-excursion (end-of-paragraph-text) (point))))
12573 (if (re-search-forward sentence-end par-end t)
12574 (skip-chars-backward " \t\n")
12575 (goto-char par-end)))
12579 The @code{let} expression creates and binds the local variable
12580 @code{par-end}. As we shall see, this local variable is designed to
12581 provide a bound or limit to the regular expression search. If the
12582 search fails to find a proper sentence ending in the paragraph, it will
12583 stop on reaching the end of the paragraph.
12585 But first, let us examine how @code{par-end} is bound to the value of
12586 the end of the paragraph. What happens is that the @code{let} sets the
12587 value of @code{par-end} to the value returned when the Lisp interpreter
12588 evaluates the expression
12592 (save-excursion (end-of-paragraph-text) (point))
12597 In this expression, @code{(end-of-paragraph-text)} moves point to the
12598 end of the paragraph, @code{(point)} returns the value of point, and then
12599 @code{save-excursion} restores point to its original position. Thus,
12600 the @code{let} binds @code{par-end} to the value returned by the
12601 @code{save-excursion} expression, which is the position of the end of
12602 the paragraph. (The @code{end-of-paragraph-text} function uses
12603 @code{forward-paragraph}, which we will discuss shortly.)
12606 Emacs next evaluates the body of the @code{let}, which is an @code{if}
12607 expression that looks like this:
12611 (if (re-search-forward sentence-end par-end t) ; @r{if-part}
12612 (skip-chars-backward " \t\n") ; @r{then-part}
12613 (goto-char par-end))) ; @r{else-part}
12617 The @code{if} tests whether its first argument is true and if so,
12618 evaluates its then-part; otherwise, the Emacs Lisp interpreter
12619 evaluates the else-part. The true-or-false-test of the @code{if}
12620 expression is the regular expression search.
12622 It may seem odd to have what looks like the real work of
12623 the @code{forward-sentence} function buried here, but this is a common
12624 way this kind of operation is carried out in Lisp.
12626 @node fwd-sentence re-search
12627 @unnumberedsubsec The regular expression search
12629 The @code{re-search-forward} function searches for the end of the
12630 sentence, that is, for the pattern defined by the @code{sentence-end}
12631 regular expression. If the pattern is found---if the end of the sentence is
12632 found---then the @code{re-search-forward} function does two things:
12636 The @code{re-search-forward} function carries out a side effect, which
12637 is to move point to the end of the occurrence found.
12640 The @code{re-search-forward} function returns a value of true. This is
12641 the value received by the @code{if}, and means that the search was
12646 The side effect, the movement of point, is completed before the
12647 @code{if} function is handed the value returned by the successful
12648 conclusion of the search.
12650 When the @code{if} function receives the value of true from a successful
12651 call to @code{re-search-forward}, the @code{if} evaluates the then-part,
12652 which is the expression @code{(skip-chars-backward " \t\n")}. This
12653 expression moves backwards over any blank spaces, tabs or carriage
12654 returns until a printed character is found and then leaves point after
12655 the character. Since point has already been moved to the end of the
12656 pattern that marks the end of the sentence, this action leaves point
12657 right after the closing printed character of the sentence, which is
12660 On the other hand, if the @code{re-search-forward} function fails to
12661 find a pattern marking the end of the sentence, the function returns
12662 false. The false then causes the @code{if} to evaluate its third
12663 argument, which is @code{(goto-char par-end)}: it moves point to the
12664 end of the paragraph.
12666 (And if the text is in a form or equivalent, and point may not move
12667 fully, then the @code{constrain-to-field} function comes into play.)
12669 Regular expression searches are exceptionally useful and the pattern
12670 illustrated by @code{re-search-forward}, in which the search is the
12671 test of an @code{if} expression, is handy. You will see or write code
12672 incorporating this pattern often.
12674 @node forward-paragraph
12675 @section @code{forward-paragraph}: a Goldmine of Functions
12676 @findex forward-paragraph
12680 (defun forward-paragraph (&optional arg)
12681 "Move forward to end of paragraph.
12682 With argument ARG, do it ARG times;
12683 a negative argument ARG = -N means move backward N paragraphs.
12685 A line which `paragraph-start' matches either separates paragraphs
12686 \(if `paragraph-separate' matches it also) or is the first line of a paragraph.
12687 A paragraph end is the beginning of a line which is not part of the paragraph
12688 to which the end of the previous line belongs, or the end of the buffer.
12689 Returns the count of paragraphs left to move."
12691 (or arg (setq arg 1))
12692 (let* ((opoint (point))
12693 (fill-prefix-regexp
12694 (and fill-prefix (not (equal fill-prefix ""))
12695 (not paragraph-ignore-fill-prefix)
12696 (regexp-quote fill-prefix)))
12697 ;; Remove ^ from paragraph-start and paragraph-sep if they are there.
12698 ;; These regexps shouldn't be anchored, because we look for them
12699 ;; starting at the left-margin. This allows paragraph commands to
12700 ;; work normally with indented text.
12701 ;; This hack will not find problem cases like "whatever\\|^something".
12702 (parstart (if (and (not (equal "" paragraph-start))
12703 (equal ?^ (aref paragraph-start 0)))
12704 (substring paragraph-start 1)
12706 (parsep (if (and (not (equal "" paragraph-separate))
12707 (equal ?^ (aref paragraph-separate 0)))
12708 (substring paragraph-separate 1)
12709 paragraph-separate))
12711 (if fill-prefix-regexp
12712 (concat parsep "\\|"
12713 fill-prefix-regexp "[ \t]*$")
12715 ;; This is used for searching.
12716 (sp-parstart (concat "^[ \t]*\\(?:" parstart "\\|" parsep "\\)"))
12718 (while (and (< arg 0) (not (bobp)))
12719 (if (and (not (looking-at parsep))
12720 (re-search-backward "^\n" (max (1- (point)) (point-min)) t)
12721 (looking-at parsep))
12722 (setq arg (1+ arg))
12723 (setq start (point))
12724 ;; Move back over paragraph-separating lines.
12725 (forward-char -1) (beginning-of-line)
12726 (while (and (not (bobp))
12727 (progn (move-to-left-margin)
12728 (looking-at parsep)))
12732 (setq arg (1+ arg))
12733 ;; Go to end of the previous (non-separating) line.
12735 ;; Search back for line that starts or separates paragraphs.
12736 (if (if fill-prefix-regexp
12737 ;; There is a fill prefix; it overrides parstart.
12738 (let (multiple-lines)
12739 (while (and (progn (beginning-of-line) (not (bobp)))
12740 (progn (move-to-left-margin)
12741 (not (looking-at parsep)))
12742 (looking-at fill-prefix-regexp))
12743 (unless (= (point) start)
12744 (setq multiple-lines t))
12746 (move-to-left-margin)
12747 ;; This deleted code caused a long hanging-indent line
12748 ;; not to be filled together with the following lines.
12749 ;; ;; Don't move back over a line before the paragraph
12750 ;; ;; which doesn't start with fill-prefix
12751 ;; ;; unless that is the only line we've moved over.
12752 ;; (and (not (looking-at fill-prefix-regexp))
12754 ;; (forward-line 1))
12756 (while (and (re-search-backward sp-parstart nil 1)
12757 (setq found-start t)
12758 ;; Found a candidate, but need to check if it is a
12760 (progn (setq start (point))
12761 (move-to-left-margin)
12762 (not (looking-at parsep)))
12763 (not (and (looking-at parstart)
12764 (or (not use-hard-newlines)
12767 (1- start) 'hard)))))
12768 (setq found-start nil)
12773 ;; Move forward over paragraph separators.
12774 ;; We know this cannot reach the place we started
12775 ;; because we know we moved back over a non-separator.
12776 (while (and (not (eobp))
12777 (progn (move-to-left-margin)
12778 (looking-at parsep)))
12780 ;; If line before paragraph is just margin, back up to there.
12782 (if (> (current-column) (current-left-margin))
12784 (skip-chars-backward " \t")
12786 (forward-line 1))))
12787 ;; No starter or separator line => use buffer beg.
12788 (goto-char (point-min))))))
12790 (while (and (> arg 0) (not (eobp)))
12791 ;; Move forward over separator lines...
12792 (while (and (not (eobp))
12793 (progn (move-to-left-margin) (not (eobp)))
12794 (looking-at parsep))
12796 (unless (eobp) (setq arg (1- arg)))
12797 ;; ... and one more line.
12799 (if fill-prefix-regexp
12800 ;; There is a fill prefix; it overrides parstart.
12801 (while (and (not (eobp))
12802 (progn (move-to-left-margin) (not (eobp)))
12803 (not (looking-at parsep))
12804 (looking-at fill-prefix-regexp))
12806 (while (and (re-search-forward sp-parstart nil 1)
12807 (progn (setq start (match-beginning 0))
12810 (progn (move-to-left-margin)
12811 (not (looking-at parsep)))
12812 (or (not (looking-at parstart))
12813 (and use-hard-newlines
12814 (not (get-text-property (1- start) 'hard)))))
12816 (if (< (point) (point-max))
12817 (goto-char start))))
12818 (constrain-to-field nil opoint t)
12819 ;; Return the number of steps that could not be done.
12823 The @code{forward-paragraph} function moves point forward to the end
12824 of the paragraph. It is usually bound to @kbd{M-@}} and makes use of a
12825 number of functions that are important in themselves, including
12826 @code{let*}, @code{match-beginning}, and @code{looking-at}.
12828 The function definition for @code{forward-paragraph} is considerably
12829 longer than the function definition for @code{forward-sentence}
12830 because it works with a paragraph, each line of which may begin with a
12833 A fill prefix consists of a string of characters that are repeated at
12834 the beginning of each line. For example, in Lisp code, it is a
12835 convention to start each line of a paragraph-long comment with
12836 @samp{;;; }. In Text mode, four blank spaces make up another common
12837 fill prefix, creating an indented paragraph. (@xref{Fill Prefix, , ,
12838 emacs, The GNU Emacs Manual}, for more information about fill
12841 The existence of a fill prefix means that in addition to being able to
12842 find the end of a paragraph whose lines begin on the left-most
12843 column, the @code{forward-paragraph} function must be able to find the
12844 end of a paragraph when all or many of the lines in the buffer begin
12845 with the fill prefix.
12847 Moreover, it is sometimes practical to ignore a fill prefix that
12848 exists, especially when blank lines separate paragraphs.
12849 This is an added complication.
12852 * forward-paragraph in brief:: Key parts of the function definition.
12853 * fwd-para let:: The @code{let*} expression.
12854 * fwd-para while:: The forward motion @code{while} loop.
12858 @node forward-paragraph in brief
12859 @unnumberedsubsec Shortened @code{forward-paragraph} function definition
12862 Rather than print all of the @code{forward-paragraph} function, we
12863 will only print parts of it. Read without preparation, the function
12867 In outline, the function looks like this:
12871 (defun forward-paragraph (&optional arg)
12872 "@var{documentation}@dots{}"
12874 (or arg (setq arg 1))
12877 (while (and (< arg 0) (not (bobp))) ; @r{backward-moving-code}
12879 (while (and (> arg 0) (not (eobp))) ; @r{forward-moving-code}
12884 The first parts of the function are routine: the function's argument
12885 list consists of one optional argument. Documentation follows.
12887 The lower case @samp{p} in the @code{interactive} declaration means
12888 that the processed prefix argument, if any, is passed to the function.
12889 This will be a number, and is the repeat count of how many paragraphs
12890 point will move. The @code{or} expression in the next line handles
12891 the common case when no argument is passed to the function, which occurs
12892 if the function is called from other code rather than interactively.
12893 This case was described earlier. (@xref{forward-sentence, The
12894 @code{forward-sentence} function}.) Now we reach the end of the
12895 familiar part of this function.
12898 @unnumberedsubsec The @code{let*} expression
12900 The next line of the @code{forward-paragraph} function begins a
12901 @code{let*} expression. This is a different than @code{let}. The
12902 symbol is @code{let*} not @code{let}.
12905 The @code{let*} special form is like @code{let} except that Emacs sets
12906 each variable in sequence, one after another, and variables in the
12907 latter part of the varlist can make use of the values to which Emacs
12908 set variables in the earlier part of the varlist.
12911 ( refappend save-excursion, , code save-excursion in code append-to-buffer .)
12914 (@ref{append save-excursion, , @code{save-excursion} in @code{append-to-buffer}}.)
12916 In the @code{let*} expression in this function, Emacs binds a total of
12917 seven variables: @code{opoint}, @code{fill-prefix-regexp},
12918 @code{parstart}, @code{parsep}, @code{sp-parstart}, @code{start}, and
12919 @code{found-start}.
12921 The variable @code{parsep} appears twice, first, to remove instances
12922 of @samp{^}, and second, to handle fill prefixes.
12924 The variable @code{opoint} is just the value of @code{point}. As you
12925 can guess, it is used in a @code{constrain-to-field} expression, just
12926 as in @code{forward-sentence}.
12928 The variable @code{fill-prefix-regexp} is set to the value returned by
12929 evaluating the following list:
12934 (not (equal fill-prefix ""))
12935 (not paragraph-ignore-fill-prefix)
12936 (regexp-quote fill-prefix))
12941 This is an expression whose first element is the @code{and} special form.
12943 As we learned earlier (@pxref{kill-new function, , The @code{kill-new}
12944 function}), the @code{and} special form evaluates each of its
12945 arguments until one of the arguments returns a value of @code{nil}, in
12946 which case the @code{and} expression returns @code{nil}; however, if
12947 none of the arguments returns a value of @code{nil}, the value
12948 resulting from evaluating the last argument is returned. (Since such
12949 a value is not @code{nil}, it is considered true in Lisp.) In other
12950 words, an @code{and} expression returns a true value only if all its
12951 arguments are true.
12954 In this case, the variable @code{fill-prefix-regexp} is bound to a
12955 non-@code{nil} value only if the following four expressions produce a
12956 true (i.e., a non-@code{nil}) value when they are evaluated; otherwise,
12957 @code{fill-prefix-regexp} is bound to @code{nil}.
12961 When this variable is evaluated, the value of the fill prefix, if any,
12962 is returned. If there is no fill prefix, this variable returns
12965 @item (not (equal fill-prefix "")
12966 This expression checks whether an existing fill prefix is an empty
12967 string, that is, a string with no characters in it. An empty string is
12968 not a useful fill prefix.
12970 @item (not paragraph-ignore-fill-prefix)
12971 This expression returns @code{nil} if the variable
12972 @code{paragraph-ignore-fill-prefix} has been turned on by being set to a
12973 true value such as @code{t}.
12975 @item (regexp-quote fill-prefix)
12976 This is the last argument to the @code{and} special form. If all the
12977 arguments to the @code{and} are true, the value resulting from
12978 evaluating this expression will be returned by the @code{and} expression
12979 and bound to the variable @code{fill-prefix-regexp},
12982 @findex regexp-quote
12984 The result of evaluating this @code{and} expression successfully is that
12985 @code{fill-prefix-regexp} will be bound to the value of
12986 @code{fill-prefix} as modified by the @code{regexp-quote} function.
12987 What @code{regexp-quote} does is read a string and return a regular
12988 expression that will exactly match the string and match nothing else.
12989 This means that @code{fill-prefix-regexp} will be set to a value that
12990 will exactly match the fill prefix if the fill prefix exists.
12991 Otherwise, the variable will be set to @code{nil}.
12993 The next two local variables in the @code{let*} expression are
12994 designed to remove instances of @samp{^} from @code{parstart} and
12995 @code{parsep}, the local variables which indicate the paragraph start
12996 and the paragraph separator. The next expression sets @code{parsep}
12997 again. That is to handle fill prefixes.
12999 This is the setting that requires the definition call @code{let*}
13000 rather than @code{let}. The true-or-false-test for the @code{if}
13001 depends on whether the variable @code{fill-prefix-regexp} evaluates to
13002 @code{nil} or some other value.
13004 If @code{fill-prefix-regexp} does not have a value, Emacs evaluates
13005 the else-part of the @code{if} expression and binds @code{parsep} to
13006 its local value. (@code{parsep} is a regular expression that matches
13007 what separates paragraphs.)
13009 But if @code{fill-prefix-regexp} does have a value, Emacs evaluates
13010 the then-part of the @code{if} expression and binds @code{parsep} to a
13011 regular expression that includes the @code{fill-prefix-regexp} as part
13014 Specifically, @code{parsep} is set to the original value of the
13015 paragraph separate regular expression concatenated with an alternative
13016 expression that consists of the @code{fill-prefix-regexp} followed by
13017 optional whitespace to the end of the line. The whitespace is defined
13018 by @w{@code{"[ \t]*$"}}.) The @samp{\\|} defines this portion of the
13019 regexp as an alternative to @code{parsep}.
13021 According to a comment in the code, the next local variable,
13022 @code{sp-parstart}, is used for searching, and then the final two,
13023 @code{start} and @code{found-start}, are set to @code{nil}.
13025 Now we get into the body of the @code{let*}. The first part of the body
13026 of the @code{let*} deals with the case when the function is given a
13027 negative argument and is therefore moving backwards. We will skip this
13030 @node fwd-para while
13031 @unnumberedsubsec The forward motion @code{while} loop
13033 The second part of the body of the @code{let*} deals with forward
13034 motion. It is a @code{while} loop that repeats itself so long as the
13035 value of @code{arg} is greater than zero. In the most common use of
13036 the function, the value of the argument is 1, so the body of the
13037 @code{while} loop is evaluated exactly once, and the cursor moves
13038 forward one paragraph.
13041 (while (and (> arg 0) (not (eobp)))
13043 ;; Move forward over separator lines...
13044 (while (and (not (eobp))
13045 (progn (move-to-left-margin) (not (eobp)))
13046 (looking-at parsep))
13048 (unless (eobp) (setq arg (1- arg)))
13049 ;; ... and one more line.
13052 (if fill-prefix-regexp
13053 ;; There is a fill prefix; it overrides parstart.
13054 (while (and (not (eobp))
13055 (progn (move-to-left-margin) (not (eobp)))
13056 (not (looking-at parsep))
13057 (looking-at fill-prefix-regexp))
13060 (while (and (re-search-forward sp-parstart nil 1)
13061 (progn (setq start (match-beginning 0))
13064 (progn (move-to-left-margin)
13065 (not (looking-at parsep)))
13066 (or (not (looking-at parstart))
13067 (and use-hard-newlines
13068 (not (get-text-property (1- start) 'hard)))))
13071 (if (< (point) (point-max))
13072 (goto-char start))))
13075 This part handles three situations: when point is between paragraphs,
13076 when there is a fill prefix and when there is no fill prefix.
13079 The @code{while} loop looks like this:
13083 ;; @r{going forwards and not at the end of the buffer}
13084 (while (and (> arg 0) (not (eobp)))
13086 ;; @r{between paragraphs}
13087 ;; Move forward over separator lines...
13088 (while (and (not (eobp))
13089 (progn (move-to-left-margin) (not (eobp)))
13090 (looking-at parsep))
13092 ;; @r{This decrements the loop}
13093 (unless (eobp) (setq arg (1- arg)))
13094 ;; ... and one more line.
13099 (if fill-prefix-regexp
13100 ;; There is a fill prefix; it overrides parstart;
13101 ;; we go forward line by line
13102 (while (and (not (eobp))
13103 (progn (move-to-left-margin) (not (eobp)))
13104 (not (looking-at parsep))
13105 (looking-at fill-prefix-regexp))
13110 ;; There is no fill prefix;
13111 ;; we go forward character by character
13112 (while (and (re-search-forward sp-parstart nil 1)
13113 (progn (setq start (match-beginning 0))
13116 (progn (move-to-left-margin)
13117 (not (looking-at parsep)))
13118 (or (not (looking-at parstart))
13119 (and use-hard-newlines
13120 (not (get-text-property (1- start) 'hard)))))
13125 ;; and if there is no fill prefix and if we are not at the end,
13126 ;; go to whatever was found in the regular expression search
13128 (if (< (point) (point-max))
13129 (goto-char start))))
13134 We can see that this is a decrementing counter @code{while} loop,
13135 using the expression @code{(setq arg (1- arg))} as the decrementer.
13136 That expression is not far from the @code{while}, but is hidden in
13137 another Lisp macro, an @code{unless} macro. Unless we are at the end
13138 of the buffer---that is what the @code{eobp} function determines; it
13139 is an abbreviation of @samp{End Of Buffer P}---we decrease the value
13140 of @code{arg} by one.
13142 (If we are at the end of the buffer, we cannot go forward any more and
13143 the next loop of the @code{while} expression will test false since the
13144 test is an @code{and} with @code{(not (eobp))}. The @code{not}
13145 function means exactly as you expect; it is another name for
13146 @code{null}, a function that returns true when its argument is false.)
13148 Interestingly, the loop count is not decremented until we leave the
13149 space between paragraphs, unless we come to the end of buffer or stop
13150 seeing the local value of the paragraph separator.
13152 That second @code{while} also has a @code{(move-to-left-margin)}
13153 expression. The function is self-explanatory. It is inside a
13154 @code{progn} expression and not the last element of its body, so it is
13155 only invoked for its side effect, which is to move point to the left
13156 margin of the current line.
13159 The @code{looking-at} function is also self-explanatory; it returns
13160 true if the text after point matches the regular expression given as
13163 The rest of the body of the loop looks difficult at first, but makes
13164 sense as you come to understand it.
13167 First consider what happens if there is a fill prefix:
13171 (if fill-prefix-regexp
13172 ;; There is a fill prefix; it overrides parstart;
13173 ;; we go forward line by line
13174 (while (and (not (eobp))
13175 (progn (move-to-left-margin) (not (eobp)))
13176 (not (looking-at parsep))
13177 (looking-at fill-prefix-regexp))
13183 This expression moves point forward line by line so long
13184 as four conditions are true:
13188 Point is not at the end of the buffer.
13191 We can move to the left margin of the text and are
13192 not at the end of the buffer.
13195 The text following point does not separate paragraphs.
13198 The pattern following point is the fill prefix regular expression.
13201 The last condition may be puzzling, until you remember that point was
13202 moved to the beginning of the line early in the @code{forward-paragraph}
13203 function. This means that if the text has a fill prefix, the
13204 @code{looking-at} function will see it.
13207 Consider what happens when there is no fill prefix.
13211 (while (and (re-search-forward sp-parstart nil 1)
13212 (progn (setq start (match-beginning 0))
13215 (progn (move-to-left-margin)
13216 (not (looking-at parsep)))
13217 (or (not (looking-at parstart))
13218 (and use-hard-newlines
13219 (not (get-text-property (1- start) 'hard)))))
13225 This @code{while} loop has us searching forward for
13226 @code{sp-parstart}, which is the combination of possible whitespace
13227 with the local value of the start of a paragraph or of a paragraph
13228 separator. (The latter two are within an expression starting
13229 @code{\(?:} so that they are not referenced by the
13230 @code{match-beginning} function.)
13233 The two expressions,
13237 (setq start (match-beginning 0))
13243 mean go to the start of the text matched by the regular expression
13246 The @code{(match-beginning 0)} expression is new. It returns a number
13247 specifying the location of the start of the text that was matched by
13250 The @code{match-beginning} function is used here because of a
13251 characteristic of a forward search: a successful forward search,
13252 regardless of whether it is a plain search or a regular expression
13253 search, moves point to the end of the text that is found. In this
13254 case, a successful search moves point to the end of the pattern for
13255 @code{sp-parstart}.
13257 However, we want to put point at the end of the current paragraph, not
13258 somewhere else. Indeed, since the search possibly includes the
13259 paragraph separator, point may end up at the beginning of the next one
13260 unless we use an expression that includes @code{match-beginning}.
13262 @findex match-beginning
13263 When given an argument of 0, @code{match-beginning} returns the
13264 position that is the start of the text matched by the most recent
13265 search. In this case, the most recent search looks for
13266 @code{sp-parstart}. The @code{(match-beginning 0)} expression returns
13267 the beginning position of that pattern, rather than the end position
13270 (Incidentally, when passed a positive number as an argument, the
13271 @code{match-beginning} function returns the location of point at that
13272 parenthesized expression in the last search unless that parenthesized
13273 expression begins with @code{\(?:}. I don't know why @code{\(?:}
13274 appears here since the argument is 0.)
13277 The last expression when there is no fill prefix is
13281 (if (< (point) (point-max))
13282 (goto-char start))))
13287 This says that if there is no fill prefix and if we are not at the
13288 end, point should move to the beginning of whatever was found by the
13289 regular expression search for @code{sp-parstart}.
13291 The full definition for the @code{forward-paragraph} function not only
13292 includes code for going forwards, but also code for going backwards.
13294 If you are reading this inside of GNU Emacs and you want to see the
13295 whole function, you can type @kbd{C-h f} (@code{describe-function})
13296 and the name of the function. This gives you the function
13297 documentation and the name of the library containing the function's
13298 source. Place point over the name of the library and press the RET
13299 key; you will be taken directly to the source. (Be sure to install
13300 your sources! Without them, you are like a person who tries to drive
13301 a car with his eyes shut!)
13304 @section Create Your Own @file{TAGS} File
13306 @cindex @file{TAGS} file, create own
13308 Besides @kbd{C-h f} (@code{describe-function}), another way to see the
13309 source of a function is to type @kbd{M-.} (@code{find-tag}) and the
13310 name of the function when prompted for it. This is a good habit to
13311 get into. The @kbd{M-.} (@code{find-tag}) command takes you directly
13312 to the source for a function, variable, or node. The function depends
13313 on tags tables to tell it where to go.
13315 If the @code{find-tag} function first asks you for the name of a
13316 @file{TAGS} table, give it the name of a @file{TAGS} file such as
13317 @file{/usr/local/src/emacs/src/TAGS}. (The exact path to your
13318 @file{TAGS} file depends on how your copy of Emacs was installed. I
13319 just told you the location that provides both my C and my Emacs Lisp
13322 You can also create your own @file{TAGS} file for directories that
13325 You often need to build and install tags tables yourself. They are
13326 not built automatically. A tags table is called a @file{TAGS} file;
13327 the name is in upper case letters.
13329 You can create a @file{TAGS} file by calling the @code{etags} program
13330 that comes as a part of the Emacs distribution. Usually, @code{etags}
13331 is compiled and installed when Emacs is built. (@code{etags} is not
13332 an Emacs Lisp function or a part of Emacs; it is a C program.)
13335 To create a @file{TAGS} file, first switch to the directory in which
13336 you want to create the file. In Emacs you can do this with the
13337 @kbd{M-x cd} command, or by visiting a file in the directory, or by
13338 listing the directory with @kbd{C-x d} (@code{dired}). Then run the
13339 compile command, with @w{@code{etags *.el}} as the command to execute
13342 M-x compile RET etags *.el RET
13346 to create a @file{TAGS} file for Emacs Lisp.
13348 For example, if you have a large number of files in your
13349 @file{~/emacs} directory, as I do---I have 137 @file{.el} files in it,
13350 of which I load 12---you can create a @file{TAGS} file for the Emacs
13351 Lisp files in that directory.
13354 The @code{etags} program takes all the usual shell wildcards. For
13355 example, if you have two directories for which you want a single
13356 @file{TAGS} file, type @w{@code{etags *.el ../elisp/*.el}}, where
13357 @file{../elisp/} is the second directory:
13360 M-x compile RET etags *.el ../elisp/*.el RET
13367 M-x compile RET etags --help RET
13371 to see a list of the options accepted by @code{etags} as well as a
13372 list of supported languages.
13374 The @code{etags} program handles more than 20 languages, including
13375 Emacs Lisp, Common Lisp, Scheme, C, C++, Ada, Fortran, HTML, Java,
13376 LaTeX, Pascal, Perl, PostScript, Python, TeX, Texinfo, makefiles, and
13377 most assemblers. The program has no switches for specifying the
13378 language; it recognizes the language in an input file according to its
13379 file name and contents.
13381 @file{etags} is very helpful when you are writing code yourself and
13382 want to refer back to functions you have already written. Just run
13383 @code{etags} again at intervals as you write new functions, so they
13384 become part of the @file{TAGS} file.
13386 If you think an appropriate @file{TAGS} file already exists for what
13387 you want, but do not know where it is, you can use the @code{locate}
13388 program to attempt to find it.
13390 Type @w{@kbd{M-x locate @key{RET} TAGS @key{RET}}} and Emacs will list
13391 for you the full path names of all your @file{TAGS} files. On my
13392 system, this command lists 34 @file{TAGS} files. On the other hand, a
13393 plain vanilla system I recently installed did not contain any
13396 If the tags table you want has been created, you can use the @code{M-x
13397 visit-tags-table} command to specify it. Otherwise, you will need to
13398 create the tag table yourself and then use @code{M-x
13401 @subsubheading Building Tags in the Emacs sources
13402 @cindex Building Tags in the Emacs sources
13403 @cindex Tags in the Emacs sources
13406 The GNU Emacs sources come with a @file{Makefile} that contains a
13407 sophisticated @code{etags} command that creates, collects, and merges
13408 tags tables from all over the Emacs sources and puts the information
13409 into one @file{TAGS} file in the @file{src/} directory. (The
13410 @file{src/} directory is below the top level of your Emacs directory.)
13413 To build this @file{TAGS} file, go to the top level of your Emacs
13414 source directory and run the compile command @code{make tags}:
13417 M-x compile RET make tags RET
13421 (The @code{make tags} command works well with the GNU Emacs sources,
13422 as well as with some other source packages.)
13424 For more information, see @ref{Tags, , Tag Tables, emacs, The GNU Emacs
13427 @node Regexp Review
13430 Here is a brief summary of some recently introduced functions.
13434 Repeatedly evaluate the body of the expression so long as the first
13435 element of the body tests true. Then return @code{nil}. (The
13436 expression is evaluated only for its side effects.)
13445 (insert (format "foo is %d.\n" foo))
13446 (setq foo (1- foo))))
13448 @result{} foo is 2.
13455 (The @code{insert} function inserts its arguments at point; the
13456 @code{format} function returns a string formatted from its arguments
13457 the way @code{message} formats its arguments; @code{\n} produces a new
13460 @item re-search-forward
13461 Search for a pattern, and if the pattern is found, move point to rest
13465 Takes four arguments, like @code{search-forward}:
13469 A regular expression that specifies the pattern to search for.
13470 (Remember to put quotation marks around this argument!)
13473 Optionally, the limit of the search.
13476 Optionally, what to do if the search fails, return @code{nil} or an
13480 Optionally, how many times to repeat the search; if negative, the
13481 search goes backwards.
13485 Bind some variables locally to particular values,
13486 and then evaluate the remaining arguments, returning the value of the
13487 last one. While binding the local variables, use the local values of
13488 variables bound earlier, if any.
13497 (message "`bar' is %d." bar))
13498 @result{} ‘bar’ is 21.
13502 @item match-beginning
13503 Return the position of the start of the text found by the last regular
13507 Return @code{t} for true if the text after point matches the argument,
13508 which should be a regular expression.
13511 Return @code{t} for true if point is at the end of the accessible part
13512 of a buffer. The end of the accessible part is the end of the buffer
13513 if the buffer is not narrowed; it is the end of the narrowed part if
13514 the buffer is narrowed.
13518 @node re-search Exercises
13519 @section Exercises with @code{re-search-forward}
13523 Write a function to search for a regular expression that matches two
13524 or more blank lines in sequence.
13527 Write a function to search for duplicated words, such as ``the the''.
13528 @xref{Regexps, , Syntax of Regular Expressions, emacs, The GNU Emacs
13529 Manual}, for information on how to write a regexp (a regular
13530 expression) to match a string that is composed of two identical
13531 halves. You can devise several regexps; some are better than others.
13532 The function I use is described in an appendix, along with several
13533 regexps. @xref{the-the, , @code{the-the} Duplicated Words Function}.
13536 @node Counting Words
13537 @chapter Counting via Repetition and Regexps
13538 @cindex Repetition for word counting
13539 @cindex Regular expressions for word counting
13541 Repetition and regular expression searches are powerful tools that you
13542 often use when you write code in Emacs Lisp. This chapter illustrates
13543 the use of regular expression searches through the construction of
13544 word count commands using @code{while} loops and recursion.
13547 * Why Count Words::
13548 * @value{COUNT-WORDS}:: Use a regexp, but find a problem.
13549 * recursive-count-words:: Start with case of no words in region.
13550 * Counting Exercise::
13554 @node Why Count Words
13555 @unnumberedsec Counting words
13558 The standard Emacs distribution contains functions for counting the
13559 number of lines and words within a region.
13561 Certain types of writing ask you to count words. Thus, if you write
13562 an essay, you may be limited to 800 words; if you write a novel, you
13563 may discipline yourself to write 1000 words a day. It seems odd, but
13564 for a long time, Emacs lacked a word count command. Perhaps people used
13565 Emacs mostly for code or types of documentation that did not require
13566 word counts; or perhaps they restricted themselves to the operating
13567 system word count command, @code{wc}. Alternatively, people may have
13568 followed the publishers' convention and computed a word count by
13569 dividing the number of characters in a document by five.
13571 There are many ways to implement a command to count words. Here are
13572 some examples, which you may wish to compare with the standard Emacs
13573 command, @code{count-words-region}.
13575 @node @value{COUNT-WORDS}
13576 @section The @code{@value{COUNT-WORDS}} Function
13577 @findex @value{COUNT-WORDS}
13579 A word count command could count words in a line, paragraph, region,
13580 or buffer. What should the command cover? You could design the
13581 command to count the number of words in a complete buffer. However,
13582 the Emacs tradition encourages flexibility---you may want to count
13583 words in just a section, rather than all of a buffer. So it makes
13584 more sense to design the command to count the number of words in a
13585 region. Once you have a command to count words in a region, you can,
13586 if you wish, count words in a whole buffer by marking it with
13587 @w{@kbd{C-x h}} (@code{mark-whole-buffer}).
13589 Clearly, counting words is a repetitive act: starting from the
13590 beginning of the region, you count the first word, then the second
13591 word, then the third word, and so on, until you reach the end of the
13592 region. This means that word counting is ideally suited to recursion
13593 or to a @code{while} loop.
13596 * Design @value{COUNT-WORDS}:: The definition using a @code{while} loop.
13597 * Whitespace Bug:: The Whitespace Bug in @code{@value{COUNT-WORDS}}.
13601 @node Design @value{COUNT-WORDS}
13602 @unnumberedsubsec Designing @code{@value{COUNT-WORDS}}
13605 First, we will implement the word count command with a @code{while}
13606 loop, then with recursion. The command will, of course, be
13610 The template for an interactive function definition is, as always:
13614 (defun @var{name-of-function} (@var{argument-list})
13615 "@var{documentation}@dots{}"
13616 (@var{interactive-expression}@dots{})
13621 What we need to do is fill in the slots.
13623 The name of the function should be self-explanatory and similar to the
13624 existing @code{count-lines-region} name. This makes the name easier
13625 to remember. @code{count-words-region} is the obvious choice. Since
13626 that name is now used for the standard Emacs command to count words, we
13627 will name our implementation @code{@value{COUNT-WORDS}}.
13629 The function counts words within a region. This means that the
13630 argument list must contain symbols that are bound to the two
13631 positions, the beginning and end of the region. These two positions
13632 can be called @samp{beginning} and @samp{end} respectively. The first
13633 line of the documentation should be a single sentence, since that is
13634 all that is printed as documentation by a command such as
13635 @code{apropos}. The interactive expression will be of the form
13636 @samp{(interactive "r")}, since that will cause Emacs to pass the
13637 beginning and end of the region to the function's argument list. All
13640 The body of the function needs to be written to do three tasks:
13641 first, to set up conditions under which the @code{while} loop can
13642 count words, second, to run the @code{while} loop, and third, to send
13643 a message to the user.
13645 When a user calls @code{@value{COUNT-WORDS}}, point may be at the
13646 beginning or the end of the region. However, the counting process
13647 must start at the beginning of the region. This means we will want
13648 to put point there if it is not already there. Executing
13649 @code{(goto-char beginning)} ensures this. Of course, we will want to
13650 return point to its expected position when the function finishes its
13651 work. For this reason, the body must be enclosed in a
13652 @code{save-excursion} expression.
13654 The central part of the body of the function consists of a
13655 @code{while} loop in which one expression jumps point forward word by
13656 word, and another expression counts those jumps. The true-or-false-test
13657 of the @code{while} loop should test true so long as point should jump
13658 forward, and false when point is at the end of the region.
13660 We could use @code{(forward-word 1)} as the expression for moving point
13661 forward word by word, but it is easier to see what Emacs identifies as a
13662 ``word'' if we use a regular expression search.
13664 A regular expression search that finds the pattern for which it is
13665 searching leaves point after the last character matched. This means
13666 that a succession of successful word searches will move point forward
13669 As a practical matter, we want the regular expression search to jump
13670 over whitespace and punctuation between words as well as over the
13671 words themselves. A regexp that refuses to jump over interword
13672 whitespace would never jump more than one word! This means that
13673 the regexp should include the whitespace and punctuation that follows
13674 a word, if any, as well as the word itself. (A word may end a buffer
13675 and not have any following whitespace or punctuation, so that part of
13676 the regexp must be optional.)
13678 Thus, what we want for the regexp is a pattern defining one or more
13679 word constituent characters followed, optionally, by one or more
13680 characters that are not word constituents. The regular expression for
13688 The buffer's syntax table determines which characters are and are not
13689 word constituents. For more information about syntax,
13690 @pxref{Syntax Tables, , Syntax Tables, elisp, The GNU Emacs Lisp
13694 The search expression looks like this:
13697 (re-search-forward "\\w+\\W*")
13701 (Note that paired backslashes precede the @samp{w} and @samp{W}. A
13702 single backslash has special meaning to the Emacs Lisp interpreter.
13703 It indicates that the following character is interpreted differently
13704 than usual. For example, the two characters, @samp{\n}, stand for
13705 @samp{newline}, rather than for a backslash followed by @samp{n}. Two
13706 backslashes in a row stand for an ordinary, unspecial backslash, so
13707 Emacs Lisp interpreter ends of seeing a single backslash followed by a
13708 letter. So it discovers the letter is special.)
13710 We need a counter to count how many words there are; this variable
13711 must first be set to 0 and then incremented each time Emacs goes
13712 around the @code{while} loop. The incrementing expression is simply:
13715 (setq count (1+ count))
13718 Finally, we want to tell the user how many words there are in the
13719 region. The @code{message} function is intended for presenting this
13720 kind of information to the user. The message has to be phrased so
13721 that it reads properly regardless of how many words there are in the
13722 region: we don't want to say that ``there are 1 words in the region''.
13723 The conflict between singular and plural is ungrammatical. We can
13724 solve this problem by using a conditional expression that evaluates
13725 different messages depending on the number of words in the region.
13726 There are three possibilities: no words in the region, one word in the
13727 region, and more than one word. This means that the @code{cond}
13728 special form is appropriate.
13731 All this leads to the following function definition:
13735 ;;; @r{First version; has bugs!}
13736 (defun @value{COUNT-WORDS} (beginning end)
13737 "Print number of words in the region.
13738 Words are defined as at least one word-constituent
13739 character followed by at least one character that
13740 is not a word-constituent. The buffer's syntax
13741 table determines which characters these are."
13743 (message "Counting words in region ... ")
13747 ;;; @r{1. Set up appropriate conditions.}
13749 (goto-char beginning)
13754 ;;; @r{2. Run the} while @r{loop.}
13755 (while (< (point) end)
13756 (re-search-forward "\\w+\\W*")
13757 (setq count (1+ count)))
13761 ;;; @r{3. Send a message to the user.}
13762 (cond ((zerop count)
13764 "The region does NOT have any words."))
13767 "The region has 1 word."))
13770 "The region has %d words." count))))))
13775 As written, the function works, but not in all circumstances.
13777 @node Whitespace Bug
13778 @subsection The Whitespace Bug in @code{@value{COUNT-WORDS}}
13780 The @code{@value{COUNT-WORDS}} command described in the preceding
13781 section has two bugs, or rather, one bug with two manifestations.
13782 First, if you mark a region containing only whitespace in the middle
13783 of some text, the @code{@value{COUNT-WORDS}} command tells you that the
13784 region contains one word! Second, if you mark a region containing
13785 only whitespace at the end of the buffer or the accessible portion of
13786 a narrowed buffer, the command displays an error message that looks
13790 Search failed: "\\w+\\W*"
13793 If you are reading this in Info in GNU Emacs, you can test for these
13796 First, evaluate the function in the usual manner to install it.
13798 Here is a copy of the definition. Place your cursor after the closing
13799 parenthesis and type @kbd{C-x C-e} to install it.
13803 ;; @r{First version; has bugs!}
13804 (defun @value{COUNT-WORDS} (beginning end)
13805 "Print number of words in the region.
13806 Words are defined as at least one word-constituent character followed
13807 by at least one character that is not a word-constituent. The buffer's
13808 syntax table determines which characters these are."
13812 (message "Counting words in region ... ")
13816 ;;; @r{1. Set up appropriate conditions.}
13818 (goto-char beginning)
13823 ;;; @r{2. Run the} while @r{loop.}
13824 (while (< (point) end)
13825 (re-search-forward "\\w+\\W*")
13826 (setq count (1+ count)))
13830 ;;; @r{3. Send a message to the user.}
13831 (cond ((zerop count)
13832 (message "The region does NOT have any words."))
13833 ((= 1 count) (message "The region has 1 word."))
13834 (t (message "The region has %d words." count))))))
13840 If you wish, you can also install this keybinding by evaluating it:
13843 (global-set-key "\C-c=" '@value{COUNT-WORDS})
13846 To conduct the first test, set mark and point to the beginning and end
13847 of the following line and then type @kbd{C-c =} (or @kbd{M-x
13848 @value{COUNT-WORDS}} if you have not bound @kbd{C-c =}):
13855 Emacs will tell you, correctly, that the region has three words.
13857 Repeat the test, but place mark at the beginning of the line and place
13858 point just @emph{before} the word @samp{one}. Again type the command
13859 @kbd{C-c =} (or @kbd{M-x @value{COUNT-WORDS}}). Emacs should tell you
13860 that the region has no words, since it is composed only of the
13861 whitespace at the beginning of the line. But instead Emacs tells you
13862 that the region has one word!
13864 For the third test, copy the sample line to the end of the
13865 @file{*scratch*} buffer and then type several spaces at the end of the
13866 line. Place mark right after the word @samp{three} and point at the
13867 end of line. (The end of the line will be the end of the buffer.)
13868 Type @kbd{C-c =} (or @kbd{M-x @value{COUNT-WORDS}}) as you did before.
13869 Again, Emacs should tell you that the region has no words, since it is
13870 composed only of the whitespace at the end of the line. Instead,
13871 Emacs displays an error message saying @samp{Search failed}.
13873 The two bugs stem from the same problem.
13875 Consider the first manifestation of the bug, in which the command
13876 tells you that the whitespace at the beginning of the line contains
13877 one word. What happens is this: The @code{M-x @value{COUNT-WORDS}}
13878 command moves point to the beginning of the region. The @code{while}
13879 tests whether the value of point is smaller than the value of
13880 @code{end}, which it is. Consequently, the regular expression search
13881 looks for and finds the first word. It leaves point after the word.
13882 @code{count} is set to one. The @code{while} loop repeats; but this
13883 time the value of point is larger than the value of @code{end}, the
13884 loop is exited; and the function displays a message saying the number
13885 of words in the region is one. In brief, the regular expression
13886 search looks for and finds the word even though it is outside
13889 In the second manifestation of the bug, the region is whitespace at
13890 the end of the buffer. Emacs says @samp{Search failed}. What happens
13891 is that the true-or-false-test in the @code{while} loop tests true, so
13892 the search expression is executed. But since there are no more words
13893 in the buffer, the search fails.
13895 In both manifestations of the bug, the search extends or attempts to
13896 extend outside of the region.
13898 The solution is to limit the search to the region---this is a fairly
13899 simple action, but as you may have come to expect, it is not quite as
13900 simple as you might think.
13902 As we have seen, the @code{re-search-forward} function takes a search
13903 pattern as its first argument. But in addition to this first,
13904 mandatory argument, it accepts three optional arguments. The optional
13905 second argument bounds the search. The optional third argument, if
13906 @code{t}, causes the function to return @code{nil} rather than signal
13907 an error if the search fails. The optional fourth argument is a
13908 repeat count. (In Emacs, you can see a function's documentation by
13909 typing @kbd{C-h f}, the name of the function, and then @key{RET}.)
13911 In the @code{@value{COUNT-WORDS}} definition, the value of the end of
13912 the region is held by the variable @code{end} which is passed as an
13913 argument to the function. Thus, we can add @code{end} as an argument
13914 to the regular expression search expression:
13917 (re-search-forward "\\w+\\W*" end)
13920 However, if you make only this change to the @code{@value{COUNT-WORDS}}
13921 definition and then test the new version of the definition on a
13922 stretch of whitespace, you will receive an error message saying
13923 @samp{Search failed}.
13925 What happens is this: the search is limited to the region, and fails
13926 as you expect because there are no word-constituent characters in the
13927 region. Since it fails, we receive an error message. But we do not
13928 want to receive an error message in this case; we want to receive the
13929 message ``The region does NOT have any words.''
13931 The solution to this problem is to provide @code{re-search-forward}
13932 with a third argument of @code{t}, which causes the function to return
13933 @code{nil} rather than signal an error if the search fails.
13935 However, if you make this change and try it, you will see the message
13936 ``Counting words in region ... '' and @dots{} you will keep on seeing
13937 that message @dots{}, until you type @kbd{C-g} (@code{keyboard-quit}).
13939 Here is what happens: the search is limited to the region, as before,
13940 and it fails because there are no word-constituent characters in the
13941 region, as expected. Consequently, the @code{re-search-forward}
13942 expression returns @code{nil}. It does nothing else. In particular,
13943 it does not move point, which it does as a side effect if it finds the
13944 search target. After the @code{re-search-forward} expression returns
13945 @code{nil}, the next expression in the @code{while} loop is evaluated.
13946 This expression increments the count. Then the loop repeats. The
13947 true-or-false-test tests true because the value of point is still less
13948 than the value of end, since the @code{re-search-forward} expression
13949 did not move point. @dots{} and the cycle repeats @dots{}
13951 The @code{@value{COUNT-WORDS}} definition requires yet another
13952 modification, to cause the true-or-false-test of the @code{while} loop
13953 to test false if the search fails. Put another way, there are two
13954 conditions that must be satisfied in the true-or-false-test before the
13955 word count variable is incremented: point must still be within the
13956 region and the search expression must have found a word to count.
13958 Since both the first condition and the second condition must be true
13959 together, the two expressions, the region test and the search
13960 expression, can be joined with an @code{and} special form and embedded in
13961 the @code{while} loop as the true-or-false-test, like this:
13964 (and (< (point) end) (re-search-forward "\\w+\\W*" end t))
13967 @c colon in printed section title causes problem in Info cross reference
13968 @c also trouble with an overfull hbox
13971 (For information about @code{and}, see
13972 @ref{kill-new function, , The @code{kill-new} function}.)
13976 (@xref{kill-new function, , The @code{kill-new} function}, for
13977 information about @code{and}.)
13980 The @code{re-search-forward} expression returns @code{t} if the search
13981 succeeds and as a side effect moves point. Consequently, as words are
13982 found, point is moved through the region. When the search expression
13983 fails to find another word, or when point reaches the end of the
13984 region, the true-or-false-test tests false, the @code{while} loop
13985 exits, and the @code{@value{COUNT-WORDS}} function displays one or
13986 other of its messages.
13988 After incorporating these final changes, the @code{@value{COUNT-WORDS}}
13989 works without bugs (or at least, without bugs that I have found!).
13990 Here is what it looks like:
13994 ;;; @r{Final version:} @code{while}
13995 (defun @value{COUNT-WORDS} (beginning end)
13996 "Print number of words in the region."
13998 (message "Counting words in region ... ")
14002 ;;; @r{1. Set up appropriate conditions.}
14005 (goto-char beginning)
14009 ;;; @r{2. Run the} while @r{loop.}
14010 (while (and (< (point) end)
14011 (re-search-forward "\\w+\\W*" end t))
14012 (setq count (1+ count)))
14016 ;;; @r{3. Send a message to the user.}
14017 (cond ((zerop count)
14019 "The region does NOT have any words."))
14022 "The region has 1 word."))
14025 "The region has %d words." count))))))
14029 @node recursive-count-words
14030 @section Count Words Recursively
14031 @cindex Count words recursively
14032 @cindex Recursively counting words
14033 @cindex Words, counted recursively
14035 You can write the function for counting words recursively as well as
14036 with a @code{while} loop. Let's see how this is done.
14038 First, we need to recognize that the @code{@value{COUNT-WORDS}}
14039 function has three jobs: it sets up the appropriate conditions for
14040 counting to occur; it counts the words in the region; and it sends a
14041 message to the user telling how many words there are.
14043 If we write a single recursive function to do everything, we will
14044 receive a message for every recursive call. If the region contains 13
14045 words, we will receive thirteen messages, one right after the other.
14046 We don't want this! Instead, we must write two functions to do the
14047 job, one of which (the recursive function) will be used inside of the
14048 other. One function will set up the conditions and display the
14049 message; the other will return the word count.
14051 Let us start with the function that causes the message to be displayed.
14052 We can continue to call this @code{@value{COUNT-WORDS}}.
14054 This is the function that the user will call. It will be interactive.
14055 Indeed, it will be similar to our previous versions of this
14056 function, except that it will call @code{recursive-count-words} to
14057 determine how many words are in the region.
14060 We can readily construct a template for this function, based on our
14065 ;; @r{Recursive version; uses regular expression search}
14066 (defun @value{COUNT-WORDS} (beginning end)
14067 "@var{documentation}@dots{}"
14068 (@var{interactive-expression}@dots{})
14072 ;;; @r{1. Set up appropriate conditions.}
14073 (@var{explanatory message})
14074 (@var{set-up functions}@dots{}
14078 ;;; @r{2. Count the words.}
14079 @var{recursive call}
14083 ;;; @r{3. Send a message to the user.}
14084 @var{message providing word count}))
14088 The definition looks straightforward, except that somehow the count
14089 returned by the recursive call must be passed to the message
14090 displaying the word count. A little thought suggests that this can be
14091 done by making use of a @code{let} expression: we can bind a variable
14092 in the varlist of a @code{let} expression to the number of words in
14093 the region, as returned by the recursive call; and then the
14094 @code{cond} expression, using binding, can display the value to the
14097 Often, one thinks of the binding within a @code{let} expression as
14098 somehow secondary to the primary work of a function. But in this
14099 case, what you might consider the primary job of the function,
14100 counting words, is done within the @code{let} expression.
14103 Using @code{let}, the function definition looks like this:
14107 (defun @value{COUNT-WORDS} (beginning end)
14108 "Print number of words in the region."
14113 ;;; @r{1. Set up appropriate conditions.}
14114 (message "Counting words in region ... ")
14116 (goto-char beginning)
14120 ;;; @r{2. Count the words.}
14121 (let ((count (recursive-count-words end)))
14125 ;;; @r{3. Send a message to the user.}
14126 (cond ((zerop count)
14128 "The region does NOT have any words."))
14131 "The region has 1 word."))
14134 "The region has %d words." count))))))
14138 Next, we need to write the recursive counting function.
14140 A recursive function has at least three parts: the do-again-test, the
14141 next-step-expression, and the recursive call.
14143 The do-again-test determines whether the function will or will not be
14144 called again. Since we are counting words in a region and can use a
14145 function that moves point forward for every word, the do-again-test
14146 can check whether point is still within the region. The do-again-test
14147 should find the value of point and determine whether point is before,
14148 at, or after the value of the end of the region. We can use the
14149 @code{point} function to locate point. Clearly, we must pass the
14150 value of the end of the region to the recursive counting function as an
14153 In addition, the do-again-test should also test whether the search finds a
14154 word. If it does not, the function should not call itself again.
14156 The next-step-expression changes a value so that when the recursive
14157 function is supposed to stop calling itself, it stops. More
14158 precisely, the next-step-expression changes a value so that at the
14159 right time, the do-again-test stops the recursive function from
14160 calling itself again. In this case, the next-step-expression can be
14161 the expression that moves point forward, word by word.
14163 The third part of a recursive function is the recursive call.
14165 Somewhere, we also need a part that does the work of the
14166 function, a part that does the counting. A vital part!
14169 But already, we have an outline of the recursive counting function:
14173 (defun recursive-count-words (region-end)
14174 "@var{documentation}@dots{}"
14175 @var{do-again-test}
14176 @var{next-step-expression}
14177 @var{recursive call})
14181 Now we need to fill in the slots. Let's start with the simplest cases
14182 first: if point is at or beyond the end of the region, there cannot
14183 be any words in the region, so the function should return zero.
14184 Likewise, if the search fails, there are no words to count, so the
14185 function should return zero.
14187 On the other hand, if point is within the region and the search
14188 succeeds, the function should call itself again.
14191 Thus, the do-again-test should look like this:
14195 (and (< (point) region-end)
14196 (re-search-forward "\\w+\\W*" region-end t))
14200 Note that the search expression is part of the do-again-test---the
14201 function returns @code{t} if its search succeeds and @code{nil} if it
14202 fails. (@xref{Whitespace Bug, , The Whitespace Bug in
14203 @code{@value{COUNT-WORDS}}}, for an explanation of how
14204 @code{re-search-forward} works.)
14206 The do-again-test is the true-or-false test of an @code{if} clause.
14207 Clearly, if the do-again-test succeeds, the then-part of the @code{if}
14208 clause should call the function again; but if it fails, the else-part
14209 should return zero since either point is outside the region or the
14210 search failed because there were no words to find.
14212 But before considering the recursive call, we need to consider the
14213 next-step-expression. What is it? Interestingly, it is the search
14214 part of the do-again-test.
14216 In addition to returning @code{t} or @code{nil} for the
14217 do-again-test, @code{re-search-forward} moves point forward as a side
14218 effect of a successful search. This is the action that changes the
14219 value of point so that the recursive function stops calling itself
14220 when point completes its movement through the region. Consequently,
14221 the @code{re-search-forward} expression is the next-step-expression.
14224 In outline, then, the body of the @code{recursive-count-words}
14225 function looks like this:
14229 (if @var{do-again-test-and-next-step-combined}
14231 @var{recursive-call-returning-count}
14237 How to incorporate the mechanism that counts?
14239 If you are not used to writing recursive functions, a question like
14240 this can be troublesome. But it can and should be approached
14243 We know that the counting mechanism should be associated in some way
14244 with the recursive call. Indeed, since the next-step-expression moves
14245 point forward by one word, and since a recursive call is made for
14246 each word, the counting mechanism must be an expression that adds one
14247 to the value returned by a call to @code{recursive-count-words}.
14250 Consider several cases:
14254 If there are two words in the region, the function should return
14255 a value resulting from adding one to the value returned when it counts
14256 the first word, plus the number returned when it counts the remaining
14257 words in the region, which in this case is one.
14260 If there is one word in the region, the function should return
14261 a value resulting from adding one to the value returned when it counts
14262 that word, plus the number returned when it counts the remaining
14263 words in the region, which in this case is zero.
14266 If there are no words in the region, the function should return zero.
14269 From the sketch we can see that the else-part of the @code{if} returns
14270 zero for the case of no words. This means that the then-part of the
14271 @code{if} must return a value resulting from adding one to the value
14272 returned from a count of the remaining words.
14275 The expression will look like this, where @code{1+} is a function that
14276 adds one to its argument.
14279 (1+ (recursive-count-words region-end))
14283 The whole @code{recursive-count-words} function will then look like
14288 (defun recursive-count-words (region-end)
14289 "@var{documentation}@dots{}"
14291 ;;; @r{1. do-again-test}
14292 (if (and (< (point) region-end)
14293 (re-search-forward "\\w+\\W*" region-end t))
14297 ;;; @r{2. then-part: the recursive call}
14298 (1+ (recursive-count-words region-end))
14300 ;;; @r{3. else-part}
14306 Let's examine how this works:
14308 If there are no words in the region, the else part of the @code{if}
14309 expression is evaluated and consequently the function returns zero.
14311 If there is one word in the region, the value of point is less than
14312 the value of @code{region-end} and the search succeeds. In this case,
14313 the true-or-false-test of the @code{if} expression tests true, and the
14314 then-part of the @code{if} expression is evaluated. The counting
14315 expression is evaluated. This expression returns a value (which will
14316 be the value returned by the whole function) that is the sum of one
14317 added to the value returned by a recursive call.
14319 Meanwhile, the next-step-expression has caused point to jump over the
14320 first (and in this case only) word in the region. This means that
14321 when @code{(recursive-count-words region-end)} is evaluated a second
14322 time, as a result of the recursive call, the value of point will be
14323 equal to or greater than the value of region end. So this time,
14324 @code{recursive-count-words} will return zero. The zero will be added
14325 to one, and the original evaluation of @code{recursive-count-words}
14326 will return one plus zero, which is one, which is the correct amount.
14328 Clearly, if there are two words in the region, the first call to
14329 @code{recursive-count-words} returns one added to the value returned
14330 by calling @code{recursive-count-words} on a region containing the
14331 remaining word---that is, it adds one to one, producing two, which is
14332 the correct amount.
14334 Similarly, if there are three words in the region, the first call to
14335 @code{recursive-count-words} returns one added to the value returned
14336 by calling @code{recursive-count-words} on a region containing the
14337 remaining two words---and so on and so on.
14341 With full documentation the two functions look like this:
14345 The recursive function:
14347 @findex recursive-count-words
14350 (defun recursive-count-words (region-end)
14351 "Number of words between point and REGION-END."
14355 ;;; @r{1. do-again-test}
14356 (if (and (< (point) region-end)
14357 (re-search-forward "\\w+\\W*" region-end t))
14361 ;;; @r{2. then-part: the recursive call}
14362 (1+ (recursive-count-words region-end))
14364 ;;; @r{3. else-part}
14375 ;;; @r{Recursive version}
14376 (defun @value{COUNT-WORDS} (beginning end)
14377 "Print number of words in the region.
14381 Words are defined as at least one word-constituent
14382 character followed by at least one character that is
14383 not a word-constituent. The buffer's syntax table
14384 determines which characters these are."
14388 (message "Counting words in region ... ")
14390 (goto-char beginning)
14391 (let ((count (recursive-count-words end)))
14394 (cond ((zerop count)
14396 "The region does NOT have any words."))
14400 (message "The region has 1 word."))
14403 "The region has %d words." count))))))
14407 @node Counting Exercise
14408 @section Exercise: Counting Punctuation
14410 Using a @code{while} loop, write a function to count the number of
14411 punctuation marks in a region---period, comma, semicolon, colon,
14412 exclamation mark, and question mark. Do the same using recursion.
14414 @node Words in a defun
14415 @chapter Counting Words in a @code{defun}
14416 @cindex Counting words in a @code{defun}
14417 @cindex Word counting in a @code{defun}
14419 Our next project is to count the number of words in a function
14420 definition. Clearly, this can be done using some variant of
14421 @code{@value{COUNT-WORDS}}. @xref{Counting Words, , Counting via
14422 Repetition and Regexps}. If we are just going to count the words in
14423 one definition, it is easy enough to mark the definition with the
14424 @kbd{C-M-h} (@code{mark-defun}) command, and then call
14425 @code{@value{COUNT-WORDS}}.
14427 However, I am more ambitious: I want to count the words and symbols in
14428 every definition in the Emacs sources and then print a graph that
14429 shows how many functions there are of each length: how many contain 40
14430 to 49 words or symbols, how many contain 50 to 59 words or symbols,
14431 and so on. I have often been curious how long a typical function is,
14432 and this will tell.
14435 * Divide and Conquer::
14436 * Words and Symbols:: What to count?
14437 * Syntax:: What constitutes a word or symbol?
14438 * count-words-in-defun:: Very like @code{@value{COUNT-WORDS}}.
14439 * Several defuns:: Counting several defuns in a file.
14440 * Find a File:: Do you want to look at a file?
14441 * lengths-list-file:: A list of the lengths of many definitions.
14442 * Several files:: Counting in definitions in different files.
14443 * Several files recursively:: Recursively counting in different files.
14444 * Prepare the data:: Prepare the data for display in a graph.
14448 @node Divide and Conquer
14449 @unnumberedsec Divide and Conquer
14452 Described in one phrase, the histogram project is daunting; but
14453 divided into numerous small steps, each of which we can take one at a
14454 time, the project becomes less fearsome. Let us consider what the
14459 First, write a function to count the words in one definition. This
14460 includes the problem of handling symbols as well as words.
14463 Second, write a function to list the number of words in each function
14464 in a file. This function can use the @code{count-words-in-defun}
14468 Third, write a function to list the number of words in each function
14469 in each of several files. This entails automatically finding the
14470 various files, switching to them, and counting the words in the
14471 definitions within them.
14474 Fourth, write a function to convert the list of numbers that we
14475 created in step three to a form that will be suitable for printing as
14479 Fifth, write a function to print the results as a graph.
14482 This is quite a project! But if we take each step slowly, it will not
14485 @node Words and Symbols
14486 @section What to Count?
14487 @cindex Words and symbols in defun
14489 When we first start thinking about how to count the words in a
14490 function definition, the first question is (or ought to be) what are
14491 we going to count? When we speak of ``words'' with respect to a Lisp
14492 function definition, we are actually speaking, in large part, of
14493 symbols. For example, the following @code{multiply-by-seven}
14494 function contains the five symbols @code{defun},
14495 @code{multiply-by-seven}, @code{number}, @code{*}, and @code{7}. In
14496 addition, in the documentation string, it contains the four words
14497 @samp{Multiply}, @samp{NUMBER}, @samp{by}, and @samp{seven}. The
14498 symbol @samp{number} is repeated, so the definition contains a total
14499 of ten words and symbols.
14503 (defun multiply-by-seven (number)
14504 "Multiply NUMBER by seven."
14510 However, if we mark the @code{multiply-by-seven} definition with
14511 @kbd{C-M-h} (@code{mark-defun}), and then call
14512 @code{@value{COUNT-WORDS}} on it, we will find that
14513 @code{@value{COUNT-WORDS}} claims the definition has eleven words, not
14514 ten! Something is wrong!
14516 The problem is twofold: @code{@value{COUNT-WORDS}} does not count the
14517 @samp{*} as a word, and it counts the single symbol,
14518 @code{multiply-by-seven}, as containing three words. The hyphens are
14519 treated as if they were interword spaces rather than intraword
14520 connectors: @samp{multiply-by-seven} is counted as if it were written
14521 @samp{multiply by seven}.
14523 The cause of this confusion is the regular expression search within
14524 the @code{@value{COUNT-WORDS}} definition that moves point forward word
14525 by word. In the canonical version of @code{@value{COUNT-WORDS}}, the
14533 This regular expression is a pattern defining one or more word
14534 constituent characters possibly followed by one or more characters
14535 that are not word constituents. What is meant by ``word constituent
14536 characters'' brings us to the issue of syntax, which is worth a section
14540 @section What Constitutes a Word or Symbol?
14541 @cindex Syntax categories and tables
14543 Emacs treats different characters as belonging to different
14544 @dfn{syntax categories}. For example, the regular expression,
14545 @samp{\\w+}, is a pattern specifying one or more @emph{word
14546 constituent} characters. Word constituent characters are members of
14547 one syntax category. Other syntax categories include the class of
14548 punctuation characters, such as the period and the comma, and the
14549 class of whitespace characters, such as the blank space and the tab
14550 character. (For more information, @pxref{Syntax Tables, , Syntax
14551 Tables, elisp, The GNU Emacs Lisp Reference Manual}.)
14553 Syntax tables specify which characters belong to which categories.
14554 Usually, a hyphen is not specified as a word constituent character.
14555 Instead, it is specified as being in the class of characters that are
14556 part of symbol names but not words. This means that the
14557 @code{@value{COUNT-WORDS}} function treats it in the same way it treats
14558 an interword white space, which is why @code{@value{COUNT-WORDS}}
14559 counts @samp{multiply-by-seven} as three words.
14561 There are two ways to cause Emacs to count @samp{multiply-by-seven} as
14562 one symbol: modify the syntax table or modify the regular expression.
14564 We could redefine a hyphen as a word constituent character by
14565 modifying the syntax table that Emacs keeps for each mode. This
14566 action would serve our purpose, except that a hyphen is merely the
14567 most common character within symbols that is not typically a word
14568 constituent character; there are others, too.
14570 Alternatively, we can redefine the regexp used in the
14571 @code{@value{COUNT-WORDS}} definition so as to include symbols. This
14572 procedure has the merit of clarity, but the task is a little tricky.
14575 The first part is simple enough: the pattern must match at least one
14576 character that is a word or symbol constituent. Thus:
14579 "\\(\\w\\|\\s_\\)+"
14583 The @samp{\\(} is the first part of the grouping construct that
14584 includes the @samp{\\w} and the @samp{\\s_} as alternatives, separated
14585 by the @samp{\\|}. The @samp{\\w} matches any word-constituent
14586 character and the @samp{\\s_} matches any character that is part of a
14587 symbol name but not a word-constituent character. The @samp{+}
14588 following the group indicates that the word or symbol constituent
14589 characters must be matched at least once.
14591 However, the second part of the regexp is more difficult to design.
14592 What we want is to follow the first part with optionally one or more
14593 characters that are not constituents of a word or symbol. At first,
14594 I thought I could define this with the following:
14597 "\\(\\W\\|\\S_\\)*"
14601 The upper case @samp{W} and @samp{S} match characters that are
14602 @emph{not} word or symbol constituents. Unfortunately, this
14603 expression matches any character that is either not a word constituent
14604 or not a symbol constituent. This matches any character!
14606 I then noticed that every word or symbol in my test region was
14607 followed by white space (blank space, tab, or newline). So I tried
14608 placing a pattern to match one or more blank spaces after the pattern
14609 for one or more word or symbol constituents. This failed, too. Words
14610 and symbols are often separated by whitespace, but in actual code
14611 parentheses may follow symbols and punctuation may follow words. So
14612 finally, I designed a pattern in which the word or symbol constituents
14613 are followed optionally by characters that are not white space and
14614 then followed optionally by white space.
14617 Here is the full regular expression:
14620 "\\(\\w\\|\\s_\\)+[^ \t\n]*[ \t\n]*"
14623 @node count-words-in-defun
14624 @section The @code{count-words-in-defun} Function
14625 @cindex Counting words in a @code{defun}
14627 We have seen that there are several ways to write a
14628 @code{count-words-region} function. To write a
14629 @code{count-words-in-defun}, we need merely adapt one of these
14632 The version that uses a @code{while} loop is easy to understand, so I
14633 am going to adapt that. Because @code{count-words-in-defun} will be
14634 part of a more complex program, it need not be interactive and it need
14635 not display a message but just return the count. These considerations
14636 simplify the definition a little.
14638 On the other hand, @code{count-words-in-defun} will be used within a
14639 buffer that contains function definitions. Consequently, it is
14640 reasonable to ask that the function determine whether it is called
14641 when point is within a function definition, and if it is, to return
14642 the count for that definition. This adds complexity to the
14643 definition, but saves us from needing to pass arguments to the
14647 These considerations lead us to prepare the following template:
14651 (defun count-words-in-defun ()
14652 "@var{documentation}@dots{}"
14653 (@var{set up}@dots{}
14654 (@var{while loop}@dots{})
14655 @var{return count})
14660 As usual, our job is to fill in the slots.
14664 We are presuming that this function will be called within a buffer
14665 containing function definitions. Point will either be within a
14666 function definition or not. For @code{count-words-in-defun} to work,
14667 point must move to the beginning of the definition, a counter must
14668 start at zero, and the counting loop must stop when point reaches the
14669 end of the definition.
14671 The @code{beginning-of-defun} function searches backwards for an
14672 opening delimiter such as a @samp{(} at the beginning of a line, and
14673 moves point to that position, or else to the limit of the search. In
14674 practice, this means that @code{beginning-of-defun} moves point to the
14675 beginning of an enclosing or preceding function definition, or else to
14676 the beginning of the buffer. We can use @code{beginning-of-defun} to
14677 place point where we wish to start.
14679 The @code{while} loop requires a counter to keep track of the words or
14680 symbols being counted. A @code{let} expression can be used to create
14681 a local variable for this purpose, and bind it to an initial value of zero.
14683 The @code{end-of-defun} function works like @code{beginning-of-defun}
14684 except that it moves point to the end of the definition.
14685 @code{end-of-defun} can be used as part of an expression that
14686 determines the position of the end of the definition.
14688 The set up for @code{count-words-in-defun} takes shape rapidly: first
14689 we move point to the beginning of the definition, then we create a
14690 local variable to hold the count, and finally, we record the position
14691 of the end of the definition so the @code{while} loop will know when to stop
14695 The code looks like this:
14699 (beginning-of-defun)
14701 (end (save-excursion (end-of-defun) (point))))
14706 The code is simple. The only slight complication is likely to concern
14707 @code{end}: it is bound to the position of the end of the definition
14708 by a @code{save-excursion} expression that returns the value of point
14709 after @code{end-of-defun} temporarily moves it to the end of the
14712 The second part of the @code{count-words-in-defun}, after the set up,
14713 is the @code{while} loop.
14715 The loop must contain an expression that jumps point forward word by
14716 word and symbol by symbol, and another expression that counts the
14717 jumps. The true-or-false-test for the @code{while} loop should test
14718 true so long as point should jump forward, and false when point is at
14719 the end of the definition. We have already redefined the regular
14720 expression for this, so the loop is straightforward:
14724 (while (and (< (point) end)
14726 "\\(\\w\\|\\s_\\)+[^ \t\n]*[ \t\n]*" end t))
14727 (setq count (1+ count)))
14731 The third part of the function definition returns the count of words
14732 and symbols. This part is the last expression within the body of the
14733 @code{let} expression, and can be, very simply, the local variable
14734 @code{count}, which when evaluated returns the count.
14737 Put together, the @code{count-words-in-defun} definition looks like this:
14739 @findex count-words-in-defun
14742 (defun count-words-in-defun ()
14743 "Return the number of words and symbols in a defun."
14744 (beginning-of-defun)
14746 (end (save-excursion (end-of-defun) (point))))
14750 (and (< (point) end)
14752 "\\(\\w\\|\\s_\\)+[^ \t\n]*[ \t\n]*"
14754 (setq count (1+ count)))
14759 How to test this? The function is not interactive, but it is easy to
14760 put a wrapper around the function to make it interactive; we can use
14761 almost the same code as for the recursive version of
14762 @code{@value{COUNT-WORDS}}:
14766 ;;; @r{Interactive version.}
14767 (defun count-words-defun ()
14768 "Number of words and symbols in a function definition."
14771 "Counting words and symbols in function definition ... ")
14774 (let ((count (count-words-in-defun)))
14778 "The definition does NOT have any words or symbols."))
14783 "The definition has 1 word or symbol."))
14786 "The definition has %d words or symbols." count)))))
14792 Let's re-use @kbd{C-c =} as a convenient keybinding:
14795 (global-set-key "\C-c=" 'count-words-defun)
14798 Now we can try out @code{count-words-defun}: install both
14799 @code{count-words-in-defun} and @code{count-words-defun}, and set the
14800 keybinding, and then place the cursor within the following definition:
14804 (defun multiply-by-seven (number)
14805 "Multiply NUMBER by seven."
14812 Success! The definition has 10 words and symbols.
14814 The next problem is to count the numbers of words and symbols in
14815 several definitions within a single file.
14817 @node Several defuns
14818 @section Count Several @code{defuns} Within a File
14820 A file such as @file{simple.el} may have a hundred or more function
14821 definitions within it. Our long term goal is to collect statistics on
14822 many files, but as a first step, our immediate goal is to collect
14823 statistics on one file.
14825 The information will be a series of numbers, each number being the
14826 length of a function definition. We can store the numbers in a list.
14828 We know that we will want to incorporate the information regarding one
14829 file with information about many other files; this means that the
14830 function for counting definition lengths within one file need only
14831 return the list of lengths. It need not and should not display any
14834 The word count commands contain one expression to jump point forward
14835 word by word and another expression to count the jumps. The function
14836 to return the lengths of definitions can be designed to work the same
14837 way, with one expression to jump point forward definition by
14838 definition and another expression to construct the lengths' list.
14840 This statement of the problem makes it elementary to write the
14841 function definition. Clearly, we will start the count at the
14842 beginning of the file, so the first command will be @code{(goto-char
14843 (point-min))}. Next, we start the @code{while} loop; and the
14844 true-or-false test of the loop can be a regular expression search for
14845 the next function definition---so long as the search succeeds, point
14846 is moved forward and then the body of the loop is evaluated. The body
14847 needs an expression that constructs the lengths' list. @code{cons},
14848 the list construction command, can be used to create the list. That
14849 is almost all there is to it.
14852 Here is what this fragment of code looks like:
14856 (goto-char (point-min))
14857 (while (re-search-forward "^(defun" nil t)
14859 (cons (count-words-in-defun) lengths-list)))
14863 What we have left out is the mechanism for finding the file that
14864 contains the function definitions.
14866 In previous examples, we either used this, the Info file, or we
14867 switched back and forth to some other buffer, such as the
14868 @file{*scratch*} buffer.
14870 Finding a file is a new process that we have not yet discussed.
14873 @section Find a File
14874 @cindex Find a File
14876 To find a file in Emacs, you use the @kbd{C-x C-f} (@code{find-file})
14877 command. This command is almost, but not quite right for the lengths
14881 Let's look at the source for @code{find-file}:
14885 (defun find-file (filename)
14886 "Edit file FILENAME.
14887 Switch to a buffer visiting file FILENAME,
14888 creating one if none already exists."
14889 (interactive "FFind file: ")
14890 (switch-to-buffer (find-file-noselect filename)))
14895 (The most recent version of the @code{find-file} function definition
14896 permits you to specify optional wildcards to visit multiple files; that
14897 makes the definition more complex and we will not discuss it here,
14898 since it is not relevant. You can see its source using either
14899 @kbd{M-.} (@code{find-tag}) or @kbd{C-h f} (@code{describe-function}).)
14903 (defun find-file (filename &optional wildcards)
14904 "Edit file FILENAME.
14905 Switch to a buffer visiting file FILENAME,
14906 creating one if none already exists.
14907 Interactively, the default if you just type RET is the current directory,
14908 but the visited file name is available through the minibuffer history:
14909 type M-n to pull it into the minibuffer.
14911 Interactively, or if WILDCARDS is non-nil in a call from Lisp,
14912 expand wildcards (if any) and visit multiple files. You can
14913 suppress wildcard expansion by setting `find-file-wildcards' to nil.
14915 To visit a file without any kind of conversion and without
14916 automatically choosing a major mode, use \\[find-file-literally]."
14917 (interactive (find-file-read-args "Find file: " nil))
14918 (let ((value (find-file-noselect filename nil nil wildcards)))
14920 (mapcar 'switch-to-buffer (nreverse value))
14921 (switch-to-buffer value))))
14924 The definition I am showing possesses short but complete documentation
14925 and an interactive specification that prompts you for a file name when
14926 you use the command interactively. The body of the definition
14927 contains two functions, @code{find-file-noselect} and
14928 @code{switch-to-buffer}.
14930 According to its documentation as shown by @kbd{C-h f} (the
14931 @code{describe-function} command), the @code{find-file-noselect}
14932 function reads the named file into a buffer and returns the buffer.
14933 (Its most recent version includes an optional @var{wildcards} argument,
14934 too, as well as another to read a file literally and an other you
14935 suppress warning messages. These optional arguments are irrelevant.)
14937 However, the @code{find-file-noselect} function does not select the
14938 buffer in which it puts the file. Emacs does not switch its attention
14939 (or yours if you are using @code{find-file-noselect}) to the selected
14940 buffer. That is what @code{switch-to-buffer} does: it switches the
14941 buffer to which Emacs attention is directed; and it switches the
14942 buffer displayed in the window to the new buffer. We have discussed
14943 buffer switching elsewhere. (@xref{Switching Buffers}.)
14945 In this histogram project, we do not need to display each file on the
14946 screen as the program determines the length of each definition within
14947 it. Instead of employing @code{switch-to-buffer}, we can work with
14948 @code{set-buffer}, which redirects the attention of the computer
14949 program to a different buffer but does not redisplay it on the screen.
14950 So instead of calling on @code{find-file} to do the job, we must write
14951 our own expression.
14953 The task is easy: use @code{find-file-noselect} and @code{set-buffer}.
14955 @node lengths-list-file
14956 @section @code{lengths-list-file} in Detail
14958 The core of the @code{lengths-list-file} function is a @code{while}
14959 loop containing a function to move point forward defun by defun, and
14960 a function to count the number of words and symbols in each defun.
14961 This core must be surrounded by functions that do various other tasks,
14962 including finding the file, and ensuring that point starts out at the
14963 beginning of the file. The function definition looks like this:
14964 @findex lengths-list-file
14968 (defun lengths-list-file (filename)
14969 "Return list of definitions' lengths within FILE.
14970 The returned list is a list of numbers.
14971 Each number is the number of words or
14972 symbols in one function definition."
14975 (message "Working on `%s' ... " filename)
14977 (let ((buffer (find-file-noselect filename))
14979 (set-buffer buffer)
14980 (setq buffer-read-only t)
14982 (goto-char (point-min))
14983 (while (re-search-forward "^(defun" nil t)
14985 (cons (count-words-in-defun) lengths-list)))
14986 (kill-buffer buffer)
14992 The function is passed one argument, the name of the file on which it
14993 will work. It has four lines of documentation, but no interactive
14994 specification. Since people worry that a computer is broken if they
14995 don't see anything going on, the first line of the body is a
14998 The next line contains a @code{save-excursion} that returns Emacs's
14999 attention to the current buffer when the function completes. This is
15000 useful in case you embed this function in another function that
15001 presumes point is restored to the original buffer.
15003 In the varlist of the @code{let} expression, Emacs finds the file and
15004 binds the local variable @code{buffer} to the buffer containing the
15005 file. At the same time, Emacs creates @code{lengths-list} as a local
15008 Next, Emacs switches its attention to the buffer.
15010 In the following line, Emacs makes the buffer read-only. Ideally,
15011 this line is not necessary. None of the functions for counting words
15012 and symbols in a function definition should change the buffer.
15013 Besides, the buffer is not going to be saved, even if it were changed.
15014 This line is entirely the consequence of great, perhaps excessive,
15015 caution. The reason for the caution is that this function and those
15016 it calls work on the sources for Emacs and it is inconvenient if they
15017 are inadvertently modified. It goes without saying that I did not
15018 realize a need for this line until an experiment went awry and started
15019 to modify my Emacs source files @dots{}
15021 Next comes a call to widen the buffer if it is narrowed. This
15022 function is usually not needed---Emacs creates a fresh buffer if none
15023 already exists; but if a buffer visiting the file already exists Emacs
15024 returns that one. In this case, the buffer may be narrowed and must
15025 be widened. If we wanted to be fully user-friendly, we would
15026 arrange to save the restriction and the location of point, but we
15029 The @code{(goto-char (point-min))} expression moves point to the
15030 beginning of the buffer.
15032 Then comes a @code{while} loop in which the work of the function is
15033 carried out. In the loop, Emacs determines the length of each
15034 definition and constructs a lengths' list containing the information.
15036 Emacs kills the buffer after working through it. This is to save
15037 space inside of Emacs. My version of GNU Emacs 19 contained over 300
15038 source files of interest; GNU Emacs 22 contains over a thousand source
15039 files. Another function will apply @code{lengths-list-file} to each
15042 Finally, the last expression within the @code{let} expression is the
15043 @code{lengths-list} variable; its value is returned as the value of
15044 the whole function.
15046 You can try this function by installing it in the usual fashion. Then
15047 place your cursor after the following expression and type @kbd{C-x
15048 C-e} (@code{eval-last-sexp}).
15050 @c !!! 22.1.1 lisp sources location here
15053 "/usr/local/share/emacs/22.1/lisp/emacs-lisp/debug.el")
15057 You may need to change the pathname of the file; the one here is for
15058 GNU Emacs version 22.1. To change the expression, copy it to
15059 the @file{*scratch*} buffer and edit it.
15063 Also, to see the full length of the list, rather than a truncated
15064 version, you may have to evaluate the following:
15065 @c We do not want to insert, so do not mention the zero prefix argument.
15068 (custom-set-variables '(eval-expression-print-length nil))
15072 (@xref{defcustom, , Specifying Variables using @code{defcustom}}.
15073 Then evaluate the @code{lengths-list-file} expression.)
15076 The lengths' list for @file{debug.el} takes less than a second to
15077 produce and looks like this in GNU Emacs 22:
15080 (83 113 105 144 289 22 30 97 48 89 25 52 52 88 28 29 77 49 43 290 232 587)
15084 (Using my old machine, the version 19 lengths' list for @file{debug.el}
15085 took seven seconds to produce and looked like this:
15088 (75 41 80 62 20 45 44 68 45 12 34 235)
15092 The newer version of @file{debug.el} contains more defuns than the
15093 earlier one; and my new machine is much faster than the old one.)
15095 Note that the length of the last definition in the file is first in
15098 @node Several files
15099 @section Count Words in @code{defuns} in Different Files
15101 In the previous section, we created a function that returns a list of
15102 the lengths of each definition in a file. Now, we want to define a
15103 function to return a master list of the lengths of the definitions in
15106 Working on each of a list of files is a repetitious act, so we can use
15107 either a @code{while} loop or recursion.
15110 * lengths-list-many-files:: Return a list of the lengths of defuns.
15111 * append:: Attach one list to another.
15115 @node lengths-list-many-files
15116 @unnumberedsubsec Determine the lengths of @code{defuns}
15119 The design using a @code{while} loop is routine. The argument passed
15120 to the function is a list of files. As we saw earlier (@pxref{Loop
15121 Example}), you can write a @code{while} loop so that the body of the
15122 loop is evaluated if such a list contains elements, but to exit the
15123 loop if the list is empty. For this design to work, the body of the
15124 loop must contain an expression that shortens the list each time the
15125 body is evaluated, so that eventually the list is empty. The usual
15126 technique is to set the value of the list to the value of the @sc{cdr}
15127 of the list each time the body is evaluated.
15130 The template looks like this:
15134 (while @var{test-whether-list-is-empty}
15136 @var{set-list-to-cdr-of-list})
15140 Also, we remember that a @code{while} loop returns @code{nil} (the
15141 result of evaluating the true-or-false-test), not the result of any
15142 evaluation within its body. (The evaluations within the body of the
15143 loop are done for their side effects.) However, the expression that
15144 sets the lengths' list is part of the body---and that is the value
15145 that we want returned by the function as a whole. To do this, we
15146 enclose the @code{while} loop within a @code{let} expression, and
15147 arrange that the last element of the @code{let} expression contains
15148 the value of the lengths' list. (@xref{Incrementing Example, , Loop
15149 Example with an Incrementing Counter}.)
15151 @findex lengths-list-many-files
15153 These considerations lead us directly to the function itself:
15157 ;;; @r{Use @code{while} loop.}
15158 (defun lengths-list-many-files (list-of-files)
15159 "Return list of lengths of defuns in LIST-OF-FILES."
15162 (let (lengths-list)
15164 ;;; @r{true-or-false-test}
15165 (while list-of-files
15170 ;;; @r{Generate a lengths' list.}
15172 (expand-file-name (car list-of-files)))))
15176 ;;; @r{Make files' list shorter.}
15177 (setq list-of-files (cdr list-of-files)))
15179 ;;; @r{Return final value of lengths' list.}
15184 @code{expand-file-name} is a built-in function that converts a file
15185 name to the absolute, long, path name form. The function employs the
15186 name of the directory in which the function is called.
15188 @c !!! 22.1.1 lisp sources location here
15190 Thus, if @code{expand-file-name} is called on @code{debug.el} when
15191 Emacs is visiting the
15192 @file{/usr/local/share/emacs/22.1.1/lisp/emacs-lisp/} directory,
15202 @c !!! 22.1.1 lisp sources location here
15204 /usr/local/share/emacs/22.1.1/lisp/emacs-lisp/debug.el
15207 The only other new element of this function definition is the as yet
15208 unstudied function @code{append}, which merits a short section for
15212 @subsection The @code{append} Function
15215 The @code{append} function attaches one list to another. Thus,
15218 (append '(1 2 3 4) '(5 6 7 8))
15229 This is exactly how we want to attach two lengths' lists produced by
15230 @code{lengths-list-file} to each other. The results contrast with
15234 (cons '(1 2 3 4) '(5 6 7 8))
15239 which constructs a new list in which the first argument to @code{cons}
15240 becomes the first element of the new list:
15243 ((1 2 3 4) 5 6 7 8)
15246 @node Several files recursively
15247 @section Recursively Count Words in Different Files
15249 Besides a @code{while} loop, you can work on each of a list of files
15250 with recursion. A recursive version of @code{lengths-list-many-files}
15251 is short and simple.
15253 The recursive function has the usual parts: the do-again-test, the
15254 next-step-expression, and the recursive call. The do-again-test
15255 determines whether the function should call itself again, which it
15256 will do if the @code{list-of-files} contains any remaining elements;
15257 the next-step-expression resets the @code{list-of-files} to the
15258 @sc{cdr} of itself, so eventually the list will be empty; and the
15259 recursive call calls itself on the shorter list. The complete
15260 function is shorter than this description!
15261 @findex recursive-lengths-list-many-files
15265 (defun recursive-lengths-list-many-files (list-of-files)
15266 "Return list of lengths of each defun in LIST-OF-FILES."
15267 (if list-of-files ; @r{do-again-test}
15270 (expand-file-name (car list-of-files)))
15271 (recursive-lengths-list-many-files
15272 (cdr list-of-files)))))
15277 In a sentence, the function returns the lengths' list for the first of
15278 the @code{list-of-files} appended to the result of calling itself on
15279 the rest of the @code{list-of-files}.
15281 Here is a test of @code{recursive-lengths-list-many-files}, along with
15282 the results of running @code{lengths-list-file} on each of the files
15285 Install @code{recursive-lengths-list-many-files} and
15286 @code{lengths-list-file}, if necessary, and then evaluate the
15287 following expressions. You may need to change the files' pathnames;
15288 those here work when this Info file and the Emacs sources are located
15289 in their customary places. To change the expressions, copy them to
15290 the @file{*scratch*} buffer, edit them, and then evaluate them.
15292 The results are shown after the @samp{@result{}}. (These results are
15293 for files from Emacs version 22.1.1; files from other versions of
15294 Emacs may produce different results.)
15296 @c !!! 22.1.1 lisp sources location here
15299 (cd "/usr/local/share/emacs/22.1.1/")
15301 (lengths-list-file "./lisp/macros.el")
15302 @result{} (283 263 480 90)
15306 (lengths-list-file "./lisp/mail/mailalias.el")
15307 @result{} (38 32 29 95 178 180 321 218 324)
15311 (lengths-list-file "./lisp/makesum.el")
15316 (recursive-lengths-list-many-files
15317 '("./lisp/macros.el"
15318 "./lisp/mail/mailalias.el"
15319 "./lisp/makesum.el"))
15320 @result{} (283 263 480 90 38 32 29 95 178 180 321 218 324 85 181)
15324 The @code{recursive-lengths-list-many-files} function produces the
15327 The next step is to prepare the data in the list for display in a graph.
15329 @node Prepare the data
15330 @section Prepare the Data for Display in a Graph
15332 The @code{recursive-lengths-list-many-files} function returns a list
15333 of numbers. Each number records the length of a function definition.
15334 What we need to do now is transform this data into a list of numbers
15335 suitable for generating a graph. The new list will tell how many
15336 functions definitions contain less than 10 words and
15337 symbols, how many contain between 10 and 19 words and symbols, how
15338 many contain between 20 and 29 words and symbols, and so on.
15340 In brief, we need to go through the lengths' list produced by the
15341 @code{recursive-lengths-list-many-files} function and count the number
15342 of defuns within each range of lengths, and produce a list of those
15346 * Data for Display in Detail::
15347 * Sorting:: Sorting lists.
15348 * Files List:: Making a list of files.
15349 * Counting function definitions::
15353 @node Data for Display in Detail
15354 @unnumberedsubsec The Data for Display in Detail
15357 Based on what we have done before, we can readily foresee that it
15358 should not be too hard to write a function that @sc{cdr}s down the
15359 lengths' list, looks at each element, determines which length range it
15360 is in, and increments a counter for that range.
15362 However, before beginning to write such a function, we should consider
15363 the advantages of sorting the lengths' list first, so the numbers are
15364 ordered from smallest to largest. First, sorting will make it easier
15365 to count the numbers in each range, since two adjacent numbers will
15366 either be in the same length range or in adjacent ranges. Second, by
15367 inspecting a sorted list, we can discover the highest and lowest
15368 number, and thereby determine the largest and smallest length range
15372 @subsection Sorting Lists
15375 Emacs contains a function to sort lists, called (as you might guess)
15376 @code{sort}. The @code{sort} function takes two arguments, the list
15377 to be sorted, and a predicate that determines whether the first of
15378 two list elements is less than the second.
15380 As we saw earlier (@pxref{Wrong Type of Argument, , Using the Wrong
15381 Type Object as an Argument}), a predicate is a function that
15382 determines whether some property is true or false. The @code{sort}
15383 function will reorder a list according to whatever property the
15384 predicate uses; this means that @code{sort} can be used to sort
15385 non-numeric lists by non-numeric criteria---it can, for example,
15386 alphabetize a list.
15389 The @code{<} function is used when sorting a numeric list. For example,
15392 (sort '(4 8 21 17 33 7 21 7) '<)
15400 (4 7 7 8 17 21 21 33)
15404 (Note that in this example, both the arguments are quoted so that the
15405 symbols are not evaluated before being passed to @code{sort} as
15408 Sorting the list returned by the
15409 @code{recursive-lengths-list-many-files} function is straightforward;
15410 it uses the @code{<} function:
15414 In GNU Emacs 22, eval
15416 (cd "/usr/local/share/emacs/22.0.50/")
15418 (recursive-lengths-list-many-files
15419 '("./lisp/macros.el"
15420 "./lisp/mail/mailalias.el"
15421 "./lisp/makesum.el"))
15429 (recursive-lengths-list-many-files
15430 '("./lisp/macros.el"
15431 "./lisp/mailalias.el"
15432 "./lisp/makesum.el"))
15442 (29 32 38 85 90 95 178 180 181 218 263 283 321 324 480)
15446 (Note that in this example, the first argument to @code{sort} is not
15447 quoted, since the expression must be evaluated so as to produce the
15448 list that is passed to @code{sort}.)
15451 @subsection Making a List of Files
15453 The @code{recursive-lengths-list-many-files} function requires a list
15454 of files as its argument. For our test examples, we constructed such
15455 a list by hand; but the Emacs Lisp source directory is too large for
15456 us to do for that. Instead, we will write a function to do the job
15457 for us. In this function, we will use both a @code{while} loop and a
15460 @findex directory-files
15461 We did not have to write a function like this for older versions of
15462 GNU Emacs, since they placed all the @samp{.el} files in one
15463 directory. Instead, we were able to use the @code{directory-files}
15464 function, which lists the names of files that match a specified
15465 pattern within a single directory.
15467 However, recent versions of Emacs place Emacs Lisp files in
15468 sub-directories of the top level @file{lisp} directory. This
15469 re-arrangement eases navigation. For example, all the mail related
15470 files are in a @file{lisp} sub-directory called @file{mail}. But at
15471 the same time, this arrangement forces us to create a file listing
15472 function that descends into the sub-directories.
15474 @findex files-in-below-directory
15475 We can create this function, called @code{files-in-below-directory},
15476 using familiar functions such as @code{car}, @code{nthcdr}, and
15477 @code{substring} in conjunction with an existing function called
15478 @code{directory-files-and-attributes}. This latter function not only
15479 lists all the filenames in a directory, including the names
15480 of sub-directories, but also their attributes.
15482 To restate our goal: to create a function that will enable us
15483 to feed filenames to @code{recursive-lengths-list-many-files}
15484 as a list that looks like this (but with more elements):
15488 ("./lisp/macros.el"
15489 "./lisp/mail/rmail.el"
15490 "./lisp/makesum.el")
15494 The @code{directory-files-and-attributes} function returns a list of
15495 lists. Each of the lists within the main list consists of 13
15496 elements. The first element is a string that contains the name of the
15497 file---which, in GNU/Linux, may be a @dfn{directory file}, that is to
15498 say, a file with the special attributes of a directory. The second
15499 element of the list is @code{t} for a directory, a string
15500 for symbolic link (the string is the name linked to), or @code{nil}.
15502 For example, the first @samp{.el} file in the @file{lisp/} directory
15503 is @file{abbrev.el}. Its name is
15504 @file{/usr/local/share/emacs/22.1.1/lisp/abbrev.el} and it is not a
15505 directory or a symbolic link.
15508 This is how @code{directory-files-and-attributes} lists that file and
15520 (20615 27034 579989 697000)
15522 (20615 26327 734791 805000)
15534 On the other hand, @file{mail/} is a directory within the @file{lisp/}
15535 directory. The beginning of its listing looks like this:
15546 (To learn about the different attributes, look at the documentation of
15547 @code{file-attributes}. Bear in mind that the @code{file-attributes}
15548 function does not list the filename, so its first element is
15549 @code{directory-files-and-attributes}'s second element.)
15551 We will want our new function, @code{files-in-below-directory}, to
15552 list the @samp{.el} files in the directory it is told to check, and in
15553 any directories below that directory.
15555 This gives us a hint on how to construct
15556 @code{files-in-below-directory}: within a directory, the function
15557 should add @samp{.el} filenames to a list; and if, within a directory,
15558 the function comes upon a sub-directory, it should go into that
15559 sub-directory and repeat its actions.
15561 However, we should note that every directory contains a name that
15562 refers to itself, called @file{.} (``dot''), and a name that refers to
15563 its parent directory, called @file{..} (``dot dot''). (In
15564 @file{/}, the root directory, @file{..} refers to itself, since
15565 @file{/} has no parent.) Clearly, we do not want our
15566 @code{files-in-below-directory} function to enter those directories,
15567 since they always lead us, directly or indirectly, to the current
15570 Consequently, our @code{files-in-below-directory} function must do
15575 Check to see whether it is looking at a filename that ends in
15576 @samp{.el}; and if so, add its name to a list.
15579 Check to see whether it is looking at a filename that is the name of a
15580 directory; and if so,
15584 Check to see whether it is looking at @file{.} or @file{..}; and if
15588 Or else, go into that directory and repeat the process.
15592 Let's write a function definition to do these tasks. We will use a
15593 @code{while} loop to move from one filename to another within a
15594 directory, checking what needs to be done; and we will use a recursive
15595 call to repeat the actions on each sub-directory. The recursive
15596 pattern is Accumulate
15597 (@pxref{Accumulate}),
15598 using @code{append} as the combiner.
15601 (directory-files "/usr/local/src/emacs/lisp/" t "\\.el$")
15602 (shell-command "find /usr/local/src/emacs/lisp/ -name '*.el'")
15604 (directory-files "/usr/local/share/emacs/22.1.1/lisp/" t "\\.el$")
15605 (shell-command "find /usr/local/share/emacs/22.1.1/lisp/ -name '*.el'")
15608 @c /usr/local/share/emacs/22.1.1/lisp/
15611 Here is the function:
15615 (defun files-in-below-directory (directory)
15616 "List the .el files in DIRECTORY and in its sub-directories."
15617 ;; Although the function will be used non-interactively,
15618 ;; it will be easier to test if we make it interactive.
15619 ;; The directory will have a name such as
15620 ;; "/usr/local/share/emacs/22.1.1/lisp/"
15621 (interactive "DDirectory name: ")
15624 (let (el-files-list
15625 (current-directory-list
15626 (directory-files-and-attributes directory t)))
15627 ;; while we are in the current directory
15628 (while current-directory-list
15632 ;; check to see whether filename ends in '.el'
15633 ;; and if so, append its name to a list.
15634 ((equal ".el" (substring (car (car current-directory-list)) -3))
15635 (setq el-files-list
15636 (cons (car (car current-directory-list)) el-files-list)))
15639 ;; check whether filename is that of a directory
15640 ((eq t (car (cdr (car current-directory-list))))
15641 ;; decide whether to skip or recurse
15644 (substring (car (car current-directory-list)) -1))
15645 ;; then do nothing since filename is that of
15646 ;; current directory or parent, "." or ".."
15650 ;; else descend into the directory and repeat the process
15651 (setq el-files-list
15653 (files-in-below-directory
15654 (car (car current-directory-list)))
15656 ;; move to the next filename in the list; this also
15657 ;; shortens the list so the while loop eventually comes to an end
15658 (setq current-directory-list (cdr current-directory-list)))
15659 ;; return the filenames
15664 @c (files-in-below-directory "/usr/local/src/emacs/lisp/")
15665 @c (files-in-below-directory "/usr/local/share/emacs/22.1.1/lisp/")
15667 The @code{files-in-below-directory} @code{directory-files} function
15668 takes one argument, the name of a directory.
15671 Thus, on my system,
15673 @c (length (files-in-below-directory "/usr/local/src/emacs/lisp/"))
15675 @c !!! 22.1.1 lisp sources location here
15679 (files-in-below-directory "/usr/local/share/emacs/22.1.1/lisp/"))
15684 tells me that in and below my Lisp sources directory are 1031
15687 @code{files-in-below-directory} returns a list in reverse alphabetical
15688 order. An expression to sort the list in alphabetical order looks
15694 (files-in-below-directory "/usr/local/share/emacs/22.1.1/lisp/")
15701 "Test how long it takes to find lengths of all sorted elisp defuns."
15702 (insert "\n" (current-time-string) "\n")
15705 (recursive-lengths-list-many-files
15706 (files-in-below-directory "/usr/local/src/emacs/lisp/"))
15708 (insert (format "%s" (current-time-string))))
15711 @node Counting function definitions
15712 @subsection Counting function definitions
15714 Our immediate goal is to generate a list that tells us how many
15715 function definitions contain fewer than 10 words and symbols, how many
15716 contain between 10 and 19 words and symbols, how many contain between
15717 20 and 29 words and symbols, and so on.
15719 With a sorted list of numbers, this is easy: count how many elements
15720 of the list are smaller than 10, then, after moving past the numbers
15721 just counted, count how many are smaller than 20, then, after moving
15722 past the numbers just counted, count how many are smaller than 30, and
15723 so on. Each of the numbers, 10, 20, 30, 40, and the like, is one
15724 larger than the top of that range. We can call the list of such
15725 numbers the @code{top-of-ranges} list.
15728 If we wished, we could generate this list automatically, but it is
15729 simpler to write a list manually. Here it is:
15730 @vindex top-of-ranges
15734 (defvar top-of-ranges
15737 110 120 130 140 150
15738 160 170 180 190 200
15739 210 220 230 240 250
15740 260 270 280 290 300)
15741 "List specifying ranges for `defuns-per-range'.")
15745 To change the ranges, we edit this list.
15747 Next, we need to write the function that creates the list of the
15748 number of definitions within each range. Clearly, this function must
15749 take the @code{sorted-lengths} and the @code{top-of-ranges} lists
15752 The @code{defuns-per-range} function must do two things again and
15753 again: it must count the number of definitions within a range
15754 specified by the current top-of-range value; and it must shift to the
15755 next higher value in the @code{top-of-ranges} list after counting the
15756 number of definitions in the current range. Since each of these
15757 actions is repetitive, we can use @code{while} loops for the job.
15758 One loop counts the number of definitions in the range defined by the
15759 current top-of-range value, and the other loop selects each of the
15760 top-of-range values in turn.
15762 Several entries of the @code{sorted-lengths} list are counted for each
15763 range; this means that the loop for the @code{sorted-lengths} list
15764 will be inside the loop for the @code{top-of-ranges} list, like a
15765 small gear inside a big gear.
15767 The inner loop counts the number of definitions within the range. It
15768 is a simple counting loop of the type we have seen before.
15769 (@xref{Incrementing Loop, , A loop with an incrementing counter}.)
15770 The true-or-false test of the loop tests whether the value from the
15771 @code{sorted-lengths} list is smaller than the current value of the
15772 top of the range. If it is, the function increments the counter and
15773 tests the next value from the @code{sorted-lengths} list.
15776 The inner loop looks like this:
15780 (while @var{length-element-smaller-than-top-of-range}
15781 (setq number-within-range (1+ number-within-range))
15782 (setq sorted-lengths (cdr sorted-lengths)))
15786 The outer loop must start with the lowest value of the
15787 @code{top-of-ranges} list, and then be set to each of the succeeding
15788 higher values in turn. This can be done with a loop like this:
15792 (while top-of-ranges
15793 @var{body-of-loop}@dots{}
15794 (setq top-of-ranges (cdr top-of-ranges)))
15799 Put together, the two loops look like this:
15803 (while top-of-ranges
15805 ;; @r{Count the number of elements within the current range.}
15806 (while @var{length-element-smaller-than-top-of-range}
15807 (setq number-within-range (1+ number-within-range))
15808 (setq sorted-lengths (cdr sorted-lengths)))
15810 ;; @r{Move to next range.}
15811 (setq top-of-ranges (cdr top-of-ranges)))
15815 In addition, in each circuit of the outer loop, Emacs should record
15816 the number of definitions within that range (the value of
15817 @code{number-within-range}) in a list. We can use @code{cons} for
15818 this purpose. (@xref{cons, , @code{cons}}.)
15820 The @code{cons} function works fine, except that the list it
15821 constructs will contain the number of definitions for the highest
15822 range at its beginning and the number of definitions for the lowest
15823 range at its end. This is because @code{cons} attaches new elements
15824 of the list to the beginning of the list, and since the two loops are
15825 working their way through the lengths' list from the lower end first,
15826 the @code{defuns-per-range-list} will end up largest number first.
15827 But we will want to print our graph with smallest values first and the
15828 larger later. The solution is to reverse the order of the
15829 @code{defuns-per-range-list}. We can do this using the
15830 @code{nreverse} function, which reverses the order of a list.
15837 (nreverse '(1 2 3 4))
15848 Note that the @code{nreverse} function is destructive---that is,
15849 it changes the list to which it is applied; this contrasts with the
15850 @code{car} and @code{cdr} functions, which are non-destructive. In
15851 this case, we do not want the original @code{defuns-per-range-list},
15852 so it does not matter that it is destroyed. (The @code{reverse}
15853 function provides a reversed copy of a list, leaving the original list
15858 Put all together, the @code{defuns-per-range} looks like this:
15862 (defun defuns-per-range (sorted-lengths top-of-ranges)
15863 "SORTED-LENGTHS defuns in each TOP-OF-RANGES range."
15864 (let ((top-of-range (car top-of-ranges))
15865 (number-within-range 0)
15866 defuns-per-range-list)
15871 (while top-of-ranges
15877 ;; @r{Need number for numeric test.}
15878 (car sorted-lengths)
15879 (< (car sorted-lengths) top-of-range))
15883 ;; @r{Count number of definitions within current range.}
15884 (setq number-within-range (1+ number-within-range))
15885 (setq sorted-lengths (cdr sorted-lengths)))
15887 ;; @r{Exit inner loop but remain within outer loop.}
15891 (setq defuns-per-range-list
15892 (cons number-within-range defuns-per-range-list))
15893 (setq number-within-range 0) ; @r{Reset count to zero.}
15897 ;; @r{Move to next range.}
15898 (setq top-of-ranges (cdr top-of-ranges))
15899 ;; @r{Specify next top of range value.}
15900 (setq top-of-range (car top-of-ranges)))
15904 ;; @r{Exit outer loop and count the number of defuns larger than}
15905 ;; @r{ the largest top-of-range value.}
15906 (setq defuns-per-range-list
15908 (length sorted-lengths)
15909 defuns-per-range-list))
15913 ;; @r{Return a list of the number of definitions within each range,}
15914 ;; @r{ smallest to largest.}
15915 (nreverse defuns-per-range-list)))
15921 The function is straightforward except for one subtle feature. The
15922 true-or-false test of the inner loop looks like this:
15926 (and (car sorted-lengths)
15927 (< (car sorted-lengths) top-of-range))
15933 instead of like this:
15936 (< (car sorted-lengths) top-of-range)
15939 The purpose of the test is to determine whether the first item in the
15940 @code{sorted-lengths} list is less than the value of the top of the
15943 The simple version of the test works fine unless the
15944 @code{sorted-lengths} list has a @code{nil} value. In that case, the
15945 @code{(car sorted-lengths)} expression function returns
15946 @code{nil}. The @code{<} function cannot compare a number to
15947 @code{nil}, which is an empty list, so Emacs signals an error and
15948 stops the function from attempting to continue to execute.
15950 The @code{sorted-lengths} list always becomes @code{nil} when the
15951 counter reaches the end of the list. This means that any attempt to
15952 use the @code{defuns-per-range} function with the simple version of
15953 the test will fail.
15955 We solve the problem by using the @code{(car sorted-lengths)}
15956 expression in conjunction with the @code{and} expression. The
15957 @code{(car sorted-lengths)} expression returns a non-@code{nil}
15958 value so long as the list has at least one number within it, but
15959 returns @code{nil} if the list is empty. The @code{and} expression
15960 first evaluates the @code{(car sorted-lengths)} expression, and
15961 if it is @code{nil}, returns false @emph{without} evaluating the
15962 @code{<} expression. But if the @code{(car sorted-lengths)}
15963 expression returns a non-@code{nil} value, the @code{and} expression
15964 evaluates the @code{<} expression, and returns that value as the value
15965 of the @code{and} expression.
15967 @c colon in printed section title causes problem in Info cross reference
15968 This way, we avoid an error.
15971 (For information about @code{and}, see
15972 @ref{kill-new function, , The @code{kill-new} function}.)
15976 (@xref{kill-new function, , The @code{kill-new} function}, for
15977 information about @code{and}.)
15980 Here is a short test of the @code{defuns-per-range} function. First,
15981 evaluate the expression that binds (a shortened)
15982 @code{top-of-ranges} list to the list of values, then evaluate the
15983 expression for binding the @code{sorted-lengths} list, and then
15984 evaluate the @code{defuns-per-range} function.
15988 ;; @r{(Shorter list than we will use later.)}
15989 (setq top-of-ranges
15990 '(110 120 130 140 150
15991 160 170 180 190 200))
15993 (setq sorted-lengths
15994 '(85 86 110 116 122 129 154 176 179 200 265 300 300))
15996 (defuns-per-range sorted-lengths top-of-ranges)
16002 The list returned looks like this:
16005 (2 2 2 0 0 1 0 2 0 0 4)
16009 Indeed, there are two elements of the @code{sorted-lengths} list
16010 smaller than 110, two elements between 110 and 119, two elements
16011 between 120 and 129, and so on. There are four elements with a value
16014 @c The next step is to turn this numbers' list into a graph.
16015 @node Readying a Graph
16016 @chapter Readying a Graph
16017 @cindex Readying a graph
16018 @cindex Graph prototype
16019 @cindex Prototype graph
16020 @cindex Body of graph
16022 Our goal is to construct a graph showing the numbers of function
16023 definitions of various lengths in the Emacs lisp sources.
16025 As a practical matter, if you were creating a graph, you would
16026 probably use a program such as @code{gnuplot} to do the job.
16027 (@code{gnuplot} is nicely integrated into GNU Emacs.) In this case,
16028 however, we create one from scratch, and in the process we will
16029 re-acquaint ourselves with some of what we learned before and learn
16032 In this chapter, we will first write a simple graph printing function.
16033 This first definition will be a @dfn{prototype}, a rapidly written
16034 function that enables us to reconnoiter this unknown graph-making
16035 territory. We will discover dragons, or find that they are myth.
16036 After scouting the terrain, we will feel more confident and enhance
16037 the function to label the axes automatically.
16040 * Columns of a graph::
16041 * graph-body-print:: How to print the body of a graph.
16042 * recursive-graph-body-print::
16044 * Line Graph Exercise::
16048 @node Columns of a graph
16049 @unnumberedsec Printing the Columns of a Graph
16052 Since Emacs is designed to be flexible and work with all kinds of
16053 terminals, including character-only terminals, the graph will need to
16054 be made from one of the typewriter symbols. An asterisk will do; as
16055 we enhance the graph-printing function, we can make the choice of
16056 symbol a user option.
16058 We can call this function @code{graph-body-print}; it will take a
16059 @code{numbers-list} as its only argument. At this stage, we will not
16060 label the graph, but only print its body.
16062 The @code{graph-body-print} function inserts a vertical column of
16063 asterisks for each element in the @code{numbers-list}. The height of
16064 each line is determined by the value of that element of the
16065 @code{numbers-list}.
16067 Inserting columns is a repetitive act; that means that this function can
16068 be written either with a @code{while} loop or recursively.
16070 Our first challenge is to discover how to print a column of asterisks.
16071 Usually, in Emacs, we print characters onto a screen horizontally,
16072 line by line, by typing. We have two routes we can follow: write our
16073 own column-insertion function or discover whether one exists in Emacs.
16075 To see whether there is one in Emacs, we can use the @kbd{M-x apropos}
16076 command. This command is like the @kbd{C-h a} (@code{command-apropos})
16077 command, except that the latter finds only those functions that are
16078 commands. The @kbd{M-x apropos} command lists all symbols that match
16079 a regular expression, including functions that are not interactive.
16082 What we want to look for is some command that prints or inserts
16083 columns. Very likely, the name of the function will contain either
16084 the word ``print'' or the word ``insert'' or the word ``column''.
16085 Therefore, we can simply type @kbd{M-x apropos RET
16086 print\|insert\|column RET} and look at the result. On my system, this
16087 command once took quite some time, and then produced a list of 79
16088 functions and variables. Now it does not take much time at all and
16089 produces a list of 211 functions and variables. Scanning down the
16090 list, the only function that looks as if it might do the job is
16091 @code{insert-rectangle}.
16094 Indeed, this is the function we want; its documentation says:
16099 Insert text of RECTANGLE with upper left corner at point.
16100 RECTANGLE's first line is inserted at point,
16101 its second line is inserted at a point vertically under point, etc.
16102 RECTANGLE should be a list of strings.
16103 After this command, the mark is at the upper left corner
16104 and point is at the lower right corner.
16108 We can run a quick test, to make sure it does what we expect of it.
16110 Here is the result of placing the cursor after the
16111 @code{insert-rectangle} expression and typing @kbd{C-u C-x C-e}
16112 (@code{eval-last-sexp}). The function inserts the strings
16113 @samp{"first"}, @samp{"second"}, and @samp{"third"} at and below
16114 point. Also the function returns @code{nil}.
16118 (insert-rectangle '("first" "second" "third"))first
16125 Of course, we won't be inserting the text of the
16126 @code{insert-rectangle} expression itself into the buffer in which we
16127 are making the graph, but will call the function from our program. We
16128 shall, however, have to make sure that point is in the buffer at the
16129 place where the @code{insert-rectangle} function will insert its
16132 If you are reading this in Info, you can see how this works by
16133 switching to another buffer, such as the @file{*scratch*} buffer,
16134 placing point somewhere in the buffer, typing @kbd{M-:}, typing the
16135 @code{insert-rectangle} expression into the minibuffer at the prompt,
16136 and then typing @key{RET}. This causes Emacs to evaluate the
16137 expression in the minibuffer, but to use as the value of point the
16138 position of point in the @file{*scratch*} buffer. (@kbd{M-:} is the
16139 keybinding for @code{eval-expression}. Also, @code{nil} does not
16140 appear in the @file{*scratch*} buffer since the expression is
16141 evaluated in the minibuffer.)
16143 We find when we do this that point ends up at the end of the last
16144 inserted line---that is to say, this function moves point as a
16145 side-effect. If we were to repeat the command, with point at this
16146 position, the next insertion would be below and to the right of the
16147 previous insertion. We don't want this! If we are going to make a
16148 bar graph, the columns need to be beside each other.
16150 So we discover that each cycle of the column-inserting @code{while}
16151 loop must reposition point to the place we want it, and that place
16152 will be at the top, not the bottom, of the column. Moreover, we
16153 remember that when we print a graph, we do not expect all the columns
16154 to be the same height. This means that the top of each column may be
16155 at a different height from the previous one. We cannot simply
16156 reposition point to the same line each time, but moved over to the
16157 right---or perhaps we can@dots{}
16159 We are planning to make the columns of the bar graph out of asterisks.
16160 The number of asterisks in the column is the number specified by the
16161 current element of the @code{numbers-list}. We need to construct a
16162 list of asterisks of the right length for each call to
16163 @code{insert-rectangle}. If this list consists solely of the requisite
16164 number of asterisks, then we will have to position point the right number
16165 of lines above the base for the graph to print correctly. This could
16168 Alternatively, if we can figure out some way to pass
16169 @code{insert-rectangle} a list of the same length each time, then we
16170 can place point on the same line each time, but move it over one
16171 column to the right for each new column. If we do this, however, some
16172 of the entries in the list passed to @code{insert-rectangle} must be
16173 blanks rather than asterisks. For example, if the maximum height of
16174 the graph is 5, but the height of the column is 3, then
16175 @code{insert-rectangle} requires an argument that looks like this:
16178 (" " " " "*" "*" "*")
16181 This last proposal is not so difficult, so long as we can determine
16182 the column height. There are two ways for us to specify the column
16183 height: we can arbitrarily state what it will be, which would work
16184 fine for graphs of that height; or we can search through the list of
16185 numbers and use the maximum height of the list as the maximum height
16186 of the graph. If the latter operation were difficult, then the former
16187 procedure would be easiest, but there is a function built into Emacs
16188 that determines the maximum of its arguments. We can use that
16189 function. The function is called @code{max} and it returns the
16190 largest of all its arguments, which must be numbers. Thus, for
16198 returns 7. (A corresponding function called @code{min} returns the
16199 smallest of all its arguments.)
16203 However, we cannot simply call @code{max} on the @code{numbers-list};
16204 the @code{max} function expects numbers as its argument, not a list of
16205 numbers. Thus, the following expression,
16208 (max '(3 4 6 5 7 3))
16213 produces the following error message;
16216 Wrong type of argument: number-or-marker-p, (3 4 6 5 7 3)
16220 We need a function that passes a list of arguments to a function.
16221 This function is @code{apply}. This function applies its first
16222 argument (a function) to its remaining arguments, the last of which
16229 (apply 'max 3 4 7 3 '(4 8 5))
16235 (Incidentally, I don't know how you would learn of this function
16236 without a book such as this. It is possible to discover other
16237 functions, like @code{search-forward} or @code{insert-rectangle}, by
16238 guessing at a part of their names and then using @code{apropos}. Even
16239 though its base in metaphor is clear---apply its first argument to
16240 the rest---I doubt a novice would come up with that particular word
16241 when using @code{apropos} or other aid. Of course, I could be wrong;
16242 after all, the function was first named by someone who had to invent
16245 The second and subsequent arguments to @code{apply} are optional, so
16246 we can use @code{apply} to call a function and pass the elements of a
16247 list to it, like this, which also returns 8:
16250 (apply 'max '(4 8 5))
16253 This latter way is how we will use @code{apply}. The
16254 @code{recursive-lengths-list-many-files} function returns a numbers'
16255 list to which we can apply @code{max} (we could also apply @code{max} to
16256 the sorted numbers' list; it does not matter whether the list is
16260 Hence, the operation for finding the maximum height of the graph is this:
16263 (setq max-graph-height (apply 'max numbers-list))
16266 Now we can return to the question of how to create a list of strings
16267 for a column of the graph. Told the maximum height of the graph
16268 and the number of asterisks that should appear in the column, the
16269 function should return a list of strings for the
16270 @code{insert-rectangle} command to insert.
16272 Each column is made up of asterisks or blanks. Since the function is
16273 passed the value of the height of the column and the number of
16274 asterisks in the column, the number of blanks can be found by
16275 subtracting the number of asterisks from the height of the column.
16276 Given the number of blanks and the number of asterisks, two
16277 @code{while} loops can be used to construct the list:
16281 ;;; @r{First version.}
16282 (defun column-of-graph (max-graph-height actual-height)
16283 "Return list of strings that is one column of a graph."
16284 (let ((insert-list nil)
16285 (number-of-top-blanks
16286 (- max-graph-height actual-height)))
16290 ;; @r{Fill in asterisks.}
16291 (while (> actual-height 0)
16292 (setq insert-list (cons "*" insert-list))
16293 (setq actual-height (1- actual-height)))
16297 ;; @r{Fill in blanks.}
16298 (while (> number-of-top-blanks 0)
16299 (setq insert-list (cons " " insert-list))
16300 (setq number-of-top-blanks
16301 (1- number-of-top-blanks)))
16305 ;; @r{Return whole list.}
16310 If you install this function and then evaluate the following
16311 expression you will see that it returns the list as desired:
16314 (column-of-graph 5 3)
16322 (" " " " "*" "*" "*")
16325 As written, @code{column-of-graph} contains a major flaw: the symbols
16326 used for the blank and for the marked entries in the column are
16327 hard-coded as a space and asterisk. This is fine for a prototype,
16328 but you, or another user, may wish to use other symbols. For example,
16329 in testing the graph function, you may want to use a period in place
16330 of the space, to make sure the point is being repositioned properly
16331 each time the @code{insert-rectangle} function is called; or you might
16332 want to substitute a @samp{+} sign or other symbol for the asterisk.
16333 You might even want to make a graph-column that is more than one
16334 display column wide. The program should be more flexible. The way to
16335 do that is to replace the blank and the asterisk with two variables
16336 that we can call @code{graph-blank} and @code{graph-symbol} and define
16337 those variables separately.
16339 Also, the documentation is not well written. These considerations
16340 lead us to the second version of the function:
16344 (defvar graph-symbol "*"
16345 "String used as symbol in graph, usually an asterisk.")
16349 (defvar graph-blank " "
16350 "String used as blank in graph, usually a blank space.
16351 graph-blank must be the same number of columns wide
16357 (For an explanation of @code{defvar}, see
16358 @ref{defvar, , Initializing a Variable with @code{defvar}}.)
16362 ;;; @r{Second version.}
16363 (defun column-of-graph (max-graph-height actual-height)
16364 "Return MAX-GRAPH-HEIGHT strings; ACTUAL-HEIGHT are graph-symbols.
16368 The graph-symbols are contiguous entries at the end
16370 The list will be inserted as one column of a graph.
16371 The strings are either graph-blank or graph-symbol."
16375 (let ((insert-list nil)
16376 (number-of-top-blanks
16377 (- max-graph-height actual-height)))
16381 ;; @r{Fill in @code{graph-symbols}.}
16382 (while (> actual-height 0)
16383 (setq insert-list (cons graph-symbol insert-list))
16384 (setq actual-height (1- actual-height)))
16388 ;; @r{Fill in @code{graph-blanks}.}
16389 (while (> number-of-top-blanks 0)
16390 (setq insert-list (cons graph-blank insert-list))
16391 (setq number-of-top-blanks
16392 (1- number-of-top-blanks)))
16394 ;; @r{Return whole list.}
16399 If we wished, we could rewrite @code{column-of-graph} a third time to
16400 provide optionally for a line graph as well as for a bar graph. This
16401 would not be hard to do. One way to think of a line graph is that it
16402 is no more than a bar graph in which the part of each bar that is
16403 below the top is blank. To construct a column for a line graph, the
16404 function first constructs a list of blanks that is one shorter than
16405 the value, then it uses @code{cons} to attach a graph symbol to the
16406 list; then it uses @code{cons} again to attach the top blanks to
16409 It is easy to see how to write such a function, but since we don't
16410 need it, we will not do it. But the job could be done, and if it were
16411 done, it would be done with @code{column-of-graph}. Even more
16412 important, it is worth noting that few changes would have to be made
16413 anywhere else. The enhancement, if we ever wish to make it, is
16416 Now, finally, we come to our first actual graph printing function.
16417 This prints the body of a graph, not the labels for the vertical and
16418 horizontal axes, so we can call this @code{graph-body-print}.
16420 @node graph-body-print
16421 @section The @code{graph-body-print} Function
16422 @findex graph-body-print
16424 After our preparation in the preceding section, the
16425 @code{graph-body-print} function is straightforward. The function
16426 will print column after column of asterisks and blanks, using the
16427 elements of a numbers' list to specify the number of asterisks in each
16428 column. This is a repetitive act, which means we can use a
16429 decrementing @code{while} loop or recursive function for the job. In
16430 this section, we will write the definition using a @code{while} loop.
16432 The @code{column-of-graph} function requires the height of the graph
16433 as an argument, so we should determine and record that as a local variable.
16435 This leads us to the following template for the @code{while} loop
16436 version of this function:
16440 (defun graph-body-print (numbers-list)
16441 "@var{documentation}@dots{}"
16442 (let ((height @dots{}
16447 (while numbers-list
16448 @var{insert-columns-and-reposition-point}
16449 (setq numbers-list (cdr numbers-list)))))
16454 We need to fill in the slots of the template.
16456 Clearly, we can use the @code{(apply 'max numbers-list)} expression to
16457 determine the height of the graph.
16459 The @code{while} loop will cycle through the @code{numbers-list} one
16460 element at a time. As it is shortened by the @code{(setq numbers-list
16461 (cdr numbers-list))} expression, the @sc{car} of each instance of the
16462 list is the value of the argument for @code{column-of-graph}.
16464 At each cycle of the @code{while} loop, the @code{insert-rectangle}
16465 function inserts the list returned by @code{column-of-graph}. Since
16466 the @code{insert-rectangle} function moves point to the lower right of
16467 the inserted rectangle, we need to save the location of point at the
16468 time the rectangle is inserted, move back to that position after the
16469 rectangle is inserted, and then move horizontally to the next place
16470 from which @code{insert-rectangle} is called.
16472 If the inserted columns are one character wide, as they will be if
16473 single blanks and asterisks are used, the repositioning command is
16474 simply @code{(forward-char 1)}; however, the width of a column may be
16475 greater than one. This means that the repositioning command should be
16476 written @code{(forward-char symbol-width)}. The @code{symbol-width}
16477 itself is the length of a @code{graph-blank} and can be found using
16478 the expression @code{(length graph-blank)}. The best place to bind
16479 the @code{symbol-width} variable to the value of the width of graph
16480 column is in the varlist of the @code{let} expression.
16483 These considerations lead to the following function definition:
16487 (defun graph-body-print (numbers-list)
16488 "Print a bar graph of the NUMBERS-LIST.
16489 The numbers-list consists of the Y-axis values."
16491 (let ((height (apply 'max numbers-list))
16492 (symbol-width (length graph-blank))
16497 (while numbers-list
16498 (setq from-position (point))
16500 (column-of-graph height (car numbers-list)))
16501 (goto-char from-position)
16502 (forward-char symbol-width)
16505 ;; @r{Draw graph column by column.}
16507 (setq numbers-list (cdr numbers-list)))
16510 ;; @r{Place point for X axis labels.}
16511 (forward-line height)
16518 The one unexpected expression in this function is the
16519 @w{@code{(sit-for 0)}} expression in the @code{while} loop. This
16520 expression makes the graph printing operation more interesting to
16521 watch than it would be otherwise. The expression causes Emacs to
16522 @dfn{sit} or do nothing for a zero length of time and then redraw the
16523 screen. Placed here, it causes Emacs to redraw the screen column by
16524 column. Without it, Emacs would not redraw the screen until the
16527 We can test @code{graph-body-print} with a short list of numbers.
16531 Install @code{graph-symbol}, @code{graph-blank},
16532 @code{column-of-graph}, which are in
16534 @ref{Readying a Graph, , Readying a Graph},
16537 @ref{Columns of a graph},
16539 and @code{graph-body-print}.
16543 Copy the following expression:
16546 (graph-body-print '(1 2 3 4 6 4 3 5 7 6 5 2 3))
16550 Switch to the @file{*scratch*} buffer and place the cursor where you
16551 want the graph to start.
16554 Type @kbd{M-:} (@code{eval-expression}).
16557 Yank the @code{graph-body-print} expression into the minibuffer
16558 with @kbd{C-y} (@code{yank)}.
16561 Press @key{RET} to evaluate the @code{graph-body-print} expression.
16565 Emacs will print a graph like this:
16579 @node recursive-graph-body-print
16580 @section The @code{recursive-graph-body-print} Function
16581 @findex recursive-graph-body-print
16583 The @code{graph-body-print} function may also be written recursively.
16584 The recursive solution is divided into two parts: an outside wrapper
16585 that uses a @code{let} expression to determine the values of several
16586 variables that need only be found once, such as the maximum height of
16587 the graph, and an inside function that is called recursively to print
16591 The wrapper is uncomplicated:
16595 (defun recursive-graph-body-print (numbers-list)
16596 "Print a bar graph of the NUMBERS-LIST.
16597 The numbers-list consists of the Y-axis values."
16598 (let ((height (apply 'max numbers-list))
16599 (symbol-width (length graph-blank))
16601 (recursive-graph-body-print-internal
16608 The recursive function is a little more difficult. It has four parts:
16609 the do-again-test, the printing code, the recursive call, and the
16610 next-step-expression. The do-again-test is a @code{when}
16611 expression that determines whether the @code{numbers-list} contains
16612 any remaining elements; if it does, the function prints one column of
16613 the graph using the printing code and calls itself again. The
16614 function calls itself again according to the value produced by the
16615 next-step-expression which causes the call to act on a shorter
16616 version of the @code{numbers-list}.
16620 (defun recursive-graph-body-print-internal
16621 (numbers-list height symbol-width)
16622 "Print a bar graph.
16623 Used within recursive-graph-body-print function."
16628 (setq from-position (point))
16630 (column-of-graph height (car numbers-list)))
16633 (goto-char from-position)
16634 (forward-char symbol-width)
16635 (sit-for 0) ; @r{Draw graph column by column.}
16636 (recursive-graph-body-print-internal
16637 (cdr numbers-list) height symbol-width)))
16642 After installation, this expression can be tested; here is a sample:
16645 (recursive-graph-body-print '(3 2 5 6 7 5 3 4 6 4 3 2 1))
16649 Here is what @code{recursive-graph-body-print} produces:
16663 Either of these two functions, @code{graph-body-print} or
16664 @code{recursive-graph-body-print}, create the body of a graph.
16667 @section Need for Printed Axes
16669 A graph needs printed axes, so you can orient yourself. For a do-once
16670 project, it may be reasonable to draw the axes by hand using Emacs's
16671 Picture mode; but a graph drawing function may be used more than once.
16673 For this reason, I have written enhancements to the basic
16674 @code{print-graph-body} function that automatically print labels for
16675 the horizontal and vertical axes. Since the label printing functions
16676 do not contain much new material, I have placed their description in
16677 an appendix. @xref{Full Graph, , A Graph with Labeled Axes}.
16679 @node Line Graph Exercise
16682 Write a line graph version of the graph printing functions.
16684 @node Emacs Initialization
16685 @chapter Your @file{.emacs} File
16686 @cindex @file{.emacs} file
16687 @cindex Customizing your @file{.emacs} file
16688 @cindex Initialization file
16690 ``You don't have to like Emacs to like it''---this seemingly
16691 paradoxical statement is the secret of GNU Emacs. The plain, out-of-the-box
16692 Emacs is a generic tool. Most people who use it customize
16693 it to suit themselves.
16695 GNU Emacs is mostly written in Emacs Lisp; this means that by writing
16696 expressions in Emacs Lisp you can change or extend Emacs.
16699 * Default Configuration::
16700 * Site-wide Init:: You can write site-wide init files.
16701 * defcustom:: Emacs will write code for you.
16702 * Beginning init File:: How to write a @file{.emacs} init file.
16703 * Text and Auto-fill:: Automatically wrap lines.
16704 * Mail Aliases:: Use abbreviations for email addresses.
16705 * Indent Tabs Mode:: Don't use tabs with @TeX{}
16706 * Keybindings:: Create some personal keybindings.
16707 * Keymaps:: More about key binding.
16708 * Loading Files:: Load (i.e., evaluate) files automatically.
16709 * Autoload:: Make functions available.
16710 * Simple Extension:: Define a function; bind it to a key.
16711 * X11 Colors:: Colors in X.
16713 * Mode Line:: How to customize your mode line.
16717 @node Default Configuration
16718 @unnumberedsec Emacs's Default Configuration
16721 There are those who appreciate Emacs's default configuration. After
16722 all, Emacs starts you in C mode when you edit a C file, starts you in
16723 Fortran mode when you edit a Fortran file, and starts you in
16724 Fundamental mode when you edit an unadorned file. This all makes
16725 sense, if you do not know who is going to use Emacs. Who knows what a
16726 person hopes to do with an unadorned file? Fundamental mode is the
16727 right default for such a file, just as C mode is the right default for
16728 editing C code. (Enough programming languages have syntaxes
16729 that enable them to share or nearly share features, so C mode is
16730 now provided by CC mode, the C Collection.)
16732 But when you do know who is going to use Emacs---you,
16733 yourself---then it makes sense to customize Emacs.
16735 For example, I seldom want Fundamental mode when I edit an
16736 otherwise undistinguished file; I want Text mode. This is why I
16737 customize Emacs: so it suits me.
16739 You can customize and extend Emacs by writing or adapting a
16740 @file{~/.emacs} file. This is your personal initialization file; its
16741 contents, written in Emacs Lisp, tell Emacs what to do.@footnote{You
16742 may also add @file{.el} to @file{~/.emacs} and call it a
16743 @file{~/.emacs.el} file. In the past, you were forbidden to type the
16744 extra keystrokes that the name @file{~/.emacs.el} requires, but now
16745 you may. The new format is consistent with the Emacs Lisp file
16746 naming conventions; the old format saves typing.}
16748 A @file{~/.emacs} file contains Emacs Lisp code. You can write this
16749 code yourself; or you can use Emacs's @code{customize} feature to write
16750 the code for you. You can combine your own expressions and
16751 auto-written Customize expressions in your @file{.emacs} file.
16753 (I myself prefer to write my own expressions, except for those,
16754 particularly fonts, that I find easier to manipulate using the
16755 @code{customize} command. I combine the two methods.)
16757 Most of this chapter is about writing expressions yourself. It
16758 describes a simple @file{.emacs} file; for more information, see
16759 @ref{Init File, , The Init File, emacs, The GNU Emacs Manual}, and
16760 @ref{Init File, , The Init File, elisp, The GNU Emacs Lisp Reference
16763 @node Site-wide Init
16764 @section Site-wide Initialization Files
16766 @cindex @file{default.el} init file
16767 @cindex @file{site-init.el} init file
16768 @cindex @file{site-load.el} init file
16769 In addition to your personal initialization file, Emacs automatically
16770 loads various site-wide initialization files, if they exist. These
16771 have the same form as your @file{.emacs} file, but are loaded by
16774 Two site-wide initialization files, @file{site-load.el} and
16775 @file{site-init.el}, are loaded into Emacs and then dumped if a
16776 dumped version of Emacs is created, as is most common. (Dumped
16777 copies of Emacs load more quickly. However, once a file is loaded and
16778 dumped, a change to it does not lead to a change in Emacs unless you
16779 load it yourself or re-dump Emacs. @xref{Building Emacs, , Building
16780 Emacs, elisp, The GNU Emacs Lisp Reference Manual}, and the
16781 @file{INSTALL} file.)
16783 Three other site-wide initialization files are loaded automatically
16784 each time you start Emacs, if they exist. These are
16785 @file{site-start.el}, which is loaded @emph{before} your @file{.emacs}
16786 file, and @file{default.el}, and the terminal type file, which are both
16787 loaded @emph{after} your @file{.emacs} file.
16789 Settings and definitions in your @file{.emacs} file will overwrite
16790 conflicting settings and definitions in a @file{site-start.el} file,
16791 if it exists; but the settings and definitions in a @file{default.el}
16792 or terminal type file will overwrite those in your @file{.emacs} file.
16793 (You can prevent interference from a terminal type file by setting
16794 @code{term-file-prefix} to @code{nil}. @xref{Simple Extension, , A
16795 Simple Extension}.)
16797 @c Rewritten to avoid overfull hbox.
16798 The @file{INSTALL} file that comes in the distribution contains
16799 descriptions of the @file{site-init.el} and @file{site-load.el} files.
16801 The @file{loadup.el}, @file{startup.el}, and @file{loaddefs.el} files
16802 control loading. These files are in the @file{lisp} directory of the
16803 Emacs distribution and are worth perusing.
16805 The @file{loaddefs.el} file contains a good many suggestions as to
16806 what to put into your own @file{.emacs} file, or into a site-wide
16807 initialization file.
16810 @section Specifying Variables using @code{defcustom}
16813 You can specify variables using @code{defcustom} so that you and
16814 others can then use Emacs's @code{customize} feature to set their
16815 values. (You cannot use @code{customize} to write function
16816 definitions; but you can write @code{defuns} in your @file{.emacs}
16817 file. Indeed, you can write any Lisp expression in your @file{.emacs}
16820 The @code{customize} feature depends on the @code{defcustom} macro.
16821 Although you can use @code{defvar} or @code{setq} for variables that
16822 users set, the @code{defcustom} macro is designed for the job.
16824 You can use your knowledge of @code{defvar} for writing the
16825 first three arguments for @code{defcustom}. The first argument to
16826 @code{defcustom} is the name of the variable. The second argument is
16827 the variable's initial value, if any; and this value is set only if
16828 the value has not already been set. The third argument is the
16831 The fourth and subsequent arguments to @code{defcustom} specify types
16832 and options; these are not featured in @code{defvar}. (These
16833 arguments are optional.)
16835 Each of these arguments consists of a keyword followed by a value.
16836 Each keyword starts with the colon character @samp{:}.
16839 For example, the customizable user option variable
16840 @code{text-mode-hook} looks like this:
16844 (defcustom text-mode-hook nil
16845 "Normal hook run when entering Text mode and many related modes."
16847 :options '(turn-on-auto-fill flyspell-mode)
16853 The name of the variable is @code{text-mode-hook}; it has no default
16854 value; and its documentation string tells you what it does.
16856 The @code{:type} keyword tells Emacs the kind of data to which
16857 @code{text-mode-hook} should be set and how to display the value in a
16858 Customization buffer.
16860 The @code{:options} keyword specifies a suggested list of values for
16861 the variable. Usually, @code{:options} applies to a hook.
16862 The list is only a suggestion; it is not exclusive; a person who sets
16863 the variable may set it to other values; the list shown following the
16864 @code{:options} keyword is intended to offer convenient choices to a
16867 Finally, the @code{:group} keyword tells the Emacs Customization
16868 command in which group the variable is located. This tells where to
16871 The @code{defcustom} macro recognizes more than a dozen keywords.
16872 For more information, see @ref{Customization, , Writing Customization
16873 Definitions, elisp, The GNU Emacs Lisp Reference Manual}.
16875 Consider @code{text-mode-hook} as an example.
16877 There are two ways to customize this variable. You can use the
16878 customization command or write the appropriate expressions yourself.
16881 Using the customization command, you can type:
16888 and find that the group for editing files of text is called ``Text''.
16889 Enter that group. Text Mode Hook is the first member. You can click
16890 on its various options, such as @code{turn-on-auto-fill}, to set the
16891 values. After you click on the button to
16894 Save for Future Sessions
16898 Emacs will write an expression into your @file{.emacs} file.
16899 It will look like this:
16903 (custom-set-variables
16904 ;; custom-set-variables was added by Custom.
16905 ;; If you edit it by hand, you could mess it up, so be careful.
16906 ;; Your init file should contain only one such instance.
16907 ;; If there is more than one, they won't work right.
16908 '(text-mode-hook (quote (turn-on-auto-fill text-mode-hook-identify))))
16913 (The @code{text-mode-hook-identify} function tells
16914 @code{toggle-text-mode-auto-fill} which buffers are in Text mode.
16915 It comes on automatically.)
16917 The @code{custom-set-variables} function works somewhat differently
16918 than a @code{setq}. While I have never learned the differences, I
16919 modify the @code{custom-set-variables} expressions in my @file{.emacs}
16920 file by hand: I make the changes in what appears to me to be a
16921 reasonable manner and have not had any problems. Others prefer to use
16922 the Customization command and let Emacs do the work for them.
16924 Another @code{custom-set-@dots{}} function is @code{custom-set-faces}.
16925 This function sets the various font faces. Over time, I have set a
16926 considerable number of faces. Some of the time, I re-set them using
16927 @code{customize}; other times, I simply edit the
16928 @code{custom-set-faces} expression in my @file{.emacs} file itself.
16930 The second way to customize your @code{text-mode-hook} is to set it
16931 yourself in your @file{.emacs} file using code that has nothing to do
16932 with the @code{custom-set-@dots{}} functions.
16935 When you do this, and later use @code{customize}, you will see a
16939 CHANGED outside Customize; operating on it here may be unreliable.
16943 This message is only a warning. If you click on the button to
16946 Save for Future Sessions
16950 Emacs will write a @code{custom-set-@dots{}} expression near the end
16951 of your @file{.emacs} file that will be evaluated after your
16952 hand-written expression. It will, therefore, overrule your
16953 hand-written expression. No harm will be done. When you do this,
16954 however, be careful to remember which expression is active; if you
16955 forget, you may confuse yourself.
16957 So long as you remember where the values are set, you will have no
16958 trouble. In any event, the values are always set in your
16959 initialization file, which is usually called @file{.emacs}.
16961 I myself use @code{customize} for hardly anything. Mostly, I write
16962 expressions myself.
16966 Incidentally, to be more complete concerning defines: @code{defsubst}
16967 defines an inline function. The syntax is just like that of
16968 @code{defun}. @code{defconst} defines a symbol as a constant. The
16969 intent is that neither programs nor users should ever change a value
16970 set by @code{defconst}. (You can change it; the value set is a
16971 variable; but please do not.)
16973 @node Beginning init File
16974 @section Beginning a @file{.emacs} File
16975 @cindex @file{.emacs} file, beginning of
16977 When you start Emacs, it loads your @file{.emacs} file unless you tell
16978 it not to by specifying @samp{-q} on the command line. (The
16979 @code{emacs -q} command gives you a plain, out-of-the-box Emacs.)
16981 A @file{.emacs} file contains Lisp expressions. Often, these are no
16982 more than expressions to set values; sometimes they are function
16985 @xref{Init File, , The Init File @file{~/.emacs}, emacs, The GNU Emacs
16986 Manual}, for a short description of initialization files.
16988 This chapter goes over some of the same ground, but is a walk among
16989 extracts from a complete, long-used @file{.emacs} file---my own.
16991 The first part of the file consists of comments: reminders to myself.
16992 By now, of course, I remember these things, but when I started, I did
16998 ;;;; Bob's .emacs file
16999 ; Robert J. Chassell
17000 ; 26 September 1985
17005 Look at that date! I started this file a long time ago. I have been
17006 adding to it ever since.
17010 ; Each section in this file is introduced by a
17011 ; line beginning with four semicolons; and each
17012 ; entry is introduced by a line beginning with
17013 ; three semicolons.
17018 This describes the usual conventions for comments in Emacs Lisp.
17019 Everything on a line that follows a semicolon is a comment. Two,
17020 three, and four semicolons are used as subsection and section markers.
17021 (@xref{Comments, ,, elisp, The GNU Emacs Lisp Reference Manual}, for
17022 more about comments.)
17027 ; Control-h is the help key;
17028 ; after typing control-h, type a letter to
17029 ; indicate the subject about which you want help.
17030 ; For an explanation of the help facility,
17031 ; type control-h two times in a row.
17036 Just remember: type @kbd{C-h} two times for help.
17040 ; To find out about any mode, type control-h m
17041 ; while in that mode. For example, to find out
17042 ; about mail mode, enter mail mode and then type
17048 ``Mode help'', as I call this, is very helpful. Usually, it tells you
17049 all you need to know.
17051 Of course, you don't need to include comments like these in your
17052 @file{.emacs} file. I included them in mine because I kept forgetting
17053 about Mode help or the conventions for comments---but I was able to
17054 remember to look here to remind myself.
17056 @node Text and Auto-fill
17057 @section Text and Auto Fill Mode
17059 Now we come to the part that turns on Text mode and
17064 ;;; Text mode and Auto Fill mode
17065 ;; The next two lines put Emacs into Text mode
17066 ;; and Auto Fill mode, and are for writers who
17067 ;; want to start writing prose rather than code.
17068 (setq-default major-mode 'text-mode)
17069 (add-hook 'text-mode-hook 'turn-on-auto-fill)
17073 Here is the first part of this @file{.emacs} file that does something
17074 besides remind a forgetful human!
17076 The first of the two lines in parentheses tells Emacs to turn on Text
17077 mode when you find a file, @emph{unless} that file should go into some
17078 other mode, such as C mode.
17080 @cindex Per-buffer, local variables list
17081 @cindex Local variables list, per-buffer,
17082 @cindex Automatic mode selection
17083 @cindex Mode selection, automatic
17084 When Emacs reads a file, it looks at the extension to the file name,
17085 if any. (The extension is the part that comes after a @samp{.}.) If
17086 the file ends with a @samp{.c} or @samp{.h} extension then Emacs turns
17087 on C mode. Also, Emacs looks at first nonblank line of the file; if
17088 the line says @w{@samp{-*- C -*-}}, Emacs turns on C mode. Emacs
17089 possesses a list of extensions and specifications that it uses
17090 automatically. In addition, Emacs looks near the last page for a
17091 per-buffer, local variables list, if any.
17094 @xref{Choosing Modes, , How Major Modes are Chosen, emacs, The GNU
17097 @xref{File Variables, , Local Variables in Files, emacs, The GNU Emacs
17101 See sections ``How Major Modes are Chosen'' and ``Local Variables in
17102 Files'' in @cite{The GNU Emacs Manual}.
17105 Now, back to the @file{.emacs} file.
17108 Here is the line again; how does it work?
17110 @cindex Text Mode turned on
17112 (setq major-mode 'text-mode)
17116 This line is a short, but complete Emacs Lisp expression.
17118 We are already familiar with @code{setq}. It sets the following variable,
17119 @code{major-mode}, to the subsequent value, which is @code{text-mode}.
17120 The single quote mark before @code{text-mode} tells Emacs to deal directly
17121 with the @code{text-mode} symbol, not with whatever it might stand for.
17122 @xref{set & setq, , Setting the Value of a Variable},
17123 for a reminder of how @code{setq} works.
17124 The main point is that there is no difference between the procedure you
17125 use to set a value in your @file{.emacs} file and the procedure you use
17126 anywhere else in Emacs.
17129 Here is the next line:
17131 @cindex Auto Fill mode turned on
17134 (add-hook 'text-mode-hook 'turn-on-auto-fill)
17138 In this line, the @code{add-hook} command adds
17139 @code{turn-on-auto-fill} to the variable.
17141 @code{turn-on-auto-fill} is the name of a program, that, you guessed
17142 it!, turns on Auto Fill mode.
17144 Every time Emacs turns on Text mode, Emacs runs the commands hooked
17145 onto Text mode. So every time Emacs turns on Text mode, Emacs also
17146 turns on Auto Fill mode.
17148 In brief, the first line causes Emacs to enter Text mode when you edit a
17149 file, unless the file name extension, a first non-blank line, or local
17150 variables to tell Emacs otherwise.
17152 Text mode among other actions, sets the syntax table to work
17153 conveniently for writers. In Text mode, Emacs considers an apostrophe
17154 as part of a word like a letter; but Emacs does not consider a period
17155 or a space as part of a word. Thus, @kbd{M-f} moves you over
17156 @samp{it's}. On the other hand, in C mode, @kbd{M-f} stops just after
17157 the @samp{t} of @samp{it's}.
17159 The second line causes Emacs to turn on Auto Fill mode when it turns
17160 on Text mode. In Auto Fill mode, Emacs automatically breaks a line
17161 that is too wide and brings the excessively wide part of the line down
17162 to the next line. Emacs breaks lines between words, not within them.
17164 When Auto Fill mode is turned off, lines continue to the right as you
17165 type them. Depending on how you set the value of
17166 @code{truncate-lines}, the words you type either disappear off the
17167 right side of the screen, or else are shown, in a rather ugly and
17168 unreadable manner, as a continuation line on the screen.
17171 In addition, in this part of my @file{.emacs} file, I tell the Emacs
17172 fill commands to insert two spaces after a colon:
17175 (setq colon-double-space t)
17179 @section Mail Aliases
17181 Here is a @code{setq} that turns on mail aliases, along with more
17187 ; To enter mail mode, type 'C-x m'
17188 ; To enter RMAIL (for reading mail),
17190 (setq mail-aliases t)
17194 @cindex Mail aliases
17196 This @code{setq} command sets the value of the variable
17197 @code{mail-aliases} to @code{t}. Since @code{t} means true, the line
17198 says, in effect, ``Yes, use mail aliases.''
17200 Mail aliases are convenient short names for long email addresses or
17201 for lists of email addresses. The file where you keep your aliases
17202 is @file{~/.mailrc}. You write an alias like this:
17205 alias geo george@@foobar.wiz.edu
17209 When you write a message to George, address it to @samp{geo}; the
17210 mailer will automatically expand @samp{geo} to the full address.
17212 @node Indent Tabs Mode
17213 @section Indent Tabs Mode
17214 @cindex Tabs, preventing
17215 @findex indent-tabs-mode
17217 By default, Emacs inserts tabs in place of multiple spaces when it
17218 formats a region. (For example, you might indent many lines of text
17219 all at once with the @code{indent-region} command.) Tabs look fine on
17220 a terminal or with ordinary printing, but they produce badly indented
17221 output when you use @TeX{} or Texinfo since @TeX{} ignores tabs.
17224 The following turns off Indent Tabs mode:
17228 ;;; Prevent Extraneous Tabs
17229 (setq-default indent-tabs-mode nil)
17233 Note that this line uses @code{setq-default} rather than the
17234 @code{setq} command that we have seen before. The @code{setq-default}
17235 command sets values only in buffers that do not have their own local
17236 values for the variable.
17239 @xref{Just Spaces, , Tabs vs.@: Spaces, emacs, The GNU Emacs Manual}.
17241 @xref{File Variables, , Local Variables in Files, emacs, The GNU Emacs
17245 See sections ``Tabs vs.@: Spaces'' and ``Local Variables in
17246 Files'' in @cite{The GNU Emacs Manual}.
17251 @section Some Keybindings
17253 Now for some personal keybindings:
17257 ;;; Compare windows
17258 (global-set-key "\C-cw" 'compare-windows)
17262 @findex compare-windows
17263 @code{compare-windows} is a nifty command that compares the text in
17264 your current window with text in the next window. It makes the
17265 comparison by starting at point in each window, moving over text in
17266 each window as far as they match. I use this command all the time.
17268 This also shows how to set a key globally, for all modes.
17270 @cindex Setting a key globally
17271 @cindex Global set key
17272 @cindex Key setting globally
17273 @findex global-set-key
17274 The command is @code{global-set-key}. It is followed by the
17275 keybinding. In a @file{.emacs} file, the keybinding is written as
17276 shown: @code{\C-c} stands for Control-C, which means to press the
17277 control key and the @key{c} key at the same time. The @code{w} means
17278 to press the @key{w} key. The keybinding is surrounded by double
17279 quotation marks. In documentation, you would write this as
17280 @w{@kbd{C-c w}}. (If you were binding a @key{META} key, such as
17281 @kbd{M-c}, rather than a @key{CTRL} key, you would write
17282 @w{@code{\M-c}} in your @file{.emacs} file. @xref{Init Rebinding, ,
17283 Rebinding Keys in Your Init File, emacs, The GNU Emacs Manual}, for
17286 The command invoked by the keys is @code{compare-windows}. Note that
17287 @code{compare-windows} is preceded by a single quote; otherwise, Emacs
17288 would first try to evaluate the symbol to determine its value.
17290 These three things, the double quotation marks, the backslash before
17291 the @samp{C}, and the single quote mark are necessary parts of
17292 keybinding that I tend to forget. Fortunately, I have come to
17293 remember that I should look at my existing @file{.emacs} file, and
17294 adapt what is there.
17296 As for the keybinding itself: @kbd{C-c w}. This combines the prefix
17297 key, @kbd{C-c}, with a single character, in this case, @kbd{w}. This
17298 set of keys, @kbd{C-c} followed by a single character, is strictly
17299 reserved for individuals' own use. (I call these @dfn{own} keys, since
17300 these are for my own use.) You should always be able to create such a
17301 keybinding for your own use without stomping on someone else's
17302 keybinding. If you ever write an extension to Emacs, please avoid
17303 taking any of these keys for public use. Create a key like @kbd{C-c
17304 C-w} instead. Otherwise, we will run out of own keys.
17307 Here is another keybinding, with a comment:
17311 ;;; Keybinding for 'occur'
17312 ; I use occur a lot, so let's bind it to a key:
17313 (global-set-key "\C-co" 'occur)
17318 The @code{occur} command shows all the lines in the current buffer
17319 that contain a match for a regular expression. Matching lines are
17320 shown in a buffer called @file{*Occur*}. That buffer serves as a menu
17321 to jump to occurrences.
17323 @findex global-unset-key
17324 @cindex Unbinding key
17325 @cindex Key unbinding
17327 Here is how to unbind a key, so it does not
17333 (global-unset-key "\C-xf")
17337 There is a reason for this unbinding: I found I inadvertently typed
17338 @w{@kbd{C-x f}} when I meant to type @kbd{C-x C-f}. Rather than find a
17339 file, as I intended, I accidentally set the width for filled text,
17340 almost always to a width I did not want. Since I hardly ever reset my
17341 default width, I simply unbound the key.
17343 @findex list-buffers, @r{rebound}
17344 @findex buffer-menu, @r{bound to key}
17346 The following rebinds an existing key:
17350 ;;; Rebind 'C-x C-b' for 'buffer-menu'
17351 (global-set-key "\C-x\C-b" 'buffer-menu)
17355 By default, @kbd{C-x C-b} runs the
17356 @code{list-buffers} command. This command lists
17357 your buffers in @emph{another} window. Since I
17358 almost always want to do something in that
17359 window, I prefer the @code{buffer-menu}
17360 command, which not only lists the buffers,
17361 but moves point into that window.
17366 @cindex Rebinding keys
17368 Emacs uses @dfn{keymaps} to record which keys call which commands.
17369 When you use @code{global-set-key} to set the keybinding for a single
17370 command in all parts of Emacs, you are specifying the keybinding in
17371 @code{current-global-map}.
17373 Specific modes, such as C mode or Text mode, have their own keymaps;
17374 the mode-specific keymaps override the global map that is shared by
17377 The @code{global-set-key} function binds, or rebinds, the global
17378 keymap. For example, the following binds the key @kbd{C-x C-b} to the
17379 function @code{buffer-menu}:
17382 (global-set-key "\C-x\C-b" 'buffer-menu)
17385 Mode-specific keymaps are bound using the @code{define-key} function,
17386 which takes a specific keymap as an argument, as well as the key and
17387 the command. For example, my @file{.emacs} file contains the
17388 following expression to bind the @code{texinfo-insert-@@group} command
17389 to @kbd{C-c C-c g}:
17393 (define-key texinfo-mode-map "\C-c\C-cg" 'texinfo-insert-@@group)
17398 The @code{texinfo-insert-@@group} function itself is a little extension
17399 to Texinfo mode that inserts @samp{@@group} into a Texinfo file. I
17400 use this command all the time and prefer to type the three strokes
17401 @kbd{C-c C-c g} rather than the six strokes @kbd{@@ g r o u p}.
17402 (@samp{@@group} and its matching @samp{@@end group} are commands that
17403 keep all enclosed text together on one page; many multi-line examples
17404 in this book are surrounded by @samp{@@group @dots{} @@end group}.)
17407 Here is the @code{texinfo-insert-@@group} function definition:
17411 (defun texinfo-insert-@@group ()
17412 "Insert the string @@group in a Texinfo buffer."
17414 (beginning-of-line)
17415 (insert "@@group\n"))
17419 (Of course, I could have used Abbrev mode to save typing, rather than
17420 write a function to insert a word; but I prefer key strokes consistent
17421 with other Texinfo mode key bindings.)
17423 You will see numerous @code{define-key} expressions in
17424 @file{loaddefs.el} as well as in the various mode libraries, such as
17425 @file{cc-mode.el} and @file{lisp-mode.el}.
17427 @xref{Key Bindings, , Customizing Key Bindings, emacs, The GNU Emacs
17428 Manual}, and @ref{Keymaps, , Keymaps, elisp, The GNU Emacs Lisp
17429 Reference Manual}, for more information about keymaps.
17431 @node Loading Files
17432 @section Loading Files
17433 @cindex Loading files
17436 Many people in the GNU Emacs community have written extensions to
17437 Emacs. As time goes by, these extensions are often included in new
17438 releases. For example, the Calendar and Diary packages are now part
17439 of the standard GNU Emacs, as is Calc.
17441 You can use a @code{load} command to evaluate a complete file and
17442 thereby install all the functions and variables in the file into Emacs.
17445 @c (auto-compression-mode t)
17448 (load "~/emacs/slowsplit")
17451 This evaluates, i.e., loads, the @file{slowsplit.el} file or if it
17452 exists, the faster, byte compiled @file{slowsplit.elc} file from the
17453 @file{emacs} sub-directory of your home directory. The file contains
17454 the function @code{split-window-quietly}, which John Robinson wrote in
17457 The @code{split-window-quietly} function splits a window with the
17458 minimum of redisplay. I installed it in 1989 because it worked well
17459 with the slow 1200 baud terminals I was then using. Nowadays, I only
17460 occasionally come across such a slow connection, but I continue to use
17461 the function because I like the way it leaves the bottom half of a
17462 buffer in the lower of the new windows and the top half in the upper
17466 To replace the key binding for the default
17467 @code{split-window-vertically}, you must also unset that key and bind
17468 the keys to @code{split-window-quietly}, like this:
17472 (global-unset-key "\C-x2")
17473 (global-set-key "\C-x2" 'split-window-quietly)
17478 If you load many extensions, as I do, then instead of specifying the
17479 exact location of the extension file, as shown above, you can specify
17480 that directory as part of Emacs's @code{load-path}. Then, when Emacs
17481 loads a file, it will search that directory as well as its default
17482 list of directories. (The default list is specified in @file{paths.h}
17483 when Emacs is built.)
17486 The following command adds your @file{~/emacs} directory to the
17487 existing load path:
17491 ;;; Emacs Load Path
17492 (setq load-path (cons "~/emacs" load-path))
17496 Incidentally, @code{load-library} is an interactive interface to the
17497 @code{load} function. The complete function looks like this:
17499 @findex load-library
17502 (defun load-library (library)
17503 "Load the Emacs Lisp library named LIBRARY.
17504 This is an interface to the function `load'. LIBRARY is searched
17505 for in `load-path', both with and without `load-suffixes' (as
17506 well as `load-file-rep-suffixes').
17508 See Info node `(emacs)Lisp Libraries' for more details.
17509 See `load-file' for a different interface to `load'."
17511 (list (completing-read "Load library: "
17512 (apply-partially 'locate-file-completion-table
17514 (get-load-suffixes)))))
17519 The name of the function, @code{load-library}, comes from the use of
17520 ``library'' as a conventional synonym for ``file''. The source for the
17521 @code{load-library} command is in the @file{files.el} library.
17523 Another interactive command that does a slightly different job is
17524 @code{load-file}. @xref{Lisp Libraries, , Libraries of Lisp Code for
17525 Emacs, emacs, The GNU Emacs Manual}, for information on the
17526 distinction between @code{load-library} and this command.
17529 @section Autoloading
17532 Instead of installing a function by loading the file that contains it,
17533 or by evaluating the function definition, you can make the function
17534 available but not actually install it until it is first called. This
17535 is called @dfn{autoloading}.
17537 When you execute an autoloaded function, Emacs automatically evaluates
17538 the file that contains the definition, and then calls the function.
17540 Emacs starts quicker with autoloaded functions, since their libraries
17541 are not loaded right away; but you need to wait a moment when you
17542 first use such a function, while its containing file is evaluated.
17544 Rarely used functions are frequently autoloaded. The
17545 @file{loaddefs.el} library contains thousands of autoloaded functions,
17546 from @code{5x5} to @code{zone}. Of course, you may
17547 come to use a rare function frequently. When you do, you should
17548 load that function's file with a @code{load} expression in your
17549 @file{.emacs} file.
17551 In my @file{.emacs} file, I load 14 libraries that contain functions
17552 that would otherwise be autoloaded. (Actually, it would have been
17553 better to include these files in my dumped Emacs, but I forgot.
17554 @xref{Building Emacs, , Building Emacs, elisp, The GNU Emacs Lisp
17555 Reference Manual}, and the @file{INSTALL} file for more about
17558 You may also want to include autoloaded expressions in your @file{.emacs}
17559 file. @code{autoload} is a built-in function that takes up to five
17560 arguments, the final three of which are optional. The first argument
17561 is the name of the function to be autoloaded; the second is the name
17562 of the file to be loaded. The third argument is documentation for the
17563 function, and the fourth tells whether the function can be called
17564 interactively. The fifth argument tells what type of
17565 object---@code{autoload} can handle a keymap or macro as well as a
17566 function (the default is a function).
17569 Here is a typical example:
17573 (autoload 'html-helper-mode
17574 "html-helper-mode" "Edit HTML documents" t)
17579 (@code{html-helper-mode} is an older alternative to @code{html-mode},
17580 which is a standard part of the distribution.)
17583 This expression autoloads the @code{html-helper-mode} function. It
17584 takes it from the @file{html-helper-mode.el} file (or from the byte
17585 compiled version @file{html-helper-mode.elc}, if that exists.) The
17586 file must be located in a directory specified by @code{load-path}.
17587 The documentation says that this is a mode to help you edit documents
17588 written in the HyperText Markup Language. You can call this mode
17589 interactively by typing @kbd{M-x html-helper-mode}. (You need to
17590 duplicate the function's regular documentation in the autoload
17591 expression because the regular function is not yet loaded, so its
17592 documentation is not available.)
17594 @xref{Autoload, , Autoload, elisp, The GNU Emacs Lisp Reference
17595 Manual}, for more information.
17597 @node Simple Extension
17598 @section A Simple Extension: @code{line-to-top-of-window}
17599 @findex line-to-top-of-window
17600 @cindex Simple extension in @file{.emacs} file
17602 Here is a simple extension to Emacs that moves the line point is on to
17603 the top of the window. I use this all the time, to make text easier
17606 You can put the following code into a separate file and then load it
17607 from your @file{.emacs} file, or you can include it within your
17608 @file{.emacs} file.
17611 Here is the definition:
17615 ;;; Line to top of window;
17616 ;;; replace three keystroke sequence C-u 0 C-l
17617 (defun line-to-top-of-window ()
17618 "Move the line point is on to top of window."
17625 Now for the keybinding.
17627 Nowadays, function keys as well as mouse button events and
17628 non-@sc{ascii} characters are written within square brackets, without
17629 quotation marks. (In Emacs version 18 and before, you had to write
17630 different function key bindings for each different make of terminal.)
17632 I bind @code{line-to-top-of-window} to my @key{F6} function key like
17636 (global-set-key [f6] 'line-to-top-of-window)
17639 For more information, see @ref{Init Rebinding, , Rebinding Keys in
17640 Your Init File, emacs, The GNU Emacs Manual}.
17642 @cindex Conditional 'twixt two versions of Emacs
17643 @cindex Version of Emacs, choosing
17644 @cindex Emacs version, choosing
17645 If you run two versions of GNU Emacs, such as versions 22 and 23, and
17646 use one @file{.emacs} file, you can select which code to evaluate with
17647 the following conditional:
17652 ((= 22 emacs-major-version)
17653 ;; evaluate version 22 code
17655 ((= 23 emacs-major-version)
17656 ;; evaluate version 23 code
17661 For example, recent versions blink
17662 their cursors by default. I hate such blinking, as well as other
17663 features, so I placed the following in my @file{.emacs}
17664 file@footnote{When I start instances of Emacs that do not load my
17665 @file{.emacs} file or any site file, I also turn off blinking:
17668 emacs -q --no-site-file -eval '(blink-cursor-mode nil)'
17670 @exdent Or nowadays, using an even more sophisticated set of options,
17678 (when (>= emacs-major-version 21)
17679 (blink-cursor-mode 0)
17680 ;; Insert newline when you press 'C-n' (next-line)
17681 ;; at the end of the buffer
17682 (setq next-line-add-newlines t)
17685 ;; Turn on image viewing
17686 (auto-image-file-mode t)
17689 ;; Turn on menu bar (this bar has text)
17690 ;; (Use numeric argument to turn on)
17694 ;; Turn off tool bar (this bar has icons)
17695 ;; (Use numeric argument to turn on)
17696 (tool-bar-mode nil)
17699 ;; Turn off tooltip mode for tool bar
17700 ;; (This mode causes icon explanations to pop up)
17701 ;; (Use numeric argument to turn on)
17703 ;; If tooltips turned on, make tips appear promptly
17704 (setq tooltip-delay 0.1) ; default is 0.7 second
17710 @section X11 Colors
17712 You can specify colors when you use Emacs with the MIT X Windowing
17715 I dislike the default colors and specify my own.
17718 Here are the expressions in my @file{.emacs}
17719 file that set values:
17723 ;; Set cursor color
17724 (set-cursor-color "white")
17727 (set-mouse-color "white")
17729 ;; Set foreground and background
17730 (set-foreground-color "white")
17731 (set-background-color "darkblue")
17735 ;;; Set highlighting colors for isearch and drag
17736 (set-face-foreground 'highlight "white")
17737 (set-face-background 'highlight "blue")
17741 (set-face-foreground 'region "cyan")
17742 (set-face-background 'region "blue")
17746 (set-face-foreground 'secondary-selection "skyblue")
17747 (set-face-background 'secondary-selection "darkblue")
17751 ;; Set calendar highlighting colors
17752 (add-hook 'calendar-load-hook
17754 (set-face-foreground 'diary-face "skyblue")
17755 (set-face-background 'holiday-face "slate blue")
17756 (set-face-foreground 'holiday-face "white")))
17760 The various shades of blue soothe my eye and prevent me from seeing
17761 the screen flicker.
17763 Alternatively, I could have set my specifications in various X
17764 initialization files. For example, I could set the foreground,
17765 background, cursor, and pointer (i.e., mouse) colors in my
17766 @file{~/.Xresources} file like this:
17770 Emacs*foreground: white
17771 Emacs*background: darkblue
17772 Emacs*cursorColor: white
17773 Emacs*pointerColor: white
17777 In any event, since it is not part of Emacs, I set the root color of
17778 my X window in my @file{~/.xinitrc} file, like this@footnote{I also
17779 run more modern window managers, such as Enlightenment, Gnome, or KDE;
17780 in those cases, I often specify an image rather than a plain color.}:
17783 xsetroot -solid Navy -fg white &
17787 @node Miscellaneous
17788 @section Miscellaneous Settings for a @file{.emacs} File
17791 Here are a few miscellaneous settings:
17796 Set the shape and color of the mouse cursor:
17800 ; Cursor shapes are defined in
17801 ; '/usr/include/X11/cursorfont.h';
17802 ; for example, the 'target' cursor is number 128;
17803 ; the 'top_left_arrow' cursor is number 132.
17807 (let ((mpointer (x-get-resource "*mpointer"
17808 "*emacs*mpointer")))
17809 ;; If you have not set your mouse pointer
17810 ;; then set it, otherwise leave as is:
17811 (if (eq mpointer nil)
17812 (setq mpointer "132")) ; top_left_arrow
17815 (setq x-pointer-shape (string-to-int mpointer))
17816 (set-mouse-color "white"))
17821 Or you can set the values of a variety of features in an alist, like
17827 default-frame-alist
17828 '((cursor-color . "white")
17829 (mouse-color . "white")
17830 (foreground-color . "white")
17831 (background-color . "DodgerBlue4")
17832 ;; (cursor-type . bar)
17833 (cursor-type . box)
17836 (tool-bar-lines . 0)
17837 (menu-bar-lines . 1)
17841 "-Misc-Fixed-Medium-R-Normal--20-200-75-75-C-100-ISO8859-1")
17847 Convert @kbd{@key{CTRL}-h} into @key{DEL} and @key{DEL}
17848 into @kbd{@key{CTRL}-h}.@*
17849 (Some older keyboards needed this, although I have not seen the
17854 ;; Translate 'C-h' to <DEL>.
17855 ; (keyboard-translate ?\C-h ?\C-?)
17857 ;; Translate <DEL> to 'C-h'.
17858 (keyboard-translate ?\C-? ?\C-h)
17862 @item Turn off a blinking cursor!
17866 (if (fboundp 'blink-cursor-mode)
17867 (blink-cursor-mode -1))
17872 or start GNU Emacs with the command @code{emacs -nbc}.
17875 @item When using @command{grep}@*
17876 @samp{-i}@w{ } Ignore case distinctions@*
17877 @samp{-n}@w{ } Prefix each line of output with line number@*
17878 @samp{-H}@w{ } Print the filename for each match.@*
17879 @samp{-e}@w{ } Protect patterns beginning with a hyphen character, @samp{-}
17882 (setq grep-command "grep -i -nH -e ")
17886 @c Evidently, no longer needed in GNU Emacs 22
17888 item Automatically uncompress compressed files when visiting them
17891 (load "uncompress")
17896 @item Find an existing buffer, even if it has a different name@*
17897 This avoids problems with symbolic links.
17900 (setq find-file-existing-other-name t)
17903 @item Set your language environment and default input method
17907 (set-language-environment "latin-1")
17908 ;; Remember you can enable or disable multilingual text input
17909 ;; with the @code{toggle-input-method'} (@kbd{C-\}) command
17910 (setq default-input-method "latin-1-prefix")
17914 If you want to write with Chinese GB characters, set this instead:
17918 (set-language-environment "Chinese-GB")
17919 (setq default-input-method "chinese-tonepy")
17924 @subsubheading Fixing Unpleasant Key Bindings
17925 @cindex Key bindings, fixing
17926 @cindex Bindings, key, fixing unpleasant
17928 Some systems bind keys unpleasantly. Sometimes, for example, the
17929 @key{CTRL} key appears in an awkward spot rather than at the far left
17932 Usually, when people fix these sorts of keybindings, they do not
17933 change their @file{~/.emacs} file. Instead, they bind the proper keys
17934 on their consoles with the @code{loadkeys} or @code{install-keymap}
17935 commands in their boot script and then include @code{xmodmap} commands
17936 in their @file{.xinitrc} or @file{.Xsession} file for X Windows.
17944 loadkeys /usr/share/keymaps/i386/qwerty/emacs2.kmap.gz
17946 install-keymap emacs2
17952 For a @file{.xinitrc} or @file{.Xsession} file when the @key{Caps
17953 Lock} key is at the far left of the home row:
17957 # Bind the key labeled 'Caps Lock' to 'Control'
17958 # (Such a broken user interface suggests that keyboard manufacturers
17959 # think that computers are typewriters from 1885.)
17961 xmodmap -e "clear Lock"
17962 xmodmap -e "add Control = Caps_Lock"
17968 In a @file{.xinitrc} or @file{.Xsession} file, to convert an @key{ALT}
17969 key to a @key{META} key:
17973 # Some ill designed keyboards have a key labeled ALT and no Meta
17974 xmodmap -e "keysym Alt_L = Meta_L Alt_L"
17980 @section A Modified Mode Line
17981 @vindex mode-line-format
17982 @cindex Mode line format
17984 Finally, a feature I really like: a modified mode line.
17986 When I work over a network, I forget which machine I am using. Also,
17987 I tend to I lose track of where I am, and which line point is on.
17989 So I reset my mode line to look like this:
17992 -:-- foo.texi rattlesnake:/home/bob/ Line 1 (Texinfo Fill) Top
17995 I am visiting a file called @file{foo.texi}, on my machine
17996 @file{rattlesnake} in my @file{/home/bob} buffer. I am on line 1, in
17997 Texinfo mode, and am at the top of the buffer.
18000 My @file{.emacs} file has a section that looks like this:
18004 ;; Set a Mode Line that tells me which machine, which directory,
18005 ;; and which line I am on, plus the other customary information.
18006 (setq-default mode-line-format
18010 "mouse-1: select window, mouse-2: delete others ..."))
18011 mode-line-mule-info
18013 mode-line-frame-identification
18017 mode-line-buffer-identification
18020 (system-name) 0 (string-match "\\..+" (system-name))))
18025 "mouse-1: select window, mouse-2: delete others ..."))
18026 (line-number-mode " Line %l ")
18032 "mouse-1: select window, mouse-2: delete others ..."))
18033 (:eval (mode-line-mode-name))
18036 #("%n" 0 2 (help-echo "mouse-2: widen" local-map (keymap ...)))
18045 Here, I redefine the default mode line. Most of the parts are from
18046 the original; but I make a few changes. I set the @emph{default} mode
18047 line format so as to permit various modes, such as Info, to override
18050 Many elements in the list are self-explanatory:
18051 @code{mode-line-modified} is a variable that tells whether the buffer
18052 has been modified, @code{mode-name} tells the name of the mode, and so
18053 on. However, the format looks complicated because of two features we
18054 have not discussed.
18056 @cindex Properties, in mode line example
18057 The first string in the mode line is a dash or hyphen, @samp{-}. In
18058 the old days, it would have been specified simply as @code{"-"}. But
18059 nowadays, Emacs can add properties to a string, such as highlighting
18060 or, as in this case, a help feature. If you place your mouse cursor
18061 over the hyphen, some help information appears (By default, you must
18062 wait seven-tenths of a second before the information appears. You can
18063 change that timing by changing the value of @code{tooltip-delay}.)
18066 The new string format has a special syntax:
18069 #("-" 0 1 (help-echo "mouse-1: select window, ..."))
18073 The @code{#(} begins a list. The first element of the list is the
18074 string itself, just one @samp{-}. The second and third
18075 elements specify the range over which the fourth element applies. A
18076 range starts @emph{after} a character, so a zero means the range
18077 starts just before the first character; a 1 means that the range ends
18078 just after the first character. The third element is the property for
18079 the range. It consists of a property list, a
18080 property name, in this case, @samp{help-echo}, followed by a value, in this
18081 case, a string. The second, third, and fourth elements of this new
18082 string format can be repeated.
18084 @xref{Text Properties, , Text Properties, elisp, The GNU Emacs Lisp
18085 Reference Manual}, and see @ref{Mode Line Format, , Mode Line Format,
18086 elisp, The GNU Emacs Lisp Reference Manual}, for more information.
18088 @code{mode-line-buffer-identification}
18089 displays the current buffer name. It is a list
18090 beginning @code{(#("%12b" 0 4 @dots{}}.
18091 The @code{#(} begins the list.
18093 The @samp{"%12b"} displays the current buffer name, using the
18094 @code{buffer-name} function with which we are familiar; the @samp{12}
18095 specifies the maximum number of characters that will be displayed.
18096 When a name has fewer characters, whitespace is added to fill out to
18097 this number. (Buffer names can and often should be longer than 12
18098 characters; this length works well in a typical 80 column wide
18101 @code{:eval} says to evaluate the following form and use the result as
18102 a string to display. In this case, the expression displays the first
18103 component of the full system name. The end of the first component is
18104 a @samp{.} (period), so I use the @code{string-match} function to
18105 tell me the length of the first component. The substring from the
18106 zeroth character to that length is the name of the machine.
18109 This is the expression:
18114 (system-name) 0 (string-match "\\..+" (system-name))))
18118 @samp{%[} and @samp{%]} cause a pair of square brackets
18119 to appear for each recursive editing level. @samp{%n} says ``Narrow''
18120 when narrowing is in effect. @samp{%P} tells you the percentage of
18121 the buffer that is above the bottom of the window, or ``Top'', ``Bottom'',
18122 or ``All''. (A lower case @samp{p} tell you the percentage above the
18123 @emph{top} of the window.) @samp{%-} inserts enough dashes to fill
18126 Remember, you don't have to like Emacs to like it---your own
18127 Emacs can have different colors, different commands, and different
18128 keys than a default Emacs.
18130 On the other hand, if you want to bring up a plain out-of-the-box
18131 Emacs, with no customization, type:
18138 This will start an Emacs that does @emph{not} load your
18139 @file{~/.emacs} initialization file. A plain, default Emacs. Nothing
18146 GNU Emacs has two debuggers, @code{debug} and @code{edebug}. The
18147 first is built into the internals of Emacs and is always with you;
18148 the second requires that you instrument a function before you can use it.
18150 Both debuggers are described extensively in @ref{Debugging, ,
18151 Debugging Lisp Programs, elisp, The GNU Emacs Lisp Reference Manual}.
18152 In this chapter, I will walk through a short example of each.
18155 * debug:: How to use the built-in debugger.
18156 * debug-on-entry:: Start debugging when you call a function.
18157 * debug-on-quit:: Start debugging when you quit with @kbd{C-g}.
18158 * edebug:: How to use Edebug, a source level debugger.
18159 * Debugging Exercises::
18163 @section @code{debug}
18166 Suppose you have written a function definition that is intended to
18167 return the sum of the numbers 1 through a given number. (This is the
18168 @code{triangle} function discussed earlier. @xref{Decrementing
18169 Example, , Example with Decrementing Counter}, for a discussion.)
18170 @c xref{Decrementing Loop,, Loop with a Decrementing Counter}, for a discussion.)
18172 However, your function definition has a bug. You have mistyped
18173 @samp{1=} for @samp{1-}. Here is the broken definition:
18175 @findex triangle-bugged
18178 (defun triangle-bugged (number)
18179 "Return sum of numbers 1 through NUMBER inclusive."
18181 (while (> number 0)
18182 (setq total (+ total number))
18183 (setq number (1= number))) ; @r{Error here.}
18188 If you are reading this in Info, you can evaluate this definition in
18189 the normal fashion. You will see @code{triangle-bugged} appear in the
18193 Now evaluate the @code{triangle-bugged} function with an
18197 (triangle-bugged 4)
18201 In a recent GNU Emacs, you will create and enter a @file{*Backtrace*}
18207 ---------- Buffer: *Backtrace* ----------
18208 Debugger entered--Lisp error: (void-function 1=)
18210 (setq number (1= number))
18211 (while (> number 0) (setq total (+ total number))
18212 (setq number (1= number)))
18213 (let ((total 0)) (while (> number 0) (setq total ...)
18214 (setq number ...)) total)
18218 eval((triangle-bugged 4))
18219 eval-last-sexp-1(nil)
18220 eval-last-sexp(nil)
18221 call-interactively(eval-last-sexp)
18222 ---------- Buffer: *Backtrace* ----------
18227 (I have reformatted this example slightly; the debugger does not fold
18228 long lines. As usual, you can quit the debugger by typing @kbd{q} in
18229 the @file{*Backtrace*} buffer.)
18231 In practice, for a bug as simple as this, the Lisp error line will
18232 tell you what you need to know to correct the definition. The
18233 function @code{1=} is void.
18237 In GNU Emacs 20 and before, you will see:
18240 Symbol's function definition is void:@: 1=
18244 which has the same meaning as the @file{*Backtrace*} buffer line in
18248 However, suppose you are not quite certain what is going on?
18249 You can read the complete backtrace.
18251 In this case, you need to run a recent GNU Emacs, which automatically
18252 starts the debugger that puts you in the @file{*Backtrace*} buffer; or
18253 else, you need to start the debugger manually as described below.
18255 Read the @file{*Backtrace*} buffer from the bottom up; it tells you
18256 what Emacs did that led to the error. Emacs made an interactive call
18257 to @kbd{C-x C-e} (@code{eval-last-sexp}), which led to the evaluation
18258 of the @code{triangle-bugged} expression. Each line above tells you
18259 what the Lisp interpreter evaluated next.
18262 The third line from the top of the buffer is
18265 (setq number (1= number))
18269 Emacs tried to evaluate this expression; in order to do so, it tried
18270 to evaluate the inner expression shown on the second line from the
18279 This is where the error occurred; as the top line says:
18282 Debugger entered--Lisp error: (void-function 1=)
18286 You can correct the mistake, re-evaluate the function definition, and
18287 then run your test again.
18289 @node debug-on-entry
18290 @section @code{debug-on-entry}
18291 @findex debug-on-entry
18293 A recent GNU Emacs starts the debugger automatically when your
18294 function has an error.
18297 GNU Emacs version 20 and before did not; it simply
18298 presented you with an error message. You had to start the debugger
18302 Incidentally, you can start the debugger manually for all versions of
18303 Emacs; the advantage is that the debugger runs even if you do not have
18304 a bug in your code. Sometimes your code will be free of bugs!
18306 You can enter the debugger when you call the function by calling
18307 @code{debug-on-entry}.
18314 M-x debug-on-entry RET triangle-bugged RET
18319 Now, evaluate the following:
18322 (triangle-bugged 5)
18326 All versions of Emacs will create a @file{*Backtrace*} buffer and tell
18327 you that it is beginning to evaluate the @code{triangle-bugged}
18332 ---------- Buffer: *Backtrace* ----------
18333 Debugger entered--entering a function:
18334 * triangle-bugged(5)
18335 eval((triangle-bugged 5))
18338 eval-last-sexp-1(nil)
18339 eval-last-sexp(nil)
18340 call-interactively(eval-last-sexp)
18341 ---------- Buffer: *Backtrace* ----------
18345 In the @file{*Backtrace*} buffer, type @kbd{d}. Emacs will evaluate
18346 the first expression in @code{triangle-bugged}; the buffer will look
18351 ---------- Buffer: *Backtrace* ----------
18352 Debugger entered--beginning evaluation of function call form:
18353 * (let ((total 0)) (while (> number 0) (setq total ...)
18354 (setq number ...)) total)
18355 * triangle-bugged(5)
18356 eval((triangle-bugged 5))
18359 eval-last-sexp-1(nil)
18360 eval-last-sexp(nil)
18361 call-interactively(eval-last-sexp)
18362 ---------- Buffer: *Backtrace* ----------
18367 Now, type @kbd{d} again, eight times, slowly. Each time you type
18368 @kbd{d}, Emacs will evaluate another expression in the function
18372 Eventually, the buffer will look like this:
18376 ---------- Buffer: *Backtrace* ----------
18377 Debugger entered--beginning evaluation of function call form:
18378 * (setq number (1= number))
18379 * (while (> number 0) (setq total (+ total number))
18380 (setq number (1= number)))
18383 * (let ((total 0)) (while (> number 0) (setq total ...)
18384 (setq number ...)) total)
18385 * triangle-bugged(5)
18386 eval((triangle-bugged 5))
18389 eval-last-sexp-1(nil)
18390 eval-last-sexp(nil)
18391 call-interactively(eval-last-sexp)
18392 ---------- Buffer: *Backtrace* ----------
18398 Finally, after you type @kbd{d} two more times, Emacs will reach the
18399 error, and the top two lines of the @file{*Backtrace*} buffer will look
18404 ---------- Buffer: *Backtrace* ----------
18405 Debugger entered--Lisp error: (void-function 1=)
18408 ---------- Buffer: *Backtrace* ----------
18412 By typing @kbd{d}, you were able to step through the function.
18414 You can quit a @file{*Backtrace*} buffer by typing @kbd{q} in it; this
18415 quits the trace, but does not cancel @code{debug-on-entry}.
18417 @findex cancel-debug-on-entry
18418 To cancel the effect of @code{debug-on-entry}, call
18419 @code{cancel-debug-on-entry} and the name of the function, like this:
18422 M-x cancel-debug-on-entry RET triangle-bugged RET
18426 (If you are reading this in Info, cancel @code{debug-on-entry} now.)
18428 @node debug-on-quit
18429 @section @code{debug-on-quit} and @code{(debug)}
18431 In addition to setting @code{debug-on-error} or calling @code{debug-on-entry},
18432 there are two other ways to start @code{debug}.
18434 @findex debug-on-quit
18435 You can start @code{debug} whenever you type @kbd{C-g}
18436 (@code{keyboard-quit}) by setting the variable @code{debug-on-quit} to
18437 @code{t}. This is useful for debugging infinite loops.
18440 @cindex @code{(debug)} in code
18441 Or, you can insert a line that says @code{(debug)} into your code
18442 where you want the debugger to start, like this:
18446 (defun triangle-bugged (number)
18447 "Return sum of numbers 1 through NUMBER inclusive."
18449 (while (> number 0)
18450 (setq total (+ total number))
18451 (debug) ; @r{Start debugger.}
18452 (setq number (1= number))) ; @r{Error here.}
18457 The @code{debug} function is described in detail in @ref{Debugger, ,
18458 The Lisp Debugger, elisp, The GNU Emacs Lisp Reference Manual}.
18461 @section The @code{edebug} Source Level Debugger
18462 @cindex Source level debugger
18465 Edebug is a source level debugger. Edebug normally displays the
18466 source of the code you are debugging, with an arrow at the left that
18467 shows which line you are currently executing.
18469 You can walk through the execution of a function, line by line, or run
18470 quickly until reaching a @dfn{breakpoint} where execution stops.
18472 Edebug is described in @ref{Edebug, , , elisp, The GNU Emacs
18473 Lisp Reference Manual}.
18476 Here is a bugged function definition for @code{triangle-recursively}.
18477 @xref{Recursive triangle function, , Recursion in place of a counter},
18478 for a review of it.
18482 (defun triangle-recursively-bugged (number)
18483 "Return sum of numbers 1 through NUMBER inclusive.
18488 (triangle-recursively-bugged
18489 (1= number))))) ; @r{Error here.}
18494 Normally, you would install this definition by positioning your cursor
18495 after the function's closing parenthesis and typing @kbd{C-x C-e}
18496 (@code{eval-last-sexp}) or else by positioning your cursor within the
18497 definition and typing @kbd{C-M-x} (@code{eval-defun}). (By default,
18498 the @code{eval-defun} command works only in Emacs Lisp mode or in Lisp
18502 However, to prepare this function definition for Edebug, you must
18503 first @dfn{instrument} the code using a different command. You can do
18504 this by positioning your cursor within or just after the definition
18508 M-x edebug-defun RET
18512 This will cause Emacs to load Edebug automatically if it is not
18513 already loaded, and properly instrument the function.
18515 After instrumenting the function, place your cursor after the
18516 following expression and type @kbd{C-x C-e} (@code{eval-last-sexp}):
18519 (triangle-recursively-bugged 3)
18523 You will be jumped back to the source for
18524 @code{triangle-recursively-bugged} and the cursor positioned at the
18525 beginning of the @code{if} line of the function. Also, you will see
18526 an arrowhead at the left hand side of that line. The arrowhead marks
18527 the line where the function is executing. (In the following examples,
18528 we show the arrowhead with @samp{=>}; in a windowing system, you may
18529 see the arrowhead as a solid triangle in the window fringe.)
18532 =>@point{}(if (= number 1)
18537 In the example, the location of point is displayed with a star,
18538 @samp{@point{}} (in Info, it is displayed as @samp{-!-}).
18541 In the example, the location of point is displayed as @samp{@point{}}
18542 (in a printed book, it is displayed with a five pointed star).
18545 If you now press @key{SPC}, point will move to the next expression to
18546 be executed; the line will look like this:
18549 =>(if @point{}(= number 1)
18553 As you continue to press @key{SPC}, point will move from expression to
18554 expression. At the same time, whenever an expression returns a value,
18555 that value will be displayed in the echo area. For example, after you
18556 move point past @code{number}, you will see the following:
18559 Result: 3 (#o3, #x3, ?\C-c)
18563 This means the value of @code{number} is 3, which is octal three,
18564 hexadecimal three, and @sc{ascii} Control-C (the third letter of the
18565 alphabet, in case you need to know this information).
18567 You can continue moving through the code until you reach the line with
18568 the error. Before evaluation, that line looks like this:
18571 => @point{}(1= number))))) ; @r{Error here.}
18576 When you press @key{SPC} once again, you will produce an error message
18580 Symbol's function definition is void:@: 1=
18586 Press @kbd{q} to quit Edebug.
18588 To remove instrumentation from a function definition, simply
18589 re-evaluate it with a command that does not instrument it.
18590 For example, you could place your cursor after the definition's
18591 closing parenthesis and type @kbd{C-x C-e}.
18593 Edebug does a great deal more than walk with you through a function.
18594 You can set it so it races through on its own, stopping only at an
18595 error or at specified stopping points; you can cause it to display the
18596 changing values of various expressions; you can find out how many
18597 times a function is called, and more.
18599 Edebug is described in @ref{Edebug, , , elisp, The GNU Emacs
18600 Lisp Reference Manual}.
18603 @node Debugging Exercises
18604 @section Debugging Exercises
18608 Install the @code{@value{COUNT-WORDS}} function and then cause it to
18609 enter the built-in debugger when you call it. Run the command on a
18610 region containing two words. You will need to press @kbd{d} a
18611 remarkable number of times. On your system, is a hook called after
18612 the command finishes? (For information on hooks, see @ref{Command
18613 Overview, , Command Loop Overview, elisp, The GNU Emacs Lisp Reference
18617 Copy @code{@value{COUNT-WORDS}} into the @file{*scratch*} buffer,
18618 instrument the function for Edebug, and walk through its execution.
18619 The function does not need to have a bug, although you can introduce
18620 one if you wish. If the function lacks a bug, the walk-through
18621 completes without problems.
18624 While running Edebug, type @kbd{?} to see a list of all the Edebug commands.
18625 (The @code{global-edebug-prefix} is usually @kbd{C-x X}, i.e.,
18626 @kbd{@key{CTRL}-x} followed by an upper case @kbd{X}; use this prefix
18627 for commands made outside of the Edebug debugging buffer.)
18630 In the Edebug debugging buffer, use the @kbd{p}
18631 (@code{edebug-bounce-point}) command to see where in the region the
18632 @code{@value{COUNT-WORDS}} is working.
18635 Move point to some spot further down the function and then type the
18636 @kbd{h} (@code{edebug-goto-here}) command to jump to that location.
18639 Use the @kbd{t} (@code{edebug-trace-mode}) command to cause Edebug to
18640 walk through the function on its own; use an upper case @kbd{T} for
18641 @code{edebug-Trace-fast-mode}.
18644 Set a breakpoint, then run Edebug in Trace mode until it reaches the
18649 @chapter Conclusion
18651 We have now reached the end of this Introduction. You have now
18652 learned enough about programming in Emacs Lisp to set values, to write
18653 simple @file{.emacs} files for yourself and your friends, and write
18654 simple customizations and extensions to Emacs.
18656 This is a place to stop. Or, if you wish, you can now go onward, and
18659 You have learned some of the basic nuts and bolts of programming. But
18660 only some. There are a great many more brackets and hinges that are
18661 easy to use that we have not touched.
18663 A path you can follow right now lies among the sources to GNU Emacs
18666 @cite{The GNU Emacs Lisp Reference Manual}.
18669 @ref{Top, , The GNU Emacs Lisp Reference Manual, elisp, The GNU
18670 Emacs Lisp Reference Manual}.
18673 The Emacs Lisp sources are an adventure. When you read the sources and
18674 come across a function or expression that is unfamiliar, you need to
18675 figure out or find out what it does.
18677 Go to the Reference Manual. It is a thorough, complete, and fairly
18678 easy-to-read description of Emacs Lisp. It is written not only for
18679 experts, but for people who know what you know. (The @cite{Reference
18680 Manual} comes with the standard GNU Emacs distribution. Like this
18681 introduction, it comes as a Texinfo source file, so you can read it
18682 on your computer and as a typeset, printed book.)
18684 Go to the other built-in help that is part of GNU Emacs: the built-in
18685 documentation for all functions and variables, and @code{find-tag},
18686 the program that takes you to sources.
18688 Here is an example of how I explore the sources. Because of its name,
18689 @file{simple.el} is the file I looked at first, a long time ago. As
18690 it happens some of the functions in @file{simple.el} are complicated,
18691 or at least look complicated at first sight. The @code{open-line}
18692 function, for example, looks complicated.
18694 You may want to walk through this function slowly, as we did with the
18695 @code{forward-sentence} function. (@xref{forward-sentence, The
18696 @code{forward-sentence} function}.) Or you may want to skip that
18697 function and look at another, such as @code{split-line}. You don't
18698 need to read all the functions. According to
18699 @code{count-words-in-defun}, the @code{split-line} function contains
18700 102 words and symbols.
18702 Even though it is short, @code{split-line} contains expressions
18703 we have not studied: @code{skip-chars-forward}, @code{indent-to},
18704 @code{current-column} and @code{insert-and-inherit}.
18706 Consider the @code{skip-chars-forward} function.
18707 In GNU Emacs, you can find out more about @code{skip-chars-forward} by
18708 typing @kbd{C-h f} (@code{describe-function}) and the name of the
18709 function. This gives you the function documentation.
18711 You may be able to guess what is done by a well named function such as
18712 @code{indent-to}; or you can look it up, too. Incidentally, the
18713 @code{describe-function} function itself is in @file{help.el}; it is
18714 one of those long, but decipherable functions. You can look up
18715 @code{describe-function} using the @kbd{C-h f} command!
18717 In this instance, since the code is Lisp, the @file{*Help*} buffer
18718 contains the name of the library containing the function's source.
18719 You can put point over the name of the library and press the RET key,
18720 which in this situation is bound to @code{help-follow}, and be taken
18721 directly to the source, in the same way as @kbd{M-.}
18724 The definition for @code{describe-function} illustrates how to
18725 customize the @code{interactive} expression without using the standard
18726 character codes; and it shows how to create a temporary buffer.
18728 (The @code{indent-to} function is written in C rather than Emacs Lisp;
18729 it is a built-in function. @code{help-follow} takes you to its
18730 source as does @code{find-tag}, when properly set up.)
18732 You can look at a function's source using @code{find-tag}, which is
18733 bound to @kbd{M-.} Finally, you can find out what the Reference
18734 Manual has to say by visiting the manual in Info, and typing @kbd{i}
18735 (@code{Info-index}) and the name of the function, or by looking up the
18736 function in the index to a printed copy of the manual.
18738 Similarly, you can find out what is meant by
18739 @code{insert-and-inherit}.
18741 Other interesting source files include @file{paragraphs.el},
18742 @file{loaddefs.el}, and @file{loadup.el}. The @file{paragraphs.el}
18743 file includes short, easily understood functions as well as longer
18744 ones. The @file{loaddefs.el} file contains the many standard
18745 autoloads and many keymaps. I have never looked at it all; only at
18746 parts. @file{loadup.el} is the file that loads the standard parts of
18747 Emacs; it tells you a great deal about how Emacs is built.
18748 (@xref{Building Emacs, , Building Emacs, elisp, The GNU Emacs Lisp
18749 Reference Manual}, for more about building.)
18751 As I said, you have learned some nuts and bolts; however, and very
18752 importantly, we have hardly touched major aspects of programming; I
18753 have said nothing about how to sort information, except to use the
18754 predefined @code{sort} function; I have said nothing about how to store
18755 information, except to use variables and lists; I have said nothing
18756 about how to write programs that write programs. These are topics for
18757 another, and different kind of book, a different kind of learning.
18759 What you have done is learn enough for much practical work with GNU
18760 Emacs. What you have done is get started. This is the end of a
18763 @c ================ Appendix ================
18766 @appendix The @code{the-the} Function
18768 @cindex Duplicated words function
18769 @cindex Words, duplicated
18771 Sometimes when you you write text, you duplicate words---as with ``you
18772 you'' near the beginning of this sentence. I find that most
18773 frequently, I duplicate ``the''; hence, I call the function for
18774 detecting duplicated words, @code{the-the}.
18777 As a first step, you could use the following regular expression to
18778 search for duplicates:
18781 \\(\\w+[ \t\n]+\\)\\1
18785 This regexp matches one or more word-constituent characters followed
18786 by one or more spaces, tabs, or newlines. However, it does not detect
18787 duplicated words on different lines, since the ending of the first
18788 word, the end of the line, is different from the ending of the second
18789 word, a space. (For more information about regular expressions, see
18790 @ref{Regexp Search, , Regular Expression Searches}, as well as
18791 @ref{Regexps, , Syntax of Regular Expressions, emacs, The GNU Emacs
18792 Manual}, and @ref{Regular Expressions, , Regular Expressions, elisp,
18793 The GNU Emacs Lisp Reference Manual}.)
18795 You might try searching just for duplicated word-constituent
18796 characters but that does not work since the pattern detects doubles
18797 such as the two occurrences of ``th'' in ``with the''.
18799 Another possible regexp searches for word-constituent characters
18800 followed by non-word-constituent characters, reduplicated. Here,
18801 @w{@samp{\\w+}} matches one or more word-constituent characters and
18802 @w{@samp{\\W*}} matches zero or more non-word-constituent characters.
18805 \\(\\(\\w+\\)\\W*\\)\\1
18811 Here is the pattern that I use. It is not perfect, but good enough.
18812 @w{@samp{\\b}} matches the empty string, provided it is at the beginning
18813 or end of a word; @w{@samp{[^@@ \n\t]+}} matches one or more occurrences of
18814 any characters that are @emph{not} an @@-sign, space, newline, or tab.
18817 \\b\\([^@@ \n\t]+\\)[ \n\t]+\\1\\b
18820 One can write more complicated expressions, but I found that this
18821 expression is good enough, so I use it.
18823 Here is the @code{the-the} function, as I include it in my
18824 @file{.emacs} file, along with a handy global key binding:
18829 "Search forward for for a duplicated word."
18831 (message "Searching for for duplicated words ...")
18835 ;; This regexp is not perfect
18836 ;; but is fairly good over all:
18837 (if (re-search-forward
18838 "\\b\\([^@@ \n\t]+\\)[ \n\t]+\\1\\b" nil 'move)
18839 (message "Found duplicated word.")
18840 (message "End of buffer")))
18844 ;; Bind 'the-the' to C-c \
18845 (global-set-key "\C-c\\" 'the-the)
18854 one two two three four five
18859 You can substitute the other regular expressions shown above in the
18860 function definition and try each of them on this list.
18863 @appendix Handling the Kill Ring
18864 @cindex Kill ring handling
18865 @cindex Handling the kill ring
18866 @cindex Ring, making a list like a
18868 The kill ring is a list that is transformed into a ring by the
18869 workings of the @code{current-kill} function. The @code{yank} and
18870 @code{yank-pop} commands use the @code{current-kill} function.
18872 This appendix describes the @code{current-kill} function as well as
18873 both the @code{yank} and the @code{yank-pop} commands, but first,
18874 consider the workings of the kill ring.
18877 * What the Kill Ring Does::
18879 * yank:: Paste a copy of a clipped element.
18880 * yank-pop:: Insert element pointed to.
18885 @node What the Kill Ring Does
18886 @unnumberedsec What the Kill Ring Does
18890 The kill ring has a default maximum length of sixty items; this number
18891 is too large for an explanation. Instead, set it to four. Please
18892 evaluate the following:
18896 (setq old-kill-ring-max kill-ring-max)
18897 (setq kill-ring-max 4)
18902 Then, please copy each line of the following indented example into the
18903 kill ring. You may kill each line with @kbd{C-k} or mark it and copy
18907 (In a read-only buffer, such as the @file{*info*} buffer, the kill
18908 command, @kbd{C-k} (@code{kill-line}), will not remove the text,
18909 merely copy it to the kill ring. However, your machine may beep at
18910 you. Alternatively, for silence, you may copy the region of each line
18911 with the @kbd{M-w} (@code{kill-ring-save}) command. You must mark
18912 each line for this command to succeed, but it does not matter at which
18913 end you put point or mark.)
18917 Please invoke the calls in order, so that five elements attempt to
18918 fill the kill ring:
18923 second piece of text
18925 fourth line of text
18932 Then find the value of @code{kill-ring} by evaluating
18944 ("fifth bit of text" "fourth line of text"
18945 "third line" "second piece of text")
18950 The first element, @samp{first some text}, was dropped.
18953 To return to the old value for the length of the kill ring, evaluate:
18956 (setq kill-ring-max old-kill-ring-max)
18960 @appendixsec The @code{current-kill} Function
18961 @findex current-kill
18963 The @code{current-kill} function changes the element in the kill ring
18964 to which @code{kill-ring-yank-pointer} points. (Also, the
18965 @code{kill-new} function sets @code{kill-ring-yank-pointer} to point
18966 to the latest element of the kill ring. The @code{kill-new}
18967 function is used directly or indirectly by @code{kill-append},
18968 @code{copy-region-as-kill}, @code{kill-ring-save}, @code{kill-line},
18969 and @code{kill-region}.)
18972 * Code for current-kill::
18973 * Understanding current-kill::
18977 @node Code for current-kill
18978 @unnumberedsubsec The code for @code{current-kill}
18983 The @code{current-kill} function is used by @code{yank} and by
18984 @code{yank-pop}. Here is the code for @code{current-kill}:
18988 (defun current-kill (n &optional do-not-move)
18989 "Rotate the yanking point by N places, and then return that kill.
18990 If N is zero and `interprogram-paste-function' is set to a
18991 function that returns a string or a list of strings, and if that
18992 function doesn't return nil, then that string (or list) is added
18993 to the front of the kill ring and the string (or first string in
18994 the list) is returned as the latest kill.
18997 If N is not zero, and if `yank-pop-change-selection' is
18998 non-nil, use `interprogram-cut-function' to transfer the
18999 kill at the new yank point into the window system selection.
19002 If optional arg DO-NOT-MOVE is non-nil, then don't actually
19003 move the yanking point; just return the Nth kill forward."
19005 (let ((interprogram-paste (and (= n 0)
19006 interprogram-paste-function
19007 (funcall interprogram-paste-function))))
19010 (if interprogram-paste
19012 ;; Disable the interprogram cut function when we add the new
19013 ;; text to the kill ring, so Emacs doesn't try to own the
19014 ;; selection, with identical text.
19015 (let ((interprogram-cut-function nil))
19016 (if (listp interprogram-paste)
19017 (mapc 'kill-new (nreverse interprogram-paste))
19018 (kill-new interprogram-paste)))
19022 (or kill-ring (error "Kill ring is empty"))
19023 (let ((ARGth-kill-element
19024 (nthcdr (mod (- n (length kill-ring-yank-pointer))
19025 (length kill-ring))
19027 (unless do-not-move
19028 (setq kill-ring-yank-pointer ARGth-kill-element)
19029 (when (and yank-pop-change-selection
19031 interprogram-cut-function)
19032 (funcall interprogram-cut-function (car ARGth-kill-element))))
19033 (car ARGth-kill-element)))))
19037 Remember also that the @code{kill-new} function sets
19038 @code{kill-ring-yank-pointer} to the latest element of the kill
19039 ring, which means that all the functions that call it set the value
19040 indirectly: @code{kill-append}, @code{copy-region-as-kill},
19041 @code{kill-ring-save}, @code{kill-line}, and @code{kill-region}.
19044 Here is the line in @code{kill-new}, which is explained in
19045 @ref{kill-new function, , The @code{kill-new} function}.
19048 (setq kill-ring-yank-pointer kill-ring)
19052 @node Understanding current-kill
19053 @unnumberedsubsec @code{current-kill} in Outline
19056 The @code{current-kill} function looks complex, but as usual, it can
19057 be understood by taking it apart piece by piece. First look at it in
19062 (defun current-kill (n &optional do-not-move)
19063 "Rotate the yanking point by N places, and then return that kill."
19069 This function takes two arguments, one of which is optional. It has a
19070 documentation string. It is @emph{not} interactive.
19073 * Body of current-kill::
19074 * Digression concerning error:: How to mislead humans, but not computers.
19075 * Determining the Element::
19079 @node Body of current-kill
19080 @unnumberedsubsubsec The Body of @code{current-kill}
19083 The body of the function definition is a @code{let} expression, which
19084 itself has a body as well as a @var{varlist}.
19086 The @code{let} expression declares a variable that will be only usable
19087 within the bounds of this function. This variable is called
19088 @code{interprogram-paste} and is for copying to another program. It
19089 is not for copying within this instance of GNU Emacs. Most window
19090 systems provide a facility for interprogram pasting. Sadly, that
19091 facility usually provides only for the last element. Most windowing
19092 systems have not adopted a ring of many possibilities, even though
19093 Emacs has provided it for decades.
19095 The @code{if} expression has two parts, one if there exists
19096 @code{interprogram-paste} and one if not.
19099 Let us consider the else-part of the @code{current-kill}
19100 function. (The then-part uses the @code{kill-new} function, which
19101 we have already described. @xref{kill-new function, , The
19102 @code{kill-new} function}.)
19106 (or kill-ring (error "Kill ring is empty"))
19107 (let ((ARGth-kill-element
19108 (nthcdr (mod (- n (length kill-ring-yank-pointer))
19109 (length kill-ring))
19112 (setq kill-ring-yank-pointer ARGth-kill-element))
19113 (car ARGth-kill-element))
19118 The code first checks whether the kill ring has content; otherwise it
19122 Note that the @code{or} expression is very similar to testing length
19129 (if (zerop (length kill-ring)) ; @r{if-part}
19130 (error "Kill ring is empty")) ; @r{then-part}
19136 If there is not anything in the kill ring, its length must be zero and
19137 an error message sent to the user: @samp{Kill ring is empty}. The
19138 @code{current-kill} function uses an @code{or} expression which is
19139 simpler. But an @code{if} expression reminds us what goes on.
19141 This @code{if} expression uses the function @code{zerop} which returns
19142 true if the value it is testing is zero. When @code{zerop} tests
19143 true, the then-part of the @code{if} is evaluated. The then-part is a
19144 list starting with the function @code{error}, which is a function that
19145 is similar to the @code{message} function
19146 (@pxref{message, , The @code{message} Function}) in that
19147 it prints a one-line message in the echo area. However, in addition
19148 to printing a message, @code{error} also stops evaluation of the
19149 function within which it is embedded. This means that the rest of the
19150 function will not be evaluated if the length of the kill ring is zero.
19152 Then the @code{current-kill} function selects the element to return.
19153 The selection depends on the number of places that @code{current-kill}
19154 rotates and on where @code{kill-ring-yank-pointer} points.
19156 Next, either the optional @code{do-not-move} argument is true or the
19157 current value of @code{kill-ring-yank-pointer} is set to point to the
19158 list. Finally, another expression returns the first element of the
19159 list even if the @code{do-not-move} argument is true.
19162 @node Digression concerning error
19163 @unnumberedsubsubsec Digression about the word ``error''
19166 In my opinion, it is slightly misleading, at least to humans, to use
19167 the term ``error'' as the name of the @code{error} function. A better
19168 term would be ``cancel''. Strictly speaking, of course, you cannot
19169 point to, much less rotate a pointer to a list that has no length, so
19170 from the point of view of the computer, the word ``error'' is correct.
19171 But a human expects to attempt this sort of thing, if only to find out
19172 whether the kill ring is full or empty. This is an act of
19175 From the human point of view, the act of exploration and discovery is
19176 not necessarily an error, and therefore should not be labeled as one,
19177 even in the bowels of a computer. As it is, the code in Emacs implies
19178 that a human who is acting virtuously, by exploring his or her
19179 environment, is making an error. This is bad. Even though the computer
19180 takes the same steps as it does when there is an error, a term such as
19181 ``cancel'' would have a clearer connotation.
19184 @node Determining the Element
19185 @unnumberedsubsubsec Determining the Element
19188 Among other actions, the else-part of the @code{if} expression sets
19189 the value of @code{kill-ring-yank-pointer} to
19190 @code{ARGth-kill-element} when the kill ring has something in it and
19191 the value of @code{do-not-move} is @code{nil}.
19194 The code looks like this:
19198 (nthcdr (mod (- n (length kill-ring-yank-pointer))
19199 (length kill-ring))
19204 This needs some examination. Unless it is not supposed to move the
19205 pointer, the @code{current-kill} function changes where
19206 @code{kill-ring-yank-pointer} points.
19208 @w{@code{(setq kill-ring-yank-pointer ARGth-kill-element))}}
19209 expression does. Also, clearly, @code{ARGth-kill-element} is being
19210 set to be equal to some @sc{cdr} of the kill ring, using the
19211 @code{nthcdr} function that is described in an earlier section.
19212 (@xref{copy-region-as-kill}.) How does it do this?
19214 As we have seen before (@pxref{nthcdr}), the @code{nthcdr} function
19215 works by repeatedly taking the @sc{cdr} of a list---it takes the
19216 @sc{cdr} of the @sc{cdr} of the @sc{cdr} @dots{}
19219 The two following expressions produce the same result:
19223 (setq kill-ring-yank-pointer (cdr kill-ring))
19225 (setq kill-ring-yank-pointer (nthcdr 1 kill-ring))
19229 However, the @code{nthcdr} expression is more complicated. It uses
19230 the @code{mod} function to determine which @sc{cdr} to select.
19232 (You will remember to look at inner functions first; indeed, we will
19233 have to go inside the @code{mod}.)
19235 The @code{mod} function returns the value of its first argument modulo
19236 the second; that is to say, it returns the remainder after dividing
19237 the first argument by the second. The value returned has the same
19238 sign as the second argument.
19246 @result{} 0 ;; @r{because there is no remainder}
19253 In this case, the first argument is often smaller than the second.
19265 We can guess what the @code{-} function does. It is like @code{+} but
19266 subtracts instead of adds; the @code{-} function subtracts its second
19267 argument from its first. Also, we already know what the @code{length}
19268 function does (@pxref{length}). It returns the length of a list.
19270 And @code{n} is the name of the required argument to the
19271 @code{current-kill} function.
19274 So when the first argument to @code{nthcdr} is zero, the @code{nthcdr}
19275 expression returns the whole list, as you can see by evaluating the
19280 ;; kill-ring-yank-pointer @r{and} kill-ring @r{have a length of four}
19281 ;; @r{and} (mod (- 0 4) 4) @result{} 0
19282 (nthcdr (mod (- 0 4) 4)
19283 '("fourth line of text"
19285 "second piece of text"
19286 "first some text"))
19291 When the first argument to the @code{current-kill} function is one,
19292 the @code{nthcdr} expression returns the list without its first
19297 (nthcdr (mod (- 1 4) 4)
19298 '("fourth line of text"
19300 "second piece of text"
19301 "first some text"))
19305 @cindex @samp{global variable} defined
19306 @cindex @samp{variable, global}, defined
19307 Incidentally, both @code{kill-ring} and @code{kill-ring-yank-pointer}
19308 are @dfn{global variables}. That means that any expression in Emacs
19309 Lisp can access them. They are not like the local variables set by
19310 @code{let} or like the symbols in an argument list.
19311 Local variables can only be accessed
19312 within the @code{let} that defines them or the function that specifies
19313 them in an argument list (and within expressions called by them).
19316 @c texi2dvi fails when the name of the section is within ifnottex ...
19317 (@xref{Prevent confusion, , @code{let} Prevents Confusion}, and
19318 @ref{defun, , The @code{defun} Macro}.)
19322 @appendixsec @code{yank}
19325 After learning about @code{current-kill}, the code for the
19326 @code{yank} function is almost easy.
19328 The @code{yank} function does not use the
19329 @code{kill-ring-yank-pointer} variable directly. It calls
19330 @code{insert-for-yank} which calls @code{current-kill} which sets the
19331 @code{kill-ring-yank-pointer} variable.
19334 The code looks like this:
19339 (defun yank (&optional arg)
19340 "Reinsert (\"paste\") the last stretch of killed text.
19341 More precisely, reinsert the stretch of killed text most recently
19342 killed OR yanked. Put point at end, and set mark at beginning.
19343 With just \\[universal-argument] as argument, same but put point at beginning (and mark at end).
19344 With argument N, reinsert the Nth most recently killed stretch of killed
19347 When this command inserts killed text into the buffer, it honors
19348 `yank-excluded-properties' and `yank-handler' as described in the
19349 doc string for `insert-for-yank-1', which see.
19351 See also the command `yank-pop' (\\[yank-pop])."
19355 (setq yank-window-start (window-start))
19356 ;; If we don't get all the way thru, make last-command indicate that
19357 ;; for the following command.
19358 (setq this-command t)
19359 (push-mark (point))
19362 (insert-for-yank (current-kill (cond
19367 ;; This is like exchange-point-and-mark, but doesn't activate the mark.
19368 ;; It is cleaner to avoid activation, even though the command
19369 ;; loop would deactivate the mark because we inserted text.
19370 (goto-char (prog1 (mark t)
19371 (set-marker (mark-marker) (point) (current-buffer)))))
19374 ;; If we do get all the way thru, make this-command indicate that.
19375 (if (eq this-command t)
19376 (setq this-command 'yank))
19381 The key expression is @code{insert-for-yank}, which inserts the string
19382 returned by @code{current-kill}, but removes some text properties from
19385 However, before getting to that expression, the function sets the value
19386 of @code{yank-window-start} to the position returned by the
19387 @code{(window-start)} expression, the position at which the display
19388 currently starts. The @code{yank} function also sets
19389 @code{this-command} and pushes the mark.
19391 After it yanks the appropriate element, if the optional argument is a
19392 @sc{cons} rather than a number or nothing, it puts point at beginning
19393 of the yanked text and mark at its end.
19395 (The @code{prog1} function is like @code{progn} but returns the value
19396 of its first argument rather than the value of its last argument. Its
19397 first argument is forced to return the buffer's mark as an integer.
19398 You can see the documentation for these functions by placing point
19399 over them in this buffer and then typing @kbd{C-h f}
19400 (@code{describe-function}) followed by a @kbd{RET}; the default is the
19403 The last part of the function tells what to do when it succeeds.
19406 @appendixsec @code{yank-pop}
19409 After understanding @code{yank} and @code{current-kill}, you know how
19410 to approach the @code{yank-pop} function. Leaving out the
19411 documentation to save space, it looks like this:
19416 (defun yank-pop (&optional arg)
19419 (if (not (eq last-command 'yank))
19420 (error "Previous command was not a yank"))
19423 (setq this-command 'yank)
19424 (unless arg (setq arg 1))
19425 (let ((inhibit-read-only t)
19426 (before (< (point) (mark t))))
19430 (funcall (or yank-undo-function 'delete-region) (point) (mark t))
19431 (funcall (or yank-undo-function 'delete-region) (mark t) (point)))
19432 (setq yank-undo-function nil)
19435 (set-marker (mark-marker) (point) (current-buffer))
19436 (insert-for-yank (current-kill arg))
19437 ;; Set the window start back where it was in the yank command,
19439 (set-window-start (selected-window) yank-window-start t)
19443 ;; This is like exchange-point-and-mark,
19444 ;; but doesn't activate the mark.
19445 ;; It is cleaner to avoid activation, even though the command
19446 ;; loop would deactivate the mark because we inserted text.
19447 (goto-char (prog1 (mark t)
19448 (set-marker (mark-marker)
19450 (current-buffer))))))
19455 The function is interactive with a small @samp{p} so the prefix
19456 argument is processed and passed to the function. The command can
19457 only be used after a previous yank; otherwise an error message is
19458 sent. This check uses the variable @code{last-command} which is set
19459 by @code{yank} and is discussed elsewhere.
19460 (@xref{copy-region-as-kill}.)
19462 The @code{let} clause sets the variable @code{before} to true or false
19463 depending whether point is before or after mark and then the region
19464 between point and mark is deleted. This is the region that was just
19465 inserted by the previous yank and it is this text that will be
19468 @code{funcall} calls its first argument as a function, passing
19469 remaining arguments to it. The first argument is whatever the
19470 @code{or} expression returns. The two remaining arguments are the
19471 positions of point and mark set by the preceding @code{yank} command.
19473 There is more, but that is the hardest part.
19476 @appendixsec The @file{ring.el} File
19477 @cindex @file{ring.el} file
19479 Interestingly, GNU Emacs posses a file called @file{ring.el} that
19480 provides many of the features we just discussed. But functions such
19481 as @code{kill-ring-yank-pointer} do not use this library, possibly
19482 because they were written earlier.
19485 @appendix A Graph with Labeled Axes
19487 Printed axes help you understand a graph. They convey scale. In an
19488 earlier chapter (@pxref{Readying a Graph, , Readying a Graph}), we
19489 wrote the code to print the body of a graph. Here we write the code
19490 for printing and labeling vertical and horizontal axes, along with the
19494 * Labeled Example::
19495 * print-graph Varlist:: @code{let} expression in @code{print-graph}.
19496 * print-Y-axis:: Print a label for the vertical axis.
19497 * print-X-axis:: Print a horizontal label.
19498 * Print Whole Graph:: The function to print a complete graph.
19502 @node Labeled Example
19503 @unnumberedsec Labeled Example Graph
19506 Since insertions fill a buffer to the right and below point, the new
19507 graph printing function should first print the Y or vertical axis,
19508 then the body of the graph, and finally the X or horizontal axis.
19509 This sequence lays out for us the contents of the function:
19519 Print body of graph.
19526 Here is an example of how a finished graph should look:
19539 1 - ****************
19546 In this graph, both the vertical and the horizontal axes are labeled
19547 with numbers. However, in some graphs, the horizontal axis is time
19548 and would be better labeled with months, like this:
19562 Indeed, with a little thought, we can easily come up with a variety of
19563 vertical and horizontal labeling schemes. Our task could become
19564 complicated. But complications breed confusion. Rather than permit
19565 this, it is better choose a simple labeling scheme for our first
19566 effort, and to modify or replace it later.
19569 These considerations suggest the following outline for the
19570 @code{print-graph} function:
19574 (defun print-graph (numbers-list)
19575 "@var{documentation}@dots{}"
19576 (let ((height @dots{}
19580 (print-Y-axis height @dots{} )
19581 (graph-body-print numbers-list)
19582 (print-X-axis @dots{} )))
19586 We can work on each part of the @code{print-graph} function definition
19589 @node print-graph Varlist
19590 @appendixsec The @code{print-graph} Varlist
19591 @cindex @code{print-graph} varlist
19593 In writing the @code{print-graph} function, the first task is to write
19594 the varlist in the @code{let} expression. (We will leave aside for the
19595 moment any thoughts about making the function interactive or about the
19596 contents of its documentation string.)
19598 The varlist should set several values. Clearly, the top of the label
19599 for the vertical axis must be at least the height of the graph, which
19600 means that we must obtain this information here. Note that the
19601 @code{print-graph-body} function also requires this information. There
19602 is no reason to calculate the height of the graph in two different
19603 places, so we should change @code{print-graph-body} from the way we
19604 defined it earlier to take advantage of the calculation.
19606 Similarly, both the function for printing the X axis labels and the
19607 @code{print-graph-body} function need to learn the value of the width of
19608 each symbol. We can perform the calculation here and change the
19609 definition for @code{print-graph-body} from the way we defined it in the
19612 The length of the label for the horizontal axis must be at least as long
19613 as the graph. However, this information is used only in the function
19614 that prints the horizontal axis, so it does not need to be calculated here.
19616 These thoughts lead us directly to the following form for the varlist
19617 in the @code{let} for @code{print-graph}:
19621 (let ((height (apply 'max numbers-list)) ; @r{First version.}
19622 (symbol-width (length graph-blank)))
19627 As we shall see, this expression is not quite right.
19631 @appendixsec The @code{print-Y-axis} Function
19632 @cindex Axis, print vertical
19633 @cindex Y axis printing
19634 @cindex Vertical axis printing
19635 @cindex Print vertical axis
19637 The job of the @code{print-Y-axis} function is to print a label for
19638 the vertical axis that looks like this:
19656 The function should be passed the height of the graph, and then should
19657 construct and insert the appropriate numbers and marks.
19660 * print-Y-axis in Detail::
19661 * Height of label:: What height for the Y axis?
19662 * Compute a Remainder:: How to compute the remainder of a division.
19663 * Y Axis Element:: Construct a line for the Y axis.
19664 * Y-axis-column:: Generate a list of Y axis labels.
19665 * print-Y-axis Penultimate:: A not quite final version.
19669 @node print-Y-axis in Detail
19670 @unnumberedsubsec The @code{print-Y-axis} Function in Detail
19673 It is easy enough to see in the figure what the Y axis label should
19674 look like; but to say in words, and then to write a function
19675 definition to do the job is another matter. It is not quite true to
19676 say that we want a number and a tic every five lines: there are only
19677 three lines between the @samp{1} and the @samp{5} (lines 2, 3, and 4),
19678 but four lines between the @samp{5} and the @samp{10} (lines 6, 7, 8,
19679 and 9). It is better to say that we want a number and a tic mark on
19680 the base line (number 1) and then that we want a number and a tic on
19681 the fifth line from the bottom and on every line that is a multiple of
19685 @node Height of label
19686 @unnumberedsubsec What height should the label be?
19689 The next issue is what height the label should be? Suppose the maximum
19690 height of tallest column of the graph is seven. Should the highest
19691 label on the Y axis be @samp{5 -}, and should the graph stick up above
19692 the label? Or should the highest label be @samp{7 -}, and mark the peak
19693 of the graph? Or should the highest label be @code{10 -}, which is a
19694 multiple of five, and be higher than the topmost value of the graph?
19696 The latter form is preferred. Most graphs are drawn within rectangles
19697 whose sides are an integral number of steps long---5, 10, 15, and so
19698 on for a step distance of five. But as soon as we decide to use a
19699 step height for the vertical axis, we discover that the simple
19700 expression in the varlist for computing the height is wrong. The
19701 expression is @code{(apply 'max numbers-list)}. This returns the
19702 precise height, not the maximum height plus whatever is necessary to
19703 round up to the nearest multiple of five. A more complex expression
19706 As usual in cases like this, a complex problem becomes simpler if it is
19707 divided into several smaller problems.
19709 First, consider the case when the highest value of the graph is an
19710 integral multiple of five---when it is 5, 10, 15, or some higher
19711 multiple of five. We can use this value as the Y axis height.
19713 A fairly simply way to determine whether a number is a multiple of
19714 five is to divide it by five and see if the division results in a
19715 remainder. If there is no remainder, the number is a multiple of
19716 five. Thus, seven divided by five has a remainder of two, and seven
19717 is not an integral multiple of five. Put in slightly different
19718 language, more reminiscent of the classroom, five goes into seven
19719 once, with a remainder of two. However, five goes into ten twice,
19720 with no remainder: ten is an integral multiple of five.
19722 @node Compute a Remainder
19723 @appendixsubsec Side Trip: Compute a Remainder
19725 @findex % @r{(remainder function)}
19726 @cindex Remainder function, @code{%}
19727 In Lisp, the function for computing a remainder is @code{%}. The
19728 function returns the remainder of its first argument divided by its
19729 second argument. As it happens, @code{%} is a function in Emacs Lisp
19730 that you cannot discover using @code{apropos}: you find nothing if you
19731 type @kbd{M-x apropos @key{RET} remainder @key{RET}}. The only way to
19732 learn of the existence of @code{%} is to read about it in a book such
19733 as this or in the Emacs Lisp sources.
19735 You can try the @code{%} function by evaluating the following two
19747 The first expression returns 2 and the second expression returns 0.
19749 To test whether the returned value is zero or some other number, we
19750 can use the @code{zerop} function. This function returns @code{t} if
19751 its argument, which must be a number, is zero.
19763 Thus, the following expression will return @code{t} if the height
19764 of the graph is evenly divisible by five:
19767 (zerop (% height 5))
19771 (The value of @code{height}, of course, can be found from @code{(apply
19772 'max numbers-list)}.)
19774 On the other hand, if the value of @code{height} is not a multiple of
19775 five, we want to reset the value to the next higher multiple of five.
19776 This is straightforward arithmetic using functions with which we are
19777 already familiar. First, we divide the value of @code{height} by five
19778 to determine how many times five goes into the number. Thus, five
19779 goes into twelve twice. If we add one to this quotient and multiply by
19780 five, we will obtain the value of the next multiple of five that is
19781 larger than the height. Five goes into twelve twice. Add one to two,
19782 and multiply by five; the result is fifteen, which is the next multiple
19783 of five that is higher than twelve. The Lisp expression for this is:
19786 (* (1+ (/ height 5)) 5)
19790 For example, if you evaluate the following, the result is 15:
19793 (* (1+ (/ 12 5)) 5)
19796 All through this discussion, we have been using 5 as the value
19797 for spacing labels on the Y axis; but we may want to use some other
19798 value. For generality, we should replace 5 with a variable to
19799 which we can assign a value. The best name I can think of for this
19800 variable is @code{Y-axis-label-spacing}.
19803 Using this term, and an @code{if} expression, we produce the
19808 (if (zerop (% height Y-axis-label-spacing))
19811 (* (1+ (/ height Y-axis-label-spacing))
19812 Y-axis-label-spacing))
19817 This expression returns the value of @code{height} itself if the height
19818 is an even multiple of the value of the @code{Y-axis-label-spacing} or
19819 else it computes and returns a value of @code{height} that is equal to
19820 the next higher multiple of the value of the @code{Y-axis-label-spacing}.
19822 We can now include this expression in the @code{let} expression of the
19823 @code{print-graph} function (after first setting the value of
19824 @code{Y-axis-label-spacing}):
19825 @vindex Y-axis-label-spacing
19829 (defvar Y-axis-label-spacing 5
19830 "Number of lines from one Y axis label to next.")
19835 (let* ((height (apply 'max numbers-list))
19836 (height-of-top-line
19837 (if (zerop (% height Y-axis-label-spacing))
19842 (* (1+ (/ height Y-axis-label-spacing))
19843 Y-axis-label-spacing)))
19844 (symbol-width (length graph-blank))))
19850 (Note use of the @code{let*} function: the initial value of height is
19851 computed once by the @code{(apply 'max numbers-list)} expression and
19852 then the resulting value of @code{height} is used to compute its
19853 final value. @xref{fwd-para let, , The @code{let*} expression}, for
19854 more about @code{let*}.)
19856 @node Y Axis Element
19857 @appendixsubsec Construct a Y Axis Element
19859 When we print the vertical axis, we want to insert strings such as
19860 @w{@samp{5 -}} and @w{@samp{10 - }} every five lines.
19861 Moreover, we want the numbers and dashes to line up, so shorter
19862 numbers must be padded with leading spaces. If some of the strings
19863 use two digit numbers, the strings with single digit numbers must
19864 include a leading blank space before the number.
19866 @findex number-to-string
19867 To figure out the length of the number, the @code{length} function is
19868 used. But the @code{length} function works only with a string, not with
19869 a number. So the number has to be converted from being a number to
19870 being a string. This is done with the @code{number-to-string} function.
19875 (length (number-to-string 35))
19878 (length (number-to-string 100))
19884 (@code{number-to-string} is also called @code{int-to-string}; you will
19885 see this alternative name in various sources.)
19887 In addition, in each label, each number is followed by a string such
19888 as @w{@samp{ - }}, which we will call the @code{Y-axis-tic} marker.
19889 This variable is defined with @code{defvar}:
19894 (defvar Y-axis-tic " - "
19895 "String that follows number in a Y axis label.")
19899 The length of the Y label is the sum of the length of the Y axis tic
19900 mark and the length of the number of the top of the graph.
19903 (length (concat (number-to-string height) Y-axis-tic)))
19906 This value will be calculated by the @code{print-graph} function in
19907 its varlist as @code{full-Y-label-width} and passed on. (Note that we
19908 did not think to include this in the varlist when we first proposed it.)
19910 To make a complete vertical axis label, a tic mark is concatenated
19911 with a number; and the two together may be preceded by one or more
19912 spaces depending on how long the number is. The label consists of
19913 three parts: the (optional) leading spaces, the number, and the tic
19914 mark. The function is passed the value of the number for the specific
19915 row, and the value of the width of the top line, which is calculated
19916 (just once) by @code{print-graph}.
19920 (defun Y-axis-element (number full-Y-label-width)
19921 "Construct a NUMBERed label element.
19922 A numbered element looks like this ` 5 - ',
19923 and is padded as needed so all line up with
19924 the element for the largest number."
19927 (let* ((leading-spaces
19928 (- full-Y-label-width
19930 (concat (number-to-string number)
19935 (make-string leading-spaces ? )
19936 (number-to-string number)
19941 The @code{Y-axis-element} function concatenates together the leading
19942 spaces, if any; the number, as a string; and the tic mark.
19944 To figure out how many leading spaces the label will need, the
19945 function subtracts the actual length of the label---the length of the
19946 number plus the length of the tic mark---from the desired label width.
19948 @findex make-string
19949 Blank spaces are inserted using the @code{make-string} function. This
19950 function takes two arguments: the first tells it how long the string
19951 will be and the second is a symbol for the character to insert, in a
19952 special format. The format is a question mark followed by a blank
19953 space, like this, @samp{? }. @xref{Character Type, , Character Type,
19954 elisp, The GNU Emacs Lisp Reference Manual}, for a description of the
19955 syntax for characters. (Of course, you might want to replace the
19956 blank space by some other character @dots{} You know what to do.)
19958 The @code{number-to-string} function is used in the concatenation
19959 expression, to convert the number to a string that is concatenated
19960 with the leading spaces and the tic mark.
19962 @node Y-axis-column
19963 @appendixsubsec Create a Y Axis Column
19965 The preceding functions provide all the tools needed to construct a
19966 function that generates a list of numbered and blank strings to insert
19967 as the label for the vertical axis:
19969 @findex Y-axis-column
19972 (defun Y-axis-column (height width-of-label)
19973 "Construct list of Y axis labels and blank strings.
19974 For HEIGHT of line above base and WIDTH-OF-LABEL."
19978 (while (> height 1)
19979 (if (zerop (% height Y-axis-label-spacing))
19980 ;; @r{Insert label.}
19983 (Y-axis-element height width-of-label)
19987 ;; @r{Else, insert blanks.}
19990 (make-string width-of-label ? )
19992 (setq height (1- height)))
19993 ;; @r{Insert base line.}
19995 (cons (Y-axis-element 1 width-of-label) Y-axis))
19996 (nreverse Y-axis)))
20000 In this function, we start with the value of @code{height} and
20001 repetitively subtract one from its value. After each subtraction, we
20002 test to see whether the value is an integral multiple of the
20003 @code{Y-axis-label-spacing}. If it is, we construct a numbered label
20004 using the @code{Y-axis-element} function; if not, we construct a
20005 blank label using the @code{make-string} function. The base line
20006 consists of the number one followed by a tic mark.
20009 @node print-Y-axis Penultimate
20010 @appendixsubsec The Not Quite Final Version of @code{print-Y-axis}
20012 The list constructed by the @code{Y-axis-column} function is passed to
20013 the @code{print-Y-axis} function, which inserts the list as a column.
20015 @findex print-Y-axis
20018 (defun print-Y-axis (height full-Y-label-width)
20019 "Insert Y axis using HEIGHT and FULL-Y-LABEL-WIDTH.
20020 Height must be the maximum height of the graph.
20021 Full width is the width of the highest label element."
20022 ;; Value of height and full-Y-label-width
20023 ;; are passed by print-graph.
20026 (let ((start (point)))
20028 (Y-axis-column height full-Y-label-width))
20029 ;; @r{Place point ready for inserting graph.}
20031 ;; @r{Move point forward by value of} full-Y-label-width
20032 (forward-char full-Y-label-width)))
20036 The @code{print-Y-axis} uses the @code{insert-rectangle} function to
20037 insert the Y axis labels created by the @code{Y-axis-column} function.
20038 In addition, it places point at the correct position for printing the body of
20041 You can test @code{print-Y-axis}:
20049 Y-axis-label-spacing
20058 Copy the following expression:
20061 (print-Y-axis 12 5)
20065 Switch to the @file{*scratch*} buffer and place the cursor where you
20066 want the axis labels to start.
20069 Type @kbd{M-:} (@code{eval-expression}).
20072 Yank the @code{graph-body-print} expression into the minibuffer
20073 with @kbd{C-y} (@code{yank)}.
20076 Press @key{RET} to evaluate the expression.
20079 Emacs will print labels vertically, the top one being @w{@samp{10 -@w{
20080 }}}. (The @code{print-graph} function will pass the value of
20081 @code{height-of-top-line}, which in this case will end up as 15,
20082 thereby getting rid of what might appear as a bug.)
20086 @appendixsec The @code{print-X-axis} Function
20087 @cindex Axis, print horizontal
20088 @cindex X axis printing
20089 @cindex Print horizontal axis
20090 @cindex Horizontal axis printing
20092 X axis labels are much like Y axis labels, except that the ticks are on a
20093 line above the numbers. Labels should look like this:
20102 The first tic is under the first column of the graph and is preceded by
20103 several blank spaces. These spaces provide room in rows above for the Y
20104 axis labels. The second, third, fourth, and subsequent ticks are all
20105 spaced equally, according to the value of @code{X-axis-label-spacing}.
20107 The second row of the X axis consists of numbers, preceded by several
20108 blank spaces and also separated according to the value of the variable
20109 @code{X-axis-label-spacing}.
20111 The value of the variable @code{X-axis-label-spacing} should itself be
20112 measured in units of @code{symbol-width}, since you may want to change
20113 the width of the symbols that you are using to print the body of the
20114 graph without changing the ways the graph is labeled.
20117 * Similarities differences:: Much like @code{print-Y-axis}, but not exactly.
20118 * X Axis Tic Marks:: Create tic marks for the horizontal axis.
20122 @node Similarities differences
20123 @unnumberedsubsec Similarities and differences
20126 The @code{print-X-axis} function is constructed in more or less the
20127 same fashion as the @code{print-Y-axis} function except that it has
20128 two lines: the line of tic marks and the numbers. We will write a
20129 separate function to print each line and then combine them within the
20130 @code{print-X-axis} function.
20132 This is a three step process:
20136 Write a function to print the X axis tic marks, @code{print-X-axis-tic-line}.
20139 Write a function to print the X numbers, @code{print-X-axis-numbered-line}.
20142 Write a function to print both lines, the @code{print-X-axis} function,
20143 using @code{print-X-axis-tic-line} and
20144 @code{print-X-axis-numbered-line}.
20147 @node X Axis Tic Marks
20148 @appendixsubsec X Axis Tic Marks
20150 The first function should print the X axis tic marks. We must specify
20151 the tic marks themselves and their spacing:
20155 (defvar X-axis-label-spacing
20156 (if (boundp 'graph-blank)
20157 (* 5 (length graph-blank)) 5)
20158 "Number of units from one X axis label to next.")
20163 (Note that the value of @code{graph-blank} is set by another
20164 @code{defvar}. The @code{boundp} predicate checks whether it has
20165 already been set; @code{boundp} returns @code{nil} if it has not. If
20166 @code{graph-blank} were unbound and we did not use this conditional
20167 construction, in a recent GNU Emacs, we would enter the debugger and
20168 see an error message saying @samp{@w{Debugger entered--Lisp error:}
20169 @w{(void-variable graph-blank)}}.)
20172 Here is the @code{defvar} for @code{X-axis-tic-symbol}:
20176 (defvar X-axis-tic-symbol "|"
20177 "String to insert to point to a column in X axis.")
20182 The goal is to make a line that looks like this:
20188 The first tic is indented so that it is under the first column, which is
20189 indented to provide space for the Y axis labels.
20191 A tic element consists of the blank spaces that stretch from one tic to
20192 the next plus a tic symbol. The number of blanks is determined by the
20193 width of the tic symbol and the @code{X-axis-label-spacing}.
20196 The code looks like this:
20200 ;;; X-axis-tic-element
20204 ;; @r{Make a string of blanks.}
20205 (- (* symbol-width X-axis-label-spacing)
20206 (length X-axis-tic-symbol))
20208 ;; @r{Concatenate blanks with tic symbol.}
20214 Next, we determine how many blanks are needed to indent the first tic
20215 mark to the first column of the graph. This uses the value of
20216 @code{full-Y-label-width} passed it by the @code{print-graph} function.
20219 The code to make @code{X-axis-leading-spaces}
20224 ;; X-axis-leading-spaces
20226 (make-string full-Y-label-width ? )
20231 We also need to determine the length of the horizontal axis, which is
20232 the length of the numbers list, and the number of ticks in the horizontal
20239 (length numbers-list)
20245 (* symbol-width X-axis-label-spacing)
20249 ;; number-of-X-ticks
20250 (if (zerop (% (X-length tic-width)))
20251 (/ (X-length tic-width))
20252 (1+ (/ (X-length tic-width))))
20257 All this leads us directly to the function for printing the X axis tic line:
20259 @findex print-X-axis-tic-line
20262 (defun print-X-axis-tic-line
20263 (number-of-X-tics X-axis-leading-spaces X-axis-tic-element)
20264 "Print ticks for X axis."
20265 (insert X-axis-leading-spaces)
20266 (insert X-axis-tic-symbol) ; @r{Under first column.}
20269 ;; @r{Insert second tic in the right spot.}
20272 (- (* symbol-width X-axis-label-spacing)
20273 ;; @r{Insert white space up to second tic symbol.}
20274 (* 2 (length X-axis-tic-symbol)))
20276 X-axis-tic-symbol))
20279 ;; @r{Insert remaining ticks.}
20280 (while (> number-of-X-tics 1)
20281 (insert X-axis-tic-element)
20282 (setq number-of-X-tics (1- number-of-X-tics))))
20286 The line of numbers is equally straightforward:
20289 First, we create a numbered element with blank spaces before each number:
20291 @findex X-axis-element
20294 (defun X-axis-element (number)
20295 "Construct a numbered X axis element."
20296 (let ((leading-spaces
20297 (- (* symbol-width X-axis-label-spacing)
20298 (length (number-to-string number)))))
20299 (concat (make-string leading-spaces ? )
20300 (number-to-string number))))
20304 Next, we create the function to print the numbered line, starting with
20305 the number 1 under the first column:
20307 @findex print-X-axis-numbered-line
20310 (defun print-X-axis-numbered-line
20311 (number-of-X-tics X-axis-leading-spaces)
20312 "Print line of X-axis numbers"
20313 (let ((number X-axis-label-spacing))
20314 (insert X-axis-leading-spaces)
20320 ;; @r{Insert white space up to next number.}
20321 (- (* symbol-width X-axis-label-spacing) 2)
20323 (number-to-string number)))
20326 ;; @r{Insert remaining numbers.}
20327 (setq number (+ number X-axis-label-spacing))
20328 (while (> number-of-X-tics 1)
20329 (insert (X-axis-element number))
20330 (setq number (+ number X-axis-label-spacing))
20331 (setq number-of-X-tics (1- number-of-X-tics)))))
20335 Finally, we need to write the @code{print-X-axis} that uses
20336 @code{print-X-axis-tic-line} and
20337 @code{print-X-axis-numbered-line}.
20339 The function must determine the local values of the variables used by both
20340 @code{print-X-axis-tic-line} and @code{print-X-axis-numbered-line}, and
20341 then it must call them. Also, it must print the carriage return that
20342 separates the two lines.
20344 The function consists of a varlist that specifies five local variables,
20345 and calls to each of the two line printing functions:
20347 @findex print-X-axis
20350 (defun print-X-axis (numbers-list)
20351 "Print X axis labels to length of NUMBERS-LIST."
20352 (let* ((leading-spaces
20353 (make-string full-Y-label-width ? ))
20356 ;; symbol-width @r{is provided by} graph-body-print
20357 (tic-width (* symbol-width X-axis-label-spacing))
20358 (X-length (length numbers-list))
20366 ;; @r{Make a string of blanks.}
20367 (- (* symbol-width X-axis-label-spacing)
20368 (length X-axis-tic-symbol))
20372 ;; @r{Concatenate blanks with tic symbol.}
20373 X-axis-tic-symbol))
20377 (if (zerop (% X-length tic-width))
20378 (/ X-length tic-width)
20379 (1+ (/ X-length tic-width)))))
20382 (print-X-axis-tic-line tic-number leading-spaces X-tic)
20384 (print-X-axis-numbered-line tic-number leading-spaces)))
20389 You can test @code{print-X-axis}:
20393 Install @code{X-axis-tic-symbol}, @code{X-axis-label-spacing},
20394 @code{print-X-axis-tic-line}, as well as @code{X-axis-element},
20395 @code{print-X-axis-numbered-line}, and @code{print-X-axis}.
20398 Copy the following expression:
20403 (let ((full-Y-label-width 5)
20406 '(1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16))))
20411 Switch to the @file{*scratch*} buffer and place the cursor where you
20412 want the axis labels to start.
20415 Type @kbd{M-:} (@code{eval-expression}).
20418 Yank the test expression into the minibuffer
20419 with @kbd{C-y} (@code{yank)}.
20422 Press @key{RET} to evaluate the expression.
20426 Emacs will print the horizontal axis like this:
20436 @node Print Whole Graph
20437 @appendixsec Printing the Whole Graph
20438 @cindex Printing the whole graph
20439 @cindex Whole graph printing
20440 @cindex Graph, printing all
20442 Now we are nearly ready to print the whole graph.
20444 The function to print the graph with the proper labels follows the
20445 outline we created earlier (@pxref{Full Graph, , A Graph with Labeled
20446 Axes}), but with additions.
20449 Here is the outline:
20453 (defun print-graph (numbers-list)
20454 "@var{documentation}@dots{}"
20455 (let ((height @dots{}
20459 (print-Y-axis height @dots{} )
20460 (graph-body-print numbers-list)
20461 (print-X-axis @dots{} )))
20466 * The final version:: A few changes.
20467 * Test print-graph:: Run a short test.
20468 * Graphing words in defuns:: Executing the final code.
20469 * lambda:: How to write an anonymous function.
20470 * mapcar:: Apply a function to elements of a list.
20471 * Another Bug:: Yet another bug @dots{} most insidious.
20472 * Final printed graph:: The graph itself!
20476 @node The final version
20477 @unnumberedsubsec Changes for the Final Version
20480 The final version is different from what we planned in two ways:
20481 first, it contains additional values calculated once in the varlist;
20482 second, it carries an option to specify the labels' increment per row.
20483 This latter feature turns out to be essential; otherwise, a graph may
20484 have more rows than fit on a display or on a sheet of paper.
20487 This new feature requires a change to the @code{Y-axis-column}
20488 function, to add @code{vertical-step} to it. The function looks like
20491 @findex Y-axis-column @r{Final version.}
20494 ;;; @r{Final version.}
20495 (defun Y-axis-column
20496 (height width-of-label &optional vertical-step)
20497 "Construct list of labels for Y axis.
20498 HEIGHT is maximum height of graph.
20499 WIDTH-OF-LABEL is maximum width of label.
20500 VERTICAL-STEP, an option, is a positive integer
20501 that specifies how much a Y axis label increments
20502 for each line. For example, a step of 5 means
20503 that each line is five units of the graph."
20507 (number-per-line (or vertical-step 1)))
20508 (while (> height 1)
20509 (if (zerop (% height Y-axis-label-spacing))
20512 ;; @r{Insert label.}
20516 (* height number-per-line)
20521 ;; @r{Else, insert blanks.}
20524 (make-string width-of-label ? )
20526 (setq height (1- height)))
20529 ;; @r{Insert base line.}
20530 (setq Y-axis (cons (Y-axis-element
20531 (or vertical-step 1)
20534 (nreverse Y-axis)))
20538 The values for the maximum height of graph and the width of a symbol
20539 are computed by @code{print-graph} in its @code{let} expression; so
20540 @code{graph-body-print} must be changed to accept them.
20542 @findex graph-body-print @r{Final version.}
20545 ;;; @r{Final version.}
20546 (defun graph-body-print (numbers-list height symbol-width)
20547 "Print a bar graph of the NUMBERS-LIST.
20548 The numbers-list consists of the Y-axis values.
20549 HEIGHT is maximum height of graph.
20550 SYMBOL-WIDTH is number of each column."
20553 (let (from-position)
20554 (while numbers-list
20555 (setq from-position (point))
20557 (column-of-graph height (car numbers-list)))
20558 (goto-char from-position)
20559 (forward-char symbol-width)
20562 ;; @r{Draw graph column by column.}
20564 (setq numbers-list (cdr numbers-list)))
20565 ;; @r{Place point for X axis labels.}
20566 (forward-line height)
20572 Finally, the code for the @code{print-graph} function:
20574 @findex print-graph @r{Final version.}
20577 ;;; @r{Final version.}
20579 (numbers-list &optional vertical-step)
20580 "Print labeled bar graph of the NUMBERS-LIST.
20581 The numbers-list consists of the Y-axis values.
20585 Optionally, VERTICAL-STEP, a positive integer,
20586 specifies how much a Y axis label increments for
20587 each line. For example, a step of 5 means that
20588 each row is five units."
20591 (let* ((symbol-width (length graph-blank))
20592 ;; @code{height} @r{is both the largest number}
20593 ;; @r{and the number with the most digits.}
20594 (height (apply 'max numbers-list))
20597 (height-of-top-line
20598 (if (zerop (% height Y-axis-label-spacing))
20601 (* (1+ (/ height Y-axis-label-spacing))
20602 Y-axis-label-spacing)))
20605 (vertical-step (or vertical-step 1))
20606 (full-Y-label-width
20612 (* height-of-top-line vertical-step))
20618 height-of-top-line full-Y-label-width vertical-step)
20622 numbers-list height-of-top-line symbol-width)
20623 (print-X-axis numbers-list)))
20627 @node Test print-graph
20628 @appendixsubsec Testing @code{print-graph}
20631 We can test the @code{print-graph} function with a short list of numbers:
20635 Install the final versions of @code{Y-axis-column},
20636 @code{graph-body-print}, and @code{print-graph} (in addition to the
20640 Copy the following expression:
20643 (print-graph '(3 2 5 6 7 5 3 4 6 4 3 2 1))
20647 Switch to the @file{*scratch*} buffer and place the cursor where you
20648 want the axis labels to start.
20651 Type @kbd{M-:} (@code{eval-expression}).
20654 Yank the test expression into the minibuffer
20655 with @kbd{C-y} (@code{yank)}.
20658 Press @key{RET} to evaluate the expression.
20662 Emacs will print a graph that looks like this:
20683 On the other hand, if you pass @code{print-graph} a
20684 @code{vertical-step} value of 2, by evaluating this expression:
20687 (print-graph '(3 2 5 6 7 5 3 4 6 4 3 2 1) 2)
20692 The graph looks like this:
20713 (A question: is the @samp{2} on the bottom of the vertical axis a bug or a
20714 feature? If you think it is a bug, and should be a @samp{1} instead, (or
20715 even a @samp{0}), you can modify the sources.)
20717 @node Graphing words in defuns
20718 @appendixsubsec Graphing Numbers of Words and Symbols
20720 Now for the graph for which all this code was written: a graph that
20721 shows how many function definitions contain fewer than 10 words and
20722 symbols, how many contain between 10 and 19 words and symbols, how
20723 many contain between 20 and 29 words and symbols, and so on.
20725 This is a multi-step process. First make sure you have loaded all the
20729 It is a good idea to reset the value of @code{top-of-ranges} in case
20730 you have set it to some different value. You can evaluate the
20735 (setq top-of-ranges
20738 110 120 130 140 150
20739 160 170 180 190 200
20740 210 220 230 240 250
20741 260 270 280 290 300)
20746 Next create a list of the number of words and symbols in each range.
20750 Evaluate the following:
20754 (setq list-for-graph
20757 (recursive-lengths-list-many-files
20758 (directory-files "/usr/local/emacs/lisp"
20766 On my old machine, this took about an hour. It looked though 303 Lisp
20767 files in my copy of Emacs version 19.23. After all that computing,
20768 the @code{list-for-graph} had this value:
20772 (537 1027 955 785 594 483 349 292 224 199 166 120 116 99
20773 90 80 67 48 52 45 41 33 28 26 25 20 12 28 11 13 220)
20778 This means that my copy of Emacs had 537 function definitions with
20779 fewer than 10 words or symbols in them, 1,027 function definitions
20780 with 10 to 19 words or symbols in them, 955 function definitions with
20781 20 to 29 words or symbols in them, and so on.
20783 Clearly, just by looking at this list we can see that most function
20784 definitions contain ten to thirty words and symbols.
20786 Now for printing. We do @emph{not} want to print a graph that is
20787 1,030 lines high @dots{} Instead, we should print a graph that is
20788 fewer than twenty-five lines high. A graph that height can be
20789 displayed on almost any monitor, and easily printed on a sheet of paper.
20791 This means that each value in @code{list-for-graph} must be reduced to
20792 one-fiftieth its present value.
20794 Here is a short function to do just that, using two functions we have
20795 not yet seen, @code{mapcar} and @code{lambda}.
20799 (defun one-fiftieth (full-range)
20800 "Return list, each number one-fiftieth of previous."
20801 (mapcar (lambda (arg) (/ arg 50)) full-range))
20806 @appendixsubsec A @code{lambda} Expression: Useful Anonymity
20807 @cindex Anonymous function
20810 @code{lambda} is the symbol for an anonymous function, a function
20811 without a name. Every time you use an anonymous function, you need to
20812 include its whole body.
20819 (lambda (arg) (/ arg 50))
20823 is a function that returns the value resulting from
20824 dividing whatever is passed to it as @code{arg} by 50.
20827 Earlier, for example, we had a function @code{multiply-by-seven}; it
20828 multiplied its argument by 7. This function is similar, except it
20829 divides its argument by 50; and, it has no name. The anonymous
20830 equivalent of @code{multiply-by-seven} is:
20833 (lambda (number) (* 7 number))
20837 (@xref{defun, , The @code{defun} Macro}.)
20841 If we want to multiply 3 by 7, we can write:
20843 @c clear print-postscript-figures
20844 @c lambda example diagram #1
20848 (multiply-by-seven 3)
20849 \_______________/ ^
20855 @ifset print-postscript-figures
20858 @center @image{lambda-1}
20862 @ifclear print-postscript-figures
20866 (multiply-by-seven 3)
20867 \_______________/ ^
20876 This expression returns 21.
20880 Similarly, we can write:
20882 @c lambda example diagram #2
20886 ((lambda (number) (* 7 number)) 3)
20887 \____________________________/ ^
20889 anonymous function argument
20893 @ifset print-postscript-figures
20896 @center @image{lambda-2}
20900 @ifclear print-postscript-figures
20904 ((lambda (number) (* 7 number)) 3)
20905 \____________________________/ ^
20907 anonymous function argument
20915 If we want to divide 100 by 50, we can write:
20917 @c lambda example diagram #3
20921 ((lambda (arg) (/ arg 50)) 100)
20922 \______________________/ \_/
20924 anonymous function argument
20928 @ifset print-postscript-figures
20931 @center @image{lambda-3}
20935 @ifclear print-postscript-figures
20939 ((lambda (arg) (/ arg 50)) 100)
20940 \______________________/ \_/
20942 anonymous function argument
20949 This expression returns 2. The 100 is passed to the function, which
20950 divides that number by 50.
20952 @xref{Lambda Expressions, , Lambda Expressions, elisp, The GNU Emacs
20953 Lisp Reference Manual}, for more about @code{lambda}. Lisp and lambda
20954 expressions derive from the Lambda Calculus.
20957 @appendixsubsec The @code{mapcar} Function
20960 @code{mapcar} is a function that calls its first argument with each
20961 element of its second argument, in turn. The second argument must be
20964 The @samp{map} part of the name comes from the mathematical phrase,
20965 ``mapping over a domain'', meaning to apply a function to each of the
20966 elements in a domain. The mathematical phrase is based on the
20967 metaphor of a surveyor walking, one step at a time, over an area he is
20968 mapping. And @samp{car}, of course, comes from the Lisp notion of the
20977 (mapcar '1+ '(2 4 6))
20983 The function @code{1+} which adds one to its argument, is executed on
20984 @emph{each} element of the list, and a new list is returned.
20986 Contrast this with @code{apply}, which applies its first argument to
20988 (@xref{Readying a Graph, , Readying a Graph}, for a explanation of
20992 In the definition of @code{one-fiftieth}, the first argument is the
20993 anonymous function:
20996 (lambda (arg) (/ arg 50))
21000 and the second argument is @code{full-range}, which will be bound to
21001 @code{list-for-graph}.
21004 The whole expression looks like this:
21007 (mapcar (lambda (arg) (/ arg 50)) full-range))
21010 @xref{Mapping Functions, , Mapping Functions, elisp, The GNU Emacs
21011 Lisp Reference Manual}, for more about @code{mapcar}.
21013 Using the @code{one-fiftieth} function, we can generate a list in
21014 which each element is one-fiftieth the size of the corresponding
21015 element in @code{list-for-graph}.
21019 (setq fiftieth-list-for-graph
21020 (one-fiftieth list-for-graph))
21025 The resulting list looks like this:
21029 (10 20 19 15 11 9 6 5 4 3 3 2 2
21030 1 1 1 1 0 1 0 0 0 0 0 0 0 0 0 0 0 4)
21035 This, we are almost ready to print! (We also notice the loss of
21036 information: many of the higher ranges are 0, meaning that fewer than
21037 50 defuns had that many words or symbols---but not necessarily meaning
21038 that none had that many words or symbols.)
21041 @appendixsubsec Another Bug @dots{} Most Insidious
21042 @cindex Bug, most insidious type
21043 @cindex Insidious type of bug
21045 I said ``almost ready to print''! Of course, there is a bug in the
21046 @code{print-graph} function @dots{} It has a @code{vertical-step}
21047 option, but not a @code{horizontal-step} option. The
21048 @code{top-of-range} scale goes from 10 to 300 by tens. But the
21049 @code{print-graph} function will print only by ones.
21051 This is a classic example of what some consider the most insidious
21052 type of bug, the bug of omission. This is not the kind of bug you can
21053 find by studying the code, for it is not in the code; it is an omitted
21054 feature. Your best actions are to try your program early and often;
21055 and try to arrange, as much as you can, to write code that is easy to
21056 understand and easy to change. Try to be aware, whenever you can,
21057 that whatever you have written, @emph{will} be rewritten, if not soon,
21058 eventually. A hard maxim to follow.
21060 It is the @code{print-X-axis-numbered-line} function that needs the
21061 work; and then the @code{print-X-axis} and the @code{print-graph}
21062 functions need to be adapted. Not much needs to be done; there is one
21063 nicety: the numbers ought to line up under the tic marks. This takes
21067 Here is the corrected @code{print-X-axis-numbered-line}:
21071 (defun print-X-axis-numbered-line
21072 (number-of-X-tics X-axis-leading-spaces
21073 &optional horizontal-step)
21074 "Print line of X-axis numbers"
21075 (let ((number X-axis-label-spacing)
21076 (horizontal-step (or horizontal-step 1)))
21079 (insert X-axis-leading-spaces)
21080 ;; @r{Delete extra leading spaces.}
21083 (length (number-to-string horizontal-step)))))
21088 ;; @r{Insert white space.}
21090 X-axis-label-spacing)
21093 (number-to-string horizontal-step)))
21097 (* number horizontal-step))))
21100 ;; @r{Insert remaining numbers.}
21101 (setq number (+ number X-axis-label-spacing))
21102 (while (> number-of-X-tics 1)
21103 (insert (X-axis-element
21104 (* number horizontal-step)))
21105 (setq number (+ number X-axis-label-spacing))
21106 (setq number-of-X-tics (1- number-of-X-tics)))))
21111 If you are reading this in Info, you can see the new versions of
21112 @code{print-X-axis} @code{print-graph} and evaluate them. If you are
21113 reading this in a printed book, you can see the changed lines here
21114 (the full text is too much to print).
21119 (defun print-X-axis (numbers-list horizontal-step)
21121 (print-X-axis-numbered-line
21122 tic-number leading-spaces horizontal-step))
21130 &optional vertical-step horizontal-step)
21132 (print-X-axis numbers-list horizontal-step))
21140 (defun print-X-axis (numbers-list horizontal-step)
21141 "Print X axis labels to length of NUMBERS-LIST.
21142 Optionally, HORIZONTAL-STEP, a positive integer,
21143 specifies how much an X axis label increments for
21147 ;; Value of symbol-width and full-Y-label-width
21148 ;; are passed by print-graph.
21149 (let* ((leading-spaces
21150 (make-string full-Y-label-width ? ))
21151 ;; symbol-width @r{is provided by} graph-body-print
21152 (tic-width (* symbol-width X-axis-label-spacing))
21153 (X-length (length numbers-list))
21159 ;; @r{Make a string of blanks.}
21160 (- (* symbol-width X-axis-label-spacing)
21161 (length X-axis-tic-symbol))
21165 ;; @r{Concatenate blanks with tic symbol.}
21166 X-axis-tic-symbol))
21168 (if (zerop (% X-length tic-width))
21169 (/ X-length tic-width)
21170 (1+ (/ X-length tic-width)))))
21174 (print-X-axis-tic-line
21175 tic-number leading-spaces X-tic)
21177 (print-X-axis-numbered-line
21178 tic-number leading-spaces horizontal-step)))
21185 (numbers-list &optional vertical-step horizontal-step)
21186 "Print labeled bar graph of the NUMBERS-LIST.
21187 The numbers-list consists of the Y-axis values.
21191 Optionally, VERTICAL-STEP, a positive integer,
21192 specifies how much a Y axis label increments for
21193 each line. For example, a step of 5 means that
21194 each row is five units.
21198 Optionally, HORIZONTAL-STEP, a positive integer,
21199 specifies how much an X axis label increments for
21201 (let* ((symbol-width (length graph-blank))
21202 ;; @code{height} @r{is both the largest number}
21203 ;; @r{and the number with the most digits.}
21204 (height (apply 'max numbers-list))
21207 (height-of-top-line
21208 (if (zerop (% height Y-axis-label-spacing))
21211 (* (1+ (/ height Y-axis-label-spacing))
21212 Y-axis-label-spacing)))
21215 (vertical-step (or vertical-step 1))
21216 (full-Y-label-width
21220 (* height-of-top-line vertical-step))
21225 height-of-top-line full-Y-label-width vertical-step)
21227 numbers-list height-of-top-line symbol-width)
21228 (print-X-axis numbers-list horizontal-step)))
21235 Graphing Definitions Re-listed
21238 Here are all the graphing definitions in their final form:
21242 (defvar top-of-ranges
21245 110 120 130 140 150
21246 160 170 180 190 200
21247 210 220 230 240 250)
21248 "List specifying ranges for `defuns-per-range'.")
21252 (defvar graph-symbol "*"
21253 "String used as symbol in graph, usually an asterisk.")
21257 (defvar graph-blank " "
21258 "String used as blank in graph, usually a blank space.
21259 graph-blank must be the same number of columns wide
21264 (defvar Y-axis-tic " - "
21265 "String that follows number in a Y axis label.")
21269 (defvar Y-axis-label-spacing 5
21270 "Number of lines from one Y axis label to next.")
21274 (defvar X-axis-tic-symbol "|"
21275 "String to insert to point to a column in X axis.")
21279 (defvar X-axis-label-spacing
21280 (if (boundp 'graph-blank)
21281 (* 5 (length graph-blank)) 5)
21282 "Number of units from one X axis label to next.")
21288 (defun count-words-in-defun ()
21289 "Return the number of words and symbols in a defun."
21290 (beginning-of-defun)
21292 (end (save-excursion (end-of-defun) (point))))
21297 (and (< (point) end)
21299 "\\(\\w\\|\\s_\\)+[^ \t\n]*[ \t\n]*"
21301 (setq count (1+ count)))
21308 (defun lengths-list-file (filename)
21309 "Return list of definitions' lengths within FILE.
21310 The returned list is a list of numbers.
21311 Each number is the number of words or
21312 symbols in one function definition."
21316 (message "Working on `%s' ... " filename)
21318 (let ((buffer (find-file-noselect filename))
21320 (set-buffer buffer)
21321 (setq buffer-read-only t)
21323 (goto-char (point-min))
21327 (while (re-search-forward "^(defun" nil t)
21329 (cons (count-words-in-defun) lengths-list)))
21330 (kill-buffer buffer)
21337 (defun lengths-list-many-files (list-of-files)
21338 "Return list of lengths of defuns in LIST-OF-FILES."
21339 (let (lengths-list)
21340 ;;; @r{true-or-false-test}
21341 (while list-of-files
21347 ;;; @r{Generate a lengths' list.}
21349 (expand-file-name (car list-of-files)))))
21350 ;;; @r{Make files' list shorter.}
21351 (setq list-of-files (cdr list-of-files)))
21352 ;;; @r{Return final value of lengths' list.}
21359 (defun defuns-per-range (sorted-lengths top-of-ranges)
21360 "SORTED-LENGTHS defuns in each TOP-OF-RANGES range."
21361 (let ((top-of-range (car top-of-ranges))
21362 (number-within-range 0)
21363 defuns-per-range-list)
21368 (while top-of-ranges
21372 ;; @r{Need number for numeric test.}
21373 (car sorted-lengths)
21374 (< (car sorted-lengths) top-of-range))
21376 ;; @r{Count number of definitions within current range.}
21377 (setq number-within-range (1+ number-within-range))
21378 (setq sorted-lengths (cdr sorted-lengths)))
21382 ;; @r{Exit inner loop but remain within outer loop.}
21384 (setq defuns-per-range-list
21385 (cons number-within-range defuns-per-range-list))
21386 (setq number-within-range 0) ; @r{Reset count to zero.}
21388 ;; @r{Move to next range.}
21389 (setq top-of-ranges (cdr top-of-ranges))
21390 ;; @r{Specify next top of range value.}
21391 (setq top-of-range (car top-of-ranges)))
21395 ;; @r{Exit outer loop and count the number of defuns larger than}
21396 ;; @r{ the largest top-of-range value.}
21397 (setq defuns-per-range-list
21399 (length sorted-lengths)
21400 defuns-per-range-list))
21402 ;; @r{Return a list of the number of definitions within each range,}
21403 ;; @r{ smallest to largest.}
21404 (nreverse defuns-per-range-list)))
21410 (defun column-of-graph (max-graph-height actual-height)
21411 "Return list of MAX-GRAPH-HEIGHT strings;
21412 ACTUAL-HEIGHT are graph-symbols.
21413 The graph-symbols are contiguous entries at the end
21415 The list will be inserted as one column of a graph.
21416 The strings are either graph-blank or graph-symbol."
21420 (let ((insert-list nil)
21421 (number-of-top-blanks
21422 (- max-graph-height actual-height)))
21424 ;; @r{Fill in @code{graph-symbols}.}
21425 (while (> actual-height 0)
21426 (setq insert-list (cons graph-symbol insert-list))
21427 (setq actual-height (1- actual-height)))
21431 ;; @r{Fill in @code{graph-blanks}.}
21432 (while (> number-of-top-blanks 0)
21433 (setq insert-list (cons graph-blank insert-list))
21434 (setq number-of-top-blanks
21435 (1- number-of-top-blanks)))
21437 ;; @r{Return whole list.}
21444 (defun Y-axis-element (number full-Y-label-width)
21445 "Construct a NUMBERed label element.
21446 A numbered element looks like this ` 5 - ',
21447 and is padded as needed so all line up with
21448 the element for the largest number."
21451 (let* ((leading-spaces
21452 (- full-Y-label-width
21454 (concat (number-to-string number)
21459 (make-string leading-spaces ? )
21460 (number-to-string number)
21467 (defun print-Y-axis
21468 (height full-Y-label-width &optional vertical-step)
21469 "Insert Y axis by HEIGHT and FULL-Y-LABEL-WIDTH.
21470 Height must be the maximum height of the graph.
21471 Full width is the width of the highest label element.
21472 Optionally, print according to VERTICAL-STEP."
21475 ;; Value of height and full-Y-label-width
21476 ;; are passed by 'print-graph'.
21477 (let ((start (point)))
21479 (Y-axis-column height full-Y-label-width vertical-step))
21482 ;; @r{Place point ready for inserting graph.}
21484 ;; @r{Move point forward by value of} full-Y-label-width
21485 (forward-char full-Y-label-width)))
21491 (defun print-X-axis-tic-line
21492 (number-of-X-tics X-axis-leading-spaces X-axis-tic-element)
21493 "Print ticks for X axis."
21494 (insert X-axis-leading-spaces)
21495 (insert X-axis-tic-symbol) ; @r{Under first column.}
21498 ;; @r{Insert second tic in the right spot.}
21501 (- (* symbol-width X-axis-label-spacing)
21502 ;; @r{Insert white space up to second tic symbol.}
21503 (* 2 (length X-axis-tic-symbol)))
21505 X-axis-tic-symbol))
21508 ;; @r{Insert remaining ticks.}
21509 (while (> number-of-X-tics 1)
21510 (insert X-axis-tic-element)
21511 (setq number-of-X-tics (1- number-of-X-tics))))
21517 (defun X-axis-element (number)
21518 "Construct a numbered X axis element."
21519 (let ((leading-spaces
21520 (- (* symbol-width X-axis-label-spacing)
21521 (length (number-to-string number)))))
21522 (concat (make-string leading-spaces ? )
21523 (number-to-string number))))
21529 (defun graph-body-print (numbers-list height symbol-width)
21530 "Print a bar graph of the NUMBERS-LIST.
21531 The numbers-list consists of the Y-axis values.
21532 HEIGHT is maximum height of graph.
21533 SYMBOL-WIDTH is number of each column."
21536 (let (from-position)
21537 (while numbers-list
21538 (setq from-position (point))
21540 (column-of-graph height (car numbers-list)))
21541 (goto-char from-position)
21542 (forward-char symbol-width)
21545 ;; @r{Draw graph column by column.}
21547 (setq numbers-list (cdr numbers-list)))
21548 ;; @r{Place point for X axis labels.}
21549 (forward-line height)
21556 (defun Y-axis-column
21557 (height width-of-label &optional vertical-step)
21558 "Construct list of labels for Y axis.
21559 HEIGHT is maximum height of graph.
21560 WIDTH-OF-LABEL is maximum width of label.
21563 VERTICAL-STEP, an option, is a positive integer
21564 that specifies how much a Y axis label increments
21565 for each line. For example, a step of 5 means
21566 that each line is five units of the graph."
21568 (number-per-line (or vertical-step 1)))
21571 (while (> height 1)
21572 (if (zerop (% height Y-axis-label-spacing))
21573 ;; @r{Insert label.}
21577 (* height number-per-line)
21582 ;; @r{Else, insert blanks.}
21585 (make-string width-of-label ? )
21587 (setq height (1- height)))
21590 ;; @r{Insert base line.}
21591 (setq Y-axis (cons (Y-axis-element
21592 (or vertical-step 1)
21595 (nreverse Y-axis)))
21601 (defun print-X-axis-numbered-line
21602 (number-of-X-tics X-axis-leading-spaces
21603 &optional horizontal-step)
21604 "Print line of X-axis numbers"
21605 (let ((number X-axis-label-spacing)
21606 (horizontal-step (or horizontal-step 1)))
21609 (insert X-axis-leading-spaces)
21611 (delete-char (- (1- (length (number-to-string horizontal-step)))))
21614 ;; @r{Insert white space up to next number.}
21615 (- (* symbol-width X-axis-label-spacing)
21616 (1- (length (number-to-string horizontal-step)))
21619 (number-to-string (* number horizontal-step))))
21622 ;; @r{Insert remaining numbers.}
21623 (setq number (+ number X-axis-label-spacing))
21624 (while (> number-of-X-tics 1)
21625 (insert (X-axis-element (* number horizontal-step)))
21626 (setq number (+ number X-axis-label-spacing))
21627 (setq number-of-X-tics (1- number-of-X-tics)))))
21633 (defun print-X-axis (numbers-list horizontal-step)
21634 "Print X axis labels to length of NUMBERS-LIST.
21635 Optionally, HORIZONTAL-STEP, a positive integer,
21636 specifies how much an X axis label increments for
21640 ;; Value of symbol-width and full-Y-label-width
21641 ;; are passed by 'print-graph'.
21642 (let* ((leading-spaces
21643 (make-string full-Y-label-width ? ))
21644 ;; symbol-width @r{is provided by} graph-body-print
21645 (tic-width (* symbol-width X-axis-label-spacing))
21646 (X-length (length numbers-list))
21652 ;; @r{Make a string of blanks.}
21653 (- (* symbol-width X-axis-label-spacing)
21654 (length X-axis-tic-symbol))
21658 ;; @r{Concatenate blanks with tic symbol.}
21659 X-axis-tic-symbol))
21661 (if (zerop (% X-length tic-width))
21662 (/ X-length tic-width)
21663 (1+ (/ X-length tic-width)))))
21667 (print-X-axis-tic-line
21668 tic-number leading-spaces X-tic)
21670 (print-X-axis-numbered-line
21671 tic-number leading-spaces horizontal-step)))
21677 (defun one-fiftieth (full-range)
21678 "Return list, each number of which is 1/50th previous."
21679 (mapcar (lambda (arg) (/ arg 50)) full-range))
21686 (numbers-list &optional vertical-step horizontal-step)
21687 "Print labeled bar graph of the NUMBERS-LIST.
21688 The numbers-list consists of the Y-axis values.
21692 Optionally, VERTICAL-STEP, a positive integer,
21693 specifies how much a Y axis label increments for
21694 each line. For example, a step of 5 means that
21695 each row is five units.
21699 Optionally, HORIZONTAL-STEP, a positive integer,
21700 specifies how much an X axis label increments for
21702 (let* ((symbol-width (length graph-blank))
21703 ;; @code{height} @r{is both the largest number}
21704 ;; @r{and the number with the most digits.}
21705 (height (apply 'max numbers-list))
21708 (height-of-top-line
21709 (if (zerop (% height Y-axis-label-spacing))
21712 (* (1+ (/ height Y-axis-label-spacing))
21713 Y-axis-label-spacing)))
21716 (vertical-step (or vertical-step 1))
21717 (full-Y-label-width
21721 (* height-of-top-line vertical-step))
21727 height-of-top-line full-Y-label-width vertical-step)
21729 numbers-list height-of-top-line symbol-width)
21730 (print-X-axis numbers-list horizontal-step)))
21737 @node Final printed graph
21738 @appendixsubsec The Printed Graph
21740 When made and installed, you can call the @code{print-graph} command
21746 (print-graph fiftieth-list-for-graph 50 10)
21776 50 - ***************** * *
21778 10 50 100 150 200 250 300 350
21785 The largest group of functions contain 10--19 words and symbols each.
21787 @node Free Software and Free Manuals
21788 @appendix Free Software and Free Manuals
21790 @strong{by Richard M. Stallman}
21793 The biggest deficiency in free operating systems is not in the
21794 software---it is the lack of good free manuals that we can include in
21795 these systems. Many of our most important programs do not come with
21796 full manuals. Documentation is an essential part of any software
21797 package; when an important free software package does not come with a
21798 free manual, that is a major gap. We have many such gaps today.
21800 Once upon a time, many years ago, I thought I would learn Perl. I got
21801 a copy of a free manual, but I found it hard to read. When I asked
21802 Perl users about alternatives, they told me that there were better
21803 introductory manuals---but those were not free.
21805 Why was this? The authors of the good manuals had written them for
21806 O'Reilly Associates, which published them with restrictive terms---no
21807 copying, no modification, source files not available---which exclude
21808 them from the free software community.
21810 That wasn't the first time this sort of thing has happened, and (to
21811 our community's great loss) it was far from the last. Proprietary
21812 manual publishers have enticed a great many authors to restrict their
21813 manuals since then. Many times I have heard a GNU user eagerly tell me
21814 about a manual that he is writing, with which he expects to help the
21815 GNU project---and then had my hopes dashed, as he proceeded to explain
21816 that he had signed a contract with a publisher that would restrict it
21817 so that we cannot use it.
21819 Given that writing good English is a rare skill among programmers, we
21820 can ill afford to lose manuals this way.
21822 Free documentation, like free software, is a matter of freedom, not
21823 price. The problem with these manuals was not that O'Reilly Associates
21824 charged a price for printed copies---that in itself is fine. The Free
21825 Software Foundation @uref{http://shop.fsf.org, sells printed copies} of
21826 free @uref{http://www.gnu.org/doc/doc.html, GNU manuals}, too.
21827 But GNU manuals are available in source code form, while these manuals
21828 are available only on paper. GNU manuals come with permission to copy
21829 and modify; the Perl manuals do not. These restrictions are the
21832 The criterion for a free manual is pretty much the same as for free
21833 software: it is a matter of giving all users certain
21834 freedoms. Redistribution (including commercial redistribution) must be
21835 permitted, so that the manual can accompany every copy of the program,
21836 on-line or on paper. Permission for modification is crucial too.
21838 As a general rule, I don't believe that it is essential for people to
21839 have permission to modify all sorts of articles and books. The issues
21840 for writings are not necessarily the same as those for software. For
21841 example, I don't think you or I are obliged to give permission to
21842 modify articles like this one, which describe our actions and our
21845 But there is a particular reason why the freedom to modify is crucial
21846 for documentation for free software. When people exercise their right
21847 to modify the software, and add or change its features, if they are
21848 conscientious they will change the manual too---so they can provide
21849 accurate and usable documentation with the modified program. A manual
21850 which forbids programmers to be conscientious and finish the job, or
21851 more precisely requires them to write a new manual from scratch if
21852 they change the program, does not fill our community's needs.
21854 While a blanket prohibition on modification is unacceptable, some
21855 kinds of limits on the method of modification pose no problem. For
21856 example, requirements to preserve the original author's copyright
21857 notice, the distribution terms, or the list of authors, are ok. It is
21858 also no problem to require modified versions to include notice that
21859 they were modified, even to have entire sections that may not be
21860 deleted or changed, as long as these sections deal with nontechnical
21861 topics. (Some GNU manuals have them.)
21863 These kinds of restrictions are not a problem because, as a practical
21864 matter, they don't stop the conscientious programmer from adapting the
21865 manual to fit the modified program. In other words, they don't block
21866 the free software community from making full use of the manual.
21868 However, it must be possible to modify all the technical content of
21869 the manual, and then distribute the result in all the usual media,
21870 through all the usual channels; otherwise, the restrictions do block
21871 the community, the manual is not free, and so we need another manual.
21873 Unfortunately, it is often hard to find someone to write another
21874 manual when a proprietary manual exists. The obstacle is that many
21875 users think that a proprietary manual is good enough---so they don't
21876 see the need to write a free manual. They do not see that the free
21877 operating system has a gap that needs filling.
21879 Why do users think that proprietary manuals are good enough? Some have
21880 not considered the issue. I hope this article will do something to
21883 Other users consider proprietary manuals acceptable for the same
21884 reason so many people consider proprietary software acceptable: they
21885 judge in purely practical terms, not using freedom as a
21886 criterion. These people are entitled to their opinions, but since
21887 those opinions spring from values which do not include freedom, they
21888 are no guide for those of us who do value freedom.
21890 Please spread the word about this issue. We continue to lose manuals
21891 to proprietary publishing. If we spread the word that proprietary
21892 manuals are not sufficient, perhaps the next person who wants to help
21893 GNU by writing documentation will realize, before it is too late, that
21894 he must above all make it free.
21896 We can also encourage commercial publishers to sell free, copylefted
21897 manuals instead of proprietary ones. One way you can help this is to
21898 check the distribution terms of a manual before you buy it, and prefer
21899 copylefted manuals to non-copylefted ones.
21903 Note: The Free Software Foundation maintains a page on its Web site
21904 that lists free books available from other publishers:@*
21905 @uref{http://www.gnu.org/doc/other-free-books.html}
21907 @node GNU Free Documentation License
21908 @appendix GNU Free Documentation License
21910 @cindex FDL, GNU Free Documentation License
21911 @include doclicense.texi
21917 MENU ENTRY: NODE NAME.
21923 @c Place biographical information on right-hand (verso) page
21926 \par\vfill\supereject
21928 \global\evenheadline={\hfil} \global\evenfootline={\hfil}
21929 \global\oddheadline={\hfil} \global\oddfootline={\hfil}
21932 % \par\vfill\supereject
21933 \global\evenheadline={\hfil} \global\evenfootline={\hfil}
21934 \global\oddheadline={\hfil} \global\oddfootline={\hfil}
21935 %\page\hbox{}%\page
21936 %\page\hbox{}%\page
21943 @c ================ Biographical information ================
21947 @center About the Author
21952 @node About the Author
21953 @unnumbered About the Author
21957 Robert J. Chassell has worked with GNU Emacs since 1985. He writes
21958 and edits, teaches Emacs and Emacs Lisp, and speaks throughout the
21959 world on software freedom. Chassell was a founding Director and
21960 Treasurer of the Free Software Foundation, Inc. He is co-author of
21961 the @cite{Texinfo} manual, and has edited more than a dozen other
21962 books. He graduated from Cambridge University, in England. He has an
21963 abiding interest in social and economic history and flies his own
21970 @c @c Prevent page number on blank verso, so eject it first.
21972 @c \par\vfill\supereject
21977 @c @evenheading @thispage @| @| @thistitle
21978 @c @oddheading @| @| @thispage