You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it is not possible to distinguish a particular instance of Notepad ++ (from the same .exe file or different .exe files). This cause that from another program I cannot refer to a specific instance of NPP and open the file in it. Let say we have two separate Notepad++ folder (portable):
A\notepad++.exe (shortly A)
B\notepad++.exe (shortly B)
Both are run at the same time. Step to reproduce:
run A -multiInst
run B -multiInst << let say this NPP was the last active
go to other window folder (or program)
do sth like this A\notepad++.exe file.txt (in console or through another program)
Our file will be open in B (not A) - it looks like due to recent activity on B. Even if we use only A and we open two instance we cannot distinguish them other than the order in the system bar or the PID of the process. Both solutions are not permanent and they are changes when we restart the program or when we change the order on the system bar.
With an additional argument that adding something to the title, it is very easy to distinguish different processes from each other. So when I starting Notepad ++ I can set some text in title, and then I can easily select such a window based on the title and then open the specific file / files in it:
run A -multiInst -subtitle="main"
runB -multiInst
go to other window folder (or program)
in console use some commands/tools that select/active window base on (sub)title and do sth like this A\notepad++.exe file.txt
Our file will be open in A (not B as previouse example).
In my case lack of such possibility is a problem. Very often I work with many versions of NPP at the same time (each for different purposes), and I am not able to delegate files to the correct instances of the program. Very often I forget to select the correct window before I running the openning action and have to repeat the whole process.
Debug Information
Notepad++ v7.9.2 (32-bit)
Build time : Jan 27 2021 - 17:53:35
Path : D:\_test\NPPClean\notepad++.exe
Admin mode : ON
Local Conf mode : ON
OS Name : Windows 7 Ultimate (64-bit)
OS Build : 7601.0
Current ANSI codepage : 1250
Plugins : HexEditor.dll
The text was updated successfully, but these errors were encountered:
Anyone know of a plugin that can modify the title? At startup, I could pass a fictitious argument with some value, read it in the plugin and set it in the title.
Description of the Issue
Currently, it is not possible to distinguish a particular instance of Notepad ++ (from the same
.exe
file or different.exe
files). This cause that from another program I cannot refer to a specific instance of NPP and open the file in it. Let say we have two separate Notepad++ folder (portable):Both are run at the same time. Step to reproduce:
A -multiInst
B -multiInst
<< let say this NPP was the last activeA\notepad++.exe file.txt
(in console or through another program)Our file will be open in
B
(notA
) - it looks like due to recent activity onB
. Even if we use onlyA
and we open two instance we cannot distinguish them other than the order in the system bar or the PID of the process. Both solutions are not permanent and they are changes when we restart the program or when we change the order on the system bar.With an additional argument that adding something to the title, it is very easy to distinguish different processes from each other. So when I starting Notepad ++ I can set some text in title, and then I can easily select such a window based on the title and then open the specific file / files in it:
A -multiInst -subtitle="main"
B -multiInst
A\notepad++.exe file.txt
Our file will be open in
A
(notB
as previouse example).In my case lack of such possibility is a problem. Very often I work with many versions of NPP at the same time (each for different purposes), and I am not able to delegate files to the correct instances of the program. Very often I forget to select the correct window before I running the openning action and have to repeat the whole process.
Debug Information
The text was updated successfully, but these errors were encountered: