Mercurial > hg > xemacs-beta
comparison man/xemacs/trouble.texi @ 412:697ef44129c6 r21-2-14
Import from CVS: tag r21-2-14
| author | cvs |
|---|---|
| date | Mon, 13 Aug 2007 11:20:41 +0200 |
| parents | de805c49cfc1 |
| children |
comparison
equal
deleted
inserted
replaced
| 411:12e008d41344 | 412:697ef44129c6 |
|---|---|
| 330 debugger is possible only if you know how to make the bug happen again. Do | 330 debugger is possible only if you know how to make the bug happen again. Do |
| 331 note the error message the first time the bug happens, so if you can't make | 331 note the error message the first time the bug happens, so if you can't make |
| 332 it happen again, you can report at least that. | 332 it happen again, you can report at least that. |
| 333 | 333 |
| 334 Check whether any programs you have loaded into the Lisp world, including | 334 Check whether any programs you have loaded into the Lisp world, including |
| 335 your init file, set any variables that may affect the functioning of | 335 your @file{.emacs} file, set any variables that may affect the functioning |
| 336 Emacs. @xref{Init File}. Also, see whether the problem happens in a | 336 of Emacs. Also, see whether the problem happens in a freshly started Emacs |
| 337 freshly started Emacs without loading your init file (start Emacs with | 337 without loading your @file{.emacs} file (start Emacs with the @code{-q} switch |
| 338 the @code{-q} switch to prevent loading the init file). If the problem | 338 to prevent loading the init file). If the problem does @var{not} occur |
| 339 does @var{not} occur then, it is essential that we know the contents of | 339 then, it is essential that we know the contents of any programs that you |
| 340 any programs that you must load into the Lisp world in order to cause | 340 must load into the Lisp world in order to cause the problem to occur. |
| 341 the problem to occur. | |
| 342 | 341 |
| 343 If the problem does depend on an init file or other Lisp programs that | 342 If the problem does depend on an init file or other Lisp programs that |
| 344 are not part of the standard Emacs system, then you should make sure it is | 343 are not part of the standard Emacs system, then you should make sure it is |
| 345 not a bug in those programs by complaining to their maintainers first. | 344 not a bug in those programs by complaining to their maintainers first. |
| 346 After they verify that they are using Emacs in a way that is supposed to | 345 After they verify that they are using Emacs in a way that is supposed to |
| 377 | 376 |
| 378 @example | 377 @example |
| 379 (open-termscript "~/termscript") | 378 (open-termscript "~/termscript") |
| 380 @end example | 379 @end example |
| 381 | 380 |
| 382 @noindent using @kbd{Meta-@key{ESC}} or from the @samp{*scratch*} buffer | 381 @noindent |
| 383 just after starting Emacs. From then on, all output from Emacs to the | 382 using @kbd{Meta-@key{ESC}} or from the @samp{*scratch*} buffer just |
| 384 terminal will be written in the specified termscript file as well, until | 383 after starting Emacs. From then on, all output from Emacs to the terminal |
| 385 the Emacs process is killed. If the problem happens when Emacs starts | 384 will be written in the specified termscript file as well, until the Emacs |
| 386 up, put this expression into your init file so that the termscript file | 385 process is killed. If the problem happens when Emacs starts up, put this |
| 387 will be open when Emacs displays the screen for the first time. | 386 expression into your @file{.emacs} file so that the termscript file will |
| 388 @xref{Init File}. Be warned: it is often difficult, and sometimes | 387 be open when Emacs displays the screen for the first time. Be warned: |
| 389 impossible, to fix a terminal-dependent bug without access to a terminal | 388 it is often difficult, and sometimes impossible, to fix a terminal-dependent |
| 390 of the type that stimulates the bug.@refill | 389 bug without access to a terminal of the type that stimulates the bug.@refill |
| 391 | 390 |
| 392 The newsgroup @samp{comp.emacs.xemacs} may be used for bug reports, | 391 The newsgroup @samp{comp.emacs.xemacs} may be used for bug reports, |
| 393 other discussions and requests for assistance. | 392 other discussions and requests for assistance. |
| 394 | 393 |
| 395 If you don't have access to this newgroup, you can subscribe to the | 394 If you don't have access to this newgroup, you can subscribe to the |