def script_reportActiveConfigurationProfile(self, gesture):

"(self, gesture):" » "(self,gesture):" (See a few lines below)

What global input gesture is used for this command? NVDA+CTRL+Shift+P would be possible. And I guess that the message output will be via speech and braille together, right?

You could consider assigning shift+NVDA+p as default.

"(self, gesture):" » "(self,gesture):" (See a few lines below)

Visually, code without spaces is harder to read. So while much of the code is formatted this way, though certainly not all, I hope we are able to start to transition.

And I guess that the message output will be via speech and braille together, right?

Correct, although I have not tested with a braille display.

You could consider assigning shift+NVDA+p as default.

Given the revised approach to #9325 (not changing the title text), this command might not be so urgent. If there is demand for it, we could still consider including it. However I think we should be cautious about assigning a default gesture.

@feerrenrut: Not only visually, also on a braille display. As I'm not familiar with Python, I didn't know that both methods are valid and equal. I thought it was a typo. Thanks for the explanation.

You could consider assigning shift+NVDA+p as default.

As @DrSooom proposed in #9325 (comment) I think NVDA+control+shift+p is more relevant as it would:

• be more coherent with NVDA+control+p for profile configuration dialog
• leave NVDA+shift+p for Modify NVDA behavior with CLDR characters #9707, which in turn is coherent with NVDA+p for cycle through speech symbols level

Btw, I am not at all in favor of unassigned default gestures for commands that can be useful for beginners to intermediate users.

The issue this PR attempted to address was resolved in the PR. However I think it could still be useful functionality, so I'll mark it as ready for review. Since sensible gestures are short supply I'd prefer to leave this unbound initially. I don't think that working with profiles is a beginner feature.

@lukaszgo1 has a good point.

I have addressed the changes. The core concept was already reviewed. I'm going to merge this PR.

is this documented accordingly in the user guide?

@Adriani90 Are all commands documented in the user guide? It's not a particularly interesting command in need of explanation, and is listed in the gestures dialog.

Then we have two places to maintain the list of commands, and two places to keep translations consistent. I don't think adding something to the user guide is a good way to make a new feature discoverable, it's main purpose is to explain confusing or complicated options. The changes file was updated, its purpose is discoverability. Otherwise, for a listing of all commands users should consult the inputGestures dialog. To specifically make unassigned commands more discoverable, we should enhance the input gestures dialog with filters.

@feerrenrut I agree. If there is a filter implemented, then it would help to have a cathegory which displays only the unassigned gestures for example.