Hi all,
Version 1.4.1.969 (x64)
strangely, I got this message from time to time (not very often):
There is no file list called Mix, nor Mix is contained in any filename of my configured file lists.
My filelists look all like
E:\m\l\filelist_name1.txt
E:\m\l\filelist_name2.txt
E:\m\l\filelist_name3.txt
E:\m\l\filelist_name4.txt
...
Please recognize, that my filelists are stored in E:\m\l\
The above message shows E:\m\p\ which is the folder, where everything lives. In the folder E:\m\p\ is also no file containing Mix as a part of its filename.
So I wonder, why such a message will pop up...
Any Ideas?
Unable to open file list ? (which does not exist and is not configured)
-
- Posts: 65
- Joined: Mon Jun 19, 2017 1:45 pm
Re: Unable to open file list ? (which does not exist and is not configured)
This error is shown when you open a file list in Everything and the file list is not valid (missing the filename column).
This will occur if you run Everything with the following command line options:
Everything.exe mix
mix would have to exist in the same location as Everything.exe for this specific error message.
Is there a folder or file called mix in E:\m\p ?
seems odd the file exists, otherwise the error would say e:\m\p\mix not found
Are you trying to perform a command line search for mix? -If so, please use the -s <search-text> command line option. For example:
Everything.exe -s mix
Were you opening file lists when this error message was shown?
This will occur if you run Everything with the following command line options:
Everything.exe mix
mix would have to exist in the same location as Everything.exe for this specific error message.
Is there a folder or file called mix in E:\m\p ?
seems odd the file exists, otherwise the error would say e:\m\p\mix not found
Are you trying to perform a command line search for mix? -If so, please use the -s <search-text> command line option. For example:
Everything.exe -s mix
Were you opening file lists when this error message was shown?
Re: Unable to open file list ? (which does not exist and is not configured)
(I'll just note... going by memory... so ...
If you run Everything from a relative path, oddities can occur
Like if you are in C:\TEST
& Everything is in C:\EV (C:\EV\Everything.exe)
& you run (from within C:\TEST), ..\EV\Everything.exe
Everything executes as if you were in C:\EV rather then if you were in C:\TEST
Now say that you had a .efu in C:\TEST (C:\TEST\test.efu)
If you did something like (from within C:\TEST), ..\EV\Everything.exe test.efu,
that would not work [I don't think] (unless there happened to be a test.efu in C:\EV).
[Don't even know if the above is valid, just using as example.]
I think it was something like that.
[And without thinking, that's probably mentioned above.])
If you run Everything from a relative path, oddities can occur
Like if you are in C:\TEST
& Everything is in C:\EV (C:\EV\Everything.exe)
& you run (from within C:\TEST), ..\EV\Everything.exe
Everything executes as if you were in C:\EV rather then if you were in C:\TEST
Now say that you had a .efu in C:\TEST (C:\TEST\test.efu)
If you did something like (from within C:\TEST), ..\EV\Everything.exe test.efu,
that would not work [I don't think] (unless there happened to be a test.efu in C:\EV).
[Don't even know if the above is valid, just using as example.]
I think it was something like that.
[And without thinking, that's probably mentioned above.])