emacs: man/trouble.texi comparison

comparison man/trouble.texi @ 83507:81f2d90dee68

Merged from Patches applied: * emacs@sv.gnu.org/emacs--devo--0--patch-188 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-189 Merge from gnus--rel--5.10 * emacs@sv.gnu.org/emacs--devo--0--patch-190 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-191 Undo incorrect merge of etc/images/README from Gnus 5.10 * emacs@sv.gnu.org/emacs--devo--0--patch-192 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-193 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-194 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-195 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-196 Merge from gnus--rel--5.10 * emacs@sv.gnu.org/emacs--devo--0--patch-197 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-198 Merge from gnus--rel--5.10 * emacs@sv.gnu.org/emacs--devo--0--patch-199 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-200 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-201 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-202 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-203 Merge from gnus--rel--5.10 * emacs@sv.gnu.org/emacs--devo--0--patch-204 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-205 Update from CVS * emacs@sv.gnu.org/emacs--devo--0--patch-206 Update from CVS * emacs@sv.gnu.org/gnus--rel--5.10--patch-73 Update from CVS * emacs@sv.gnu.org/gnus--rel--5.10--patch-74 Update from CVS * emacs@sv.gnu.org/gnus--rel--5.10--patch-75 Update from CVS * emacs@sv.gnu.org/gnus--rel--5.10--patch-76 Update from CVS: README: Addition from 5.10.6 tar ball. * emacs@sv.gnu.org/gnus--rel--5.10--patch-77 Update from CVS * emacs@sv.gnu.org/gnus--rel--5.10--patch-78 Update from CVS * emacs@sv.gnu.org/gnus--rel--5.10--patch-79 Update from CVS * emacs@sv.gnu.org/gnus--rel--5.10--patch-80 Update from CVS git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-547

author	Karoly Lorentey <lorentey@elte.hu>
date	Mon, 10 Apr 2006 14:52:24 +0000
parents	601830ae280c
children	017a2a1beeee c156f6a9e7b5

comparison

equal deleted inserted replaced

-:9905fc171253
+:81f2d90dee68
 Abort all recursive editing levels that are currently executing.
 @item C-x u
 Cancel a previously made change in the buffer contents (@code{undo}).
 @end table
-There are two ways of canceling commands which are not finished
+There are two ways of canceling a command before it has finished:
-executing: @dfn{quitting} with @kbd{C-g}, and @dfn{aborting} with
+@dfn{quitting} with @kbd{C-g}, and @dfn{aborting} with @kbd{C-]} or
-@kbd{C-]} or @kbd{M-x top-level}.  Quitting cancels a partially typed
+@kbd{M-x top-level}.  Quitting cancels a partially typed command, or
-command or one which is already running.  Aborting exits a recursive
+one which is still running.  Aborting exits a recursive editing level
-editing level and cancels the command that invoked the recursive edit.
+and cancels the command that invoked the recursive edit.
 (@xref{Recursive Edit}.)
 @cindex quitting
 @kindex C-g
-Quitting with @kbd{C-g} is used for getting rid of a partially typed
+Quitting with @kbd{C-g} is the way to get rid of a partially typed
 command, or a numeric argument that you don't want.  It also stops a
 running command in the middle in a relatively safe way, so you can use
 it if you accidentally give a command which takes a long time.  In
-particular, it is safe to quit out of killing; either your text will
+particular, it is safe to quit out of a kill command; either your text
-@emph{all} still be in the buffer, or it will @emph{all} be in the kill
+will @emph{all} still be in the buffer, or it will @emph{all} be in
-ring (or maybe both).  Quitting an incremental search does special
+the kill ring, or maybe both.  Quitting an incremental search does
-things documented under searching; in general, it may take two
+special things, documented under searching; it may take two successive
-successive @kbd{C-g} characters to get out of a search
+@kbd{C-g} characters to get out of a search (@pxref{Incremental
-(@pxref{Incremental Search}).
+Search}).
 On MS-DOS, the character @kbd{C-@key{BREAK}} serves as a quit character
 like @kbd{C-g}.  The reason is that it is not feasible, on MS-DOS, to
 recognize @kbd{C-g} while a command is running, between interactions
 with the user.  By contrast, it @emph{is} feasible to recognize
-@kbd{C-@key{BREAK}} at all times.  @xref{MS-DOS Keyboard}.
+@kbd{C-@key{BREAK}} at all times.  @xref{MS-DOS Keyboard,,,emacs-xtra,
+Specialized Emacs Features}.
 @findex keyboard-quit
 @kbd{C-g} works by setting the variable @code{quit-flag} to @code{t}
 the instant @kbd{C-g} is typed; Emacs Lisp checks this variable
-frequently and quits if it is non-@code{nil}.  @kbd{C-g} is only
+frequently, and quits if it is non-@code{nil}.  @kbd{C-g} is only
 actually executed as a command if you type it while Emacs is waiting for
 input.  In that case, the command it runs is @code{keyboard-quit}.
 On a text terminal, if you quit with @kbd{C-g} a second time before
 the first @kbd{C-g} is recognized, you activate the ``emergency
 escape'' feature and return to the shell.  @xref{Emergency Escape}.
 @cindex NFS and quitting
-There may be times when you cannot quit.  When Emacs is waiting for
+There are some situations where you cannot quit.  When Emacs is
-the operating system to do something, quitting is impossible unless
+waiting for the operating system to do something, quitting is
-special pains are taken for the particular system call within Emacs
+impossible unless special pains are taken for the particular system
-where the waiting occurs.  We have done this for the system calls that
+call within Emacs where the waiting occurs.  We have done this for the
-users are likely to want to quit from, but it's possible you will find
+system calls that users are likely to want to quit from, but it's
-another.  In one very common case---waiting for file input or output
+possible you will a case not handled.  In one very common
-using NFS---Emacs itself knows how to quit, but many NFS implementations
+case---waiting for file input or output using NFS---Emacs itself knows
-simply do not allow user programs to stop waiting for NFS when the NFS
+how to quit, but many NFS implementations simply do not allow user
-server is hung.
+programs to stop waiting for NFS when the NFS server is hung.
 @cindex aborting recursive edit
 @findex abort-recursive-edit
 @kindex C-]
 Aborting with @kbd{C-]} (@code{abort-recursive-edit}) is used to get
 argument, you can cancel that argument with @kbd{C-g} and remain in the
 recursive edit.
 @findex keyboard-escape-quit
 @kindex ESC ESC ESC
