Releases: walles/moar
v1.25.0: Tail files, not just streams
With this release, if you open a (log?) file in moar, and more lines are added to the file after you start moar, moar will pick up the new lines and display them.
Also, if you have a terminal editor (nano, vim etc), and press "v" to edit a file, moar will now not steal the first byte from your editor any more. Improved on Unix, Windows unchanged, PRs welcome.
v1.24.6
v1.24.5: Fix editing files on Windows
Before this release, pressing v to edit a file on Windows would tell you your editor was not executable.
With this release, executability detection on Windows should now work.
v1.24.4: Support opening piped input in editor
By pressing v.
Before this change, v only worked for actual files.
With this change in place, v will also work for piped input.
Piped input will be written into a temporary file, then the editor will be opened with that file.
v1.24.3: Fix a shutdown issue
Take II.
v1.24.2: Fix crash with --quit-if-one-screen
Fix crash with --quit-if-one-screen
v1.24.1: Fix terminal editor lagginess
Before this release, if you pressed v to open the current file in your $EDITOR, and the editor was terminal based (think nano, vim), then the editor was really laggy.
That lagginess has been fixed in this release.
v1.24.0: Support pressing 'v' to launch an editor
With this release, if you press v while viewing a file, moar will launch an editor to edit the file. The editor is determined by the $VISUAL and $EDITOR environment variables.
Fixes #211.
v1.23.15: Faster search in large files
Before this release, searching was single threaded.
With this release, searching now uses all available cores, which makes searching large files a lot faster.
Searching a nine hundred thousand lines file now works fine on my laptop, which it did not before.
Make search 65% faster
Noticeable in large files. This is relative to the previous release, where we would on average search the whole file 1.5 times.
With this change, we will on average search the whole file once.