[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20071017222114.GE2156@elf.ucw.cz>
Date: Thu, 18 Oct 2007 00:21:14 +0200
From: Pavel Machek <pavel@....cz>
To: Jan Engelhardt <jengelh@...putergmbh.de>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
adaplas@...il.com
Subject: Re: [PATCH] vc bell config
Hi!
> >> It is already possible to deactivate the vc bell on a per-tty basis,
> >> by using echo -en "\e[11;0]", but this is reset on reset(1).
> >>
> >> This adds a sysfs parameter to globally control the vc bell, as well
> >> as sysfs parameters for default pitch and duration.
> >>
> >> Signed-off-by: Jan Engelhardt <jengelh@....de>
> >
> >There are more parameters that should be set during reset... like
> >cursor size and color, palette, .... What about /sys/.../string_to_interpret
> >_on_reset ?
>
> On reset(1), cursor size, palette, and bell parameters _do_ get reset
> to the defaults. Some defaults may already be changed by the user,
> like palette or default_utf8.
>
> Bell configuration is currently not one of them so, should a program
> decide to reset the tty, or should it happen that your output is
> garbled (forcing you to do reset), some settings change back to
> "unwanted defaults".
Ok, and I'm suggesting general method for the "unwanted defaults"
problem. Just have a /sys/.../terminal_init_string.
During reset, let console code interpret terminal_init_string, to set
_wanted_ defaults. So you'd do:
echo -en "\e[11;0]" > /sys/.../terminal_init_string... and I'd do
something similar with softcursor settings. (Which are currently reset
to compiled-in defaults, and that is "unwanted defaults" to me).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists