Moor: vanhemmat versiot ja versiohistoria

Before this release, man pages formatted by groff 1.22.4, which ships
with for example Ubuntu 22.04, could show bold text, underlines and
bullets as letters separated by red '<' markers. That version of groff
sometimes repeats each overstruck character to make it look extra bold,
and moor did not recognize those repeats.
With this release, moor renders those repeats as regular bold, underline
and bullets, and searching and copying text from such pages works as
expected. Thanks @yermulnik for reporting
#472!

Before this release, scrolling down quickly, like with an inertial
trackpad flick, could make moor freeze and then jump ahead, especially
in large terminal windows. Scrolling up was fine.
With this release, scrolling down is as smooth as scrolling up. Thanks
@injust for reporting #471!

With this release, moor supports scrolling with the mouse wheel and
selecting text in all terminals supporting Alternate Scroll Mode.
This makes Ptyxis work out of the box, and should also help in other
terminals moor doesn't know about yet, and over ssh. Thanks @j4james for
the suggestion in #53!

Like searching and filtering.

With this release, & filter shares history with / search: press up/down
while filtering to browse patterns you've typed into either prompt,
instead of retyping them from scratch.
Getting there also fixed two filter bugs:
- PgUp/PgDown while the filter prompt was open silently did nothing,
instead of switching to viewing mode like it does when searching
- Cancelling a filter with ESC left the view wherever filtering had
landed, instead of restoring your pre-filter scroll position
Also in this release:
- Tuned the search hit line highlight color to be a bit less strong
- Clarified --terminal-fg's help text: it resets both foreground and
background, and is helpful on transparent backgrounds
- Log explanation for flickering on --quit-if-one-screen when input
stream is slow

With this release, moor drops back to requiring Go 1.25 instead of 1.27,
so it can still be built from source on distros like RHEL10 that haven't
caught up with the latest Go toolchain yet. Going forward, moor's Go
version requirement will never be newer than the most recently
end-of-lifed Go release.
Also in this release:
- twin, moor's terminal library, is now an external project
(github.com/walles/twin) instead of living in this repository
- Fixed potential screen tearing on quick window resizes (twin v0.9.3)

With this release, applications that embed moor can supply their own
twin.Screen via PageFromStreamWithScreen instead of moor always owning
the real terminal, and feed it input using the new NewEventRune,
NewEventKeyCode, and NewEventMouse constructors.
Also, this release bumps Go to 1.27, bringing in Unicode 17 support.

With this release, moor reports to the terminal when it's busy loading,
using the OSC 9;4 progress protocol supported by terminals such as
iTerm2.
Also in this release:
- Fixed a data loss bug where two moor instances sharing a search
history file could silently overwrite each other's committed
searches
- Pressing 'n'/'N' with no active search now resumes the most recently
used search history entry instead of doing nothing. Thanks @knirch
for #455!
- Fixed the status bar missing its separator between the filename and
the percentage while the reader was still paused during initial
loading
- Importing search history from less now only imports its search
history, not its sub-command history
- --help now documents the existing "+/pattern" syntax for searching
immediately on start

Before this release, --quit-if-one-screen made the terminal flash even
when the contents fit on one screen. Moor switched to the alternate
screen, painted a frame, and switched right back before printing the
contents where they belong.
With this release, when the contents fit on one screen moor prints them
without ever touching the alternate screen, so there is nothing to see
but the text.
Getting there also meant waiting for syntax highlighting before deciding
whether the contents fit: highlighting can turn one line of JSON into a
hundred, so source files and piped JSON used to flash where a .txt file
did not.
Also in this release:
- Moor now resets the terminal style before exiting, so a colored last
line no longer bleeds into your next shell prompt. This affected
--no-clear-on-exit and --quit-if-one-screen output as wide as the
screen
- With --no-clear-on-exit-margin 0, the last line of the contents is
no longer silently dropped on exit
- If the reader panics, moor now keeps going with whatever it read
instead of spinning its spinner forever
- pkg/moor: the terminal is restored even if paging panics, rather than
leaving the embedding process on the alternate screen in raw mode
- pkg/moor: embedders no longer lose the last line of short contents
Known limitation: input that is short but arrives slowly can still flash.
Fixing that requires waiting a fixed amount of time before showing
anything, and nobody has picked a number yet.