-The command @kbd{@key{ESC} @key{ESC} @key{ESC}}
+The sequence @kbd{@key{ESC} @key{ESC} @key{ESC}}
-(@code{keyboard-escape-quit}) can either quit or abort.  This key was
+(@code{keyboard-escape-quit}) can either quit or abort.  (We defined
-defined because @key{ESC} is used to ``get out'' in many PC programs.
+it this way because @key{ESC} means ``get out'' in many PC programs.)
-It can cancel a prefix argument, clear a selected region, or get out of
+It can cancel a prefix argument, clear a selected region, or get out
-a Query Replace, like @kbd{C-g}.  It can get out of the minibuffer or a
+of a Query Replace, like @kbd{C-g}.  It can get out of the minibuffer
-recursive edit, like @kbd{C-]}.  It can also get out of splitting the
+or a recursive edit, like @kbd{C-]}.  It can also get out of splitting
-frame into multiple windows, like @kbd{C-x 1}.  One thing it cannot do,
+the frame into multiple windows, as with @kbd{C-x 1}.  One thing it
-however, is stop a command that is running.  That's because it executes
+cannot do, however, is stop a command that is running.  That's because
-as an ordinary command, and Emacs doesn't notice it until it is ready
+it executes as an ordinary command, and Emacs doesn't notice it until
-for a command.
+it is ready for the next command.
 @findex top-level
 The command @kbd{M-x top-level} is equivalent to ``enough'' @kbd{C-]}
 commands to get you out of all the levels of recursive edits that you
 are in.  @kbd{C-]} gets you out one level at a time, but @kbd{M-x
 @menu
 * DEL Does Not Delete::   What to do if @key{DEL} doesn't delete.
 * Stuck Recursive::       `[...]' in mode line around the parentheses.
 * Screen Garbled::        Garbage on the screen.
 * Text Garbled::          Garbage in the text.
-* Unasked-for Search::    Spontaneous entry to incremental search.
 * Memory Full::           How to cope when you run out of memory.
 * After a Crash::         Recovering editing in an Emacs session that crashed.
 * Emergency Escape::      Emergency escape---
 What to do if Emacs stops responding.
 * Total Frustration::     When you are at your wits' end.
 isn't.
 In all of those cases, the immediate remedy is the same: use the
 command @kbd{M-x normal-erase-is-backspace-mode}.  This toggles
 between the two modes that Emacs supports for handling @key{DEL}, so
-if Emacs starts in the wrong mode, it should switch to the right mode.
+if Emacs starts in the wrong mode, this should switch to the right
-On a text-only terminal, if you want to ask for help when @key{BS} is
+mode.  On a text-only terminal, if you want to ask for help when
-treated as @key{DEL}, use @key{F1}; @kbd{C-?} may also work, if it
+@key{BS} is treated as @key{DEL}, use @key{F1}; @kbd{C-?} may also
-sends character code 127.
+work, if it sends character code 127.
 @findex normal-erase-is-backspace-mode
 To fix the problem automatically for every Emacs session, you can
 put one of the following lines into your @file{.emacs} file
 (@pxref{Init File}).  For the first case above, where @key{DELETE}
 see whether it is wrong in the buffer.  Type @kbd{C-l} to redisplay
 the entire screen.  If the screen appears correct after this, the
 problem was entirely in the previous screen update.  (Otherwise, see
 the following section.)
-Display updating problems often result from an incorrect termcap entry
+Display updating problems often result from an incorrect terminfo
-for the terminal you are using.  The file @file{etc/TERMS} in the Emacs
+entry for the terminal you are using.  The file @file{etc/TERMS} in
-distribution gives the fixes for known problems of this sort.
+the Emacs distribution gives the fixes for known problems of this
-@file{INSTALL} contains general advice for these problems in one of its
+sort.  @file{INSTALL} contains general advice for these problems in
-sections.  Very likely there is simply insufficient padding for certain
+one of its sections.  To investigate the possibility that you have
-display operations.  To investigate the possibility that you have this sort
+this sort of problem, try Emacs on another terminal made by a
-of problem, try Emacs on another terminal made by a different manufacturer.
+different manufacturer.  If problems happen frequently on one kind of
-If problems happen frequently on one kind of terminal but not another kind,
+terminal but not another kind, it is likely to be a bad terminfo entry,
-it is likely to be a bad termcap entry, though it could also be due to a
+though it could also be due to a bug in Emacs that appears for
-bug in Emacs that appears for terminals that have or that lack specific
+terminals that have or that lack specific features.
-features.
 @node Text Garbled
 @subsection Garbage in the Text
-If @kbd{C-l} shows that the text is wrong, try undoing the changes to it
+If @kbd{C-l} shows that the text is wrong, first type @kbd{C-h l} to
-using @kbd{C-x u} until it gets back to a state you consider correct.  Also
+see what commands you typed to produce the observed results.  Then try
-try @kbd{C-h l} to find out what command you typed to produce the observed
+undoing the changes step by step using @kbd{C-x u}, until it gets back
-results.
+to a state you consider correct.
 If a large portion of text appears to be missing at the beginning or
 end of the buffer, check for the word @samp{Narrow} in the mode line.
 If it appears, the text you don't see is probably still present, but
 temporarily off-limits.  To make it accessible again, type @kbd{C-x n
 w}.  @xref{Narrowing}.
-@node Unasked-for Search
-@subsection Spontaneous Entry to Incremental Search
-If Emacs spontaneously displays @samp{I-search:} at the bottom of the
-screen, it means that the terminal is sending @kbd{C-s} and @kbd{C-q}
-according to the poorly designed xon/xoff ``flow control'' protocol.
-If this happens to you, your best recourse is to put the terminal in a
-mode where it will not use flow control, or give it so much padding that
-it will never send a @kbd{C-s}.  (One way to increase the amount of
-padding is to set the variable @code{baud-rate} to a larger value.  Its
-value is the terminal output speed, measured in the conventional units
-of baud.)
-@cindex flow control
-@cindex xon-xoff
-@findex enable-flow-control
-If you don't succeed in turning off flow control, the next best thing
-is to tell Emacs to cope with it.  To do this, call the function
-@code{enable-flow-control}.
-@findex enable-flow-control-on
-Typically there are particular terminal types with which you must use
-flow control.  You can conveniently ask for flow control on those
-terminal types only, using @code{enable-flow-control-on}.  For example,
-if you find you must use flow control on VT-100 and H19 terminals, put
-the following in your @file{.emacs} file:
-@example
-(enable-flow-control-on "vt100" "h19")
-@end example
-When flow control is enabled, you must type @kbd{C-\} to get the
-effect of a @kbd{C-s}, and type @kbd{C-^} to get the effect of a
-@kbd{C-q}.
 @node Memory Full
 @subsection Running out of Memory
 @cindex memory full
 @cindex out of memory
 This command initially displays a buffer which lists interrupted
 session files, each with its date.  You must choose which session to
 recover from.  Typically the one you want is the most recent one.  Move
 point to the one you choose, and type @kbd{C-c C-c}.
-Then @code{recover-session} asks about each of the files that you were
+Then @code{recover-session} considers each of the files that you
-editing during that session; it asks whether to recover that file.  If
+were editing during that session; for each such file, it asks whether
-you answer @kbd{y} for a file, it shows the dates of that file and its
+to recover that file.  If you answer @kbd{y} for a file, it shows the
-auto-save file, then asks once again whether to recover that file.  For
+dates of that file and its auto-save file, then asks once again
-the second question, you must confirm with @kbd{yes}.  If you do, Emacs
+whether to recover that file.  For the second question, you must
-visits the file but gets the text from the auto-save file.
+confirm with @kbd{yes}.  If you do, Emacs visits the file but gets the
+text from the auto-save file.
 When @code{recover-session} is done, the files you've chosen to
 recover are present in Emacs buffers.  You should then save them.  Only
 this---saving them---updates the files themselves.
 have recorded important changes, you can use the
 @file{etc/emacs-buffer.gdb} script with GDB (the GNU Debugger) to
 retrieve them from a core dump--provided that a core dump was saved,
 and that the Emacs executable was not stripped of its debugging
 symbols.
+As soon as you get the core dump, rename it to another name such as
+@file{core.emacs}, so that another crash won't overwrite it.
 To use this script, run @code{gdb} with the file name of your Emacs
 executable and the file name of the core dump, e.g. @samp{gdb
 /usr/bin/emacs core.emacs}.  At the @code{(gdb)} prompt, load the
 recovery script: @samp{source /usr/src/emacs/etc/emacs-buffer.gdb}.
 not make a backup of its old contents.
 @node Emergency Escape
 @subsection Emergency Escape
-Because at times there have been bugs causing Emacs to loop without
+On text-only terminals, the @dfn{emergency escape} feature suspends
-checking @code{quit-flag}, a special feature causes Emacs to be suspended
+Emacs immediately if you type @kbd{C-g} a second time before Emacs can
-immediately if you type a second @kbd{C-g} while the flag is already set,
+actually respond to the first one by quitting.  This is so you can
-so you can always get out of GNU Emacs.  Normally Emacs recognizes and
+always get out of GNU Emacs no matter how badly it might be hung.
-clears @code{quit-flag} (and quits!) quickly enough to prevent this from
+When things are working properly, Emacs recognizes and handles the
-happening.  (On MS-DOS and compatible systems, type @kbd{C-@key{BREAK}}
+first @kbd{C-g} so fast that the second one won't trigger emergency
-twice.)
+escape.  However, if some problem prevents Emacs from handling the
+first @kbd{C-g} properly, then the second one will get you back to the
-When you resume Emacs after a suspension caused by multiple @kbd{C-g}, it
+shell.
-asks two questions before going back to what it had been doing:
+When you resume Emacs after a suspension caused by emergency escape,
+it asks two questions before going back to what it had been doing:
 @example
 Auto-save? (y or n)
 Abort (and dump core)? (y or n)
 @end example
 @noindent
 Answer each one with @kbd{y} or @kbd{n} followed by @key{RET}.
-Saying @kbd{y} to @samp{Auto-save?} causes immediate auto-saving of all
+Saying @kbd{y} to @samp{Auto-save?} causes immediate auto-saving of
-modified buffers in which auto-saving is enabled.
+all modified buffers in which auto-saving is enabled.  Saying @kbd{n}
+skips this.
-Saying @kbd{y} to @samp{Abort (and dump core)?} causes an illegal instruction to be
-executed, dumping core.  This is to enable a wizard to figure out why Emacs
+Saying @kbd{y} to @samp{Abort (and dump core)?} causes Emacs to
-was failing to quit in the first place.  Execution does not continue
+crash, dumping core.  This is to enable a wizard to figure out why
-after a core dump.  If you answer @kbd{n}, execution does continue.  With
+Emacs was failing to quit in the first place.  Execution does not
-luck, GNU Emacs will ultimately check @code{quit-flag} and quit normally.
+continue after a core dump.
-If not, and you type another @kbd{C-g}, it is suspended again.
+If you answer this question @kbd{n}, Emacs execution resumes.  With
+luck, Emacs will ultimately do the requested quit.  If not, each
+subsequent @kbd{C-g} invokes emergency escape again.
 If Emacs is not really hung, just slow, you may invoke the double
-@kbd{C-g} feature without really meaning to.  Then just resume and answer
+@kbd{C-g} feature without really meaning to.  Then just resume and
-@kbd{n} to both questions, and you will arrive at your former state.
+answer @kbd{n} to both questions, and you will get back to the former
-Presumably the quit you requested will happen soon.
+state.  The quit you requested will happen by and by.
-The double @kbd{C-g} feature is turned off when Emacs is running under
+Emergency escape is active only for text terminals.  On a graphical
-the X Window System, since you can use the window manager to kill Emacs
+display that supports multiple windows, you can use the window manager
-or to create another window and run another program.
+to kill Emacs, or to switch to some other program.
-On MS-DOS and compatible systems, the emergency escape feature is
+On MS-DOS, you must type @kbd{C-@key{BREAK}} (twice) to cause
-sometimes unavailable, even if you press @kbd{C-@key{BREAK}} twice, when
+emergency escape---but there are cases where it won't work, when
-some system call (MS-DOS or BIOS) hangs, or when Emacs is stuck in a
+system call hangs or when Emacs is stuck in a tight loop in C code.
-very tight endless loop (in C code, @strong{not} in Lisp code).
 @node Total Frustration
 @subsection Help for Total Frustration
 @cindex Eliza
 @cindex doctor
 @kbd{C-g C-g} to get out of it and then start a new one.
 @findex doctor
 Second, type @kbd{M-x doctor @key{RET}}.
-The doctor will help you feel better.  Each time you say something to
+The Emacs psychotherapist will help you feel better.  Each time you
-the doctor, you must end it by typing @key{RET} @key{RET}.  This lets
+say something to the psychotherapist, you must end it by typing
-the doctor know you are finished.
+@key{RET} @key{RET}.  This indicates you are finished typing.
 @node Bugs, Contributing, Lossage, Top
 @section Reporting Bugs
 @cindex bugs
 @end menu
 @node Bug Criteria
 @subsection When Is There a Bug
-If Emacs executes an illegal instruction, or dies with an operating
+If Emacs accesses an invalid memory location (``segmentation
-system error message that indicates a problem in the program (as opposed to
+fault''), or exits with an operating system error message that
-something like ``disk full''), then it is certainly a bug.
+indicates a problem in the program (as opposed to something like
+``disk full''), then it is certainly a bug.
 If Emacs updates the display in a way that does not correspond to what is
 in the buffer, then it is certainly a bug.  If a command seems to do the
 wrong thing but the problem corrects itself if you type @kbd{C-l}, it is a
 case of incorrect display updating.
 of problem, but it is also a matter of judgment.  Also, it is easy to
 come to such a conclusion out of ignorance of some of the existing
 features.  It is probably best not to complain about such a problem
 until you have checked the documentation in the usual ways, feel
 confident that you understand it, and know for certain that what you
-want is not available.  If you are not sure what the command is
+want is not available.  Ask other Emacs users, too.  If you are not
-supposed to do after a careful reading of the manual, check the index
+sure what the command is supposed to do after a careful reading of the
-and glossary for any terms that may be unclear.
+manual, check the index and glossary for any terms that may be
+unclear.
 If after careful rereading of the manual you still do not understand
 what the command should do, that indicates a bug in the manual, which
 you should report.  The manual's job is to make everything clear to
 people who are not Emacs experts---including you.  It is just as
 facts.  If the explanations are based on guesses about how Emacs is
 implemented, they will be useless; meanwhile, lacking the facts, we will
 have no real information about the bug.
 For example, suppose that you type @kbd{C-x C-f /glorp/baz.ugh
-@key{RET}}, visiting a file which (you know) happens to be rather large,
+@key{RET}}, visiting a file which (you know) happens to be rather
-and Emacs displayed @samp{I feel pretty today}.  The best way to report
+large, and Emacs displays @samp{I feel pretty today}.  The best way to
-the bug is with a sentence like the preceding one, because it gives all
+report the bug is with a sentence like the preceding one, because it
-the facts.
+gives all the facts.
 A bad way would be to assume that the problem is due to the size of
 the file and say, ``I visited a large file, and Emacs displayed @samp{I
 feel pretty today}.''  This is what we mean by ``guessing
 explanations.''  The problem is just as likely to be due to the fact
 You should not even say ``visit a file'' instead of @kbd{C-x C-f} unless
 you @emph{know} that it makes no difference which visiting command is used.
 Similarly, rather than saying ``if I have three characters on the line,''
 say ``after I type @kbd{@key{RET} A B C @key{RET} C-p},'' if that is
-the way you entered the text.@refill
+the way you entered the text.
 So please don't guess any explanations when you report a bug.  If you
 want to actually @emph{debug} the problem, and report explanations that
 are more than guesses, that is useful---but please include the facts as
 well.
 in order to ask you for more information.  If your data is more than
 500,000 bytes, please don't include it directly in the bug report;
 instead, offer to send it on request, or make it available by ftp and
 say where.
-If you can't send electronic mail, then mail the bug report on paper
-or machine-readable media to this address:
-@format
-GNU Emacs Bugs
-Free Software Foundation
-51 Franklin Street, Fifth Floor
-Boston, MA 02110-1301 USA
-@end format
-We do not promise to fix the bug; but if the bug is serious,
-or ugly, or easy to fix, chances are we will want to.
 @findex report-emacs-bug
 A convenient way to send a bug report for Emacs is to use the command
 @kbd{M-x report-emacs-bug}.  This sets up a mail buffer (@pxref{Sending
 Mail}) and automatically inserts @emph{some} of the essential
 information.  However, it cannot supply all the necessary information;
 The complete text of any files needed to reproduce the bug.
 If you can tell us a way to cause the problem without visiting any files,
 please do so.  This makes it much easier to debug.  If you do need files,
 make sure you arrange for us to see their exact contents.  For example, it
-can often matter whether there are spaces at the ends of lines, or a
+can matter whether there are spaces at the ends of lines, or a
 newline after the last line in the buffer (nothing ought to care whether
 the last line is terminated, but try telling the bugs that).
 @item
 The precise commands we need to type to reproduce the bug.
 @findex open-dribble-file
 @cindex dribble file
 @cindex logging keystrokes
 The easy way to record the input to Emacs precisely is to write a
 dribble file.  To start the file, execute the Lisp expression
 @example
 (open-dribble-file "~/dribble")
 @end example
 your @file{.emacs} file so that the termscript file will be open when
 Emacs displays the screen for the first time.
 Be warned: it is often difficult, and sometimes impossible, to fix a
 terminal-dependent bug without access to a terminal of the type that
-stimulates the bug.@refill
+stimulates the bug.
 @item
 If non-@acronym{ASCII} text or internationalization is relevant, the locale that
 was current when you started Emacs.  On GNU/Linux and Unix systems, or
 if you use a Posix-style shell such as Bash, you can use this shell
 @findex toggle-debug-on-error
 @pindex Edebug
 To make a backtrace for the error, use @kbd{M-x toggle-debug-on-error}
 before the error happens (that is to say, you must give that command
-and then make the bug happen).  This causes the error to run the Lisp
+and then make the bug happen).  This causes the error to start the Lisp
 debugger, which shows you a backtrace.  Copy the text of the
 debugger's backtrace into the bug report.  @xref{Debugger,, The Lisp
 Debugger, elisp, the Emacs Lisp Reference Manual}, for information on
 debugging Emacs Lisp programs with the Edebug package.
 you need not explain its purpose in the change log.  Thus, if you add a
 new function, all you need to say about it is that it is new.  If you
 feel that the purpose needs explaining, it probably does---but put the
 explanation in comments in the code.  It will be more useful there.
-Please read the @file{ChangeLog} files in the @file{src} and @file{lisp}
+Please read the @file{ChangeLog} files in the @file{src} and
-directories to see what sorts of information to put in, and to learn the
+@file{lisp} directories to see what sorts of information to put in,
-style that we use.  If you would like your name to appear in the header
+and to learn the style that we use.  @xref{Change Log}.
-line, showing who made the change, send us the header line.
-@xref{Change Log}.
 @item
 When you write the fix, keep in mind that we can't install a change that
 would break other systems.  Please think about what effect your change
 will have if compiled on another type of system.
 possible to suggest ways to make your extension fit in better with the
 rest of Emacs.
 The development version of Emacs can be downloaded from the CVS
 repository where it is actively maintained by a group of developers.
-See the Emacs project page http://savannah.gnu.org/projects/emacs/ for
+See the Emacs project page
-details.
+@url{http://savannah.gnu.org/projects/emacs/} for details.
 @node Service, Copying, Contributing, Top
 @section How To Get Help with GNU Emacs
 If you need help installing, using or changing GNU Emacs, there are two

Mercurial > emacs

comparison man/trouble.texi @ 83507:81f2d90dee68