forking a definition doesn't change the scope to match that of the source definition

[ixera]

forking a definition leaves the user's scope setting unchanged -- while it'd be sort of be unintuitive to leave it changed after adding the new definition, I expect my new definition to be posted to the same scope as the source definition, unless I manually change it. I'm not exactly sure how this could/should be fixed (add a separate "post to scope" field for posting, maybe?)

[uakci]

Hi, thanks for filing an issue for this.

I’m not actually convinced pulling the scope from under the user’s feet is the right choice – for example, when mass-translating. For this reason I’m going to leave the issue open for the time being. Toadua should probably get a settings menu to configure these kinds of things, and/or a dropdown so that actions like “fork with scope” don’t take up space and distract the casual user. (I can’t say when that is going to happen.)