Displaying files with special characters in the file name
=========================================================

Files that do not need postprocessing by lesspipe (ordinary files) will
be displayed unconditionally.

Other files that get processed by lesspipe.sh and that have one of the
special shell characters $ * ? [ ] or \ in the file name will not be
properly expanded.

As an example a gzipped text file named a\$b.gz would not be shown unexpanded
and produces error messages. To force an unexpanded display lesspipe.sh can
be switched off temporarily using less -L <filename> or cat <filename> | less

On the contrary file names that do contain other shell metacharacters: space
(frequently used in windows file names), the characters | & ; ( ) ` < > " '
# ~ or = will be processed properly. These metacharacters must be escaped
when used in the shell, e.g. less a\ b.tar.gz:a\"b will display the file a"b
contained in the gzipped tar archive a b.tar.gz.

Files within an archive that do have an isolated colon in the name cannot be
displayed as well, as the colon is interpreted as a separator character
between the archive name and contained files (or even archives again).

Syntax highlighting
===================

The enabling of syntax highlighting contains OS dependent code and is not
guaranteed to work (it was tested on Linux, Solaris, IRIX, HPUX, AIX,
MacOS X, Cygwin and FreeBSD). It is deactivated by default and regarded by
me as an experimental feature. It can be activated using "configure" or
"make MODE=ask".

Much better syntax highlighting is obtained using the less emulation of vim:
Define a function lessc (bash, zsh, ksh users)

  lessc () { /usr/share/vim/vim63/macros/less.sh "$@"}

or an alias lessc (csh, tcsh users)

  alias lessc /usr/share/vim/vim63/macros/less.sh

and use "lessc filename" to view the colorful file contents.

If you encounter other bugs please drop me an email
Wolfgang DOT Friebel AT desy DOT de

Man page install location
=========================

At the moment the man page will be installed only in the directory
$PREFIX/share/man/man1 if it is existing

Recognition of correct file type
================================

The correct file type is not always recognized by using the 'file' command.
This may be due to old versions of 'file'. The support for Openoffice files
e.g. is not contained in 'magic files' from file-4.16 or older.
In addition there are ambiguities, so that an UTF-16 file may be reported as
MPEG ADTS, layer I, v1 file. This could be corrected by supplying a magic file
tailored to the needs of lesspipe. I plan to include such a file in a future
version of lesspipe.