Set either the default keybind layout to match with PowerBI/VSC standard or enable easy access to it.

[arekchr1]

Is your feature request related to a problem? Please describe

It's a little frustrating to have to go through every keybind one by one and figure out which ones are the ones I want to edit and being forced to google what could the keybind possibly be called in regards to its function when it's a commonly found keybind layout across MS space.

Describe the solution you'd like

Currently there's a number of keybinds that TE2 and TE3 don't use by default.
The ones mostly in question are:
ALT+SHIFT+DOWN = copy line down.
ALT+SHIFT+UP = copy line up.
CTRL+SHIFT+L = select all occurences of currently selected text.

There's obviously more, but it'd be helpful if the DAX editor in TE would inherit the same keybinds as the native one or at least allow the option to easily swap to it without searching through entire keybind list.

Additionally, down the road, it'd be nice if some teams were particular pedantic about their keybinds, it could be beneficial to allow downloadable layouts that can then be shared with ease and imported into TE as a new profile.

Goals

1. Inherit PowerBI's DAX editor / VSC's keybind layout that is common across Microsoft tools.
2. Alternatively easily allow to switch between TE default and the PowerBI default.
3. Additionally down the road, downloadable layouts that can be imported and reused as profiles for teams that want to customize.

Background

No response

Additional context

This issue was previously raised here: #1454

However it did not contain the additional context of perhaps setting an alternative keybind layout as an option.

[otykier]

This is a really great suggestion - thanks a lot!

Just to give some historical context, the code editor in TE3 is based on the Scintilla open-source text editor (which is used by tools like Notepad++). Scintilla has default keybindings that are different from the defaults in the Monaco code editor used by Power BI and VS Code. The default keybindings of Scintilla are more "old school", and I definitely know a few folks who appreciate that they are what they are.

That being said, I know not everyone has the same background, so it makes perfect sense that we provide at least two different keybinding "templates"; one for the classic Scintilla style, and another for the Monaco style bindings.

For what it's worth, any customization made to the bindings is stored in the %LocalAppData%\TabularEditor3\UiPreferences.json file under the KeyboardCustomizations section. If you wish, you can share this file (or just that part of the file) with colleagues who wish to use the same bindings.

[arekchr1]

That makes a lot of sense, thanks for clarifying!

As for the Bindings stored in the .json it didn't occur to me they were already accessible, that is more than sufficient for my needs at this point in time, thanks!