summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp/cl-generic.el
diff options
context:
space:
mode:
authorJim Porter <jporterbugs@gmail.com>2024-01-28 15:49:03 -0800
committerJim Porter <jporterbugs@gmail.com>2024-01-28 15:54:46 -0800
commit1f5a13d5843306af2e6a74fbdfd6d00af8804a23 (patch)
tree7ab1a6ba1a4fbd6e27b4e64e23a861b467481ccb /lisp/emacs-lisp/cl-generic.el
parente734f8e502e315441214936e89ecd1e11e981fca (diff)
downloademacs-1f5a13d5843306af2e6a74fbdfd6d00af8804a23.tar.gz
emacs-1f5a13d5843306af2e6a74fbdfd6d00af8804a23.tar.bz2
emacs-1f5a13d5843306af2e6a74fbdfd6d00af8804a23.zip
In Eshell, allow an escaped newline at the end of a command
Normally, "echo<RET>" runs the command "echo". Likewise, "echo\<RET><RET>" should too: we escape the first newline, and then the second one is unescaped and should send the command input to Eshell. Previously, you had to press RET a third time, but now it works as expected. * lisp/eshell/esh-arg.el (eshell-looking-at-backslash-return): Make obsolete. (eshell-parse-backslash): A backslash sequence is only incomplete if there's nothing at all after it. * test/lisp/eshell/esh-arg-tests.el (esh-arg-test/escape/newline) (esh-arg-test/escape-quoted/newline): Remove inaccurate comment; escaped newlines are always special. (esh-arg-test/escape/trailing-newline): New test.
Diffstat (limited to 'lisp/emacs-lisp/cl-generic.el')
0 files changed, 0 insertions, 0 deletions