summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp/byte-run.el
diff options
context:
space:
mode:
authorRobert Pluim <rpluim@gmail.com>2020-04-02 17:52:01 +0200
committerRobert Pluim <rpluim@gmail.com>2020-04-03 14:45:49 +0200
commitd08e81ce5a19a0394c2efbdfeb4ebb246d609635 (patch)
tree765bef42ad5bf8278eebb654571f87cbfb4b352f /lisp/emacs-lisp/byte-run.el
parent463f635171683ae3b6907f156305f12fc58ca68e (diff)
downloademacs-d08e81ce5a19a0394c2efbdfeb4ebb246d609635.tar.gz
emacs-d08e81ce5a19a0394c2efbdfeb4ebb246d609635.tar.bz2
emacs-d08e81ce5a19a0394c2efbdfeb4ebb246d609635.zip
Make make-{network,serial}-process handle :coding nil consistently
The handling of :coding nil was different between make-{network,serial}-process and make-{pipe}process. Now they all handle :coding nil as if :coding had not been specified. * process.c (Fmake_serial_process) (set_network_socket_coding_system): Use plist-get to check if :coding has been specified instead of plist-member, to ensure that ":coding nil" does not override coding-system-for-{read,write}. * network-stream-tests.el (check-network-process-coding-system-bind) (check-network-process-coding-system-no-override) (check-network-process-coding-system-override): New tests. * etc/NEWS: Describe change in make-network-process and make-serial-process :coding behavior.
Diffstat (limited to 'lisp/emacs-lisp/byte-run.el')
0 files changed, 0 insertions, 0 deletions