Evan Teran

I'll take a look at it and get back to you. But we should probably lean more towards the "store too much" over potentially storing too little.

Yea, so we do that because the user may have changed the symbols directory. We could probably remember the previous value and reload only if it is actually changed.

The core functionality is in there. Now we just need to make use of it in things like the `QDisassemblyView`

Yup, I like this. It is also related to issue #220 as well

An interesting approach. I'd like the Patch manager to be a plugin which registers for this information somehow. We'll have to think about the API a but, but I like...

Yea, I like the "patch oriented" write API idea, it is a fairly clean solution to the "what do we want to care about" problem. So as far as the...

The in tree session directory has been replaced with `$HOME/.cache/codef00.com/edb/sessions` by default. We already store some trivial information those session files and reload them on opening the same binary again....

Currently the shortcut is `Alt + X`. This is for consistency with OllyDbg, so I don't predict changing it explicitly. However, perhaps at some point in the future, we may...

I think we will need to make a "configuration changed" signal that things can register for. I'll start with that :-)

@10110111 I've stubbed out the code for this. I've added a signal to `Configuration` which the `OdbgRegisterView` now connects to its `settingsUpdated` function. And it already has some code to...