Samuel Bronson writes:
I've been seeing a lot of ^Ms in the output of various processes
lately.
There was a bunch of work done trying to update comint to work with
more recent gdb and gud front-ends for XEmacs. Unfortunately, it
didn't work well and bunches of stuff got reverted.
I think the long-run solution is a "universal eol" eol type a la
Python. (There's also a Unicode TR that has something to say about
this.)
I'm experimenting with the following in my init file:
;; assume process output to use DOS line-end style
(setcar default-process-coding-system 'undecided-dos)
This probably also works, although you'll likely get stair-stepping
when you actually do work with Unix-style line endings.
and that seems to work for this stuff, but I'm concerned that
this
might run afoul of elisp programs trying to read binary data from
processes. Any thoughts?
Programs trying to read binary data had better specify it with
'binary. If you run into a problem with binary I/O because of your
default setting, that's a bug in the program, not in your config.
If you have some applications where you're unwilling to risk data loss
even if you're entirely justified in changing the default, be specific
and we can audit them or you can test them.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta