procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge from origin/emacs-28

Browse source 
756b8a5f1b Fix typos in documentation
38fdeaef46 ; * etc/DEBUG: Fix last change.
This commit is contained in:
Stefan Kangas 2021-11-24 07:00:27 +01:00
commit d112c75f53
3 changed files with 11 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/lispref/anti.texi
View file

@ -135,7 +135,7 @@ the programmers should be trusted to know what they are doing.
@item
We deleted several features of the @code{pcase} macro, in accordance
with our general plane to remove @code{pcase} from Emacs:
with our general plan to remove @code{pcase} from Emacs:
@itemize @minus
@item

6
doc/misc/efaq.texi
View file

@ -1086,7 +1086,7 @@ Emacs Lisp form at point.
@cindex pasting text on text terminals
@cindex bracketed paste mode
@item
On text terminals that support the ``bracketed paste mode'' EMacs now
On text terminals that support the ``bracketed paste mode'' Emacs now
uses that mode by default. This mode allows Emacs to distinguish
between pasted text and text typed by the user.
@ -2542,12 +2542,12 @@ load @code{dired-x} by adding the following to your @file{.emacs} file:
(require 'dired-x))
@end lisp
With @code{dired-x} loaded, @kbd{M-o} toggles omitting in each dired buffer.
With @code{dired-x} loaded, @kbd{C-x M-o} toggles omitting in each dired buffer.
You can make omitting the default for new dired buffers by putting the
following in your @file{.emacs}:
@lisp
(add-hook 'dired-mode-hook 'dired-omit-toggle)
(add-hook 'dired-mode-hook 'dired-omit-mode)
@end lisp
If you're tired of seeing backup files whenever you do an @samp{ls} at

11
etc/DEBUG
View file

@ -591,10 +591,13 @@ If you cannot figure out the cause for the problem using the above,
native-compile the problematic file after setting the variable
'comp-libgccjit-reproducer' to a non-nil value. That should produce a
file named ELNFILENAME_libgccjit_repro.c, where ELNFILENAME is the
name of the problematic .eln file in the same directory where the .eln
file is produced, or a file repro.c under your ~/.emacs.d/eln-cache
(which one depends on how the native-compilation is invoked). Then
attach that reproducer C file to your bug report.
name of the problematic .eln file, either in the same directory where
the .eln file is produced, or under your ~/.emacs.d/eln-cache (which
one depends on how the native-compilation is invoked). It is also
possible that the reproducer file's name will be something like
subr--trampoline-XXXXXXX_FUNCTION_libgccjit_repro.c, where XXXXXXX is
a long string of hex digits and FUNCTION is some function from the
compiled .el file. Attach that reproducer C file to your bug report.
** Following longjmp call.