Roman Joost

Yeah I like the idea and agree for the low priority. Hence no 1.0 milestone on the bug.

Yeah I still like it and want it. I'm pretty sure I'd file it again if we close this one here :)

We've contacted the maintainer of dyre. The project seems to be asleep unfortunately. Perhaps it could be handed over in order to get patches in.

@frasertweedale perhaps we could also consider a patch in the NixOS package as a possible solution which is only nix specific?

Hm.. I think this problem is not only related to NixOS. I made a new purebred build yesterday and after upgrading the executables mtime is basically the build time: ```...

I pulled down the RPM, unpacked it and checked again the `mtime`: ``` stat purebred File: purebred Size: 15072 Blocks: 32 IO Block: 4096 regular file Access: 2019-02-18 16:54:40.000000000 +1000...

Hm.. yes can confirm. It has something to do that the error message was created from a widget which isn't displayed any more. So either it must be created with...

Hm.. on a second thought, looking into the code displaying the errors: when the editor is invoked, any error message due to abnormal termination is displayed in the `StatusBar` which...

Ok back to square one, my comment https://github.com/purebred-mua/purebred/issues/429#issuecomment-813227871 was made based on the wrong setup. I must have reverted the test back to it's initial form making it pass.

I've found work done here: https://github.com/rootmos/haskeline but the haskeline API is pretty closed at the moment. Therefore I've filed an issue https://github.com/judah/haskeline/issues/118 to ask what's the better way to get...