public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: FreeDOS <linux-msdos@vger.kernel.org>
Subject: Re: piping escape into dosemu
Date: Mon, 08 Mar 2010 17:07:52 -0600	[thread overview]
Message-ID: <4B958348.4050802@sbcglobal.net> (raw)
In-Reply-To: <ca6f72e21003081340r7385a2d9v307d120e6fe31f17@mail.gmail.com>

TW wrote:
> Hi Mike,
> 
> thanks for your patience.  I'm sorry if my wording was confusing -
> English is not my mother tongue.

No problem.

> It appears the following problem is equivalent to mine, but simpler to
> describe because it neither involves pipes nor echo:
> 
> Say I have a DOS program that shows kind of a splash screen which can
> be bypassed by hitting ESC.  (This is just an example.)  I'd like to
> automate this, so I start dosemu like
> 
>   dosemu -input 'thedosapp.exe\r\^['
> 
> because in the readme[1] I'm told that "\^[" is the syntax for the
> escape key.  At least that's how I interpret the "\^x" section.

Ok, we have a use/mention problem, I think. In your example, you
give a string enclosed in 'single quotes'. That string, as you
show it, should have two characters after the '\r'. I suspect
that you are typing three characters '\', '^', and '['. That
is not the intended action. What is intended is that you type
a BACKSLASH ('\'), and an ESC. The shell displays on your
screen two characters when you type ESC, but that is a single keystroke.

You may have to type ESC twice to make it work with your shell. In any
case, you should not be typing the '^' and '[' characters; those
are just how the shell displays the input on the screen.

> Unfortunately, this doesn't work.  So what's the syntax for the escape
> key?  I tried to find hints in the source code, but my C know-how is

The ESC key. You may, as I said, have to type it twice. I had to.

> pretty basic.  All I figured out is that the uhook_keystroke()
> function in dosemu/src/base/misc/userhook.c must be the function that
> handles the keystroke command.

Well, let's hope that gets you going!

Mike
-- 
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!

  reply	other threads:[~2010-03-08 23:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 22:18 piping escape into dosemu Mike McCarty
2010-03-06  2:50 ` TW
2010-03-06  2:56   ` TW
2010-03-08  8:16   ` Mike McCarty
2010-03-08  8:29     ` Mike McCarty
2010-03-08 21:40     ` TW
2010-03-08 23:07       ` Mike McCarty [this message]
2010-03-10 20:11         ` TW
2010-03-11  6:26           ` Mike McCarty
2010-03-11  8:11             ` TW
2010-03-11  6:55           ` Mike McCarty
2010-03-11  9:11             ` TW
2010-03-11  9:19               ` Andrew Bird (Sphere Systems)
2010-03-11 12:50                 ` TW
     [not found]               ` <4B98F8EC.9030206@pobox.com>
     [not found]                 ` <ca6f72e21003111250x31e6ca3dt6732fefb59ef2a90@mail.gmail.com>
     [not found]                   ` <4B995B03.40906@pobox.com>
2010-03-11 22:24                     ` TW
  -- strict thread matches above, loose matches on Subject: below --
2010-02-25 20:21 TW
2010-03-05  7:21 ` TW
2010-03-05 17:59   ` solarflow99
2010-02-24 21:09 x.zupftom

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=4B958348.4050802@sbcglobal.net \
    --to=mike.mccarty@sbcglobal.net \
    --cc=linux-msdos@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox