For an overview of new features, see here.

The following versions contain fixed bugs (click on them to see which bugs
were solved) were:

7.1
7.0a
7.0
6.3l
6.3k
6.3h
6.3d
6.3c
6.3b
6.3a

Solved in release 7.1

   * In an expression, multiple brackets could not occur with spacing:
     ( (3)) yielded an error.
   * In an expression, the unary minus in combination with brackets gave
     an incorrect result:
     -(3+5)+8 yielded -16 instead of 0.
   * In very rare circumstances, it was possible for TV to incorrectly
     report 'out of memory' when the correct error would have been
     'Unable to open inputfile'. This applies to the 'y'-command.
   * In even rarer circumstances (never reported!) an internal code
     confusion could have caused very unpredictable behaviour. It
     probably never happened, and now it certainly won't.
   * A register-switch TO an illegally named buffer FROM a non-default
     buffer (e.g.: 'A') incorrectly exchanged the contents of that
     buffer with the original default buffer.
   * The mechanism that prevented CTRL_D from being used after the
     settings-requester caused changes to any of the CTRL_X-settings
     did not work, and messed up the command-hstory.
   * Some outdated OS-names have been updated (e.g. DECUX is now OSF).
   * The new setting 'Log file' was not consistently named. In the
     settings-requester, 'Command-debug' was used instead.
   * The backup-file did not correctly contain changes made via the
     settings-requester (only applicable for tab size and trigger
     regions).
   * In error-messages, the register name relevant to an error was not
     correctly displayed for the 'M'-command.
   * The alternative use of 'c', 'v', 'b', 'f' and 'g' as cursor-movement
     keys (after CTRL_^) was enabled for the Amiga, even if it was not
     needed on that platform. Users hooked on this feature on other
     platforms can now use it more generally.
   * Suppression of creation of a TVback-file (via an empty -b option)
     did not work on all platforms.
   * Several corrections in screen-refresh logic straighten out a few
     minor bugs (failing to display the most recent changes).
   * Attempts to define a key for which key-definitions are not permitted
     resulted in an incorect error-message.
   * Attempts to create intuition-reactions on non-Amiga platforms were
     silently ignored instead of being punished with the appropriate
     error-message.
   * Switching into a register can never be done via an array-index,
     which was not properly checked in the code.

Solved in release 7.0a

   * The mines (Unix only) example now correctly no longer counts time
     spent in 'pause'.

Solved in release 7.0

   * The irksome version-number in the TV path is removed (Unix versions only).
   * Re-implemented fix 6.3k (which got lost; don't ask).
   * The script 'start.tv' was renamed 'start_tv' to avoid the confusion that
     it might be a macro-file (as examples now consistently have the '.tv'
     extension).
   * A file-requester on Unix is no longer popped up if the '-s' flag is
     active, as the standard input is no longer available and a choice could
     not be made anyway.
   * The lxt-window will not open simply to tell that a file can't be read.
     This is now done in the main window by means of a tester program.
   * Illegible characters are now displayed more meaningfully (Linux only).
   * Function keys F1-F12 are now all recognized (Linux only).
   * Shifted function keys F1-F10 are now all recognized as F11-F20 (Linux only).
   * New files no longer have the execute-bit set in the protection bits.
   * The cursor is now displayed with the 't' command.
   * The scripting has been adapted so that the '-s'/'-c' options are now
     usable for editing of standard input. When '-s' is active, reading and
     writing of standard input/output is no longer logged.
   * The way examples are distributed is cleaned up.
   * Loads of bugs in curses have been bypassed (as curses was removed).
     This has disadvantages as well; curses was actually pretty good at figuring
     out terminal capabilities, and the replacement is not. It assumes colours
     are supported. If this causes garbage, try setting (and exporting) the
     environment-variable COLORS with value 'false'. That will revert TV to a
     black-and-white version. This change has been made on Linux only.
   * The delay at the end (to reassure that the last file write really happened)
     is no longer executed when CTRL_C caused the abort.

Solved in release 6.3l

   * The command '0/2>' gave an expression error because of a bug in
     the expression handler when skippiong commands (e.g. iterating 0 times).

Solved in release 6.3k

   * A vague bug in the command parser was fixed. If a key (e.g. F7) was
     defines as follows:
     7;i1,1;cNE<:m hello>
     (with an obvious missing ascape after 'hello' and nothing, not even a
     return, following the '>') no error-message was generated if the key
     was executed from a register. If executed in an iteration the problem
     did not occur.
     This is not something the average user would ever see happening.

Solved in release 6.3h

   * The supporting program 'lxt' is shipped in an updated revision. When used
     as popup-generator (lxt -p) it could core-dump if no further parameters
     were given. This applies to the digital alpha and sun solaris platforms
     only.
   * The solaris-version of tv is compiled on a different system, which is in
     most cases sufficient for resolving compatibility-issues with shared libs
     on other installations.
   Note: the executable contained is still version 6.3f.

Solved in release 6.3d

   * The messages no longer appear as pop-up window on top of the text-
     buffer. They now have an area between text-buffer and input-area. As
     a consequence the text-buffer is now only 18 lines long instead of 20.
     This change affects Unix versions only.
   * When using CTRL_X with argument 6 (stop locking title) the title is now
     refreshed before accepting subsequent updates.
   * Searching or replacing strings in a range with no match caused the cursor
     position to be one higher than expected.

Solved in release 6.3c

   * Skipping of ':W' and ';W' (for instance in a loop executed 0 times)
     could lead to a parser error.
   * Skipping of '^' and 'v' (for instance in a loop executed 0 times)
     could lead to a parser error if the list-termination was a RETURN.

Solved in release 6.3b

   * Differences in compilers led to problems with backup-files on some
     platforms.
   * For Unix versions, the core-dump request (usually CTRL_$) is now
     disabled.
   * For Unix versions, the terminal settings are now correctly restored
     after TV is continued (usually fg) after having been put in the
     background (usually CTRL_Z).
   * The alternative use of 'c', 'v', 'b', 'f' and 'g' as cursor-movement
     keys (after CTRL_^) now works as advertised for Unix versions.
   * The irregularities surrounding the error-report "iteration not closed"
     in combination with the screen-refresh after CTRL_D have been removed.

Solved in release 6.3a

   * Incorrect processing of searching/replacing in a range could lead
     to numeric expression errors when skipping commands (for instance
     in a loop executed 0 times).