Re: git: 225639e7db68 - main - vt: Disable bell by default

On Tue, Oct 19, 2021 at 06:55:34PM -0700, Kevin Bowling wrote:
> On Tue, Oct 19, 2021 at 6:25 PM Alexey Dokuchaev wrote:
> > On Tue, Oct 19, 2021 at 01:37:00PM +0200, Emmanuel Vadot wrote:
> > > On Tue, 19 Oct 2021 14:21:33 +0300, Slawa Olhovchenkov wrote:
> > > > On Tue, Oct 19, 2021 at 07:38:15AM +0000, Emmanuel Vadot wrote:
> > > > > commit 225639e7db685a4047e384abdbc296c0e02bd147
> > > > >
> > > > >  vt: Disable bell by default
> > > > >
> > > > >  Bell is either useless if you're working on remote servers or
> > > > >  really annoying when you're working with a local machine that
> > > > >  have a loud buzzer.  Switch the default to have it disable.
> > > >
> > > > For you, not for me, for example. Also, this is violate POLA.
> > >
> > > Just set kern.vt.enable_bell=1 in /etc/sysctl.conf and you will be
> > > happy again.
> >
> > Actually, it should've been the other way around: it if annoys *you*,
> > then you should just set kern.vt.enable_bell=0 in /etc/sysctl.conf
> > and be happy.  I'm also used to it, it's a nice indicator that things
> > work normally, including the bell itself.
> >
> > > And POLA doesn't means that we can't change a thing.
> 
> I think a POLA violation here was that some equipment emits a
> jarringly loud noise, and rushing to turn that off is more stressful
> than the change of turning it on if you value it.

If "some equipment" has a buzzer so annoying that it stresses one
enough that she gets lost as to how to turn it off then perhaps admin
of such equipment should complain to its vendor instead.

> Safe defaults.

When I issue BEL (\a) on the console, I expect to hear the beep, and
should not do anything to enable it.  Computers don't have many ways
to talk back to us, muting one of the low-level signals like this is
dubious at the very least and should've undergone broader discussion.

./danfe