GNU bug report logs -
#67023
comint comments commend field=input
Previous Next
To reply to this bug, email your comments to 67023 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#67023
; Package
emacs
.
(Thu, 09 Nov 2023 18:26:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
JD Smith <jdtsmith <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Thu, 09 Nov 2023 18:26:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
comint.el contains the following comment at line 1959, applicable when comint-use-prompt-regexp=nil:
;; Give old user input a field property of `input', to
;; distinguish it from both process output and unsent
;; input. The terminating newline is put into a special
;; `boundary' field to make cursor movement between input
;; and output fields smoother.
But this is not actually done. Just as for unsent input at the process mark, old input has text property field=nil.
I traced it back and this change was made in Emacs 22, at the same time overlay properties for the various comint fields were replaced by text properties. Perhaps this is the desired behavior, and only fixing the comments is required. However, the stated rationale to “distinguish from output and current unsent input” still seems applicable.
Note that `comint-next-prompt’ checks explicitly for a null field value to know when it has moved past a prompt. Comments in that function erroneously mention field=nil as pertaining only to unsent input at the end of the comint buffer.
This bug report was last modified 1 year and 14 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.