NppExec F6 not working

PaoloRicardo

Alan

Yes, F6 is there after navigating to ‘Execute’. Pressing F6 at this point has no effect.

Paul

Meta Chuh

some of the possibilities, that might prevent [F6] from triggering plugins > nppexec > execute are:

there’s another plugin or custom setting, like a run menu entry at your shortcuts.xml, that also has [F6] set as a keyboard shortcut, producing a conflicting keyboard combination.
fix for that: go to settings > shortcut mapperand browse all categories manually, searching for another “rogue” [F6] entry.
(alternatively you could try to set a different keyboard shortcut to your plugins > nppexec > execute menu.)
you are using a notebook or multimedia keyboard, where the [F6] key has a system function, like brightness or volume, and does not work as [F6] without simultaneously pressing the [FN] button.
fix for that: you would have to press [FN]+[F6].

if none of the mentioned possibilities is the cause of your experience, we would need your current debug info, to eventually be of help.
please go to ? > debug info... > copy debug info into clipboard and paste it here.

PeterJones

@Meta-Chuh said:

browse all categories manually, searching for another “rogue” [F6] entry.

Even easier, if you have a new enough (*) Notepad++, if you go to Settings > Shortcut Mapper > Plugin Commands, and go down to the NppExec.dll entry Execute..., it will tell you where the conflict is.

[*] “new enough”: even v7.2.2 shows which item it has a conflict with. Sometime after v7.5.0, and by v7.5.4, they added a column to show you which plugin DLL supplied each entry in the Plugin Commands tab; in v7.5.5, they added a filter, so that you could type execute in the filter box, and it would quickly take you to that.

----
Oh, weird, there’s a bug. If I intentionally make a conflict on NppExec’s Execute… F6: it shows the conflict properly if I scroll down normally:
But if I filter, it marks the Execute... line red, as if there is a conflict, but the message shows no conflict:. I will be submitting a bug report for that soon.

PeterJones

Submitted https://github.com/notepad-plus-plus/notepad-plus-plus/issues/5374

Meta Chuh

@PeterJones

Oh, weird, there’s a bug. If I intentionally make a conflict on NppExec’s Execute… F6: it shows the conflict properly if I scroll down normally
But if I filter, it marks the Execute… line red, as if there is a conflict, but the message shows no conflict

thank god you found this, otherwise my

and browse all categories manually, searching for another “rogue” [F6] entry.

would have looked pretty stupid ;-)

thanks for reporting this issue.
i don’t file any further new issues for now, as the last one i’ve submitted back in january for @Franckybleu has not been fixed or regressed by CookiePLMonster or anybody else yet.
(UCharDet 0.0.6 is working properly if compiled on mac and linux, but it is behaving erratically, if the unmodified source code is compiled on windows, which broke the autodetect character encoding)

PaoloRicardo

I presume I must wait for the bug to be fixed before F6 will work as designed?

Meta Chuh

I presume I must wait for the de-bug info in order to eventually assist you, using F6 to trigger plugins > nppexec > execute,
as it does work for pretty everybody else? ;-)

Meta Chuh

@PaoloRicardo

if i understood you correctly at another thread:

I realised that I did not have the most recent version of Notepad++ (7.63). Installing this now means F6 correctly brings up the NppExec dialog.

you have already upgraded from 7.5.9 to 7.6.3 - 32 bit, and everything works fine now.
in this case, i’m very glad it works for you again … or was it a question ?

PaoloRicardo

Meta

Not a question more a statement :-). NppExec F6 now working.

Thanks.

PeterJones

@PaoloRicardo said:

I presume I must wait for the bug to be fixed before F6 will work as designed?

No, that’s not what we were saying there at all.

We said that you could use the Shortcut Mapper to tell you why there was a conflict with the NppExec’s F6 and something else that was also apparently mapped to F6. We strayed a bit into a tangent about how the Shortcut Mapper displays certain items when you have a filter applied, but as my first screenshot showed, the Shortcut Mapper does tell you when there’s a conflict, and tell you where that conflict is, as long as you don’t have a filter applied.

Since installing 7.6.3 solved your F6 problem (by resetting whatever item conflicted with NppExec’s F6), I mostly posted this clarification so that future readers of this thread won’t think that 7.5.9 breaks the F6 key; it doesn’t.