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
    • h-jangraH

      NppVim 1.14.0.0 Release : Added nppvim.rc support

      Watching Ignoring Scheduled Pinned Locked Moved Notepad++ & Plugin Development
      1
      1 Votes
      1 Posts
      178 Views
      No one has replied
    • PeterJonesP

      Announcing Perl-based automation of Notepad++

      Watching Ignoring Scheduled Pinned Locked Moved Notepad++ & Plugin Development perl automation
      17
      6 Votes
      17 Posts
      7k Views
      PeterJonesP
      v0.012 released to CPAN Update for Notpead++ v8.5.4 - v8.9.6.4 Update Editor messages and enumerations (hashes) Update Notepad++ menu commands and messages Remove notepad->prompt() and the Win32::GUI dependency [#91] Please comment on Issue #92 if this call is important to you <https://github.com/pryrt/Win32-Mechanize-NotepadPlusPlus/issues/92> Improve test suite Get it working through Perl v5.42 Don’t test as many old versions (too much compute overhead) See CHANGES file for full history, including interveninng v0.009, v0.010, and v0.011 I don’t always post about new versions here (mostly because I get distracted and forget to). But I thought it was important on this one, because notepad->prompt() has been disabled in this version: if notepad->prompt() is important to you, please comment on https://github.com/pryrt/Win32-Mechanize-NotepadPlusPlus/issues/92 and stick with v0.011, which (until further notice) is the most recent version to include the notepad->prompt()
    • Thomas KnoefelT

      [New Plugin] MultiReplace

      Watching Ignoring Scheduled Pinned Locked Moved Notepad++ & Plugin Development
      78
      3 Votes
      78 Posts
      71k Views
      Thomas KnoefelT
      MultiReplace 6.0 is out and will land in Plugin Admin with the next Notepad++ release. The focus of this release is a second formula engine: ExprTk now sits alongside Lua for math, string and conditional replacements, joined by multi-list tabs, tandem mode, and a series of UI and workflow improvements. Several new options live under Plugins > MultiReplace > Settings. Download: Latest build Key Features & Improvements New Formula Engine (ExprTk): A second engine alongside Lua for math, string and conditional replacements. Its standout is the built-in output formatter - a single declarative spec that turns any result into fixed decimals, hex/binary, padded and aligned fields, time durations or formatted dates, applied right where the value is produced. Switch per tab via the (L) / (E) indicator next to Formula Support. The ExprTk integration - the (?=...) marker and the formula functions for reading captures and earlier results - follows the approach pioneered by @Coises in Columns++. Full syntax and examples are in the ExprTk formula reference. List Tabs: Keep different replacement sets available across tabs. State is fully separate per tab. Tandem Mode: MR panel snaps to the Notepad++ window edge and follows it around. Toggle via the plugin menu. Reopen on Startup: Reopens MR automatically if it was open when you closed Notepad++. Opt-in via the plugin menu. Compact Toolbar: New top toolbar layout - more horizontal space for the list. Always Visible List: Keeps the list visible instead of collapsing when you toggle it off. Requires “Keep list always visible” enabled in Settings. Bookmark Matches: Sets a Notepad++ bookmark on every match line. Toggle via the new checkbox next to Mark Matches. Column Reorder & Lock: Drag column headers to rearrange. Right-click for “Lock column width” or “Reset Column Order”. Modified Timestamp Column: Optional column tracking the last edit per entry. A dirty-flag stripe on the left edge marks unsaved changes. Excel-Compatible CSV: Lists save in the standard CSV dialect used by spreadsheets - opens cleanly in Excel, edit there, load back without conversion. Keyboard Shortcuts Ctrl+Up/Down: Move selected rows up or down (auto-repeat) Ctrl+L: Toggle list visibility from anywhere in the panel Alt+Up/Down: Round-trip between input fields and a selected row Ctrl+Shift + button click: Run from the input fields while the list stays open Ctrl+Shift+H: Pull selected editor text into Find what (optionally auto-escaped for Regex/Extended mode) [image: 1780756837071-multireplace6.png] Issues or suggestions: GitHub. Happy replacing!
    • isaacjuanI

      [New Plugin] AI Chat — chat with LLMs directly inside Notepad++

      Watching Ignoring Scheduled Pinned Locked Moved Notepad++ & Plugin Development
      1
      1 Votes
      1 Posts
      361 Views
      No one has replied
    • EkopalypseE

      DAP client plugin

      Watching Ignoring Scheduled Pinned Locked Moved Notepad++ & Plugin Development
      16
      3 Votes
      16 Posts
      2k Views
      EkopalypseE
      @PeterJones It all sounded so logical to me when I wrote it, but now that I’m reading it again, I have to agree with you— that wasn’t my best explanation of how this is supposed to work. Thanks for clarifying, and yes, Prefer installed Python libraries and a local Python installation are necessary in this scenario. Regarding sys.path, yes, that makes sense. I should have tested all of this in a sandbox; then I would have noticed how my own setup differs from a standard installation. And yes, the procedure, which is ONLY necessary to debug PythonScript scripts, is that you have one Npp instance, in which the script is debugged—let’s call it instance A—and another, let’s call this instance B, in which the script to be debugged actually runs. So, Instance A starts the debugging session via Plugins->NppDebugger->Start. This results in a new Npp instance B being launched. Now, in Instance B, the script that configures debugpy must be started. This causes debugpy to launch another Python process pydevd which is the real python debugger. This means that NppDebugger, from Npp instance A, waits for debugpy in Npp instance B to start the Python debugger pydevd AND for debugpy to start a TCP server to which NppDebugger can then connect. NppDebugger(tcp client) <-> debugy(tcp server) <-intern-> debugy(tcp client) <-> pydevd(tcp server) As soon as NppDebugger establishes a connection, it begins communicating with debugpy via DAP messages. Is the long-term plan … Yes, ultimately, the plugin should be designed to minimize the need for manual configuration editing. For debuggers that work with compiled source code, such as gdb, delve, lldb, etc., this is usually a project-specific setting and something that a user must set at least once per project. I don’t see how the plugin could figure this out on its own. For PythonScript debugging, a simple variable substitution, as you mentioned, seems sufficient. @Lycan-Thrope said: They have a Trial Version If I find the time, I’ll give it a try… but that might take a while… :) @Lycan-Thrope said: What the heck, … :D - thank you :D