Johan Walles
Johan Walles
Pressing `v` will solve at least part of this, it opens the current file's contents in your configured `$EDITOR`. Can you try that and see how that works out for...
So is it something like this you want to do? ```bash cut -f2- file.txt | moor | wc -l ``` And the expected behavior is: 1. get to view the...
This might be doable by having `moor` using stderr rather than stdout for its display. I *think* terminals should be fine with that. Then after exit, moor could dump (or...
I feel I'm missing something here, can you give a concrete example that I can follow? > When working with LLMs, they'll often call a tool that pipes into a...
Can you ask your LLM to call `git` with `--no-pager`? Does that help? ``` git --no-pager status ```
Or maybe try `PAGER=cat external-tool.sh`?
> since `moor` will try `$VISUAL` first, that environment variable is more suitable I agree that setting `$VISUAL` rather than (or in combination with) setting `$PAGER` might be required, thanks...
Can you post the file so I can try? And also, can you please update the screenshot so that all four window borders are clearly visible?
Your log file is UTF-16 encoded, which is currently not supported by `moor`. I'll treat this as a feature request. As a workaround until `moor` supports UTF-16, you might consider...
> how did you check abou encoding. I loaded the file in Visual Studio Code. It rendered fine in there, and the editor said "UTF-16 LE" ("Little Endian") at the...