Yeah, you said everything I was working on for my response, but much more succinctly.

@Stefan-Huus-Gregersen ,

As for “the “Feature request” … seems to be locked”. Yes, the FAQ thread is locked. But as the text of the FAQ itself says, this forum is not the place for feature requests. The place for feature requests is linked in that FAQ. So follow that link, and you can make your feature request there.

Thanks for the additional details: it helped Scott give an excellent response. I had been writing my response assuming that you didn’t know about the "$(FULL_CURRENT_PATH)", so I appreciate that you posted that update, so I wouldn’t waste your time with things you already knew.

You might also consider the NppExec plugin (available using that link, or thru the plugin manager), which was mentioned in @Claudia-Frank’s link, and would allow you to build a batch file that gets run in a pane of the Notepad++ GUI, rather than spawning an external cmd.exe window. That gets rid of the need for the “pause” and “hit any key…”, because it gets captured into an interactive sub-window of NPP.

===

Oh, i see your update. If you want F5 to be run-current-file, you can just edit the shortcuts.

** Settings > Shortcut Mapper > Macros > Run With Python** (or whatever you named your shortcut before): change it to F5. Before you hit OK, it will say “conflict found”, and below will say something like “Main Menu | 269 Run…”. Make note of that, then hit OK. Go to the Main Menu tab, and replace the normal Run shortcut with Ctrl+F5. Swap complete, F5 will do what you want.

maybe this link is helpful for you as well.

Cheers
Claudia

Okay, so there are many approaches to this…and probably @PeterJones is better at this than I am…but perhaps the very simplest is to Save your Run box command (D:\Python_scripts\notepad++runfile\runPythonScript.bat “$(FULL_CURRENT_PATH)”), giving it a name (“Python Run Current File”…?)and possibly a keycombination.

This has the added benefit of chopping 1 step off at run time…with your existing approach you are presented with the Run box and you have to OK it…with the above approach that is skipped.

Of course, this may be what you meant above when you were talking about “CTRL + F5”, but I don’t see why saving the command (which never changes) would be objectionable…

Workflow example:
Pressing the run button in Notepad++ with " D:\Python_scripts\notepad++runfile\runPythonScript.bat “$(FULL_CURRENT_PATH)” " written in the textbox
Bat file opens
It gets the filepath of the current open file in Notepad++ from “$(FULL_CURRENT_PATH)”
Then opens the python file by writing py (and then the path that it receives)
Now my Python script crashes
Then it pauses the bat so it wont continue so i can read the error that occured

Does that help you understand what i am doing? :)

Thanks for the recommendation of the “Feature request” but it kinda seems to be locked so i can’t use it hmm…

Well…I meant describe more of your overall workflow…you hint at Python and a batch file (which somehow gets the name of your N++ current file)…but to offer up solutions–to your generic problem, not necessarily your very specific one–more details are needed.

However, since you seem to be fixated on “gotta have the Run box keep the text over Notepad++ runs”, no one can offer up much (unless someone has an exact cure for that…anyone?) in the form of a “adjust your workflow” type solution, which may in fact lead you to think, “Why was I ever doing this with the Run box anyway?”.

But I understand that you want what you want. So I will kindly point you to the proper way to make feature requests for Notepad++ and that is here.

It would probably help if you could describe a bit more this workflow you only hint at. Then there could be alternate solutions rather than just the one you’ve requested. Walk us through what you do and I’ll be a good solution comes out of it.