Guillaume Maudoux

That is it for today. I think it should work now @bburdette :tada: :yum: See https://gist.github.com/layus/e10b4fab9938e9a1777530fe296f0623 for an example on how it behaves with a nixos module error.

/cc @kamadorueda . Someone told me you are working on improving error messages, and could want to have a look at this one ;-)

Well, I am wrong, we do have an Expr, but not all Expr have a position to use for error reporting. I wonder if it is a deliberate design decision....

> My working hypothesis is that the `^` points (correctly) at the start of the Expr. If that's an `ExprCall`, the start of the call is equal to the start...

Another example; ``` nix-instantiate --eval --expr 'if "hello" then true else false' (nix) error: value is a string while a Boolean was expected at «string»:1:1: 1| if "hello" then true...

Oh, actually first intuition was right. We only have an Expr when we use evalXXX fucntions, but forceXXX functions do not have that property. Back to the first idea then.

> Note that it works fine if you switch to another X11 app. Maybe we're missing a focus-out event or something. @emersion Do you have any idea how to make...

As usual, asking the question triggers the answer (`xev` in this case). The difference is a single LeaveNotify event. In each case there is a `$mod` KeyPress event before changing...

I found a unique relevant occurrence in xwayland at https://github.com/freedesktop/xorg-xserver/blob/5315f988d9f175e4850f4259f691a68d95ce7ac2/hw/xwayland/xwayland-input.c#L2557.

Or maybe make Ctrl preserve the selection until it is released ? A key would also move the behavior switch away from the cli options.