Elazar Leibovich

@q2dg the problem with `dmesg -C` is that you do not have persistent place to keep the last record. You can work around that with ``` $ sudo journalctl --show-cursor...

@mrc0mmand journalctl don't have a place to persist things, hence I think you'll have to. I don't suggest using `--cursor-file`, since: 1. It's not supported by older versions 2. You...

@mrc0mmand I was referring to the case you do not want to destroy the file, but just to view from it. `journalctl --after-cursor=$(cat /tmp/cursor)`. Indeed it can work for destructive...

@mrc0mmand Does not work for my version ``` $ sudo journalctl --show-cursor -qk -n 0 >/tmp/cursor $ sudo journalctl -k -c "$(cat /tmp/cursor)" Failed to seek to cursor: Invalid argument...

@mrc0mmand as I said, for the `dmesg -C` use case, the `cursor-file` doesn't help, since you don't want to destroy the file each time you show history. Hence I had...

@poettering , yes I apologize. Will edit to clarify.

@d4nuu8 hmm... I don't like the fact that the formatting don't just change the formatting, but also change the time source. Then again, this is what happens regardless of the...

> >Then again, this is what happens regardless of the feature. > But that's how it works right now, as far as I know. Agreed. That's my understanding as well....

@mrc0mmand totally agree it could be useful never the less. I understand and accept your stance about having a different format option for diff, given the current state of affairs....

Please consider a utility `rg --compile-expr a -and b -and c` generates relevant DFA. Usage something like `rg --dfa $(rg --compile-expr a -and -not b)`. This will seal complexity only...