notepad-plus-plus / notepad-plus-plus/notepad-plus-plus
Virtual desktop not remembered after Windows restart
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29.4k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for such an amazing app.
Currently if Windows is restarted with Notepad++ running, Notepad++ will start on login after reboot (works as expected). It always starts on the first virtual desktop, not the one it was originally running on, however. It would be nice for it to start on the same virtual desktop after reboot.
Steps to Reproduce the Issue
- Switch to virtual desktop 2 (or subsequent)
- Start Notepad++ on virtual desktop 2 (or subsequent)
- Reboot Windows. On login Notepad++ starts on the first virtual desktop (not virtual desktop 2 (or subsequent))
Expected Behavior
Notepad++ should start on the virtual desktop where it was originally running on Windows restart.
Debug Information
Notepad++ v8.6.2 (64-bit)
Build time : Jan 14 2024 - 02:16:00
Path : C:\Program Files\Notepad++\notepad++.exe
Command Line :
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : OFF
OS Name : Windows 11 Pro (64-bit)
OS Version : 23H2
OS Build : 22631.3155
Current ANSI codepage : 1252
Plugins :
JSMinNPP (1.2205)
mimeTools (3)
NppConverter (4.5)
NppExport (0.4)
XMLTools (3.1.1.13)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the restart flow on Windows 11 using the listed steps, then trace the application's startup and Windows-session restoration handling. Done means a Notepad++ instance started on a later virtual desktop returns to that same desktop after Windows restarts and login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100