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
4
Issues
4
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
66b6c480
Commit
66b6c480
authored
Aug 07, 2000
by
Miles Bader
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add note about comint field changes (`comint-prompt-regexp removal').
parent
46645f4b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
0 deletions
+9
-0
etc/NEWS
etc/NEWS
+9
-0
No files found.
etc/NEWS
View file @
66b6c480
...
...
@@ -596,6 +596,15 @@ mode.
** Comint (subshell) changes
By default, comint no longer uses the variable `comint-prompt-regexp' to
distiguish prompts from user-input. Instead, it notices which parts of
the text were output by the process, and which entered by the user, and
attaches `field' properties to allow emacs commands to use this information.
Common movement commands, notably beginning-of-line, respect field
boundaries in a fairly natural manner.
To disable this feature, and use the old behavior, set the variable
`comint-use-prompt-regexp-instead-of-fields'
to a non-nil value.
Comint now includes new features to send commands to running processes
and redirect the output to a designated buffer or buffers.
...
...
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