public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Javier Tarifa <xavier.tarifa@adbosch.es>
To: linux-msdos@vger.kernel.org
Subject: Re: Alt+o key combination misbehaving
Date: Mon, 11 May 2009 10:40:50 +0200	[thread overview]
Message-ID: <4A07E492.6030308@adbosch.es> (raw)
In-Reply-To: <4A02EFB6.3030902@adbosch.es>

Javier Tarifa escribió:
> Just when I thought that I had all the keys I needed working on dosemu 
> I've found one that I don't know how to fix.
> I use dosemu via ssh, and I thought that all alt+letter combination 
> were working ok until yesterday, when I found out that alt+o behaves 
> strangely. In the program
> I need to use it, it simply hangs everything until I start to bash the 
> keyboard franticly.
> In the ScanCode Show program (get it here if you want to test it : 
> ftp://ftp.simtel.net/pub/simtelnet/msdos/keyboard/scode22.zip) you can 
> see that the first alt+o keypress never shows, and subsequent presses 
> either:
> 1.- Show the alt+o keypress and the new keypress normally if they're a 
> ctrl+something or alt+something;
> 2.- Don't show the alt+o keypress neither the new keypress, but a new, 
> strange one if they're a single keypress. For example, ctr+o, g  show 
> a result of SHIFT Num 5

Strange thing I've found out: It only doesn't work well when I connect 
throught putty, connecting throught ssh works as expected.
The only difference I see in the boot.log is that when I connect 
throught ssh, it says "CONF: dosemu running on _console", but when I 
connect throught putty it says
"CONF: dosemu running on _xterm".
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-05-11  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 14:27 Alt+o key combination misbehaving Javier Tarifa
2009-05-11  8:40 ` Javier Tarifa [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=4A07E492.6030308@adbosch.es \
    --to=xavier.tarifa@adbosch.es \
    --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