all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Debug technique for comint, need stdin/stdout logger.
Date: Thu, 22 Sep 2011 01:12:55 +0300	[thread overview]
Message-ID: <j5dnhc$lhj$1@dough.gmane.org> (raw)
In-Reply-To: <j47vak$do7$1@dough.gmane.org>

07.09.2011 17:32, Oleksandr Gavenko пишет:
> When work with Emacs comint I need logger for stdin/stdout process
> interaction.
>
> So I change name of calling program in Emacs
> and that logger/script call original command and log
> stdin and stdout to files.
>
> I try write expect script:
> ...
I get working one.

It is used to debug interaction with Cygwin Python in 'python-mode'.

Expect come with all Linuxes and available under Cygwin...

#!/usr/bin/env expect

set in [open logger_in.log w]
set out [open logger_out.log w]

set timeout 3600
log_user 0
set stty_init {-echo}
# exp_internal 1

set cli [open logger_cli.log w]
foreach arg "$argv" {
     puts $cli $arg
}
close $cli
eval spawn python2.6.exe $argv
set proc_id $spawn_id

expect {
     -i $user_spawn_id -re (.+)\r?\n {
         puts -nonewline $in $expect_out(buffer)
         send -i $proc_id $expect_out(1,string)\n
         exp_continue
     } eof {
         send -i $proc_id \x04
         sleep 1
         send -i $proc_id \x04
         expect -i $proc_id -re .+ {
             puts -nonewline $out $expect_out(buffer)
             send_user $expect_out(buffer)
             exp_continue
         } eof { }
     } -i $proc_id -re .+ {
         puts -nonewline $out $expect_out(buffer)
         send_user $expect_out(buffer)
         exp_continue
     } eof { }
}
close $in
close $out
wait




      reply	other threads:[~2011-09-21 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 14:32 Debug technique for comint, need stdin/stdout logger Oleksandr Gavenko
2011-09-21 22:12 ` Oleksandr Gavenko [this message]

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='j5dnhc$lhj$1@dough.gmane.org' \
    --to=gavenkoa@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.