public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@list.ru>
To: Jakub Klawiter <jklawiter@gmail.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: lag while printing and serial redirect
Date: Thu, 22 Dec 2016 00:22:27 +0300	[thread overview]
Message-ID: <c9c2a828-e023-a979-bcb8-911e008bb3b9@list.ru> (raw)
In-Reply-To: <CAOpyoqbz148j1uDXsWmkN6EjKsh46bLViaCEmK-qgwuH+H7k5g@mail.gmail.com>

20.12.2016 23:37, Jakub Klawiter пишет:
> Hello!
>
> 2016-12-20 1:19 GMT+01:00 Stas Sergeev <stsp@list.ru>:
>>>> it's even better (larger) only problem that colors are little bit flat
>>>> this way... too flat :(
>>>> https://goo.gl/photos/WLLRvbkVGCkg9tyA6 (in front -X, back -dt) Is it
>>>> possible to change palette somewhere as it doesn't depend on my
>>>> terminal palette.
>>> Ok i fount it in other place in my terminal. everything is great right
>>> now. Thank you all for all your help!
>> Maybe you've found the palette config, but to make
>> the output independent of any config, one needs to add
>> the truecolor support (which is very new in slang library).
> It's good enough for me ;-)
>
> Anyway i've temporary switched back to -X because of kbd problems.
>
> 1. My DOS program needs decimal point instead of decimal coma on
> keypad. It should be easy to remap it, as it is used in wild countries
> ;-)
> 2. I also need there ctrl+enter to work „DOS way”. And I really have
> no idea what code sends ctrl+enter in DOS, what I know that it is not
> working when started under dosemu -dt
You mean -t.

> Anyway i'll probably try to fight with it after new year.
Key combos may be a problem, yes.
You can run "cat" and see what your key combos produce.
For example "Enter" and "Ctrl-Enter" produce the same newline,
which means making it to work the dos way is not trivial.

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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 13:26 lag while printing and serial redirect Jakub Klawiter
2016-12-13 17:04 ` Frank Cox
2016-12-13 21:13 ` Stas Sergeev
2016-12-14 14:32   ` Jakub Klawiter
2016-12-14 20:00     ` Stas Sergeev
2016-12-15 16:18       ` Jakub Klawiter
2016-12-15 21:57         ` Stas Sergeev
2016-12-15 22:10           ` Jakub Klawiter
2016-12-15 22:18             ` Stas Sergeev
2016-12-19 13:34               ` Jakub Klawiter
2016-12-19 13:53                 ` Jakub Klawiter
2016-12-20  0:19                   ` Stas Sergeev
2016-12-20 20:37                     ` Jakub Klawiter
2016-12-21 21:22                       ` Stas Sergeev [this message]
2016-12-25 14:03                         ` Jakub Klawiter
2016-12-25 16:58                           ` Stas Sergeev
2016-12-27 22:44                             ` Jakub Klawiter
2016-12-28 20:04                               ` Stas Sergeev
2016-12-20  0:17                 ` Stas Sergeev

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=c9c2a828-e023-a979-bcb8-911e008bb3b9@list.ru \
    --to=stsp@list.ru \
    --cc=jklawiter@gmail.com \
    --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