Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
7
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
8248b4ad
Commit
8248b4ad
authored
May 01, 2004
by
Luc Teirlinck
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
*** empty log message ***
parent
0dbc1dd0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
10 deletions
+14
-10
etc/NEWS
etc/NEWS
+14
-10
No files found.
etc/NEWS
View file @
8248b4ad
...
...
@@ -95,16 +95,20 @@ types any more. Add -DUSE_LISP_UNION_TYPE if you want union types.
option `comint-prompt-read-only'. This is not enabled by default,
except in IELM buffers. The read-only status of IELM prompts can be
controlled with the new user option `ielm-prompt-read-only', which
overrides `comint-prompt-read-only'. The new commands
`comint-kill-whole-line' and `comint-kill-region' support editing
comint buffers with read-only prompts. `comint-kill-whole-line' is
like `kill-whole-line', but ignores both read-only and field
properties. Hence, it will always kill entire lines, including any
prompts. `comint-kill-region' is like `kill-region', except that it
ignores read-only properties, if it is safe to do so. This means that
if any part of a prompt is deleted, then the entire prompt must be
deleted and that all prompts must stay at the beginning of a line. If
this is not the case, then `comint-kill-region' behaves just like
overrides `comint-prompt-read-only'.
The new commands `comint-kill-whole-line' and `comint-kill-region'
support editing comint buffers with read-only prompts.
`comint-kill-whole-line' is like `kill-whole-line', but ignores both
read-only and field properties. Hence, it will always kill entire
lines, including any prompts.
`comint-kill-region' is like `kill-region', except that it ignores
read-only properties, if it is safe to do so. This means that if any
part of a prompt is deleted, then the entire prompt must be deleted
and that all prompts must stay at the beginning of a line. If this is
not the case, then `comint-kill-region' behaves just like
`kill-region' if read-only are involved: it copies the text to the
kill-ring, but does not delete it.
...
...
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