(05-06-2022, 04:18 PM)RhoSigma Wrote: My best guess would be to change the second line to use $(FULL_CURRENT_PATH) too, instead of $(CURRENT_DIRECTORY).
$(CURRENT_DIRECTORY) is IMHO the current directory of the notepad++.exe and not the directory where your hello1.exe is.
Thanks for your reply. I tried that, which caused Windows to prompt
How do you want to open this file?
(Google Chrome, Notepad++, Look for an app in the Microsoft Store, More Apps)
[x] Always use this app to open .bas files.
The console output showed the problems:
NPP_RUN: C:\Users{username}\Documents\Code\qb64\programs\hello1.bas && hello1 && ".exe"
which are
- $(FULL_CURRENT_PATH) includes the source file (.bas) name
- the "&&" and quotes are interpreted as literals
Reading the NppExec help pointed me to "NppExec.txt" located in the plugin folder, which documents all the tags (and also commands - it seems NppExec has its own rudimentary scripting language!)
So $(CURRENT_DIRECTORY) was right after all, I was just appending wrong.
BTW they do have a tag for the Notepad++ EXE folder, which is $(NPP_DIRECTORY).
So after reading through the doc and examples, I found the format that worked:
QB64.EXE -c "$(FULL_CURRENT_PATH)" -o "$(FULL_CURRENT_PATH)"
NPP_RUN $(CURRENT_DIRECTORY)\$(NAME_PART).EXE
For anyone else who wants to make QB64 work with Notepad++ or do anything more fancy, check out the docs
- NppExec.txt
- NppExec_HelpAll.txt
- etc.
in the NppExec plugin folder under the Notepad++ directory, which on my Windows 10 machine was at
- C:\Program Files (x86)\Notepad++\plugins\NppExec\doc\NppExec\
Hope this helps someone?
