I made an extension which applies a workaround by copying the current search results, regex-ing for the filenames, getting their relative paths and then putting those paths into the 'files to include` filter. Find and Transform.

Specifically Using the Search Results files in another search.

Use from the context menu, Command Palette or a keybinding like:

{
  "key": "alt+shift+f", 
  "command": "runInSearchPanel",   
  "args": {
    "find": "Second",                            // plus all the other args from the findInFiles command 
    "replace": "Third",
    "filesToInclude": "${resultsFiles}",   // !!
    "triggerSearch": true                
  },
	"when": "hasSearchResult"      // I suggest this but it isn't mandatory
}

There are other ways to use the ${resultsFiles} variable as well. Such as in the find-and-transform.searchInResults command where it is automatically applied.

Using this keybinding:

  {
    "key": "alt+z",
    "command": "runInSearchPanel",
    "args": {
      "filesToInclude": "${resultsFiles}",
      "triggerSearch": true,
    }
  },

Demo:

[Since the context menu item for this really belongs in the Search results context menu but that is not currently exposed to extensions, I am going to file an issue requesting it. See https://github.com//issues/127896]

Secondary search #118128

Description

Activity

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions