aaxu
aaxu
I should almost have a rough implementation of this done.
In `commandLoop`, I see that the bg thread is handled twice. Is there a reason for this, such as handling two bg requests per loop?
Just did some testing and oddly enough, scrolling down produces a bState that doesn't match with any of the curses.BUTTONn_* constants. We might have to do a hack and just...
Woops. Not sure what happened. Fixed. I guess I just learned that two spaces can fit in the width of one character on github comments.
Maybe not really an enhancement, more of a design decision. I think we can leave this since the extra indentation is more for style and spacing (like what we use...
Woah I like it a lot actually. It makes me feel so cool LOL Also, just to make sure, this is what I'm seeing on my screen. Let me know...
Oh yeah that sounds good. The only time I found this to be an issue was when I was writing code and neared the bottom of the screen. I wanted...
> Maybe (brainstorming) we can use the saved redo. We could write the redo to disk more often. And make the hash/sha match the saved version of the file. So...
Just brainstorming as well, but maybe it would be possible to break up a tree into different sections. Upon hitting a certain number of unsaved redos, we could break off...