@c This is part of the Emacs manual.@c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 2000, 2001,@c 2002, 2003, 2004, 2005 Free Software Foundation, Inc.@c See file emacs.texi for copying conditions.@iftex@chapter Miscellaneous Commands This chapter contains several brief topics that do not fit anywhereelse: reading netnews, running shell commands and shell subprocesses,using a single shared Emacs for utilities that expect to run an editoras a subprocess, printing hardcopy, sorting text, narrowing display topart of the buffer, editing double-column files and binary files, savingan Emacs session for later resumption, emulating other editors, andvarious diversions and amusements.@end iftex@ifnottex@raisesections@end ifnottex@node Gnus, Shell, Calendar/Diary, Top@section Gnus@cindex Gnus@cindex reading netnewsGnus is an Emacs package primarily designed for reading and postingUsenet news. It can also be used to read and respond to messages from anumber of other sources---mail, remote directories, digests, and so on.Here we introduce Gnus and describe several basic features.@ifinfoFor full details, see @ref{Top, Gnus,, gnus, The Gnus Manual}.@end ifinfo@iftexFor full details on Gnus, type @kbd{M-x info} and then select the Gnusmanual.@end iftex@findex gnusTo start Gnus, type @kbd{M-x gnus @key{RET}}.@menu* Buffers of Gnus:: The group, summary, and article buffers.* Gnus Startup:: What you should know about starting Gnus.* Summary of Gnus:: A short description of the basic Gnus commands.@end menu@node Buffers of Gnus@subsection Gnus BuffersAs opposed to most normal Emacs packages, Gnus uses a number ofdifferent buffers to display information and to receive commands. Thethree buffers users spend most of their time in are the @dfn{groupbuffer}, the @dfn{summary buffer} and the @dfn{article buffer}.The @dfn{group buffer} contains a list of groups. This is the firstbuffer Gnus displays when it starts up. It normally displays only thegroups to which you subscribe and that contain unread articles. Usethis buffer to select a specific group.The @dfn{summary buffer} lists one line for each article in a singlegroup. By default, the author, the subject and the line number aredisplayed for each article, but this is customizable, like most aspectsof Gnus display. The summary buffer is created when you select a groupin the group buffer, and is killed when you exit the group. Use thisbuffer to select an article.The @dfn{article buffer} displays the article. In normal Gnus usage,you don't select this buffer---all useful article-oriented commands workin the summary buffer. But you can select the article buffer, andexecute all Gnus commands from that buffer, if you want to.@node Gnus Startup@subsection When Gnus Starts UpAt startup, Gnus reads your @file{.newsrc} news initialization fileand attempts to communicate with the local news server, which is arepository of news articles. The news server need not be the samecomputer you are logged in on.If you start Gnus and connect to the server, but do not see anynewsgroups listed in the group buffer, type @kbd{L} or @kbd{A k} to geta listing of all the groups. Then type @kbd{u} to togglesubscription to groups.The first time you start Gnus, Gnus subscribes you to a few selectedgroups. All other groups start out as @dfn{killed groups} for you; youcan list them with @kbd{A k}. All new groups that subsequently come toexist at the news server become @dfn{zombie groups} for you; type @kbd{Az} to list them. You can subscribe to a group shown in these listsusing the @kbd{u} command.When you quit Gnus with @kbd{q}, it automatically records in your@file{.newsrc} and @file{.newsrc.eld} initialization files thesubscribed or unsubscribed status of all groups. You should normallynot edit these files manually, but you may if you know how.@node Summary of Gnus@subsection Summary of Gnus CommandsReading news is a two-step process:@enumerate@itemChoose a group in the group buffer.@itemSelect articles from the summary buffer. Each article selected isdisplayed in the article buffer in a large window, below the summarybuffer in its small window.@end enumerate Each Gnus buffer has its own special commands; however, the meaningsof any given key in the various Gnus buffers are usually analogous, evenif not identical. Here are commands for the group and summary buffers:@table @kbd@kindex q @r{(Gnus Group mode)}@findex gnus-group-exit@item qIn the group buffer, update your @file{.newsrc} initialization fileand quit Gnus.In the summary buffer, exit the current group and return to thegroup buffer. Thus, typing @kbd{q} twice quits Gnus.@kindex L @r{(Gnus Group mode)}@findex gnus-group-list-all-groups@item LIn the group buffer, list all the groups available on your newsserver (except those you have killed). This may be a long list!@kindex l @r{(Gnus Group mode)}@findex gnus-group-list-groups@item lIn the group buffer, list only the groups to which you subscribe andwhich contain unread articles.@kindex u @r{(Gnus Group mode)}@findex gnus-group-unsubscribe-current-group@cindex subscribe groups@cindex unsubscribe groups@item uIn the group buffer, unsubscribe from (or subscribe to) the group listedin the line that point is on. When you quit Gnus by typing @kbd{q},Gnus lists in your @file{.newsrc} file which groups you have subscribedto. The next time you start Gnus, you won't see this group,because Gnus normally displays only subscribed-to groups.@kindex C-k @r{(Gnus)}@findex gnus-group-kill-group@item C-kIn the group buffer, ``kill'' the current line's group---don'teven list it in @file{.newsrc} from now on. This affects futureGnus sessions as well as the present session.When you quit Gnus by typing @kbd{q}, Gnus writes informationin the file @file{.newsrc} describing all newsgroups except those youhave ``killed.''@kindex SPC @r{(Gnus)}@findex gnus-group-read-group@item @key{SPC}In the group buffer, select the group on the line under the cursorand display the first unread article in that group.@need 1000In the summary buffer,@itemize @bullet@itemSelect the article on the line under the cursor if none is selected.@itemScroll the text of the selected article (if there is one).@itemSelect the next unread article if at the end of the current article.@end itemizeThus, you can move through all the articles by repeatedly typing @key{SPC}.@kindex DEL @r{(Gnus)}@item @key{DEL}In the group buffer, move point to the previous group containingunread articles.@findex gnus-summary-prev-pageIn the summary buffer, scroll the text of the article backwards.@kindex n @r{(Gnus)}@findex gnus-group-next-unread-group@findex gnus-summary-next-unread-article@item nMove point to the next unread group, or select the next unread article.@kindex p @r{(Gnus)}@findex gnus-group-prev-unread-group@findex gnus-summary-prev-unread-article@item pMove point to the previous unread group, or select the previousunread article.@kindex C-n @r{(Gnus Group mode)}@findex gnus-group-next-group@kindex C-p @r{(Gnus Group mode)}@findex gnus-group-prev-group@kindex C-n @r{(Gnus Summary mode)}@findex gnus-summary-next-subject@kindex C-p @r{(Gnus Summary mode)}@findex gnus-summary-prev-subject@item C-n@itemx C-pMove point to the next or previous item, even if it is marked as read.This does not select the article or group on that line.@kindex s @r{(Gnus Summary mode)}@findex gnus-summary-isearch-article@item sIn the summary buffer, do an incremental search of the current text inthe article buffer, just as if you switched to the article buffer andtyped @kbd{C-s}.@kindex M-s @r{(Gnus Summary mode)}@findex gnus-summary-search-article-forward@item M-s @var{regexp} @key{RET}In the summary buffer, search forward for articles containing a matchfor @var{regexp}.@end table@ignore@node Where to Look@subsection Where to Look Further@c Too many references to the name of the manual if done with xref in TeX!Gnus is powerful and customizable. Here are references to a few@ifinfoadditional topics:@end ifinfo@iftexadditional topics in @cite{The Gnus Manual}:@itemize @bullet@itemFollow discussions on specific topics.@*See section ``Threading.''@itemRead digests. See section ``Document Groups.''@itemRefer to and jump to the parent of the current article.@*See section ``Finding the Parent.''@itemRefer to articles by using Message-IDs included in the messages.@*See section ``Article Keymap.''@itemSave articles. See section ``Saving Articles.''@itemHave Gnus score articles according to various criteria, like authorname, subject, or string in the body of the articles.@*See section ``Scoring.''@itemSend an article to a newsgroup.@*See section ``Composing Messages.''@end itemize@end iftex@ifinfo@itemize @bullet@itemFollow discussions on specific topics.@*@xref{Threading, , Reading Based on Conversation Threads,gnus, The Gnus Manual}.@itemRead digests. @xref{Document Groups, , , gnus, The Gnus Manual}.@itemRefer to and jump to the parent of the current article.@*@xref{Finding the Parent, , , gnus, The Gnus Manual}.@itemRefer to articles by using Message-IDs included in the messages.@*@xref{Article Keymap, , , gnus, The Gnus Manual}.@itemSave articles. @xref{Saving Articles, , , gnus, The Gnus Manual}.@itemHave Gnus score articles according to various criteria, like authorname, subject, or string in the body of the articles.@*@xref{Scoring, , , gnus, The Gnus Manual}.@itemSend an article to a newsgroup.@*@xref{Composing Messages, , , gnus, The Gnus Manual}.@end itemize@end ifinfo@end ignore@node Shell, Emacs Server, Gnus, Top@section Running Shell Commands from Emacs@cindex subshell@cindex shell commands Emacs has commands for passing single command lines to inferior shellprocesses; it can also run a shell interactively with input and outputto an Emacs buffer named @samp{*shell*} or run a shell inside a terminalemulator window.There is a shell implemented entirely in Emacs, documented in a separatemanual. @xref{Top,Eshell,Eshell, eshell, Eshell: The Emacs Shell}.@table @kbd@item M-! @var{cmd} @key{RET}Run the shell command line @var{cmd} and display the output(@code{shell-command}).@item M-| @var{cmd} @key{RET}Run the shell command line @var{cmd} with region contents as input;optionally replace the region with the output(@code{shell-command-on-region}).@item M-x shellRun a subshell with input and output through an Emacs buffer.You can then give commands interactively.@item M-x termRun a subshell with input and output through an Emacs buffer.You can then give commands interactively.Full terminal emulation is available.@item M-x eshell@findex eshellStart the Emacs shell.@end table@menu* Single Shell:: How to run one shell command and return.* Interactive Shell:: Permanent shell taking input via Emacs.* Shell Mode:: Special Emacs commands used with permanent shell.* Shell Prompts:: Two ways to recognize shell prompts.* History: Shell History. Repeating previous commands in a shell buffer.* Directory Tracking:: Keeping track when the subshell changes directory.* Options: Shell Options. Options for customizing Shell mode.* Terminal emulator:: An Emacs window as a terminal emulator.* Term Mode:: Special Emacs commands used in Term mode.* Paging in Term:: Paging in the terminal emulator.* Remote Host:: Connecting to another computer.@end menu@node Single Shell@subsection Single Shell Commands@kindex M-!@findex shell-command @kbd{M-!} (@code{shell-command}) reads a line of text using theminibuffer and executes it as a shell command in a subshell made justfor that command. Standard input for the command comes from the nulldevice. If the shell command produces any output, the output appearseither in the echo area (if it is short), or in an Emacs buffer named@samp{*Shell Command Output*}, which is displayed in another windowbut not selected (if the output is long). For instance, one way to decompress a file @file{foo.gz} from Emacsis to type @kbd{M-! gunzip foo.gz @key{RET}}. That shell commandnormally creates the file @file{foo} and produces no terminal output. A numeric argument, as in @kbd{M-1 M-!}, says to insert terminaloutput into the current buffer instead of a separate buffer. It putspoint before the output, and sets the mark after the output. Forinstance, @kbd{M-1 M-! gunzip < foo.gz @key{RET}} would insert theuncompressed equivalent of @file{foo.gz} into the current buffer. If the shell command line ends in @samp{&}, it runs asynchronously.For a synchronous shell command, @code{shell-command} returns thecommand's exit status (0 means success), when it is called from a Lispprogram. You do not get any status information for an asynchronouscommand, since it hasn't finished yet.@kindex M-|@findex shell-command-on-region @kbd{M-|} (@code{shell-command-on-region}) is like @kbd{M-!} butpasses the contents of the region as the standard input to the shellcommand, instead of no input. If a numeric argument is used, meaninginsert the output in the current buffer, then the old region is deletedfirst and the output replaces it as the contents of the region. Itreturns the command's exit status when it is called from a Lisp program. One use for @kbd{M-|} is to run @code{gpg} to see what keys are inthe buffer. For instance, if the buffer contains a GPG key, type@kbd{C-x h M-| gpg @key{RET}} to feed the entire buffer contentsto the @code{gpg} program. That program will ignore everything exceptthe encoded keys, and will output a list of the keys it contains.@vindex shell-file-name Both @kbd{M-!} and @kbd{M-|} use @code{shell-file-name} to specify theshell to use. This variable is initialized based on your @env{SHELL}environment variable when Emacs is started. If the file name does notspecify a directory, the directories in the list @code{exec-path} aresearched; this list is initialized based on the environment variable@env{PATH} when Emacs is started. Your @file{.emacs} file can overrideeither or both of these default initializations.@refill Both @kbd{M-!} and @kbd{M-|} wait for the shell command to complete,unless you end the command with @samp{&} to make it asynchronous. Tostop waiting, type @kbd{C-g} to quit; that terminates the shellcommand with the signal @code{SIGINT}---the same signal that @kbd{C-c}normally generates in the shell. Emacs waits until the commandactually terminates. If the shell command doesn't stop (because itignores the @code{SIGINT} signal), type @kbd{C-g} again; this sendsthe command a @code{SIGKILL} signal which is impossible to ignore. Asynchronous commands ending in @samp{&} feed their output intothe buffer @samp{*Async Shell Command*}. Output arrives in thatbuffer regardless of whether it is visible in a window. To specify a coding system for @kbd{M-!} or @kbd{M-|}, use the command@kbd{C-x @key{RET} c} immediately beforehand. @xref{Specify Coding}.@vindex shell-command-default-error-buffer Error output from the command is normally intermixed with the regularoutput. If you set the variable@code{shell-command-default-error-buffer} to a string, which is a buffername, error output is inserted before point in the buffer of that name.@node Interactive Shell@subsection Interactive Inferior Shell@findex shell To run a subshell interactively, putting its typescript in an Emacsbuffer, use @kbd{M-x shell}. This creates (or reuses) a buffer named@samp{*shell*} and runs a subshell with input coming from and output goingto that buffer. That is to say, any ``terminal output'' from the subshellgoes into the buffer, advancing point, and any ``terminal input'' forthe subshell comes from text in the buffer. To give input to the subshell,go to the end of the buffer and type the input, terminated by @key{RET}. Emacs does not wait for the subshell to do anything. You can switchwindows or buffers and edit them while the shell is waiting, or while it isrunning a command. Output from the subshell waits until Emacs has time toprocess it; this happens whenever Emacs is waiting for keyboard input orfor time to elapse.@cindex @code{comint-highlight-input} face@cindex @code{comint-highlight-prompt} face Input lines, once you submit them, are displayed using the face@code{comint-highlight-input}, and prompts are displayed using theface @code{comint-highlight-prompt}. This makes it easier to seeprevious input lines in the buffer. @xref{Faces}. To make multiple subshells, you can invoke @kbd{M-x shell} with aprefix argument (e.g. @kbd{C-u M-x shell}), which will read a buffername and create (or reuse) a subshell in that buffer. You can alsorename the @samp{*shell*} buffer using @kbd{M-x rename-uniquely}, thencreate a new @samp{*shell*} buffer using plain @kbd{M-x shell}. All thesubshells in different buffers run independently and in parallel.@vindex explicit-shell-file-name@cindex environment variables for subshells@cindex @env{ESHELL} environment variable@cindex @env{SHELL} environment variable The file name used to load the subshell is the value of the variable@code{explicit-shell-file-name}, if that is non-@code{nil}. Otherwise,the environment variable @env{ESHELL} is used, or the environmentvariable @env{SHELL} if there is no @env{ESHELL}. If the file namespecified is relative, the directories in the list @code{exec-path} aresearched; this list is initialized based on the environment variable@env{PATH} when Emacs is started. Your @file{.emacs} file can overrideeither or both of these default initializations. Emacs sends the new shell the contents of the file@file{~/.emacs_@var{shellname}} as input, if it exists, where@var{shellname} is the name of the file that the shell was loadedfrom. For example, if you use bash, the file sent to it is@file{~/.emacs_bash}. To specify a coding system for the shell, you can use the command@kbd{C-x @key{RET} c} immediately before @kbd{M-x shell}. You can alsospecify a coding system after starting the shell by using @kbd{C-x@key{RET} p} in the shell buffer. @xref{Specify Coding}.@cindex @env{EMACS} environment variable Unless the environment variable @env{EMACS} is already defined,Emacs defines it in the subshell, with value @code{t}. A shell scriptcan check this variable to determine whether it has been run from anEmacs subshell.@node Shell Mode@subsection Shell Mode@cindex Shell mode@cindex mode, Shell Shell buffers use Shell mode, which defines several special keysattached to the @kbd{C-c} prefix. They are chosen to resemble the usualediting and job control characters present in shells that are not underEmacs, except that you must type @kbd{C-c} first. Here is a complete listof the special key bindings of Shell mode:@table @kbd@item @key{RET}@kindex RET @r{(Shell mode)}@findex comint-send-inputAt end of buffer send line as input; otherwise, copy current line toend of buffer and send it (@code{comint-send-input}). When a line iscopied, any prompt at the beginning of the line (text output byprograms preceding your input) is omitted. @xref{Shell Prompts}, forhow Shell mode recognizes prompts.@item @key{TAB}@kindex TAB @r{(Shell mode)}@findex comint-dynamic-completeComplete the command name or file name before point in the shell buffer(@code{comint-dynamic-complete}). @key{TAB} also completes historyreferences (@pxref{History References}) and environment variable names.@vindex shell-completion-fignore@vindex comint-completion-fignoreThe variable @code{shell-completion-fignore} specifies a list of filename extensions to ignore in Shell mode completion. The defaultsetting is @code{nil}, but some users prefer @code{("~" "#" "%")} toignore file names ending in @samp{~}, @samp{#} or @samp{%}. Otherrelated Comint modes use the variable @code{comint-completion-fignore}instead.@item M-?@kindex M-? @r{(Shell mode)}@findex comint-dynamic-list-filename@dots{}Display temporarily a list of the possible completions of the file namebefore point in the shell buffer(@code{comint-dynamic-list-filename-completions}).@item C-d@kindex C-d @r{(Shell mode)}@findex comint-delchar-or-maybe-eofEither delete a character or send @acronym{EOF}(@code{comint-delchar-or-maybe-eof}). Typed at the end of the shellbuffer, @kbd{C-d} sends @acronym{EOF} to the subshell. Typed at any otherposition in the buffer, @kbd{C-d} deletes a character as usual.@item C-c C-a@kindex C-c C-a @r{(Shell mode)}@findex comint-bol-or-process-markMove to the beginning of the line, but after the prompt if any(@code{comint-bol-or-process-mark}). If you repeat this command twicein a row, the second time it moves back to the process mark, which isthe beginning of the input that you have not yet sent to the subshell.(Normally that is the same place---the end of the prompt on thisline---but after @kbd{C-c @key{SPC}} the process mark may be in aprevious line.)@item C-c @key{SPC}Accumulate multiple lines of input, then send them together. Thiscommand inserts a newline before point, but does not send the precedingtext as input to the subshell---at least, not yet. Both lines, the onebefore this newline and the one after, will be sent together (along withthe newline that separates them), when you type @key{RET}.@item C-c C-u@kindex C-c C-u @r{(Shell mode)}@findex comint-kill-inputKill all text pending at end of buffer to be sent as input(@code{comint-kill-input}). If point is not at end of buffer,this only kills the part of this text that precedes point.@item C-c C-w@kindex C-c C-w @r{(Shell mode)}Kill a word before point (@code{backward-kill-word}).@item C-c C-c@kindex C-c C-c @r{(Shell mode)}@findex comint-interrupt-subjobInterrupt the shell or its current subjob if any(@code{comint-interrupt-subjob}). This command also killsany shell input pending in the shell buffer and not yet sent.@item C-c C-z@kindex C-c C-z @r{(Shell mode)}@findex comint-stop-subjobStop the shell or its current subjob if any (@code{comint-stop-subjob}).This command also kills any shell input pending in the shell buffer andnot yet sent.@item C-c C-\@findex comint-quit-subjob@kindex C-c C-\ @r{(Shell mode)}Send quit signal to the shell or its current subjob if any(@code{comint-quit-subjob}). This command also kills any shell inputpending in the shell buffer and not yet sent.@item C-c C-o@kindex C-c C-o @r{(Shell mode)}@findex comint-delete-outputDelete the last batch of output from a shell command(@code{comint-delete-output}). This is useful if a shell command spewsout lots of output that just gets in the way. This command used to becalled @code{comint-kill-output}.@item C-c C-s@kindex C-c C-s @r{(Shell mode)}@findex comint-write-outputWrite the last batch of output from a shell command to a file(@code{comint-write-output}). With a prefix argument, the file isappended to instead. Any prompt at the end of the output is notwritten.@item C-c C-r@itemx C-M-l@kindex C-c C-r @r{(Shell mode)}@kindex C-M-l @r{(Shell mode)}@findex comint-show-outputScroll to display the beginning of the last batch of output at the topof the window; also move the cursor there (@code{comint-show-output}).@item C-c C-e@kindex C-c C-e @r{(Shell mode)}@findex comint-show-maximum-outputScroll to put the end of the buffer at the bottom of the window(@code{comint-show-maximum-output}).@item C-c C-f@kindex C-c C-f @r{(Shell mode)}@findex shell-forward-command@vindex shell-command-regexpMove forward across one shell command, but not beyond the current line(@code{shell-forward-command}). The variable @code{shell-command-regexp}specifies how to recognize the end of a command.@item C-c C-b@kindex C-c C-b @r{(Shell mode)}@findex shell-backward-commandMove backward across one shell command, but not beyond the current line(@code{shell-backward-command}).@item M-x dirsAsk the shell what its current directory is, so that Emacs can agreewith the shell.@item M-x send-invisible @key{RET} @var{text} @key{RET}@findex send-invisibleSend @var{text} as input to the shell, after reading it withoutechoing. This is useful when a shell command runs a program that asksfor a password.Please note that Emacs will not echo passwords by default. If youreally want them to be echoed, evaluate the following Lispexpression:@example(remove-hook 'comint-output-filter-functions 'comint-watch-for-password-prompt)@end example@item M-x comint-continue-subjob@findex comint-continue-subjobContinue the shell process. This is useful if you accidentally suspendthe shell process.@footnote{You should not suspend the shell process.Suspending a subjob of the shell is a completely different matter---thatis normal practice, but you must use the shell to continue the subjob;this command won't do it.}@item M-x comint-strip-ctrl-m@findex comint-strip-ctrl-mDiscard all control-M characters from the current group of shell output.The most convenient way to use this command is to make it runautomatically when you get output from the subshell. To do that,evaluate this Lisp expression:@example(add-hook 'comint-output-filter-functions 'comint-strip-ctrl-m)@end example@item M-x comint-truncate-buffer@findex comint-truncate-bufferThis command truncates the shell buffer to a certain maximum number oflines, specified by the variable @code{comint-buffer-maximum-size}.Here's how to do this automatically each time you get output from thesubshell:@example(add-hook 'comint-output-filter-functions 'comint-truncate-buffer)@end example@end table@cindex Comint mode@cindex mode, Comint Shell mode is a derivative of Comint mode, a general-purpose mode forcommunicating with interactive subprocesses. Most of the features ofShell mode actually come from Comint mode, as you can see from thecommand names listed above. The special features of Shell mode includethe directory tracking feature, and a few user commands. Other Emacs features that use variants of Comint mode include GUD(@pxref{Debuggers}) and @kbd{M-x run-lisp} (@pxref{External Lisp}).@findex comint-run You can use @kbd{M-x comint-run} to execute any program of your choicein a subprocess using unmodified Comint mode---without thespecializations of Shell mode.@node Shell Prompts@subsection Shell Prompts@vindex shell-prompt-pattern@vindex comint-prompt-regexp@vindex comint-use-prompt-regexp@cindex prompt, shell A prompt is text output by a program to show that it is ready toaccept new user input. Normally, Comint mode (and thus Shell mode)considers the prompt to be any text output by a program at thebeginning of an input line. However, if the variable@code{comint-use-prompt-regexp} is non-@code{nil}, then Comint modeuses a regular expression to recognize prompts. In Shell mode,@code{shell-prompt-pattern} specifies the regular expression. The value of @code{comint-use-prompt-regexp} also affects manymotion and paragraph commands. If the value is non-@code{nil}, thegeneral Emacs motion commands behave as they normally do in bufferswithout special text properties. However, if the value is @code{nil},the default, then Comint mode divides the buffer into two types of``fields'' (ranges of consecutive characters having the same@code{field} text property): input and output. Prompts are part ofthe output. Most Emacs motion commands do not cross field boundaries,unless they move over multiple lines. For instance, when point is ininput on the same line as a prompt, @kbd{C-a} puts point at thebeginning of the input if @code{comint-use-prompt-regexp} is@code{nil} and at the beginning of the line otherwise. In Shell mode, only shell prompts start new paragraphs. Thus, aparagraph consists of a prompt and the input and output that followit. However, if @code{comint-use-prompt-regexp} is @code{nil}, thedefault, most paragraph commands do not cross field boundaries. Thismeans that prompts, ranges of input, and ranges of non-prompt outputbehave mostly like separate paragraphs; with this setting, numericarguments to most paragraph commands yield essentially undefinedbehavior. For the purpose of finding paragraph boundaries, Shell modeuses @code{shell-prompt-pattern}, regardless of@code{comint-use-prompt-regexp}.@node Shell History@subsection Shell Command History Shell buffers support three ways of repeating earlier commands. Youcan use keys like those used for the minibuffer history; these workmuch as they do in the minibuffer, inserting text from prior commandswhile point remains always at the end of the buffer. You can movethrough the buffer to previous inputs in their original place, thenresubmit them or copy them to the end. Or you can use a@samp{!}-style history reference.@menu* Ring: Shell Ring. Fetching commands from the history list.* Copy: Shell History Copying. Moving to a command and then copying it.* History References:: Expanding @samp{!}-style history references.@end menu@node Shell Ring@subsubsection Shell History Ring@table @kbd@findex comint-previous-input@kindex M-p @r{(Shell mode)}@item M-p@itemx C-@key{UP}Fetch the next earlier old shell command.@kindex M-n @r{(Shell mode)}@findex comint-next-input@item M-n@itemx C-@key{DOWN}Fetch the next later old shell command.@kindex M-r @r{(Shell mode)}@kindex M-s @r{(Shell mode)}@findex comint-previous-matching-input@findex comint-next-matching-input@item M-r @var{regexp} @key{RET}@itemx M-s @var{regexp} @key{RET}Search backwards or forwards for old shell commands that match @var{regexp}.@item C-c C-x@kindex C-c C-x @r{(Shell mode)}@findex comint-get-next-from-historyFetch the next subsequent command from the history.@item C-c .@kindex C-c . @r{(Shell mode)}@findex comint-input-previous-argumentFetch one argument from an old shell command.@item C-c C-l@kindex C-c C-l @r{(Shell mode)}@findex comint-dynamic-list-input-ringDisplay the buffer's history of shell commands in another window(@code{comint-dynamic-list-input-ring}).@end table Shell buffers provide a history of previously entered shell commands. Toreuse shell commands from the history, use the editing commands @kbd{M-p},@kbd{M-n}, @kbd{M-r} and @kbd{M-s}. These work just like the minibufferhistory commands except that they operate on the text at the end of theshell buffer, where you would normally insert text to send to the shell. @kbd{M-p} fetches an earlier shell command to the end of the shellbuffer. Successive use of @kbd{M-p} fetches successively earliershell commands, each replacing any text that was already present aspotential shell input. @kbd{M-n} does likewise except that it findssuccessively more recent shell commands from the buffer.@kbd{C-@key{UP}} works like @kbd{M-p}, and @kbd{C-@key{DOWN}} like@kbd{M-n}. The history search commands @kbd{M-r} and @kbd{M-s} read a regularexpression and search through the history for a matching command. Asidefrom the choice of which command to fetch, they work just like @kbd{M-p}and @kbd{M-n}. If you enter an empty regexp, these commands reuse thesame regexp used last time. When you find the previous input you want, you can resubmit it bytyping @key{RET}, or you can edit it first and then resubmit it if youwish. Often it is useful to reexecute several successive shell commands thatwere previously executed in sequence. To do this, first find andreexecute the first command of the sequence. Then type @kbd{C-c C-x};that will fetch the following command---the one that follows the commandyou just repeated. Then type @key{RET} to reexecute this command. Youcan reexecute several successive commands by typing @kbd{C-c C-x@key{RET}} over and over. The command @kbd{C-c .}@: (@code{comint-input-previous-argument})copies an individual argument from a previous command, like @kbd{ESC.} in Bash. The simplest use copies the last argument from theprevious shell command. With a prefix argument @var{n}, it copies the@var{n}th argument instead. Repeating @kbd{C-c .} copies from anearlier shell command instead, always using the same value of @var{n}(don't give a prefix argument when you repeat the @kbd{C-c .}command). These commands get the text of previous shell commands from a specialhistory list, not from the shell buffer itself. Thus, editing the shellbuffer, or even killing large parts of it, does not affect the historythat these commands access.@vindex shell-input-ring-file-name Some shells store their command histories in files so that you canrefer to commands from previous shell sessions. Emacs readsthe command history file for your chosen shell, to initialize its owncommand history. The file name is @file{~/.bash_history} for bash,@file{~/.sh_history} for ksh, and @file{~/.history} for other shells.@node Shell History Copying@subsubsection Shell History Copying@table @kbd@kindex C-c C-p @r{(Shell mode)}@findex comint-previous-prompt@item C-c C-pMove point to the previous prompt (@code{comint-previous-prompt}).@kindex C-c C-n @r{(Shell mode)}@findex comint-next-prompt@item C-c C-nMove point to the following prompt (@code{comint-next-prompt}).@kindex C-c RET @r{(Shell mode)}@findex comint-insert-input@item C-c @key{RET}Copy the input command which point is in, inserting the copy at the endof the buffer (@code{comint-insert-input}). This is useful if youmove point back to a previous command. After you copy the command, youcan submit the copy as input with @key{RET}. If you wish, you canedit the copy before resubmitting it.@item Mouse-2Copy the input command that you click on, inserting the copy at the endof the buffer.@end table Moving to a previous input and then copying it with @kbd{C-c@key{RET}} or @kbd{Mouse-2} produces the same results---the samebuffer contents---that you would get by using @kbd{M-p} enough timesto fetch that previous input from the history list. However, @kbd{C-c@key{RET}} copies the text from the buffer, which can be differentfrom what is in the history list if you edit the input text in thebuffer after it has been sent.@node History References@subsubsection Shell History References@cindex history reference Various shells including csh and bash support @dfn{historyreferences} that begin with @samp{!} and @samp{^}. Shell moderecognizes these constructs, and can perform the history substitutionfor you. If you insert a history reference and type @key{TAB}, this searchesthe input history for a matching command, performs substitution ifnecessary, and places the result in the buffer in place of the historyreference. For example, you can fetch the most recent commandbeginning with @samp{mv} with @kbd{! m v @key{TAB}}. You can edit thecommand if you wish, and then resubmit the command to the shell bytyping @key{RET}.@vindex comint-input-autoexpand@findex comint-magic-space Shell mode can optionally expand history references in the bufferwhen you send them to the shell. To request this, set the variable@code{comint-input-autoexpand} to @code{input}. You can make@key{SPC} perform history expansion by binding @key{SPC} to thecommand @code{comint-magic-space}. Shell mode recognizes history references when they follow a prompt.@xref{Shell Prompts}, for how Shell mode recognizes prompts.@node Directory Tracking@subsection Directory Tracking@cindex directory tracking@vindex shell-pushd-regexp@vindex shell-popd-regexp@vindex shell-cd-regexp Shell mode keeps track of @samp{cd}, @samp{pushd} and @samp{popd}commands given to the inferior shell, so it can keep the@samp{*shell*} buffer's default directory the same as the shell'sworking directory. It recognizes these commands syntactically, byexamining lines of input that are sent. If you use aliases for these commands, you can tell Emacs torecognize them also. For example, if the value of the variable@code{shell-pushd-regexp} matches the beginning of a shell commandline, that line is regarded as a @code{pushd} command. Change thisvariable when you add aliases for @samp{pushd}. Likewise,@code{shell-popd-regexp} and @code{shell-cd-regexp} are used torecognize commands with the meaning of @samp{popd} and @samp{cd}.These commands are recognized only at the beginning of a shell commandline.@ignore @c This seems to have been deleted long ago.@vindex shell-set-directory-error-hook If Emacs gets an error while trying to handle what it believes is a@samp{cd}, @samp{pushd} or @samp{popd} command, it runs the hook@code{shell-set-directory-error-hook} (@pxref{Hooks}).@end ignore@findex dirs If Emacs gets confused about changes in the current directory of thesubshell, use the command @kbd{M-x dirs} to ask the shell what itscurrent directory is. This command works for shells that support themost common command syntax; it may not work for unusual shells.@findex dirtrack-mode You can also use @kbd{M-x dirtrack-mode} to enable (or disable) analternative and more aggressive method of tracking changes in thecurrent directory.@node Shell Options@subsection Shell Mode Options@vindex comint-scroll-to-bottom-on-input If the variable @code{comint-scroll-to-bottom-on-input} isnon-@code{nil}, insertion and yank commands scroll the selected windowto the bottom before inserting.@vindex comint-scroll-show-maximum-output If @code{comint-scroll-show-maximum-output} is non-@code{nil}, thenarrival of output when point is at the end tries to place the last line oftext at the bottom line of the window, so as to show as much usefultext as possible. (This mimics the scrolling behavior of manyterminals.) The default is @code{nil}.@vindex comint-move-point-for-output By setting @code{comint-move-point-for-output}, you can opt forhaving point jump to the end of the buffer whenever output arrives---nomatter where in the buffer point was before. If the value is@code{this}, point jumps in the selected window. If the value is@code{all}, point jumps in each window that shows the Comint buffer. Ifthe value is @code{other}, point jumps in all nonselected windows thatshow the current buffer. The default value is @code{nil}, which meanspoint does not jump to the end.@vindex comint-prompt-read-only If you set @code{comint-prompt-read-only}, the prompts in the Comintbuffer are read-only.@vindex comint-input-ignoredups The variable @code{comint-input-ignoredups} controls whether successiveidentical inputs are stored in the input history. A non-@code{nil}value means to omit an input that is the same as the previous input.The default is @code{nil}, which means to store each input even if it isequal to the previous input.@vindex comint-completion-addsuffix@vindex comint-completion-recexact@vindex comint-completion-autolist Three variables customize file name completion. The variable@code{comint-completion-addsuffix} controls whether completion inserts aspace or a slash to indicate a fully completed file or directory name(non-@code{nil} means do insert a space or slash).@code{comint-completion-recexact}, if non-@code{nil}, directs @key{TAB}to choose the shortest possible completion if the usual Emacs completionalgorithm cannot add even a single character.@code{comint-completion-autolist}, if non-@code{nil}, says to list allthe possible completions whenever completion is not exact.@vindex shell-completion-execonly Command completion normally considers only executable files.If you set @code{shell-completion-execonly} to @code{nil},it considers nonexecutable files as well.@findex shell-pushd-tohome@findex shell-pushd-dextract@findex shell-pushd-dunique You can configure the behavior of @samp{pushd}. Variables controlwhether @samp{pushd} behaves like @samp{cd} if no argument is given(@code{shell-pushd-tohome}), pop rather than rotate with a numericargument (@code{shell-pushd-dextract}), and only add directories to thedirectory stack if they are not already on it(@code{shell-pushd-dunique}). The values you choose should match theunderlying shell, of course. If you want Shell mode to handle color output from shell commands,you can enable ANSI Color mode. Here is how to do this:@example(add-hook 'shell-mode-hook 'ansi-color-for-comint-mode-on)@end example@node Terminal emulator@subsection Emacs Terminal Emulator@findex term To run a subshell in a terminal emulator, putting its typescript inan Emacs buffer, use @kbd{M-x term}. This creates (or reuses) abuffer named @samp{*terminal*}, and runs a subshell with input comingfrom your keyboard, and output going to that buffer. The terminal emulator uses Term mode, which has two input modes. Inline mode, Term basically acts like Shell mode; see @ref{Shell Mode}. In char mode, each character is sent directly to the inferiorsubshell, as ``terminal input.'' Any ``echoing'' of your input is theresponsibility of the subshell. The sole exception is the terminalescape character, which by default is @kbd{C-c} (@pxref{Term Mode}).Any ``terminal output'' from the subshell goes into the buffer,advancing point. Some programs (such as Emacs itself) need to control the appearanceon the terminal screen in detail. They do this by sending specialcontrol codes. The exact control codes needed vary from terminal toterminal, but nowadays most terminals and terminal emulators(including @code{xterm}) understand the ANSI-standard (VT100-style)escape sequences. Term mode recognizes these escape sequences, andhandles each one appropriately, changing the buffer so that theappearance of the window matches what it would be on a real terminal.You can actually run Emacs inside an Emacs Term window. The file name used to load the subshell is determined the same wayas for Shell mode. To make multiple terminal emulators, rename thebuffer @samp{*terminal*} to something different using @kbd{M-xrename-uniquely}, just as with Shell mode. Unlike Shell mode, Term mode does not track the current directory byexamining your input. But some shells can tell Term what the currentdirectory is. This is done automatically by @code{bash} version 1.15and later.@node Term Mode@subsection Term Mode@cindex Term mode@cindex mode, Term The terminal emulator uses Term mode, which has two input modes. Inline mode, Term basically acts like Shell mode; see @ref{Shell Mode}.In char mode, each character is sent directly to the inferiorsubshell, except for the Term escape character, normally @kbd{C-c}. To switch between line and char mode, use these commands:@table @kbd@kindex C-c C-j @r{(Term mode)}@findex term-char-mode@item C-c C-jSwitch to line mode. Do nothing if already in line mode.@kindex C-c C-k @r{(Term mode)}@findex term-line-mode@item C-c C-kSwitch to char mode. Do nothing if already in char mode.@end table The following commands are only available in char mode:@table @kbd@item C-c C-cSend a literal @key{C-c} to the sub-shell.@item C-c @var{char}This is equivalent to @kbd{C-x @var{char}} in normal Emacs. Forexample, @kbd{C-c o} invokes the global binding of @kbd{C-x o}, whichis normally @samp{other-window}.@end table@node Paging in Term@subsection Page-At-A-Time Output@cindex page-at-a-time Term mode has a page-at-a-time feature. When enabled it makesoutput pause at the end of each screenful.@table @kbd@kindex C-c C-q @r{(Term mode)}@findex term-pager-toggle@item C-c C-qToggle the page-at-a-time feature. This command works in both lineand char modes. When page-at-a-time is enabled, the mode-linedisplays the word @samp{page}.@end table With page-at-a-time enabled, whenever Term receives more than ascreenful of output since your last input, it pauses, displaying@samp{**MORE**} in the mode-line. Type @key{SPC} to display the nextscreenful of output. Type @kbd{?} to see your other options. Theinterface is similar to the @code{more} program.@node Remote Host@subsection Remote Host Shell@cindex remote host@cindex connecting to remote host@cindex Telnet@cindex Rlogin You can login to a remote computer, using whatever commands youwould from a regular terminal (e.g.@: using the @code{telnet} or@code{rlogin} commands), from a Term window. A program that asks you for a password will normally suppressechoing of the password, so the password will not show up in thebuffer. This will happen just as if you were using a real terminal,if the buffer is in char mode. If it is in line mode, the password istemporarily visible, but will be erased when you hit return. (Thishappens automatically; there is no special password processing.) When you log in to a different machine, you need to specify the typeof terminal you're using, by setting the @env{TERM} environmentvariable in the environment for the remote login command. (If you usebash, you do that by writing the variable assignment before the remotelogin command, without separating comma.) Terminal types @samp{ansi}or @samp{vt100} will work on most systems.@c If you are talking to a Bourne-compatible@c shell, and your system understands the @env{TERMCAP} variable,@c you can use the command @kbd{M-x shell-send-termcap}, which@c sends a string specifying the terminal type and size.@c (This command is also useful after the window has changed size.)@c You can of course run @samp{gdb} on that remote computer. One useful@c trick: If you invoke gdb with the @code{--fullname} option,@c it will send special commands to Emacs that will cause Emacs to@c pop up the source files you're debugging. This will work@c whether or not gdb is running on a different computer than Emacs,@c as long as Emacs can access the source files specified by gdb.@ignore You cannot log in to a remote computer using the Shell mode.@c (This will change when Shell is re-written to use Term.)Instead, Emacs provides two commands for logging in to another computerand communicating with it through an Emacs buffer using Comint mode:@table @kbd@item M-x telnet @key{RET} @var{hostname} @key{RET}Set up a Telnet connection to the computer named @var{hostname}.@item M-x rlogin @key{RET} @var{hostname} @key{RET}Set up an Rlogin connection to the computer named @var{hostname}.@end table@findex telnet Use @kbd{M-x telnet} to set up a Telnet connection to anothercomputer. (Telnet is the standard Internet protocol for remote login.)It reads the host name of the other computer as an argument with theminibuffer. Once the connection is established, talking to the othercomputer works like talking to a subshell: you can edit input with theusual Emacs commands, and send it a line at a time by typing @key{RET}.The output is inserted in the Telnet buffer interspersed with the input.@findex rlogin@vindex rlogin-explicit-args Use @kbd{M-x rlogin} to set up an Rlogin connection. Rlogin isanother remote login communication protocol, essentially much like theTelnet protocol but incompatible with it, and supported only by certainsystems. Rlogin's advantages are that you can arrange not to have togive your user name and password when communicating between two machinesyou frequently use, and that you can make an 8-bit-clean connection.(To do that in Emacs, set @code{rlogin-explicit-args} to @code{("-8")}before you run Rlogin.) @kbd{M-x rlogin} sets up the default file directory of the Emacsbuffer to access the remote host via FTP (@pxref{File Names}), and ittracks the shell commands that change the current directory, just likeShell mode.@findex rlogin-directory-tracking-mode There are two ways of doing directory tracking in an Rloginbuffer---either with remote directory names@file{/@var{host}:@var{dir}/} or with local names (that works if the``remote'' machine shares file systems with your machine of origin).You can use the command @code{rlogin-directory-tracking-mode} to switchmodes. No argument means use remote directory names, a positiveargument means use local names, and a negative argument means turnoff directory tracking.@end ignore@node Emacs Server, Printing, Shell, Top@section Using Emacs as a Server@pindex emacsclient@cindex Emacs as a server@cindex server, using Emacs as@cindex @env{EDITOR} environment variable Various programs such as @code{mail} can invoke your choice of editorto edit a particular piece of text, such as a message that you aresending. By convention, most of these programs use the environmentvariable @env{EDITOR} to specify which editor to run. If you set@env{EDITOR} to @samp{emacs}, they invoke Emacs---but in aninconvenient fashion, by starting a new, separate Emacs process. Thisis inconvenient because it takes time and because the new Emacs processdoesn't share the buffers in any existing Emacs process. You can arrange to use your existing Emacs process as the editor forprograms like @code{mail} by using the Emacs client and Emacs serverprograms. Here is how.@cindex @env{TEXEDIT} environment variable First, the preparation. Within Emacs, call the function@code{server-start}. (Your @file{.emacs} file can do this automaticallyif you add the expression @code{(server-start)} to it.) Then, outsideEmacs, set the @env{EDITOR} environment variable to @samp{emacsclient}.(Note that some programs use a different environment variable; forexample, to make @TeX{} use @samp{emacsclient}, you should set the@env{TEXEDIT} environment variable to @samp{emacsclient +%d %s}.)@kindex C-x #@findex server-edit Then, whenever any program invokes your specified @env{EDITOR}program, the effect is to send a message to your principal Emacs tellingit to visit a file. (That's what the program @code{emacsclient} does.)Emacs displays the buffer immediately and you can immediately beginediting it. When you've finished editing that buffer, type @kbd{C-x #}(@code{server-edit}). This saves the file and sends a message back tothe @code{emacsclient} program telling it to exit. The programs thatuse @env{EDITOR} wait for the ``editor'' (actually, @code{emacsclient})to exit. @kbd{C-x #} also checks for other pending external requeststo edit various files, and selects the next such file. You can switch to a server buffer manually if you wish; you don'thave to arrive at it with @kbd{C-x #}. But @kbd{C-x #} is the way tosay that you are finished with one.@vindex server-kill-new-buffers@vindex server-temp-file-regexp Finishing with a server buffer also kills the buffer, unless italready existed in the Emacs session before the server asked to createit. However, if you set @code{server-kill-new-buffers} to @code{nil},then a different criterion is used: finishing with a server bufferkills it if the file name matches the regular expression@code{server-temp-file-regexp}. This is set up to distinguish certain``temporary'' files.@vindex server-window If you set the variable @code{server-window} to a window or a frame,@kbd{C-x #} displays the server buffer in that window or in that frame.@vindex server-name You can run multiple Emacs servers on the same machine by givingeach one a unique ``server name'', using the variable@code{server-name}. For example, @kbd{M-x set-variable @key{RET}server-name @key{RET} foo @key{RET}} sets the server name to@samp{foo}. The @code{emacsclient} program can visit a server by nameusing the @samp{-s} option. @xref{Invoking emacsclient}. While @code{mail} or another application is waiting for@code{emacsclient} to finish, @code{emacsclient} does not read terminalinput. So the terminal that @code{mail} was using is effectivelyblocked for the duration. In order to edit with your principal Emacs,you need to be able to use it without using that terminal. There arethree ways to do this:@itemize @bullet@itemUsing a window system, run @code{mail} and the principal Emacs in twoseparate windows. While @code{mail} is waiting for @code{emacsclient},the window where it was running is blocked, but you can use Emacs byswitching windows.@itemUsing virtual terminals, run @code{mail} in one virtual terminaland run Emacs in another.@itemUse Shell mode or Term mode in Emacs to run the other program such as@code{mail}; then, @code{emacsclient} blocks only the subshell underEmacs, and you can still use Emacs to edit the file.@end itemize If you run @code{emacsclient} with the option @samp{--no-wait}, itreturns immediately without waiting for you to ``finish'' the bufferin Emacs. Note that server buffers created in this way are not killedautomatically when you finish with them.@menu* Invoking emacsclient:: Emacs client startup options.@end menu@node Invoking emacsclient,, Emacs Server, Emacs Server@subsection Invoking @code{emacsclient} To run the @code{emacsclient} program, specify file names as arguments,and optionally line numbers as well. Do it like this:@exampleemacsclient @r{@{}@r{[}+@var{line}@r{[}@var{column}@r{]}@r{]} @var{filename}@r{@}}@dots{}@end example@noindentThis tells Emacs to visit each of the specified files; if you specify aline number for a certain file, Emacs moves to that line in the file.If you specify a column number as well, Emacs puts point on that columnin the line. Ordinarily, @code{emacsclient} does not return until you use the@kbd{C-x #} command on each of these buffers. When that happens,Emacs sends a message to the @code{emacsclient} program telling it toreturn. But if you use the option @samp{-n} or @samp{--no-wait} when running@code{emacsclient}, then it returns immediately. (You can take aslong as you like to edit the files in Emacs.) The option @samp{--alternate-editor=@var{command}} is useful whenrunning @code{emacsclient} in a script. It specifies a command to runif @code{emacsclient} fails to contact Emacs. For example, thefollowing setting for the @var{EDITOR} environment variable willalways give you an editor, even if no Emacs server is running:@exampleEDITOR="emacsclient --alternate-editor emacs +%d %s"@end example@noindentThe environment variable @var{ALTERNATE_EDITOR} has the same effect, butthe value of the @samp{--alternate-editor} takes precedence.@pindex emacs.bash Alternatively, the file @file{etc/emacs.bash} defines a bashfunction which will communicate with a running Emacs server, or startone if none exists.If you use several displays, you can tell Emacs on which display toopen the given files with the option @samp{--display=@var{DISPLAY}}.This can be used typically when connecting from home to an Emacsserver running on your machine at your workplace.If there is more than one Emacs server running, you can specify aserver name with the option @samp{-s @var{name}}.You can also use @code{emacsclient} to execute any piece of Emacs Lispcode, using the option @samp{--eval}. When this option is given, therest of the arguments is not taken as a list of files to visit but asa list of expressions to evaluate.@node Printing, Sorting, Emacs Server, Top@section Printing Hard Copies@cindex hardcopy@cindex printing Emacs provides commands for printing hard copies of either an entirebuffer or just part of one, with or without page headers. You caninvoke the printing commands directly, as detailed in the followingsection, or using the @samp{File} menu on the menu bar. See also thehardcopy commands of Dired (@pxref{Misc File Ops}) and the diary(@pxref{Displaying the Diary}).@table @kbd@item M-x print-bufferPrint hardcopy of current buffer with page headings containing the filename and page number.@item M-x lpr-bufferPrint hardcopy of current buffer without page headings.@item M-x print-regionLike @code{print-buffer} but print only the current region.@item M-x lpr-regionLike @code{lpr-buffer} but print only the current region.@end table@findex print-buffer@findex print-region@findex lpr-buffer@findex lpr-region@vindex lpr-switches The hardcopy commands (aside from the Postscript commands) pass extraswitches to the @code{lpr} program based on the value of the variable@code{lpr-switches}. Its value should be a list of strings, each stringan option starting with @samp{-}. For example, to specify a line widthof 80 columns for all the printing you do in Emacs, set@code{lpr-switches} like this:@example(setq lpr-switches '("-w80"))@end example@vindex printer-name You can specify the printer to use by setting the variable@code{printer-name}.@vindex lpr-headers-switches@vindex lpr-commands@vindex lpr-add-switches The variable @code{lpr-command} specifies the name of the printerprogram to run; the default value depends on your operating system type.On most systems, the default is @code{"lpr"}. The variable@code{lpr-headers-switches} similarly specifies the extra switches touse to make page headers. The variable @code{lpr-add-switches} controlswhether to supply @samp{-T} and @samp{-J} options (suitable for@code{lpr}) to the printer program: @code{nil} means don't add them.@code{lpr-add-switches} should be @code{nil} if your printer program isnot compatible with @code{lpr}.@menu* PostScript:: Printing buffers or regions as PostScript.* PostScript Variables:: Customizing the PostScript printing commands.* Printing Package:: An optional advanced printing interface.@end menu@node PostScript, PostScript Variables,, Printing@section PostScript Hardcopy These commands convert buffer contents to PostScript,either printing it or leaving it in another Emacs buffer.@table @kbd@item M-x ps-print-bufferPrint hardcopy of the current buffer in PostScript form.@item M-x ps-print-regionPrint hardcopy of the current region in PostScript form.@item M-x ps-print-buffer-with-facesPrint hardcopy of the current buffer in PostScript form, showing thefaces used in the text by means of PostScript features.@item M-x ps-print-region-with-facesPrint hardcopy of the current region in PostScript form, showing thefaces used in the text.@item M-x ps-spool-bufferGenerate PostScript for the current buffer text.@item M-x ps-spool-regionGenerate PostScript for the current region.@item M-x ps-spool-buffer-with-facesGenerate PostScript for the current buffer, showing the faces used.@item M-x ps-spool-region-with-facesGenerate PostScript for the current region, showing the faces used.@item M-x handwriteGenerates/prints PostScript for the current buffer as if handwritten.@end table@findex ps-print-region@findex ps-print-buffer@findex ps-print-region-with-faces@findex ps-print-buffer-with-faces The PostScript commands, @code{ps-print-buffer} and@code{ps-print-region}, print buffer contents in PostScript form. Onecommand prints the entire buffer; the other, just the region. Thecorresponding @samp{-with-faces} commands,@code{ps-print-buffer-with-faces} and @code{ps-print-region-with-faces},use PostScript features to show the faces (fonts and colors) in the textproperties of the text being printed. If you are using a color display, you can print a buffer of programcode with color highlighting by turning on Font-Lock mode in thatbuffer, and using @code{ps-print-buffer-with-faces}.@findex ps-spool-region@findex ps-spool-buffer@findex ps-spool-region-with-faces@findex ps-spool-buffer-with-faces The commands whose names have @samp{spool} instead of @samp{print}generate the PostScript output in an Emacs buffer instead of sendingit to the printer.@findex handwrite@cindex handwriting@kbd{M-x handwrite} is more frivolous. It generates a PostScriptrendition of the current buffer as a cursive handwritten document. Itcan be customized in group @code{handwrite}. This function onlysupports ISO 8859-1 characters.@ifinfo The following section describes variables for customizing these commands.@end ifinfo@node PostScript Variables, Printing Package, PostScript, Printing@section Variables for PostScript Hardcopy@vindex ps-lpr-command@vindex ps-lpr-switches@vindex ps-printer-name All the PostScript hardcopy commands use the variables@code{ps-lpr-command} and @code{ps-lpr-switches} to specify how to printthe output. @code{ps-lpr-command} specifies the command name to run,@code{ps-lpr-switches} specifies command line options to use, and@code{ps-printer-name} specifies the printer. If you don't set thefirst two variables yourself, they take their initial values from@code{lpr-command} and @code{lpr-switches}. If @code{ps-printer-name}is @code{nil}, @code{printer-name} is used.@vindex ps-print-header The variable @code{ps-print-header} controls whether these commandsadd header lines to each page---set it to @code{nil} to turn headersoff.@cindex color emulation on black-and-white printers@vindex ps-print-color-p If your printer doesn't support colors, you should turn off colorprocessing by setting @code{ps-print-color-p} to @code{nil}. Bydefault, if the display supports colors, Emacs produces hardcopy outputwith color information; on black-and-white printers, colors are emulatedwith shades of gray. This might produce illegible output, even if yourscreen colors only use shades of gray.@vindex ps-use-face-background By default, PostScript printing ignores the background colors of thefaces, unless the variable @code{ps-use-face-background} isnon-@code{nil}. This is to avoid unwanted interference with the zebrastripes and background image/text.@vindex ps-paper-type@vindex ps-page-dimensions-database The variable @code{ps-paper-type} specifies which size of paper toformat for; legitimate values include @code{a4}, @code{a3},@code{a4small}, @code{b4}, @code{b5}, @code{executive}, @code{ledger},@code{legal}, @code{letter}, @code{letter-small}, @code{statement},@code{tabloid}. The default is @code{letter}. You can defineadditional paper sizes by changing the variable@code{ps-page-dimensions-database}.@vindex ps-landscape-mode The variable @code{ps-landscape-mode} specifies the orientation ofprinting on the page. The default is @code{nil}, which stands for``portrait'' mode. Any non-@code{nil} value specifies ``landscape''mode.@vindex ps-number-of-columns The variable @code{ps-number-of-columns} specifies the number ofcolumns; it takes effect in both landscape and portrait mode. Thedefault is 1.@vindex ps-font-family@vindex ps-font-size@vindex ps-font-info-database The variable @code{ps-font-family} specifies which font family to usefor printing ordinary text. Legitimate values include @code{Courier},@code{Helvetica}, @code{NewCenturySchlbk}, @code{Palatino} and@code{Times}. The variable @code{ps-font-size} specifies the size ofthe font for ordinary text. It defaults to 8.5 points.@vindex ps-multibyte-buffer@cindex Intlfonts for PostScript printing@cindex fonts for PostScript printing Emacs supports more scripts and characters than a typical PostScriptprinter. Thus, some of the characters in your buffer might not beprintable using the fonts built into your printer. You can augmentthe fonts supplied with the printer with those from the GNU Intlfontspackage, or you can instruct Emacs to use Intlfonts exclusively. Thevariable @code{ps-multibyte-buffer} controls this: the default value,@code{nil}, is appropriate for printing @acronym{ASCII} and Latin-1characters; a value of @code{non-latin-printer} is for printers whichhave the fonts for @acronym{ASCII}, Latin-1, Japanese, and Koreancharacters built into them. A value of @code{bdf-font} arranges forthe BDF fonts from the Intlfonts package to be used for @emph{all}characters. Finally, a value of @code{bdf-font-except-latin}instructs the printer to use built-in fonts for @acronym{ASCII} and Latin-1characters, and Intlfonts BDF fonts for the rest.@vindex bdf-directory-list To be able to use the BDF fonts, Emacs needs to know where to findthem. The variable @code{bdf-directory-list} holds the list ofdirectories where Emacs should look for the fonts; the default valueincludes a single directory @file{/usr/local/share/emacs/fonts/bdf}. Many other customization variables for these commands are defined anddescribed in the Lisp files @file{ps-print.el} and @file{ps-mule.el}.@node Printing Package,, PostScript Variables, Printing@section Printing Package@cindex Printing package The basic Emacs facilities for printing hardcopy can be extendedusing the Printing package. This provides an easy-to-use interfacefor choosing what to print, previewing PostScript files beforeprinting, and setting various printing options such as print headers,landscape or portrait modes, duplex modes, and so forth. On GNU/Linuxor Unix systems, the Printing package relies on the @file{gs} and@file{gv} utilities, which are distributed as part of the GhostScriptprogram. On MS-Windows, the @file{gstools} port of Ghostscript can beused.@findex pr-interface To use the Printing package, add @code{(require 'printing)} to yourinit file (@pxref{Init File}), followed by @code{(pr-update-menus)}.This function replaces the usual printing commands in the menu barwith a @samp{Printing} submenu that contains various printing options.You can also type @kbd{M-x pr-interface RET}; this creates a@samp{*Printing Interface*} buffer, similar to a customization buffer,where you can set the printing options. After selecting what and howto print, you start the print job using the @samp{Print} button (click@kbd{mouse-2} on it, or move point over it and type @kbd{RET}). Forfurther information on the various options, use the @samp{InterfaceHelp} button.@node Sorting, Narrowing, Printing, Top@section Sorting Text@cindex sorting Emacs provides several commands for sorting text in the buffer. Alloperate on the contents of the region.They divide the text of the region into many @dfn{sort records},identify a @dfn{sort key} for each record, and then reorder the recordsinto the order determined by the sort keys. The records are ordered sothat their keys are in alphabetical order, or, for numeric sorting, innumeric order. In alphabetic sorting, all upper-case letters `A' through`Z' come before lower-case `a', in accord with the @acronym{ASCII} charactersequence. The various sort commands differ in how they divide the text into sortrecords and in which part of each record is used as the sort key. Most ofthe commands make each line a separate sort record, but some commands useparagraphs or pages as sort records. Most of the sort commands use eachentire sort record as its own sort key, but some use only a portion of therecord as the sort key.@findex sort-lines@findex sort-paragraphs@findex sort-pages@findex sort-fields@findex sort-numeric-fields@vindex sort-numeric-base@table @kbd@item M-x sort-linesDivide the region into lines, and sort by comparing the entiretext of a line. A numeric argument means sort into descending order.@item M-x sort-paragraphsDivide the region into paragraphs, and sort by comparing the entiretext of a paragraph (except for leading blank lines). A numericargument means sort into descending order.@item M-x sort-pagesDivide the region into pages, and sort by comparing the entiretext of a page (except for leading blank lines). A numericargument means sort into descending order.@item M-x sort-fieldsDivide the region into lines, and sort by comparing the contents ofone field in each line. Fields are defined as separated bywhitespace, so the first run of consecutive non-whitespace charactersin a line constitutes field 1, the second such run constitutes field2, etc.Specify which field to sort by with a numeric argument: 1 to sort byfield 1, etc. A negative argument means count fields from the rightinstead of from the left; thus, minus 1 means sort by the last field.If several lines have identical contents in the field being sorted, theykeep the same relative order that they had in the original buffer.@item M-x sort-numeric-fieldsLike @kbd{M-x sort-fields} except the specified field is convertedto an integer for each line, and the numbers are compared. @samp{10}comes before @samp{2} when considered as text, but after it whenconsidered as a number. By default, numbers are interpreted accordingto @code{sort-numeric-base}, but numbers beginning with @samp{0x} or@samp{0} are interpreted as hexadecimal and octal, respectively.@item M-x sort-columnsLike @kbd{M-x sort-fields} except that the text within each lineused for comparison comes from a fixed range of columns. See belowfor an explanation.@item M-x reverse-regionReverse the order of the lines in the region. This is useful forsorting into descending order by fields or columns, since those sortcommands do not have a feature for doing that.@end table For example, if the buffer contains this:@smallexampleOn systems where clash detection (locking of files being edited) isimplemented, Emacs also checks the first time you modify a bufferwhether the file has changed on disk since it was last visited orsaved. If it has, you are asked to confirm that you want to changethe buffer.@end smallexample@noindentapplying @kbd{M-x sort-lines} to the entire buffer produces this:@smallexampleOn systems where clash detection (locking of files being edited) isimplemented, Emacs also checks the first time you modify a buffersaved. If it has, you are asked to confirm that you want to changethe buffer.whether the file has changed on disk since it was last visited or@end smallexample@noindentwhere the upper-case @samp{O} sorts before all lower-case letters. Ifyou use @kbd{C-u 2 M-x sort-fields} instead, you get this:@smallexampleimplemented, Emacs also checks the first time you modify a buffersaved. If it has, you are asked to confirm that you want to changethe buffer.On systems where clash detection (locking of files being edited) iswhether the file has changed on disk since it was last visited or@end smallexample@noindentwhere the sort keys were @samp{Emacs}, @samp{If}, @samp{buffer},@samp{systems} and @samp{the}.@findex sort-columns @kbd{M-x sort-columns} requires more explanation. You specify thecolumns by putting point at one of the columns and the mark at the othercolumn. Because this means you cannot put point or the mark at thebeginning of the first line of the text you want to sort, this commanduses an unusual definition of ``region'': all of the line point is in isconsidered part of the region, and so is all of the line the mark is in,as well as all the lines in between. For example, to sort a table by information found in columns 10 to 15,you could put the mark on column 10 in the first line of the table, andpoint on column 15 in the last line of the table, and then run@code{sort-columns}. Equivalently, you could run it with the mark oncolumn 15 in the first line and point on column 10 in the last line. This can be thought of as sorting the rectangle specified by point andthe mark, except that the text on each line to the left or right of therectangle moves along with the text inside the rectangle.@xref{Rectangles}.@vindex sort-fold-case Many of the sort commands ignore case differences when comparing, if@code{sort-fold-case} is non-@code{nil}.@node Narrowing, Two-Column, Sorting, Top@section Narrowing@cindex widening@cindex restriction@cindex narrowing@cindex accessible portion @dfn{Narrowing} means focusing in on some portion of the buffer,making the rest temporarily inaccessible. The portion which you canstill get to is called the @dfn{accessible portion}. Canceling thenarrowing, which makes the entire buffer once again accessible, iscalled @dfn{widening}. The amount of narrowing in effect in a buffer atany time is called the buffer's @dfn{restriction}. Narrowing can make it easier to concentrate on a single subroutine orparagraph by eliminating clutter. It can also be used to restrict therange of operation of a replace command or repeating keyboard macro.@table @kbd@item C-x n nNarrow down to between point and mark (@code{narrow-to-region}).@item C-x n wWiden to make the entire buffer accessible again (@code{widen}).@item C-x n pNarrow down to the current page (@code{narrow-to-page}).@item C-x n dNarrow down to the current defun (@code{narrow-to-defun}).@end table When you have narrowed down to a part of the buffer, that part appearsto be all there is. You can't see the rest, you can't move into it(motion commands won't go outside the accessible part), you can't changeit in any way. However, it is not gone, and if you save the file allthe inaccessible text will be saved. The word @samp{Narrow} appears inthe mode line whenever narrowing is in effect.@kindex C-x n n@findex narrow-to-region The primary narrowing command is @kbd{C-x n n} (@code{narrow-to-region}).It sets the current buffer's restrictions so that the text in the currentregion remains accessible, but all text before the region or after theregion is inaccessible. Point and mark do not change.@kindex C-x n p@findex narrow-to-page@kindex C-x n d@findex narrow-to-defun Alternatively, use @kbd{C-x n p} (@code{narrow-to-page}) to narrowdown to the current page. @xref{Pages}, for the definition of a page.@kbd{C-x n d} (@code{narrow-to-defun}) narrows down to the defuncontaining point (@pxref{Defuns}).@kindex C-x n w@findex widen The way to cancel narrowing is to widen with @kbd{C-x n w}(@code{widen}). This makes all text in the buffer accessible again. You can get information on what part of the buffer you are narrowed downto using the @kbd{C-x =} command. @xref{Position Info}. Because narrowing can easily confuse users who do not understand it,@code{narrow-to-region} is normally a disabled command. Attempting to usethis command asks for confirmation and gives you the option of enabling it;if you enable the command, confirmation will no longer be required forit. @xref{Disabling}.@node Two-Column, Editing Binary Files, Narrowing, Top@section Two-Column Editing@cindex two-column editing@cindex splitting columns@cindex columns, splitting Two-column mode lets you conveniently edit two side-by-side columns oftext. It uses two side-by-side windows, each showing its ownbuffer. There are three ways to enter two-column mode:@table @asis@item @kbd{@key{F2} 2} or @kbd{C-x 6 2}@kindex F2 2@kindex C-x 6 2@findex 2C-two-columnsEnter two-column mode with the current buffer on the left, and on theright, a buffer whose name is based on the current buffer's name(@code{2C-two-columns}). If the right-hand buffer doesn't alreadyexist, it starts out empty; the current buffer's contents are notchanged.This command is appropriate when the current buffer is empty or containsjust one column and you want to add another column.@item @kbd{@key{F2} s} or @kbd{C-x 6 s}@kindex F2 s@kindex C-x 6 s@findex 2C-splitSplit the current buffer, which contains two-column text, into twobuffers, and display them side by side (@code{2C-split}). The currentbuffer becomes the left-hand buffer, but the text in the right-handcolumn is moved into the right-hand buffer. The current columnspecifies the split point. Splitting starts with the current line andcontinues to the end of the buffer.This command is appropriate when you have a buffer that already containstwo-column text, and you wish to separate the columns temporarily.@item @kbd{@key{F2} b @var{buffer} @key{RET}}@itemx @kbd{C-x 6 b @var{buffer} @key{RET}}@kindex F2 b@kindex C-x 6 b@findex 2C-associate-bufferEnter two-column mode using the current buffer as the left-hand buffer,and using buffer @var{buffer} as the right-hand buffer(@code{2C-associate-buffer}).@end table @kbd{@key{F2} s} or @kbd{C-x 6 s} looks for a column separator, whichis a string that appears on each line between the two columns. You canspecify the width of the separator with a numeric argument to@kbd{@key{F2} s}; that many characters, before point, constitute theseparator string. By default, the width is 1, so the column separatoris the character before point. When a line has the separator at the proper place, @kbd{@key{F2} s}puts the text after the separator into the right-hand buffer, anddeletes the separator. Lines that don't have the column separator atthe proper place remain unsplit; they stay in the left-hand buffer, andthe right-hand buffer gets an empty line to correspond. (This is theway to write a line that ``spans both columns while in two-columnmode'': write it in the left-hand buffer, and put an empty line in theright-hand buffer.)@kindex F2 RET@kindex C-x 6 RET@findex 2C-newline The command @kbd{C-x 6 @key{RET}} or @kbd{@key{F2} @key{RET}}(@code{2C-newline}) inserts a newline in each of the two buffers atcorresponding positions. This is the easiest way to add a new line tothe two-column text while editing it in split buffers.@kindex F2 1@kindex C-x 6 1@findex 2C-merge When you have edited both buffers as you wish, merge them with@kbd{@key{F2} 1} or @kbd{C-x 6 1} (@code{2C-merge}). This copies thetext from the right-hand buffer as a second column in the other buffer.To go back to two-column editing, use @kbd{@key{F2} s}.@kindex F2 d@kindex C-x 6 d@findex 2C-dissociate Use @kbd{@key{F2} d} or @kbd{C-x 6 d} to dissociate the two buffers,leaving each as it stands (@code{2C-dissociate}). If the other buffer,the one not current when you type @kbd{@key{F2} d}, is empty,@kbd{@key{F2} d} kills it.@node Editing Binary Files, Saving Emacs Sessions, Two-Column, Top@section Editing Binary Files@cindex Hexl mode@cindex mode, Hexl@cindex editing binary files@cindex hex editing There is a special major mode for editing binary files: Hexl mode. Touse it, use @kbd{M-x hexl-find-file} instead of @kbd{C-x C-f} to visitthe file. This command converts the file's contents to hexadecimal andlets you edit the translation. When you save the file, it is convertedautomatically back to binary. You can also use @kbd{M-x hexl-mode} to translate an existing bufferinto hex. This is useful if you visit a file normally and then discoverit is a binary file. Ordinary text characters overwrite in Hexl mode. This is to reducethe risk of accidentally spoiling the alignment of data in the file.There are special commands for insertion. Here is a list of thecommands of Hexl mode:@c I don't think individual index entries for these commands are useful--RMS.@table @kbd@item C-M-dInsert a byte with a code typed in decimal.@item C-M-oInsert a byte with a code typed in octal.@item C-M-xInsert a byte with a code typed in hex.@item C-x [Move to the beginning of a 1k-byte ``page.''@item C-x ]Move to the end of a 1k-byte ``page.''@item M-gMove to an address specified in hex.@item M-jMove to an address specified in decimal.@item C-c C-cLeave Hexl mode, going back to the major mode this buffer had before youinvoked @code{hexl-mode}.@end table@noindentOther Hexl commands let you insert strings (sequences) of binarybytes, move by @code{short}s or @code{int}s, etc.; type @kbd{C-h ahexl-@key{RET}} for details.@node Saving Emacs Sessions, Recursive Edit, Editing Binary Files, Top@section Saving Emacs Sessions@cindex saving sessions@cindex restore session@cindex remember editing session@cindex reload files@cindex desktop Use the desktop library to save the state of Emacs from one sessionto another. Once you save the Emacs @dfn{desktop}---the buffers,their file names, major modes, buffer positions, and so on---thensubsequent Emacs sessions reload the saved desktop.@findex desktop-save@vindex desktop-save-mode You can save the desktop manually with the command @kbd{M-xdesktop-save}. You can also enable automatic desktop saving whenyou exit Emacs: use the Customization buffer (@pxref{EasyCustomization}) to set @code{desktop-save-mode} to @code{t} for futuresessions, or add this line in your @file{~/.emacs} file:@example(desktop-save-mode 1)@end example@findex desktop-change-dir@findex desktop-revert When Emacs starts, it looks for a saved desktop in the currentdirectory. Thus, you can have separate saved desktops in differentdirectories, and the starting directory determines which one Emacsreloads. You can save the current desktop and reload one saved inanother directory by typing @kbd{M-x desktop-change-dir}. Typing@kbd{M-x desktop-revert} reverts to the desktop previously reloaded. Specify the option @samp{--no-desktop} on the command line when youdon't want it to reload any saved desktop. This turns off@code{desktop-save-mode} for the current session.@vindex desktop-restore-eager By default, all the buffers in the desktop are restored at one go.However, this may be slow if there are a lot of buffers in thedesktop. You can specify the maximum number of buffers to restoreimmediately with the variable @code{desktop-restore-eager}; theremaining buffers are restored ``lazily,'' when Emacs is idle.@findex desktop-clear@vindex desktop-globals-to-clear@vindex desktop-clear-preserve-buffers-regexp Type @kbd{M-x desktop-clear} to empty the Emacs desktop. This killsall buffers except for internal ones, and clears the global variableslisted in @code{desktop-globals-to-clear}. If you want this topreserve certain buffers, customize the variable@code{desktop-clear-preserve-buffers-regexp}, whose value is a regularexpression matching the names of buffers not to kill. If you want to save minibuffer history from one session toanother, use the @code{savehist} library.@node Recursive Edit, Emulation, Saving Emacs Sessions, Top@section Recursive Editing Levels@cindex recursive editing level@cindex editing level, recursive A @dfn{recursive edit} is a situation in which you are using Emacscommands to perform arbitrary editing while in the middle of anotherEmacs command. For example, when you type @kbd{C-r} inside of a@code{query-replace}, you enter a recursive edit in which you can changethe current buffer. On exiting from the recursive edit, you go back tothe @code{query-replace}.@kindex C-M-c@findex exit-recursive-edit@cindex exiting recursive edit @dfn{Exiting} the recursive edit means returning to the unfinishedcommand, which continues execution. The command to exit is @kbd{C-M-c}(@code{exit-recursive-edit}). You can also @dfn{abort} the recursive edit. This is like exiting,but also quits the unfinished command immediately. Use the command@kbd{C-]} (@code{abort-recursive-edit}) to do this. @xref{Quitting}. The mode line shows you when you are in a recursive edit by displayingsquare brackets around the parentheses that always surround the major andminor mode names. Every window's mode line shows this in the same way,since being in a recursive edit is true of Emacs as a whole rather thanany particular window or buffer. It is possible to be in recursive edits within recursive edits. Forexample, after typing @kbd{C-r} in a @code{query-replace}, you may type acommand that enters the debugger. This begins a recursive editing levelfor the debugger, within the recursive editing level for @kbd{C-r}.Mode lines display a pair of square brackets for each recursive editinglevel currently in progress. Exiting the inner recursive edit (such as with the debugger @kbd{c}command) resumes the command running in the next level up. When thatcommand finishes, you can then use @kbd{C-M-c} to exit another recursiveediting level, and so on. Exiting applies to the innermost level only.Aborting also gets out of only one level of recursive edit; it returnsimmediately to the command level of the previous recursive edit. If youwish, you can then abort the next recursive editing level. Alternatively, the command @kbd{M-x top-level} aborts all levels ofrecursive edits, returning immediately to the top-level command reader. The text being edited inside the recursive edit need not be the same textthat you were editing at top level. It depends on what the recursive editis for. If the command that invokes the recursive edit selects a differentbuffer first, that is the buffer you will edit recursively. In any case,you can switch buffers within the recursive edit in the normal manner (aslong as the buffer-switching keys have not been rebound). You couldprobably do all the rest of your editing inside the recursive edit,visiting files and all. But this could have surprising effects (such asstack overflow) from time to time. So remember to exit or abort therecursive edit when you no longer need it. In general, we try to minimize the use of recursive editing levels inGNU Emacs. This is because they constrain you to ``go back'' in aparticular order---from the innermost level toward the top level. Whenpossible, we present different activities in separate buffers so thatyou can switch between them as you please. Some commands switch to anew major mode which provides a command to switch back. Theseapproaches give you more flexibility to go back to unfinished tasks inthe order you choose.@node Emulation, Hyperlinking, Recursive Edit, Top@section Emulation@cindex emulating other editors@cindex other editors@cindex EDT@cindex vi@cindex PC key bindings@cindex scrolling all windows@cindex PC selection@cindex Motif key bindings@cindex Macintosh key bindings@cindex WordStar GNU Emacs can be programmed to emulate (more or less) most othereditors. Standard facilities can emulate these:@table @asis@item CRiSP/Brief (PC editor)@findex crisp-mode@vindex crisp-override-meta-x@findex scroll-all-mode@cindex CRiSP mode@cindex Brief emulation@cindex emulation of Brief@cindex mode, CRiSPYou can turn on key bindings to emulate the CRiSP/Brief editor with@kbd{M-x crisp-mode}. Note that this rebinds @kbd{M-x} to exit Emacsunless you set the variable @code{crisp-override-meta-x}. You canalso use the command @kbd{M-x scroll-all-mode} or set the variable@code{crisp-load-scroll-all} to emulate CRiSP's scroll-all feature(scrolling all windows together).@item EDT (DEC VMS editor)@findex edt-emulation-on@findex edt-emulation-offTurn on EDT emulation with @kbd{M-x edt-emulation-on}. @kbd{M-xedt-emulation-off} restores normal Emacs command bindings.Most of the EDT emulation commands are keypad keys, and most standardEmacs key bindings are still available. The EDT emulation rebindingsare done in the global keymap, so there is no problem switchingbuffers or major modes while in EDT emulation.@item TPU (DEC VMS editor)@findex tpu-edt-on@cindex TPU@kbd{M-x tpu-edt-on} turns on emulation of the TPU editor emulating EDT.@item vi (Berkeley editor)@findex viper-modeViper is the newest emulator for vi. It implements several levels ofemulation; level 1 is closest to vi itself, while level 5 departssomewhat from strict emulation to take advantage of the capabilities ofEmacs. To invoke Viper, type @kbd{M-x viper-mode}; it will guide youthe rest of the way and ask for the emulation level. @inforef{Top,Viper, viper}.@item vi (another emulator)@findex vi-mode@kbd{M-x vi-mode} enters a major mode that replaces the previouslyestablished major mode. All of the vi commands that, in real vi, enter``input'' mode are programmed instead to return to the previous majormode. Thus, ordinary Emacs serves as vi's ``input'' mode.Because vi emulation works through major modes, it does not workto switch buffers during emulation. Return to normal Emacs first.If you plan to use vi emulation much, you probably want to bind a keyto the @code{vi-mode} command.@item vi (alternate emulator)@findex vip-mode@kbd{M-x vip-mode} invokes another vi emulator, said to resemble real vimore thoroughly than @kbd{M-x vi-mode}. ``Input'' mode in this emulatoris changed from ordinary Emacs so you can use @key{ESC} to go back toemulated vi command mode. To get from emulated vi command mode back toordinary Emacs, type @kbd{C-z}.This emulation does not work through major modes, and it is possibleto switch buffers in various ways within the emulator. It is notso necessary to assign a key to the command @code{vip-mode} asit is with @code{vi-mode} because terminating insert mode doesnot use it.@inforef{Top, VIP, vip}, for full information.@item WordStar (old wordprocessor)@findex wordstar-mode@kbd{M-x wordstar-mode} provides a major mode with WordStar-likekey bindings.@end table@node Hyperlinking, Dissociated Press, Emulation, Top@section Hyperlinking and Navigation Features@cindex hyperlinking@cindex navigation Various modes documented elsewhere have hypertext features so thatyou can follow links, usually by clicking @kbd{Mouse-2} on the link ortyping @key{RET} while point is on the link. Clicking @kbd{Mouse-1}quickly on the link also follows it. (Hold @kbd{Mouse-1} for longerif you want to set point instead.) Info mode, Help mode and the Dired-like modes are examples of modesthat have links in the buffer. The Tags facility links between usesand definitions in source files, see @ref{Tags}. Imenu providesnavigation amongst items indexed in the current buffer, see@ref{Imenu}. Info-lookup provides mode-specific lookup of definitionsin Info indexes, see @ref{Documentation}. Speedbar maintains a framein which links to files, and locations in files are displayed, see@ref{Speedbar}. Other non-mode-specific facilities described in this section enablefollowing links from the current buffer in a context-sensitivefashion.@menu* Browse-URL:: Following URLs.* Goto-address:: Activating URLs.* FFAP:: Finding files etc. at point.@end menu@node Browse-URL@subsection Following URLs@cindex World Wide Web@cindex Web@findex browse-url@findex browse-url-at-point@findex browse-url-at-mouse@cindex Browse-URL@cindex URLs@table @kbd@item M-x browse-url @key{RET} @var{url} @key{RET}Load a URL into a Web browser.@end tableThe Browse-URL package provides facilities for following URLs specifyinglinks on the World Wide Web. Usually this works by invoking a webbrowser, but you can, for instance, arrange to invoke @code{compose-mail}from @samp{mailto:} URLs. The general way to use this feature is to type @kbd{M-x browse-url},which displays a specified URL. If point is located near a plausibleURL, that URL is used as the default. Other commands are availablewhich you might like to bind to keys, such as@code{browse-url-at-point} and @code{browse-url-at-mouse}.@vindex browse-url-browser-function You can customize Browse-URL's behavior via various options in the@code{browse-url} Customize group, particularly@code{browse-url-browser-function}. You can invoke actions dependenton the type of URL by defining @code{browse-url-browser-function} asan association list. The package's commentary available via @kbd{C-hp} under the @samp{hypermedia} keyword provides more information.Packages with facilities for following URLs should always go throughBrowse-URL, so that the customization options for Browse-URL willaffect all browsing in Emacs.@node Goto-address@subsection Activating URLs@findex goto-address@cindex Goto-address@cindex URLs, activating@table @kbd@item M-x goto-addressActivate URLs and e-mail addresses in the current buffer.@end table You can make URLs in the current buffer active with @kbd{M-xgoto-address}. This finds all the URLs in the buffer, and establishesbindings for @kbd{Mouse-2} and @kbd{C-c @key{RET}} on them. Afteractivation, if you click on a URL with @kbd{Mouse-2}, or move to a URLand type @kbd{C-c @key{RET}}, that will display the web page that the URLspecifies. For a @samp{mailto} URL, it sends mail instead, using yourselected mail-composition method (@pxref{Mail Methods}). It can be useful to add @code{goto-address} to mode hooks and thehooks used to display an incoming message.@code{rmail-show-message-hook} is the appropriate hook for Rmail, and@code{mh-show-mode-hook} for MH-E. This is not needed for Gnus,which has a similar feature of its own.@node FFAP@subsection Finding Files and URLs at Point@findex find-file-at-point@findex ffap@findex dired-at-point@findex ffap-next@findex ffap-menu@cindex finding file at point FFAP mode replaces certain key bindings for finding files, including@kbd{C-x C-f}, with commands that provide more sensitive defaults.These commands behave like the ordinary ones when given a prefixargument. Otherwise, they get the default file name or URL from thetext around point. If what is found in the buffer has the form of aURL rather than a file name, the commands use @code{browse-url} toview it. This feature is useful for following references in mail or newsbuffers, @file{README} files, @file{MANIFEST} files, and so on. The@samp{ffap} package's commentary available via @kbd{C-h p} under the@samp{files} keyword and the @code{ffap} Custom group provide details.@cindex FFAP minor mode@findex ffap-mode You can turn on FFAP minor mode by calling @code{ffap-bindings} tomake the following key bindings and to install hooks for using@code{ffap} in Rmail, Gnus and VM article buffers.@table @kbd@item C-x C-f @var{filename} @key{RET}@kindex C-x C-f @r{(FFAP)}Find @var{filename}, guessing a default from text around point(@code{find-file-at-point}).@item C-x C-r@kindex C-x C-r @r{(FFAP)}@code{ffap-read-only}, analogous to @code{find-file-read-only}.@item C-x C-v@kindex C-x C-v @r{(FFAP)}@code{ffap-alternate-file}, analogous to @code{find-alternate-file}.@item C-x d @var{directory} @key{RET}@kindex C-x d @r{(FFAP)}Start Dired on @var{directory}, defaulting to the directory name atpoint (@code{dired-at-point}).@item C-x C-d@code{ffap-list-directory}, analogous to @code{list-directory}.@item C-x 4 f@kindex C-x 4 f @r{(FFAP)}@code{ffap-other-window}, analogous to @code{find-file-other-window}.@item C-x 4 r@code{ffap-read-only-other-window}, analogous to@code{find-file-read-only-other-window}.@item C-x 4 d@code{ffap-dired-other-window}, analogous to @code{dired-other-window}.@item C-x 5 f@kindex C-x 5 f @r{(FFAP)}@code{ffap-other-frame}, analogous to @code{find-file-other-frame}.@item C-x 5 r@code{ffap-read-only-other-frame}, analogous to@code{find-file-read-only-other-frame}.@item C-x 5 d@code{ffap-dired-other-frame}, analogous to @code{dired-other-frame}.@item M-x ffap-nextSearch buffer for next file name or URL, then find that file or URL.@item S-Mouse-3@kindex S-Mouse-3 @r{(FFAP)}@code{ffap-at-mouse} finds the file guessed from text around the positionof a mouse click.@item C-S-Mouse-3@kindex C-S-Mouse-3 @r{(FFAP)}Display a menu of files and URLs mentioned in current buffer, thenfind the one you select (@code{ffap-menu}).@end table@node Dissociated Press, Amusements, Hyperlinking, Top@section Dissociated Press@findex dissociated-press @kbd{M-x dissociated-press} is a command for scrambling a file of texteither word by word or character by character. Starting from a buffer ofstraight English, it produces extremely amusing output. The input comesfrom the current Emacs buffer. Dissociated Press writes its output in abuffer named @samp{*Dissociation*}, and redisplays that buffer after everycouple of lines (approximately) so you can read the output as it comes out. Dissociated Press asks every so often whether to continue generatingoutput. Answer @kbd{n} to stop it. You can also stop at any time bytyping @kbd{C-g}. The dissociation output remains in the@samp{*Dissociation*} buffer for you to copy elsewhere if you wish.@cindex presidentagon Dissociated Press operates by jumping at random from one point in thebuffer to another. In order to produce plausible output rather thangibberish, it insists on a certain amount of overlap between the end ofone run of consecutive words or characters and the start of the next.That is, if it has just output `president' and then decides to jumpto a different point in the file, it might spot the `ent' in `pentagon'and continue from there, producing `presidentagon'.@footnote{Thisdissociword actually appeared during the Vietnam War, when it was veryappropriate.} Long sample texts produce the best results.@cindex againformation A positive argument to @kbd{M-x dissociated-press} tells it to operatecharacter by character, and specifies the number of overlap characters. Anegative argument tells it to operate word by word and specifies the numberof overlap words. In this mode, whole words are treated as the elements tobe permuted, rather than characters. No argument is equivalent to anargument of two. For your againformation, the output goes only into thebuffer @samp{*Dissociation*}. The buffer you start with is not changed.@cindex Markov chain@cindex ignoriginal@cindex techniquitous Dissociated Press produces nearly the same results as a Markov chainbased on a frequency table constructed from the sample text. It is,however, an independent, ignoriginal invention. Dissociated Presstechniquitously copies several consecutive characters from the samplebetween random choices, whereas a Markov chain would choose randomly foreach word or character. This makes for more plausible sounding results,and runs faster.@cindex outragedy@cindex buggestion@cindex properbose@cindex mustatement@cindex developediment@cindex userenced It is a mustatement that too much use of Dissociated Press can be adevelopediment to your real work. Sometimes to the point of outragedy.And keep dissociwords out of your documentation, if you want it to be welluserenced and properbose. Have fun. Your buggestions are welcome.@node Amusements, Customization, Dissociated Press, Top@section Other Amusements@cindex boredom@findex hanoi@findex yow@findex gomoku@cindex tower of Hanoi If you are a little bit bored, you can try @kbd{M-x hanoi}. If you areconsiderably bored, give it a numeric argument. If you are very, verybored, try an argument of 9. Sit back and watch.@cindex Go Moku If you want a little more personal involvement, try @kbd{M-x gomoku},which plays the game Go Moku with you.@findex blackbox@findex mpuz@findex 5x5@cindex puzzles @kbd{M-x blackbox}, @kbd{M-x mpuz} and @kbd{M-x 5x5} are kinds of puzzles.@code{blackbox} challenges you to determine the location of objectsinside a box by tomography. @code{mpuz} displays a multiplicationpuzzle with letters standing for digits in a code that you mustguess---to guess a value, type a letter and then the digit you think itstands for. The aim of @code{5x5} is to fill in all the squares.@findex decipher@cindex ciphers@cindex cryptanalysis@kbd{M-x decipher} helps you to cryptanalyze a buffer which is encryptedin a simple monoalphabetic substitution cipher.@findex dunnet @kbd{M-x dunnet} runs an adventure-style exploration game, which isa bigger sort of puzzle.@findex lm@cindex landmark game@kbd{M-x lm} runs a relatively non-participatory game in which a robotattempts to maneuver towards a tree at the center of the window based onunique olfactory cues from each of the four directions.@findex life@cindex Life@kbd{M-x life} runs Conway's ``Life'' cellular automaton.@findex morse-region@findex unmorse-region@cindex Morse code@cindex --/---/.-./.../.@kbd{M-x morse-region} converts text in a region to Morse code and@kbd{M-x unmorse-region} converts it back. No cause for remorse.@findex pong@cindex Pong game@kbd{M-x pong} plays a Pong-like game, bouncing the ball off opposingbats.@findex solitaire@cindex solitaire@kbd{M-x solitaire} plays a game of solitaire in which you jump pegsacross other pegs.@findex studlify-region@cindex StudlyCaps@kbd{M-x studlify-region} studlify-cases the region, producingtext like this:@exampleM-x stUdlIfY-RegioN stUdlIfY-CaSeS thE region.@end example@findex tetris@cindex Tetris@findex snake@cindex Snake@kbd{M-x tetris} runs an implementation of the well-known Tetris game.Likewise, @kbd{M-x snake} provides an implementation of Snake. When you are frustrated, try the famous Eliza program. Just do@kbd{M-x doctor}. End each input by typing @key{RET} twice.@cindex Zippy When you are feeling strange, type @kbd{M-x yow}.@findex zoneThe command @kbd{M-x zone} plays games with the display when Emacs isidle.@ifnottex@lowersections@end ifnottex@ignore arch-tag: 8f094220-c0d5-4e9e-af7d-3e0da8187474@end ignore