lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <D1425869-534B-4AD9-BF2E-956A76E29894@Yost.com>
Date:	Mon, 24 Sep 2012 23:01:21 -0700
From:	Dave Yost <Dave@...t.com>
To:	linux-kernel@...r.kernel.org
Subject: RFE: tty color features

(This is not a complete spec, only a sketch.)

It would be nice to be able to specify fg/bg colors at the tty level, so that echoed characters can be colorized. Then your shell can arrange that shell command input is one fg/bg color, and other input taken by commands run from the shell is another color.

For example, like this:
 
  stty color-echo=#ffdddd/#000022 color-out=#ddffdd color-err=/#220000
  stty color-fd3=/#222255
  stty color-out=

or

  stty color-type=cmd:#ffdddd/#000000
  stty color-echo=cmd
  echo foo
  stty color-echo=#eeeeee
  echo bar
  stty color-echo=cmd
  echo baz

Names of things that can be colorized might include:
  echo
  out
  err
  fd0
  fd1
  fd2
  ...

I think named colors should be supported, with at least these builtin names:
  echo-default
  in-default
  out-default
This
  stty color-type=echo-default:
tells the tty driver that echo-default does no colorizing.

I used #xxxxxx notation as a placeholder. Probably in actual use, the user would supply a terminal escape sequence.

Typeahead is tricky:

  stty color-typeahead=#ff6666/004444

This would cause typeahead to be echoed in the desired color, and then when appropriate, typeahead characters could change color, such as when they are consumed or when they are hanging there with a pending cooked read.--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