Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
de09aa52
Commit
de09aa52
authored
Oct 08, 2011
by
Chong Yidong
Browse files
* doc/emacs/mini.texi (Completion Options): Document completion-cycle-threshold.
parent
2d3fe5d7
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
38 additions
and
25 deletions
+38
-25
doc/emacs/ChangeLog
doc/emacs/ChangeLog
+4
-0
doc/emacs/mini.texi
doc/emacs/mini.texi
+26
-17
etc/NEWS
etc/NEWS
+8
-8
No files found.
doc/emacs/ChangeLog
View file @
de09aa52
2011-10-08 Chong Yidong <cyd@stupidchicken.com>
* mini.texi (Completion Options): Add completion-cycle-threshold.
2011-10-08 Eli Zaretskii <eliz@gnu.org>
2011-10-08 Eli Zaretskii <eliz@gnu.org>
* mule.texi (Bidirectional Editing): Correct some inaccuracies.
* mule.texi (Bidirectional Editing): Correct some inaccuracies.
...
...
doc/emacs/mini.texi
View file @
de09aa52
...
@@ -462,24 +462,26 @@ variable @code{read-file-name-completion-ignore-case} is
...
@@ -462,24 +462,26 @@ variable @code{read-file-name-completion-ignore-case} is
non-@code{nil}. The default value is @code{nil} on systems that have
non-@code{nil}. The default value is @code{nil} on systems that have
case-sensitive file-names, such as GNU/Linux; it is non-@code{nil} on
case-sensitive file-names, such as GNU/Linux; it is non-@code{nil} on
systems that have case-insensitive file-names, such as Microsoft
systems that have case-insensitive file-names, such as Microsoft
Windows. When completing buffer names, case
is significant by
Windows. When completing buffer names, case
differences are ignored
default; to ignore case differences, change the variable
if the variable @code{read-buffer-completion-ignore-case} is
@code{
read-buffer-completion-ignore-case} to a non-
@code{nil}
value
.
non-
@code{
nil}; the default is
@code{nil}.
@vindex completion-ignored-extensions
@vindex completion-ignored-extensions
@cindex ignored file names, in completion
@cindex ignored file names, in completion
When completing file names, Emacs usually omits certain alternatives
When completing file names, Emacs usually omits certain alternatives
that are considered unlikely to be chosen. The variable
that are considered unlikely to be chosen, as determined by the list
@code{completion-ignored-extensions} contains a list of strings; a
variable @code{completion-ignored-extensions}. Each element in the
file name ending in any of those strings is ignored as a completion
list should be a string; any file name ending in such a string is
alternative. The standard value of this variable has several elements
ignored as a completion alternative. Any element ending in a slash
including @code{".o"}, @code{".elc"}, and @code{"~"}. For example, if
(@file{/}) represents a subdirectory name. The standard value of
a directory contains @samp{foo.c} and @samp{foo.elc}, @samp{foo}
@code{completion-ignored-extensions} has several elements including
@code{".o"}, @code{".elc"}, and @code{"~"}. For example, if a
directory contains @samp{foo.c} and @samp{foo.elc}, @samp{foo}
completes to @samp{foo.c}. However, if @emph{all} possible
completes to @samp{foo.c}. However, if @emph{all} possible
completions end in ``ignored'' strings, they are not ignored: in the
completions end in ``ignored'' strings, they are not ignored: in the
previous example, @samp{foo.e} completes to @samp{foo.elc}.
previous example, @samp{foo.e} completes to @samp{foo.elc}.
Emacs
D
is
playing the completion list disregards
d
is
regards @code{completion-ignored-extensions} when showing
@code{
completion
-ignored-extensions}; all
completion
s are
list
ed
.
completion
alternatives in the
completion list.
@vindex completion-auto-help
@vindex completion-auto-help
If @code{completion-auto-help} is set to @code{nil}, the completion
If @code{completion-auto-help} is set to @code{nil}, the completion
...
@@ -490,11 +492,18 @@ In other words, if there is nothing to complete, the first @key{TAB}
...
@@ -490,11 +492,18 @@ In other words, if there is nothing to complete, the first @key{TAB}
echoes @samp{Next char not unique}; the second @key{TAB} does the
echoes @samp{Next char not unique}; the second @key{TAB} does the
completion list buffer.
completion list buffer.
If an element of @code{completion-ignored-extensions} ends in a
@vindex completion-cycle-threshold
slash (@file{/}), it's a subdirectory name; that directory and its
If @code{completion-cycle-threshold} is non-@code{nil}, completion
contents are ignored. Elements of
commands can ``cycle'' through completion alternatives. Normally, if
@code{completion-ignored-extensions} that do not end in a slash are
there is more than one completion alternative for the text in the
ordinary file names.
minibuffer, a completion command completes up to the longest common
substring. If you change @code{completion-cycle-threshold} to
@code{t}, the completion command instead completes to the first of
those completion alternatives; each subsequent invocation of the
completion command replaces that with the next completion alternative,
in a cyclic manner. If you give @code{completion-cycle-threshold} a
numeric value @var{n}, completion commands switch to this cycling
behavior only when there are fewer than @var{n} alternatives.
@cindex Icomplete mode
@cindex Icomplete mode
@findex icomplete-mode
@findex icomplete-mode
...
...
etc/NEWS
View file @
de09aa52
...
@@ -103,7 +103,7 @@ rather than their own completion code.
...
@@ -103,7 +103,7 @@ rather than their own completion code.
---
---
*** Completion in a non-minibuffer now tries to detect the end of completion
*** Completion in a non-minibuffer now tries to detect the end of completion
and pops down the *Completions* buffer accordingly.
and pops down the *Completions* buffer accordingly.
+++
*** Completion can cycle, depending on completion-cycle-threshold.
*** Completion can cycle, depending on completion-cycle-threshold.
+++
+++
*** New completion style `substring'.
*** New completion style `substring'.
...
@@ -112,13 +112,6 @@ and pops down the *Completions* buffer accordingly.
...
@@ -112,13 +112,6 @@ and pops down the *Completions* buffer accordingly.
*** Completion of buffers now uses substring completion by default.
*** Completion of buffers now uses substring completion by default.
*** `completing-read' can be customized using the new variable
`completing-read-function'.
*** minibuffer-local-filename-must-match-map is not used any more.
Instead, the bindings in minibuffer-local-filename-completion-map are combined
with minibuffer-local-must-match-map.
** Mail changes
** Mail changes
The default of `send-mail-function' is now `sendmail-query-once',
The default of `send-mail-function' is now `sendmail-query-once',
...
@@ -1133,6 +1126,13 @@ can specify various details of the data returned by `all-completions':
...
@@ -1133,6 +1126,13 @@ can specify various details of the data returned by `all-completions':
- `display-sort-function' to specify how to sort entries in *Completions*.
- `display-sort-function' to specify how to sort entries in *Completions*.
- `cycle-sort-function' to specify how to sort entries when cycling.
- `cycle-sort-function' to specify how to sort entries when cycling.
*** minibuffer-local-filename-must-match-map is not used any more.
Instead, the bindings in minibuffer-local-filename-completion-map are
combined with minibuffer-local-must-match-map.
*** New variable `completing-read-function' allows overriding the
behavior of `completing-read'.
** `glyphless-char-display' can now distinguish between graphical and
** `glyphless-char-display' can now distinguish between graphical and
text terminal display, via a char-table entry that is a cons cell.
text terminal display, via a char-table entry that is a cons cell.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment