Who is responsible for viewing and claiming users suggestions ?
-
So we finalized commands into it, to looks like this:
http://i.imgur.com/I1v9m3Y.pngIt’s is not what I need, because cls command delete everything outputted before.
No matter how many times I press F6, it will show still one most fresh output on console: http://i.imgur.com/8S2fmx8.png
But I need history of outputs, I need clear just those redundant stuff. But I need to compare outputs based on my code changes. Is possible to modify it under my needs please ?I don’t want run that script on every start of NP++, because I still need code stuff and then see result. So we keep it by F6 pressing.
And I was ticking off this setting:
http://i.imgur.com/snYUjbT.png
Because in every new NP++ run, I don’t want see console at first, I need code something without splitscreen. This untick can not keep it’s value between starts of NP++. Can it be somehow forced to not show console on each start please ?Thank you much Claudia
-
No, I meant something different.
We save the console option in a different profile like herenpe_console v- m- a+ cls npp_console off
save it, and assign it to be started when npp starts like here
Which means your actual python execution profile should then
be changed topython "$(FULL_CURRENT_PATH)"
like here.
That’s it. Everytime you start npp the assigned startup script sets your console parameters.
When pressing (SHIFT +) F6 it will execute python and console is visible again.Cheers
Claudia -
I have read your post five times. I explored everything in npp exec settings and stuff.
I don’t know where do I have to put this:
python “$(FULL_CURRENT_PATH)”In ‘Execute’ window you can’t have two separate scripts or commands. Once I save those three line commands and make it execute on NP++ start, there is no option where may I put line above.
Thanks
-
I have done this:
this commands I saved to profile A and run on start:
npe_console v- m- a+
cls
npp_console offthis I saved as profile B and supposed to be run with F6:
python “$(FULL_CURRENT_PATH)”But I cannot see what is executing, because on start I have still console appeared and by presssing F6 code is exexuting, but still no history. And also on start code get executed without F6.
I’m not sure which profile it’s executing by F6, it’s not possible to check it anyhow.If you may install other NP++ instance and try it, you will get same result.
Thanks
-
@John-Spark said:
I have done this:
this commands I saved to profile A and run on start:
npe_console v- m- a+
cls
npp_console offok
this I saved as profile B and supposed to be run with F6:
python “$(FULL_CURRENT_PATH)”ok
But I cannot see what is executing, because on start I have still console appeared and by presssing F6 code is exexuting, but still no history. And also on start code get executed without F6.
I’m not sure which profile it’s executing by F6, it’s not possible to check it anyhow.If you may install other NP++ instance and try it, you will get same result.
Thanks
of course not ok, I will try it with a new installed npp and see if this is a bug.
I will come back on this.Claudia
-
@John-Spark
it works exactly as I described.
Are you sure you have usednpp_console off
and NOT
npe_console off
?
If so,please post the content of the following two files
...\plugins\Config\npes_saved.txt
and
...\plugins\Config\NppExec.ini
Claudia
-
I apologise. I used wrong npe instead of correct npp.
However, now when I press F6, all happend so fast as blink of an eye.
Console get closed as it gets executed I assume, so I can’t even see a result.
Also I don’t want get closed console after it executes.Thanks and sorry again
-
do you remember what we said, you need to run the execute dialog everytime you start npp for the first time and only one time.
Every subsequent call can be executed by the direct execution function. As far as I remember you switched the normal keys
F6 and SHIFT+F6, didn’t you? So, press SHIFT+F6 what happens?Claudia
-
Yes yes I remember. It did that flash and every other press. Like there is no differention between first press and others. This seems buggy for real.
Here is nppexec.ini
http://i.imgur.com/zUrpp9z.png
Here is npsaved
http://i.imgur.com/ih6Ajlk.pngThanks
-
-
@John-Spark
your npes_saved.txt is wrong.
Why don’t you not just simply copy and past my example?
It must look like this::NppExec Console Settings npe_console v- m- a+ cls npp_console off ::Python python "$(FULL_CURRENT_PATH)"
do you see the difference?
Claudia
-
I’m confused now.
I did:- closed NP++
- opened npes_saved.txt
- pasted copied text from your post above
- saved
-turn on NP++
and I saw this:
http://i.imgur.com/MbqHAje.png
that txt file looks now:
http://i.imgur.com/U6jdALs.pngshortcut file from program files: http://i.imgur.com/dWTlB1p.png
shortcut file from user’s appdata folder: http://i.imgur.com/iBRgDYl.png -
look like means, as far as I know, it is similar but not equal.
You, of course need to adapt it to your needs.
I called my startup script NppExec Console Settings,
whereas you called it claudia commands.
That’s why NppExec cannot find the entry point to execute the commands
on startup, therefore the error.
You either have to change the label back to claudia commands or
change in NppExec.ini the ScriptNppStart toScriptNppStart="NppExec Console Settings"
Claudia
Btw. shortcuts.xml looks ok
-
Oh yes, what a fail of me.
I changed it to claudia commands in .txt file.
Now run NP++ and there is again that situation:- console is not loaded - which is ok
- I press F6 - nothing prompted, just eyeblink time flash something
- repeated press, same thing
-
-
correct
-
@John-Spark
but after start of npp you should press SHIFT+F6Claudia
-
@John-Spark
I double checked the shortcuts.xml
After start of npp you need to press CTRL+F6Claudia
-
Oh my Lord. There is difference between F6 and Ctrl+F6 ?
I thought, it’s just prompting screen.
It works now. On start Imust ctrl+f6.This is, how you meant it from beginning + is this best way closest to one key press as I need ? Anything better can’t be made right now ?
MANY THANKS FOR YOUR PATIENCE AND TIME AND EFFORT. I OWE YOU !
-
yes, that’s the closest we can get, First time it must run the execute dialog.
Glad to see that we’ve done it.What’s next?
If there is one, please open a new thread this one is getting to big.Claudia