From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: FreeDOS <linux-msdos@vger.kernel.org>
Subject: Re: piping escape into dosemu
Date: Thu, 11 Mar 2010 00:26:27 -0600 [thread overview]
Message-ID: <4B988D13.70008@sbcglobal.net> (raw)
In-Reply-To: <ca6f72e21003101211q6680573dh8aadac1a7f86cbea@mail.gmail.com>
TW wrote:
> 2010/3/9 Mike McCarty <Mike.McCarty@sbcglobal.net>:
>> TW wrote:
>>> [...] 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.
>> [...] 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.
>>
>
> O.K., I'm beginning to understand what you're talking about. Up to
> now I didn't really use anything but bash. At least for me, pressing
> the escape key (however often) does not display anything, but when
> trying sh and dash, I see that pressing ESC "visually" resuts in ^[.
$ set | grep SHELL
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
$ /bin/bash --version
GNU bash, version 2.05b.0(1)-release (i386-redhat-linux-gnu)
Copyright (C) 2002 Free Software Foundation, Inc.
Perhaps something in SHELLOPTS is different, and modifies that behavior.
> And yes, now something like
>
> dosemu -input 'thedosapp.exe\r\^['
>
> indeed works, many thanks for pointing me to this! Unfortunately, for
> some reason this only works with the -input switch, but not when
> piping, like
>
> echo "keystroke \^[" > dospipe
Please note that "some string" and 'some string' are NOT the same.
However, in this case, I don't see what difference it would make.
> (where ^[ is what results from pressing ESC). It doesn't work through
> dosctrl or Ruby either. I wonder why this is supported by the -input
> switch, but not by the keystroke command...
>
> I may try to find out more, but I believe fixing it (i.e. making the
> string representing a piped keystroke sequence is parsed in the same
> manner that a keystroke string passed on the command line is) will be
> beyond my possibilities.
I'm not ready to throw in the towel. If we keep plugging at it,
I think we can get there.
> Thanks for your help!
What do you get when you do this:
$ echo -n "^[" | wc
0 0 1
Do you get the " 0 0 1" output I do? If so, then we can get there.
Or try
$ echo -n '^[' | wc
0 0 1
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!
next prev parent reply other threads:[~2010-03-11 6:26 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
2010-03-10 20:11 ` TW
2010-03-11 6:26 ` Mike McCarty [this message]
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=4B988D13.70008@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