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

*** empty log message ***

Browse source
This commit is contained in:
Gerd Moellmann 2001-02-06 12:19:34 +00:00
parent 78cab5d873
commit 36710aa696
4 changed files with 16 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
etc/NEWS
View file

@ -1558,7 +1558,7 @@ appropriate for C-style escape sequences in strings.
** A new command `view-emacs-problems' (C-h P) displays the PROBLEMS file.
+++
** The Dabbrev package has a new user-option `dabbrev-ignored-regexps'
** The Dabbrev package has a new user-option `dabbrev-ignored-buffer-regexps'
containing a list of regular expressions. Buffers matching a regular
expression from that list, are not checked.

5
lisp/ChangeLog
View file

@ -1,3 +1,8 @@
2001-02-06 Gerd Moellmann <gerd@gnu.org>
* dabbrev.el (dabbrev-ignored-buffer-regexps): Renamed from
dabbrev-ignored-regexps.
2001-02-06 Eli Zaretskii <eliz@is.elta.co.il>
* simple.el (kill-line): Doc fix.

8
man/abbrevs.texi
View file

@ -350,10 +350,10 @@ buffers, unless you have set @code{dabbrev-check-all-buffers} to
@code{nil}.
@vindex dabbrev-ignored-buffer-regexps
A more fine control of the buffers that are scanned is possible by
customizing the variable @code{dabbrev-ignored-buffer-regexps}, which should
contain a list of regular expressions. Buffers matching a regular
expression from that list are not searched.
For finer control over which buffers to scan, customize the variable
@code{dabbrev-ignored-buffer-regexps}. Its value is a list of regular
expressions. If a buffer's name matches any of these regular
expressions, dynamic abbrev expansion skips that buffer.
A negative argument to @kbd{M-/}, as in @kbd{C-u - M-/}, says to
search first for expansions after point, and second for expansions

12
man/basic.texi
View file

@ -175,8 +175,7 @@ Move backward one word (@code{backward-word}).
@item C-n
Move down one line, vertically (@code{next-line}). This command
attempts to keep the horizontal position unchanged, so if you start in
the middle of one line, you end in the middle of the next. When on
the last line of text, @kbd{C-n} creates a new line and moves onto it.
the middle of one line, you end in the middle of the next.
@item C-p
Move up one line, vertically (@code{previous-line}).
@item M-r
@ -219,10 +218,11 @@ to the end of another line. Normally, @code{track-eol} is @code{nil}.
@xref{Variables}, for how to set variables such as @code{track-eol}.
@vindex next-line-add-newlines
If non-@code{nil}, @kbd{C-n} on the last line of a buffer appends a
newline to it. If the variable @code{next-line-add-newlines} is
@code{nil}, the default, then @kbd{C-n} gets an error instead (like
@kbd{C-p} on the first line).
@kbd{C-n} normally gets an error when you use it on the last line of
the buffer (just as @kbd{C-p} gets an error on the first line). But
if you set the variable @code{next-line-add-newlines} to a
non-@code{nil} value, @kbd{C-n} on the last line of a buffer creates
an additional line at the end and moves down onto it.
@node Erasing
@section Erasing Text