File -> Export...

[Stamimail]

Try to support that every file the user created by
File -> Export...
the user also will be able to import/load it in Everything as a file list.

I exported to json, and trying to load this json to Everything by
Open File List...
it shows improper file list.

[NotNull]

These non-EFU formats are intended to be used in other applications.

For example: Everything will never be able to decide if some path in an exported TXT file is a file or a folder.

[Stamimail]

These non-EFU formats are intended to be used in other applications.

This is true. But what's the problem with being able to import the list of files you created back?

For example: Everything will never be able to decide if some path in an exported TXT file is a file or a folder.

This is not true.
For TXT files Everything supports the syntax \ tail for marking folders.
C:\folder\
C:\non-folder

[NotNull]

But what's the problem with being able to import the list of files you created back?

Time. Time spent on this can not be spend on other features. It is all about priorities.

For TXT files Everything supports the syntax \ tail for marking folders.

... unless you try to open a txt file generated by Everything 1.4 ...

[Stamimail]

Time. Time spent on this can not be spend on other features. It is all about priorities.

Did I say now?
Just deciding whether it should be done or not. If indeed so, to put it on the "to do" list, and that's it.
Managing the order of priorities in the big list implementation is void's management, not ours.

[void]

Everything already supports TXT and CSV filelists.
They can be opened from File -> Open File Lists
Change the filename to: *.txt or *.csv

For TXT, Everything will import each line as a file/folder path.
a trailing \ indicates a folder.

For CSV, if a filename header is present:
each value under the filename column is a file or folder path.
a trailing \ indicates a folder.

For CSV, with no header:
The value from the first column is a file or folder path.
a trailing \ indicates a folder.
(there's a few quirks in the current versions that will be fixed in the next alpha update)

HTML and JSON will unlikely be supported.
Theses formats are outside the scope of Everything.



I will consider showing TXT and CSV filters in the Open File dialog.

[Stamimail]

Everything already supports TXT and CSV filelists.
They can be opened from File -> Open File Lists
Change the filename to: *.txt or *.csv
...
...
I will consider showing TXT and CSV filters in the Open File dialog.

Yes, it is configured to show only efu.
You can make it like open file of Word:
All Word Documents (*.docx;*.docm;*.dotx;*.dotm;*.doc;*.dot;*.htm;*.html;*.rtf;*.mht;*.mhtml;*.xml)
i.e.
All supported filelists(...)

... unless you try to open a txt file generated by Everything 1.4 ...

I think the problem is in the old files - they were created in the old syntax, which did not distinguish between a folder and a file (This was before we thought about the problem and its solution). The old files should be upgraded, and make use of the new technology.

[void]

Everything 1.5.0.1356a adds support for opening and importing CSV and TXT filelists.

Everything 1.5.0.1356a also fixes opening CSV/EFU file lists with no header.

When no header is present, the first column is treated as the filename column.
This also means the first line is treated as a file.

The file list editor will now also support opening CSV and TXT file lists.

[Stamimail]

Everything 1.5.0.1356a adds support for opening and importing CSV and TXT filelists.

When Alt+Drag efu file to Everything the tooltip changes to Open File List +.
The same thing should be for Alt+Drag of CSV and TXT files.

Also, if someone dragged without Alt (Set Search +), and now he dragging again with Alt (Open File List +) it should clear the search box.

[void]

The same thing should be for Alt+Drag of CSV and TXT files.

I will consider an option to allow drag-dropping CSV/TXT files as file lists.

Thank you for the suggestion.

For now, Everything will only support drag-dropping EFU file lists.

[Stamimail]

What about an option to export/import (selection) as an Everything db file? why not?
It will also be a convenient method to convert db to filelist.

[void]

The Everything.db is not human readable.
It cannot be opened by other programs.
Other programs cannot generate an Everything.db
Everything.db contains other information, such as the index journal, indexing state and presorted index arrays.
The Everything.db is not designed to be an exported file list.

db2efu can convert a db to an efu file.
-db can also open an Everything.db which can then be exported to an efu file.

[Stamimail]

I think the answer expalins why you don't want to support export (selection) to db.
What about import? I mean to support db in "open file list..." - will load a db as a filelist.
(more user friendly)
Is there any downside?

[void]

The next alpha update will have support for opening Everything.db files as a file lists.

This will make it easier to recover filenames from a failed drive.
Everything 1.5 will also keep a backup of your Everything.db as Everything.backup.db


The opened Everything.db will be opened as read-only.


Thank you for the suggestion.

[void]

Everything 1.5.0.1369a adds support for opening db files as file lists.

To open your Everything.db as a file list:

• In Everything 1.5, from the File menu, click Open File List....
• Select your Everything.db and click Open.