Mercurial > emacs
changeset 55302:56bb135eddf9
*** empty log message ***
| author | Luc Teirlinck <teirllm@auburn.edu> |
|---|---|
| date | Sat, 01 May 2004 22:24:39 +0000 |
| parents | c2bea9cc10a3 |
| children | d71fb69263a2 |
| files | etc/NEWS |
| diffstat | 1 files changed, 16 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/etc/NEWS Sat May 01 21:19:31 2004 +0000 +++ b/etc/NEWS Sat May 01 22:24:39 2004 +0000 @@ -91,8 +91,22 @@ * Changes in Emacs 21.4 --- -** The IELM prompt is now, by default, read-only. This can be -controlled with the new user option `ielm-prompt-read-only'. +** The comint prompt can now be made read-only, using the new user +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 +`kill-region' if read-only are involved: it copies the text to the +kill-ring, but does not delete it. ** You can now use next-error (C-x `) and previous-error to advance to the next/previous matching line found by M-x occur.