Community
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • donhoD

      Notepad++ release 8.9.9.1

      Watching Ignoring Scheduled Pinned Locked Moved Announcements
      23
      3 Votes
      23 Posts
      2k Views
      PeterJonesP
      PeterJones said: Please note that the request to move / reorder the new checkbox control is being tracked as #18639. For those who the placement/order bothers, if you haven’t already, you could go add your upvote to that issue. The fix to reorder has already been implemented, so at least that much will be in the next version. If you have strong feelings on moving it as well, further discussion could happen there.
    • Morten SiljubergM

      Why do Notepad++ keep the "Move to recycle bin" delete prompt?

      Watching Ignoring Scheduled Pinned Locked Moved General Discussion
      4
      0 Votes
      4 Posts
      553 Views
      S
      Ah, that clears it up. I didn’t realise the confirmation prompt could be controlled through the Recycle Bin properties, so it looks like the option is still there rather than being completely removed. Thanks for pointing that out!
    • J

      Duplicate context menu entries

      Watching Ignoring Scheduled Pinned Locked Moved Help wanted · · · – – – · · ·
      9
      1
      0 Votes
      9 Posts
      676 Views
      D
      Glad the second reboot held — that fits with what PeterJones described. Windows 11 does not keep these primary-menu entries in the classic HKCR*\shellex registry keys the way Windows 10 did; the “Edit with Notepad++” entry comes from NppShell.dll through a sparse package registration, and Windows caches that registration, so a stale entry can survive an uninstall and reinstall until Explorer and the shell cache are refreshed by a reboot. If it does come back, the thing I would check before reinstalling again is whether two copies of the shell extension are registered — for example a leftover 32-bit install alongside the 64-bit one, or an old install folder still on disk. Re-running the current installer as administrator and toggling the shell extension off and back on, or following the unregister and re-register steps in nppShell issue 79, is usually enough without a full reinstall. And if it returns after a future update, noting whether the Publisher field in the manifest changed would help confirm it is the same known issue rather than a new duplicate.