From: "Dmitry V. Levin" <ldv@altlinux.org>
To: kbd@lists.altlinux.org
Subject: Re: [kbd] New vt_mode tool for kbd?
Date: Tue, 22 Mar 2011 01:13:54 +0300 [thread overview]
Message-ID: <20110321221354.GB30302@altlinux.org> (raw)
In-Reply-To: <20110321214236.GA13370@graeme>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Mon, Mar 21, 2011 at 10:42:36PM +0100, Michael Schutte wrote:
> Hi Alexey,
>
> The console-setup package in Debian needs a way to check for the
> text/graphics mode of the active VT (from a shell script). This can be
> done with “setfont -v -o /dev/null”, for example, but that isn’t very
> elegant. Julien Cristau has proposed a small utility (which I’m calling
> “vt_mode” for now) to report this information in a canonical fashion.
I wonder whether you actually need to know what's the KD_ mode, or
maybe your scripts just need yes/no answers on simple two questions:
- whether the active VT is in the text mode?
- whether the active VT is in the graphics mode?
In the latter case, I suggest to implement an utility with an option or
argument specifying what mode to query, and a tty(1)-like exit status,
so its use would be as simple as "if vt_mode text; then ...; fi".
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-21 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 21:42 [kbd] New vt_mode tool for kbd? Michael Schutte
2011-03-21 22:13 ` Dmitry V. Levin [this message]
2011-03-21 22:25 ` Michael Schutte
2011-03-25 13:20 ` Alexey Gladkov
2011-03-26 17:33 ` Michael Schutte
2011-03-26 22:33 ` Dmitry V. Levin
2011-03-27 9:33 ` Alexey Gladkov
2011-03-28 10:55 ` Alexey Gladkov
2011-03-28 11:19 ` Dmitry V. Levin
2011-03-28 11:26 ` Alexey Gladkov
2011-03-28 21:07 ` Alexey Gladkov
2011-03-29 21:51 ` Dmitry V. Levin
2011-03-29 22:27 ` Alexey Gladkov
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=20110321221354.GB30302@altlinux.org \
--to=ldv@altlinux.org \
--cc=kbd@lists.altlinux.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 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.