Linux Certif

Toute la documentation sur la certification Linux LPI

vche.conf

NAME

vche.conf - configuration file for VCHE

DESCRIPTION

This file, if exists, is read by vche to set the program flags. If it does not exist, the flags will be set to their default (all off), and no warnings will be issued.

Example config file:

 # VCHE Config file
 #
 # Note: '#' are comments
 #
 # Be careful not to set "readonly" and "edit" flags to "on" at
 # the same time.
 #
 
 # Enable bell
 bell=on
 
 # Start in view mode
 edit=off
 
 # Don't mask non-printable characters
 mask=off
 
 # Mask zero bytes
 zero=on
 
 # Show the hex segment
 nohex=off
 
 # Enable read-write
 readonly=off
 
 

This file could be located at /build/buildd/vche-1.7.2/debian/vche/etc/vche.conf by default.

FLAGS

There are six flags, you could see them at the top of the screen as a set of six letters, you know when they are set when one of them is red.

bell=[on|off]

When set you will hear a beep when you do some illegal action.

mask=[on|off]

This flag "masks" control and extended ascii characters, showing a "." instead. This flag has no meaning in the vche-raw and vche-nc versions, since they can not show all the 256 characters.

edit=[on|off]

This flag is set when you are editing the file.

zero=[on|off]

This (as the mask flag) only works with the virtual console version of VCHE, it shows a dot (".") instead of the ASCII zero, this is useful when spaces and zeros confuse you, because they look the same in the character ROM.

nohex=[on|off]

Clear the hex segment. Sometimes it is useful to see only the offset and the ASCII bytes without seeing the bytes values in hex, it allows us to view a file more easily.

readonly=[on|off]

When set any file viewed will be opened readonly. The program also set this flag to "on" (even if you set it off), when a file cannot be opened read/write. When the file that we want to edit is being executed by another process this flag is also set to "on", this usually happens with the shell (which is of course always running).

SEE ALSO

vche(1), vcs(4), vcsa(4), console_codes(4), charsets(4), terminfo(5), ncurses(3x).

AUTHOR

    Diego Javier Grigna <diego@grigna.com>