public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	adaplas@gmail.com
Subject: Re: [PATCH] vc bell config
Date: Thu, 18 Oct 2007 00:21:14 +0200	[thread overview]
Message-ID: <20071017222114.GE2156@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0710171820570.28622@fbirervta.pbzchgretzou.qr>

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@gmx.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

      reply	other threads:[~2007-10-17 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 11:55 [PATCH] vc bell config Jan Engelhardt
2007-10-06  0:00 ` Andrew Morton
2007-10-06  9:55   ` Alan Cox
2007-10-06 10:02     ` Jan Engelhardt
2007-10-06 10:10   ` Jan Engelhardt
2007-10-11 18:11 ` Pavel Machek
2007-10-17 16:35   ` Jan Engelhardt
2007-10-17 22:21     ` Pavel Machek [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=20071017222114.GE2156@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=adaplas@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@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