Mercurial > hg > xemacs-beta

comparison man/xemacs/trouble.texi @ 442:abe6d1db359e r21-2-36

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2-36
author cvs
date Mon, 13 Aug 2007 11:35:02 +0200
parents 3ecd8885ac67
children 6b0000935adc
comparison
equal deleted inserted replaced
441:72a7cfa4a488 442:abe6d1db359e
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 @file{.emacs} file, set any variables that may affect the functioning 335 your init file, set any variables that may affect the functioning of
336 of Emacs. Also, see whether the problem happens in a freshly started Emacs 336 Emacs. @xref{Init File}. Also, see whether the problem happens in a
337 without loading your @file{.emacs} file (start Emacs with the @code{-q} switch 337 freshly started Emacs without loading your init file (start Emacs with
338 to prevent loading the init file). If the problem does @var{not} occur 338 the @code{-q} switch to prevent loading the init file). If the problem
339 then, it is essential that we know the contents of any programs that you 339 does @var{not} occur then, it is essential that we know the contents of
340 must load into the Lisp world in order to cause the problem to occur. 340 any programs that you must load into the Lisp world in order to cause
341 the problem to occur.
341 342
342 If the problem does depend on an init file or other Lisp programs that 343 If the problem does depend on an init file or other Lisp programs that
343 are not part of the standard Emacs system, then you should make sure it is 344 are not part of the standard Emacs system, then you should make sure it is
344 not a bug in those programs by complaining to their maintainers first. 345 not a bug in those programs by complaining to their maintainers first.
345 After they verify that they are using Emacs in a way that is supposed to 346 After they verify that they are using Emacs in a way that is supposed to
376 377
377 @example 378 @example
378 (open-termscript "~/termscript") 379 (open-termscript "~/termscript")
379 @end example 380 @end example
380 381
381 @noindent 382 @noindent using @kbd{Meta-@key{ESC}} or from the @samp{*scratch*} buffer
382 using @kbd{Meta-@key{ESC}} or from the @samp{*scratch*} buffer just 383 just after starting Emacs. From then on, all output from Emacs to the
383 after starting Emacs. From then on, all output from Emacs to the terminal 384 terminal will be written in the specified termscript file as well, until
384 will be written in the specified termscript file as well, until the Emacs 385 the Emacs process is killed. If the problem happens when Emacs starts
385 process is killed. If the problem happens when Emacs starts up, put this 386 up, put this expression into your init file so that the termscript file
386 expression into your @file{.emacs} file so that the termscript file will 387 will be open when Emacs displays the screen for the first time.
387 be open when Emacs displays the screen for the first time. Be warned: 388 @xref{Init File}. Be warned: it is often difficult, and sometimes
388 it is often difficult, and sometimes impossible, to fix a terminal-dependent 389 impossible, to fix a terminal-dependent bug without access to a terminal
389 bug without access to a terminal of the type that stimulates the bug.@refill 390 of the type that stimulates the bug.@refill
390 391
391 The newsgroup @samp{comp.emacs.xemacs} may be used for bug reports, 392 The newsgroup @samp{comp.emacs.xemacs} may be used for bug reports,
392 other discussions and requests for assistance. 393 other discussions and requests for assistance.
393 394
394 If you don't have access to this newgroup, you can subscribe to the 395 If you don't have access to this newgroup, you can subscribe to the