Searching

FlyingFiles has two search windows: Search... for finding files by criteria, and Search changes... for finding recently changed files and copying them somewhere else. Both search the folder of the active panel — on disk, in an archive or on a server.

Neither window blocks the app: you can keep working in the panels while the window stays open. A closed window remembers its results; if you reopen it while the active panel shows a different folder, it starts with an empty list.

Search

Functions → Search...

Criteria

A criterion with a checkbox next to it applies only when you check it. All checked criteria must be met at the same time.

Switches:

• Case sensitive — by default, letter case does not matter;

• Search subfolders — on by default;

• Include .ffignore file — skips items covered by the .ffignore rules of the folder you search in.

In a mask, * stands for any sequence of characters, and ? and _ for a single character. Example: report_202?.*.

Tip: Content search reads every matching file in full, as UTF-8 text. On a server or with large files, narrow the search by name, extension or size first.

Results

• Search starts the search; while it runs, the button turns into Cancel, and below the list you see "Searching... found: 120".

• Columns: Name, Path (relative to the folder you search in), Type, Size, Modified.

• Double-clicking a result takes the panel you searched from to the folder containing that file and puts the cursor on it.

• Remove from list removes the selected rows from the results (the files stay on disk).

• Esc stops a running search; pressed again, it closes the window.

Search changes

Functions → Search changes... or Cmd+F2 / Alt+F2.

This window is made for the task "copy what I've changed since yesterday" — for example, uploading changed website files to the server or moving your current work to a USB flash drive.

Finding changes

1. In the active panel, open the folder you work in (e.g. the project folder). In the other panel, open the destination with the same structure (e.g. the same project on the server).

2. Open Search changes....

3. Set Search for changes from the last: to a number and a unit: minutes, hours, days, months (30 days each) or years (365 days each).

4. Check Search in subdirectories too if needed (off by default), and optionally Include .ffignore file.

5. Click Search.

The list contains only files (no folders) changed in that period: Name, Path, Size, Modified.

Cleaning up the list

• Remove from List — the selected rows will not be copied.

• Add File to .ffignore — adds the selected files to the .ffignore rules of the folder you search in, so they do not come back next time.

• Add Folder to .ffignore — adds the folders of the selected files (available for files in subfolders).

When Include .ffignore file is on, files covered by the new rules disappear from the list right away.

Copying changes

1. Leave Show Changes checked if you want to review the plan before copying (recommended).

2. Click Copy. The app checks the folder in the other panel: for each file, the destination is the same relative path (src/app.js → <other panel>/src/app.js).

3. The question depends on the result:

   • "The destination panel directory structure matches. Copy … and overwrite existing destination files?"

   • "The destination panel directory structure does not match the change list. Copy … anyway and recreate missing subdirectories from the list?" — a sign that the other panel may be in the wrong place.

   The default answer is No.

4. With Show Changes on, the Confirm Changes window opens with the columns Copy (checkbox), Path, Operation ("Overwrite file", "Create file", "Create folders and file"), Source and Destination. Uncheck what you do not want to copy and click Confirm.

5. Files are copied over existing ones, with their dates preserved and missing folders created. Progress, the summary and the list of failed items work as in regular copying. After a successful copy, the Search changes window closes.

Warning: Copying changes overwrites files at the destination without the conflicts dialog. Review the plan in Confirm Changes, especially when the app reports a mismatched directory structure.