notepad-plus-plus / notepad-plus-plus/notepad-plus-plus

WANTED: Add support for simple 'glob' style string searches for Find as a sub-option for "Extended..." to help sieve single and multi-line matches.

Open
#13,618 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
29.4k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

THIS IS A FEATURE SUGGESTION / BEGGING

I love Notepad++ and have used it for years, even working at my job alongside a former Notepad++ developer teammate back in 2005

I hate RegEx and have never been very good at it. I recently used a "glob to regex" converter as a crutch. The situation was pretty simple:

I needed to match tags in a vcxproj file that fit the following "glob" format"

<ProjectReflibgeotiff.vcxReference>

Unfortunately no matter what I've done it came back matching any <ProjectReference line and only that single line, whereas I needed to match the entire tag so I could remove it, or it simply didn't work. Even with Extended... I couldn't get it to match, despite the fact that the lines are all pretty much identical. Maybe it was \r\n versus \n, or a whitespace issue, who knows.

It would be nice to see "glob" supported under "Extended..." in the Find dialog. It would also be nice if the Find dialog could come back with multi-line results.

I imagine it being like:

( ) Extended (\n \r \t \x ...) [ ] Treat * and ? as glob search
or just [ ] Use Glob or [ ] * and ? wildcard support

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Find dialog's Extended search option and review how current searches handle wildcards and line breaks. Clarify the intended glob syntax, matching behavior, and how multi-line results should be presented. Done means the feature scope and expected matching behavior are specified well enough to implement and test.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.