From: <miha@kamnitnik.top>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: comint-output-filter-functions and multi-line input
Date: Tue, 18 Oct 2022 09:22:39 +0200 [thread overview]
Message-ID: <87sfjlegu8.fsf@miha-pc> (raw)
In-Reply-To: <87pmepg0oo.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Ihor Radchenko <yantar92@posteo.net> writes:
> miha@kamnitnik.top writes:
>
>>> Is it possible to distinguish the actual script output, empty lines in
>>> the actual script output, and the incomplete prompts?
>>
>> You could prepend your multiline command with a dummy
>> 'echo multiline_starts_here' command have your
>> 'comint-output-filter-functions' discard output that arrives before
>> "multiline_starts_here".
>
> For context, I am asking because I am trying to figure out how ob-shell
> works in Org mode. My multiline command can be arbitrary bash script
> containing multiple single- and multi-line commands. It is hard to
> figure out which one is which.
I see. Perhaps you could turn your bash script into a single multi-line
command by encapsulating it into an 'if true' block. So given
if [ $(( 1 + 1 )) = 2 ]
then
echo "hello"
fi
echo $(( 3 + 4 ))
you could encapsulate it into something like
if true; then
echo "multiline_starts_here"
if [ $(( 1 + 1 )) = 2 ]
then
echo "hello"
fi
echo $(( 3 + 4 ))
echo "multiline_ends_here"
fi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-10-18 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 8:48 comint-output-filter-functions and multi-line input Ihor Radchenko
2022-10-17 21:23 ` miha
2022-10-18 5:28 ` Ihor Radchenko
2022-10-18 7:22 ` miha [this message]
2022-10-18 7:35 ` Ihor Radchenko
2022-10-18 11:15 ` miha
2022-10-21 5:32 ` Ihor Radchenko
2022-10-18 13:38 ` Stefan Monnier
2022-10-17 21:27 ` Stefan Monnier
2022-10-18 6:00 ` Ihor Radchenko
2022-10-18 23:22 ` Rudolf Adamkovič
2022-10-21 5:35 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfjlegu8.fsf@miha-pc \
--to=miha@kamnitnik.top \
--cc=emacs-devel@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.