Before this release, a file that the syntax highlighter saw as one
single token -- a file holding nothing but a number, for example --
came out with every character in the same color.
With this release, highlighting that would look uniform is skipped and
the text is shown plain. Thanks @knirch for reporting #445!
Also in this release:
- On Windows, arrow and function keys now work immediately after
returning from an editor opened with "v", instead of being ignored for
up to a tenth of a second
- Faster .zst decompression on arm64 (Apple Silicon), and corrupt .zst
input now reports an error rather than decoding to garbage
- Compressed files and streams are now properly closed, so moor no
longer leaks file descriptors or goroutines while reading them
- Fixed a hang and a data race when a zstd stream was closed while still
being read
- Fixed a hang on shutdown when moor was closed programmatically through
pkg/moor

Before this release, searching a huge line (hundreds of MB long) for a
common character could take ten seconds of full CPU before hits got
highlighted, and pay that same cost again on every redraw.
With this release, that same search is close to instant.

Before this release, opening a file containing a huge line would take
enormous amounts of time to read that line, and never get further into
the stream.
With this release, moor can now read a file with a 250MB line in about
a second.
Also in this release:
- Pressing 'v' to open the current file in an editor now jumps to the
line you were viewing, for vim, vi, nvim, nano, emacs and Pico.
Thanks @joeledwardson for #447!
- Fixed a data race that could corrupt rendered text while a file was
still being read
- Thanks @subotac for kicking off the escape sequence fix in #450!

Some programs put the terminal into a mode of their own choosing while
moor is still running.
Known culprits are cmd.exe on Windows, and Node.js on all platforms when
piping its output into moor.
Before this release, that could make moor miss arrow keys and sometimes
print garbage to the console.
With this release, moor sets the terminal mode it needs as it goes, so
navigation keys keep working regardless. This also covers coming back
from an editor launched with "v", which on Windows could ignore
navigation keys for many seconds afterwards.
On Windows this also fixes moor sometimes leaving the terminal in a
broken state after exiting.
Also in this release:
- Support for the Unicode 17.0.0 tables in the upcoming Go 1.27, through
an updated charlievieth/strcase dependency

This release fixes a bug where providing an initial search query on the
command line would both search and scroll to the end of the document.
With this release, we just show the first hit. Which is what we always
should have done.

This will make moor behave as if you started moor, typed / to start
searching, typed pattern as the search pattern and then pressed Enter.
For great less compatibility.

Also in this release:
- Improve file format detection by checking file contents if the file
extension didn't help
- Fix a crash when switching between files

Also, this release shuts down nicely on SIGINT and SIGTERM, restoring
the terminal state before exiting.

This release improves wrapping for indented and list-like text, such as
man page option descriptions. Wrapped continuation lines now keep a
smarter hanging indent when appropriate.
Also in this release:
- Press Ctrl-C while searching to abort search mode and return to where
you started.
- Improve UI responsiveness for very long lines by avoiding unnecessary
match scanning when no search is active.
- Unescape MAN_PN values from GNU man before displaying them, so labels
are shown correctly.

This release fixes an intermittent crash that could happen when filtering a file down to zero lines.

Also, this release improves performance for rendering long (100KB) lines.

Performance when searching and scrolling sideways to search hits has been significantly improved.
Hits are now also centered on the screen when scrolling sideways.

Also in this release:
- Fix a goroutine leak and limit CPU usage when searching
- Detect JSONL files and apply JSON syntax highlighting, thanks @scudette in #407!

In this release, moor now automatically detects if a file gets truncated/shrunk or completely rewritten and reloads it appropriately.
Also, you can now press r at any time to manually reload the current file.

Additionally, the man page got minor touchups, thanks @ssgelm in #405!

Crash reported here: https://github.com/walles/moor/issues/399

Also, this release makes filtering using & 14% faster with large input.

Support ANSI escape codes for blink, hidden, and strikethrough,
contributed by @viserctul in #402.
Thanks!

Also in this release:

- Ignore OSC8 parameters
- Make LESS_TERMCAP_md control man page headings as well

Remove 'v' temp file after $EDITOR is done

Support CTRL-f and CTRL-b for paging forward and backward, contributed
by @joshheyse in #395. Thanks!
Also in this release:
- Accept ESC as the escape character in LESS_TERMCAP_* variables
- Fix busy looping when reading from a pipe on Windows