Re: [BUG] ob-shell doesn't evaluate last line on Windows (cmd/cmdproxy) [9.6.1 ( @ c:/Users/Osher/AppData/Roaming/.emacs.d/elpa/org-9.6.1/)]

Thanks for the suggestions! On Wed, Jan 18, 2023 at 7:09 AM Matt wrote: > > 1. Another naive work around attempt. Again, I'm going from memory, > documentation, and what I have previously written. > > I have in my init a command to open a terminal when working on Windows > that looks like: > >

[BUG] Org babel does not evaluate last line in Windows shell (cmdproxy.exe) code blocks [9.5.2 (release_9.5.2-25-gaf6f12 @ c:/tools/emacs-28.1/share/emacs/28.1/lisp/org/)]

*Expected behaviour*: All lines of the shell block should be evaluated, with full output printed. *Actual behaviour*: All lines but the last are evaluated, the output ends with 'More?' instead of the last command's output. *Steps to reproduce*: In Windows, start a clean Emacs instance (I used "ru

Re: [BUG] ob-shell doesn't evaluate last line on Windows (cmd/cmdproxy) [9.6.1 ( @ c:/Users/Osher/AppData/Roaming/.emacs.d/elpa/org-9.6.1/)]

Hey, thanks for the input! My shell-file-name is indeed pointing to cmdproxy.exe, and after changing shell-command-switch to "/k" or "-k", I get a similar output: #+begin_src shell echo 1 echo 2 echo 3 #+end_src #+RESULTS: | Microsoft| Windows | [Version | 10.0.14393] | |

[BUG] ob-shell doesn't evaluate last line on Windows (cmd/cmdproxy) [9.6.1 ( @ c:/Users/Osher/AppData/Roaming/.emacs.d/elpa/org-9.6.1/)]

*Expected behaviour:*On Windows, all lines of the babel shell block should be evaluated, with full output printed. *Actual behaviour:*All lines but the last are evaluated, the output ends with 'More?' instead of the last command's output. *Steps to reproduce:*In Windows, start a clean Emacs ins