FMOF - Find My Open File

Helpful search commands based on your open files

Marketplace

What it does

File Reference Search

This is searching FOR files, meaning the extension prefills the WHAT

The Find My Open File commands perform a simple text search for your filename.

Note: you can configure if the search opens as an editor or the search veiw. I'm not making 250 different gifs to showcase how search works.

The Find All Open Files commands build a regex pattern like file1\.ts|file2\.js|file3\.vue and enables regex search mode. Special characters in filenames are automatically escaped.

Scoped Search

This is searching IN files, meaning the extension prefills the WHERE

Triggering Find in Open File will prefill the file include patterns to the currently opened file.

Triggering Find in All Open Files will prefill the file include pattern to restrict searches to all currently open tabs.

The pattern is optimized using brace expansion (e.g., src/{file1.ts,file2.ts}) to handle many files efficiently. The include pattern is not infinite, but you'd need a lot of open tabs to exceed the maximum.

What's the point

This is actually super useful all the time.

Finding file references by name:

• Component-based frameworks (Vue, Svelte, React, Angular) where component names are derived from filenames
• Configuration files referenced by name in other configs
• Module imports using filename-based resolution
• Asset files (images, stylesheets, data files) referenced across your codebase
• Any file where "Go to References" doesn't help because the filename itself is what's being referenced
• References in comments or readmes will not be discovered by any language server
• It's not that useful if your filename is very generic, like index.ts
• There's also no search for files with paths, as files are rarely referenced by their full paths (relative imports, path aliases, etc. would not be discovered, so I'm not offering this feature)

Scoping searches to open files:

• find that console.log you just added and want to clean up, but not every console.log in the codebase

No baggage

• Every button can be hidden from the context menu.
• No custom views. Complete reuse of the search UX you are familiar with.
• Comes with zero AI integrations.

Features

🔍 Search for File References

Find occurrences of your current file's name across the workspace:

📂 Search Within Open Files

Scope your searches to specific open files:

🔎 Search for All Open File Names

Find references to any of your currently open files using a regex OR pattern:

Keyboard Shortcuts

All commands have default shortcuts (see tables above). You can customize them in File > Preferences > Keyboard Shortcuts by searching for "fmof".

Note: Shortcuts work both when the editor has focus and when the search viewlet has focus, so you can quickly switch between search modes.

Settings

Context Menu Visibility

Control which commands appear in the editor context menu. The "with extension" variants are hidden by default to avoid menu pollution.

Search Behavior

Contributing

I don't expect much need for contribution here. But you can Open an issue on GitHub.