Provided by: vche_1.7.2-7_i386
vche.conf - configuration file for VCHE
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
# Start in view mode
# Don’t mask non-printable characters
# Mask zero bytes
# Show the hex segment
# Enable read-write
This file could be located at
/build/buildd/vche-1.7.2/debian/vche/etc/vche.conf by default.
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.
When set you will hear a beep when you do some illegal action.
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
This flag is set when you are editing the file.
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.
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.
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
vche(1), vcs(4), vcsa(4), console_codes(4), charsets(4), terminfo(5),
Diego Javier Grigna <firstname.lastname@example.org>