Skip to content

Keyboard shortcut for saving all changes #286

Discussion options

You must be logged in to vote

we actually decided against doing this for a few reasons, one being its not that easy to do since we have various things happening when op-code is saved (like executing the op, and checking for errors and the likes) and another one being that we would then have to be really careful to not save your patch in a broken state somehow.

we think its more clear to keep code editing and patching "seperate", even if visually happening in the same window, for now.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@anticore
Comment options

Answer selected by anticore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants