Thomas Whelan

You could split the core code you want to benchmark into a library and then change the compiler options for each version you want to build in CMake?

You can probably do it in a single binary. You can conditionally name each of the method symbols based on the compilation options and statically link against all of them.

I'm not attached to the soft hyphen, that's just the first thing I found that works. I tried the escape sequences but couldn't find a way to capture them, do...

That was something I had considered too, but that signal only provides the terminal in the callback and not the actual change itself. So as far as I could tell...

Here's a snippet for bash that patches in the Soft Hyphen in your bashrc ``` _update_ps1() { if [ "${PS1: -1}" = " " ]; then PS1=${PS1%?}$(echo -e '\u00ad') else...

Oh, it looks like `vte.get_text_range` can actually query the entire terminal history. That means it could be re-architected to just do a linear search through the buffer from the current...

Well unsurprisingly this is super slow, especially if the previous marker is very far away. I think what I have now is looking like the best compromise.

One option I could add is instead of requiring the user to add the `_update_ps1` command to their bashrc, is just using https://lazka.github.io/pgi-docs/Vte-2.91/classes/Terminal.html#Vte.Terminal.feed_child to feed the update of the `PS1`...

Even just a feature where it can move the scroll bar back to the line you were at when you last pressed Enter would do the trick. I'd thought about...

I would guess it's permissions? Try running with sudo