| 15 Mar 2026 |
 alexfmpe | Happened multiple times | 17:40:16 |
 maralorn | Well, nom tries to remember how many lines have been written and need to be cleared. It is definitely possible that something invalidates the internal computation. | 18:30:27 |
| maralorn | Other terminal applications mainly prevent this from happening by switching the terminal mode and completely owning the buffer, which I want to avoid with nom so that you normally get a valid log. | 18:32:32 |
| alexfmpe | why does it need to clear things in the first place? | 18:47:29 |
| alexfmpe | what if it was like a tmux thing | 18:47:48 |
| alexfmpe | with normal log in one pane/terminal and the monitoring in another | 18:48:23 |
| alexfmpe | my main reason for not always using nom is that the control characters and redrawing clutter the resulting log so it's harder to inspect logs after the build | 18:49:13 |
| alexfmpe | I can imagine something like
$ nom-build foo
<tmux thing>
<nix-build foo output>
<monitor output>
$ nom-build foo --detached
"To connect to the monitor ran <some command>"
<nix-build foo output>
| 18:51:11 |
| maralorn | I am not aware of a solution where nom can do "a tmux thing" an produce a viable scrollable log in the terminal which is readable after exit. | 19:44:29 |
| maralorn | But maybe that's a misconception. Maybe we can figure out how to do that. | 19:48:02 |
|  NixOS Moderation Bot banned  @jykrwn_bot:matrix.org (disagreement). | 20:27:59 |
|  isabel changed their profile picture. | 20:54:42 |
| isabel changed their profile picture. | 20:54:56 |
