Johan Walles
Johan Walles
e1ee92fb791b88d974493a7d2ab5cc85ef2375f8 introduces Nushell highlighting. Also, 4abc99f465ef708af5c95e644dd4d6625d438742 makes moar pass not-highlighted data to editors on `v`. Are these two together enough to close this ticket @boomshroom?
This release should cover your specific use-case: https://github.com/walles/moar/releases/tag/v1.32.6 As for the remaining part, how much do you believe it would actually be used in practice? By people in general?
Under what circumstances do you want to view more than one file? I would like to understand the use case. Or maybe continue this conversation in #248?
`moor *.h` is now supported in this release (just out): https://github.com/walles/moor/releases/tag/v2.3.0 I will close this ticket now, feel free to open others as needed.
Since 15ab0bd9147c5bafed6edf5e2f97e65013dcf76f `moor` will now read the `PAGER_LABEL` environment variable and use that to label stdin.
Now out in this release: https://github.com/walles/moor/releases/tag/v2.7.0
I think the reason you're getting color from `ls` in this case is that you have some configuration enforcing color. If you want color from `dir` you need to somehow...
No response, closing. @cmust do re-open as needed!
Try this: 1. `bash -c "while true ; do date ; sleep 1 ; done" | moar` 2. Inside of `moar`, press `v` to launch your editor 3. Replace everything...
Kindly try my example and tell me what you think moar should show after the editor is done.