Mercurial > emacs
comparison etc/NEWS @ 55303:d71fb69263a2
*** empty log message ***
| author | Luc Teirlinck <teirllm@auburn.edu> |
|---|---|
| date | Sat, 01 May 2004 22:39:27 +0000 |
| parents | 56bb135eddf9 |
| children | a052e022db03 |
comparison
equal
deleted
inserted
replaced
| 55302:56bb135eddf9 | 55303:d71fb69263a2 |
|---|---|
| 93 --- | 93 --- |
| 94 ** The comint prompt can now be made read-only, using the new user | 94 ** The comint prompt can now be made read-only, using the new user |
| 95 option `comint-prompt-read-only'. This is not enabled by default, | 95 option `comint-prompt-read-only'. This is not enabled by default, |
| 96 except in IELM buffers. The read-only status of IELM prompts can be | 96 except in IELM buffers. The read-only status of IELM prompts can be |
| 97 controlled with the new user option `ielm-prompt-read-only', which | 97 controlled with the new user option `ielm-prompt-read-only', which |
| 98 overrides `comint-prompt-read-only'. The new commands | 98 overrides `comint-prompt-read-only'. |
| 99 `comint-kill-whole-line' and `comint-kill-region' support editing | 99 |
| 100 comint buffers with read-only prompts. `comint-kill-whole-line' is | 100 The new commands `comint-kill-whole-line' and `comint-kill-region' |
| 101 like `kill-whole-line', but ignores both read-only and field | 101 support editing comint buffers with read-only prompts. |
| 102 properties. Hence, it will always kill entire lines, including any | 102 |
| 103 prompts. `comint-kill-region' is like `kill-region', except that it | 103 `comint-kill-whole-line' is like `kill-whole-line', but ignores both |
| 104 ignores read-only properties, if it is safe to do so. This means that | 104 read-only and field properties. Hence, it will always kill entire |
| 105 if any part of a prompt is deleted, then the entire prompt must be | 105 lines, including any prompts. |
| 106 deleted and that all prompts must stay at the beginning of a line. If | 106 |
| 107 this is not the case, then `comint-kill-region' behaves just like | 107 `comint-kill-region' is like `kill-region', except that it ignores |
| 108 read-only properties, if it is safe to do so. This means that if any | |
| 109 part of a prompt is deleted, then the entire prompt must be deleted | |
| 110 and that all prompts must stay at the beginning of a line. If this is | |
| 111 not the case, then `comint-kill-region' behaves just like | |
| 108 `kill-region' if read-only are involved: it copies the text to the | 112 `kill-region' if read-only are involved: it copies the text to the |
| 109 kill-ring, but does not delete it. | 113 kill-ring, but does not delete it. |
| 110 | 114 |
| 111 ** You can now use next-error (C-x `) and previous-error to advance to | 115 ** You can now use next-error (C-x `) and previous-error to advance to |
| 112 the next/previous matching line found by M-x occur. | 116 the next/previous matching line found by M-x occur. |