Bugs in less-340

This is a list of the known bugs in less-340. Bugs marked with a * will be fixed in the next release.

#101

Using the -s flag can put "~" lines before the beginning of the file.

#104

Using the -s flag on a file with trailing blank lines, type the "G" command. The prompt may say "99%" instead of "100%".

#130

Command "F" doesn't work if the file shrinks in size.

#138

On Solaris, searching for "a[1,2]" matches "a4".

#152

On a Solaris cmdtool, slow pipes get stalled and never show any data.

#174

Cannot search for a string which follows a null byte ('\0').

#185

On some terminals, arrow keys don't work when you set -X.

#192

In certain cases, when built with a non-POSIX regular expression library, if search highlighting is enabled and a search pattern begins with a ^, more text than the matching string may be highlighted.

#193

On some systems which use setlocale() and the LC_* environment variables, less treats some binary files as ordinary, non-binary files. You can workaround this problem by setting the environment variable LESSCHARSET to "ascii" (or whatever character set is appropriate).

#200

On Windows NT, if the screen buffer is larger than the displayed window size, lines can "leak" into the offscreen part of the buffer. (If any Windows expert can help me with this one, I'd appreciate it.)

#201

The DOS version compiled under DJGPP cannot open long (non-DOS) filenames when run on Windows-NT.

#202

The DOS version compiled under DJGPP sometimes highlights incorrectly when a highlighted line is longer than the screen width. (If any Windows expert can help me with this one, I'd appreciate it.)

#203

The Windows version compiled under Microsoft Visual C++ sometimes highlights incorrectly when a highlighted line is longer than the screen width. (If any Windows expert can help me with this one, I'd appreciate it.)

#207 *

Search command reports "Nothing to search" if there is text on the page but the first line is empty.

#208 *

Pressing h for help, then q, then '' causes less to crash.

#209 *

Search for a pattern ending in $ doesn't work with lines which end with a carriage return - line feed combination.

#211

You cannot open a file that starts or ends with a double quote.

#213 *

lesskey doesn't work with lesskey files which contain lines which end with a carriage return - line feed combination.

#218 *

Entering :d while viewing the help file causes less to crash.

Feature enhancement requests

This is a list of enhancement requests.

#102

Allow -o to work on non-pipe input (ordinary files).

#112

If the cursor is not at the bottom of the screen, begin display at the current cursor position; don't move to bottom line before displaying the first screen.

#162

Make compliant with POSIX specification for "more".

#184

Add a "bookmark" capability; that is, allow file marks to be saved on exit and restored at the next invocation of less on the same file.

#188 *

Allow ANSI color escape sequences to be displayed without -r.

#197 *

Provide a system-wide default lesskey file, which doesn't depend on $HOME directory.

#206 *

Support UTF-8 files.

#212

less -N with output redirected to a file or pipe should still output line numbers.

#214 *

The HOME key should jump to start of file and the END key should jump to end of file.

#215 *

The default LESSCHARSET should be latin1 rather than ascii.

#219 * The -w flag should cause the target line of g and p commands to be highlighted.