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
emacs
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
1
Issues
1
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
emacs
emacs
Commits
58a11372
Commit
58a11372
authored
Oct 13, 2001
by
Eli Zaretskii
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document the significance of the trailing slash in elements of
completion-ignored-extensions.
parent
d013f29b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
0 deletions
+7
-0
etc/NEWS
etc/NEWS
+7
-0
No files found.
etc/NEWS
View file @
58a11372
...
...
@@ -26,6 +26,13 @@ much pure storage it will approximately need.
`${foo}'
in the specified new value of the environment variable. To
include a `$' in the value, use `$$'.
** File-name completion can now ignore directories.
If an element of the list in `completion-ignored-extensions' ends in a
slash `/', it indicates a subdirectory that should be ignored when
completing file names. Elements of `completion-ignored-extensions'
which do not end in a slash are never considered when a completion
candidate is a directory.
** New user option `inhibit-startup-buffer-menu'.
When loading many files, for instance with `emacs *', Emacs normally
displays a buffer menu. This option turns the buffer menu off.
...
...
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