You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(sorry in case i missed this somewhere in the config!..)
i was thinking about what makes an editor great, and for me it's intuitiveness. I was wondering, could it be possible to have an option to show the name of the function being run somewhere, perhaps as an option in the status line? (i'd even think to show as default, but that's just my opinion..)
i'd guess all of the functions are in rust at the moment, which would still be cool to see(!), but more useful to see are the "commands" (of the command list) being executed. Just display the command whenever it is called. Then, later, perhaps after the scripting language comes through 🙏, show the function-name being called by the scripting language.
it would really help learning what keys-mappings do, without even knowing. It would also help debugging badly-config'ed key-mappings, lol. ;)
once we can see the commands often enough, then the realization to create keyboard-macros will come easy.
or even better, provide a history of commands listed (already saved for undo/redo?), then we'll know exactly what we're doing the most, and can better decide what macros would be most useful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
(sorry in case i missed this somewhere in the config!..)
i was thinking about what makes an editor great, and for me it's intuitiveness. I was wondering, could it be possible to have an option to show the name of the function being run somewhere, perhaps as an option in the status line? (i'd even think to show as default, but that's just my opinion..)
i'd guess all of the functions are in rust at the moment, which would still be cool to see(!), but more useful to see are the "commands" (of the command list) being executed. Just display the command whenever it is called. Then, later, perhaps after the scripting language comes through 🙏, show the function-name being called by the scripting language.
it would really help learning what keys-mappings do, without even knowing. It would also help debugging badly-config'ed key-mappings, lol. ;)
once we can see the commands often enough, then the realization to create keyboard-macros will come easy.
or even better, provide a history of commands listed (already saved for undo/redo?), then we'll know exactly what we're doing the most, and can better decide what macros would be most useful.
Beta Was this translation helpful? Give feedback.
All reactions