Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Regarding this post: viewtopic.php?f=2&t=5718
I think that in the first post it is important to be clear:
what's new in the current last nightly build,
what was added in the previous nightly builds,
and what was the last public Beta.
Something like:
Latest nightly build:
http://www.voidtools.com/Everything-1.4.1.783b.x86.zip
http://www.voidtools.com/Everything-1.4.1.783b.x64.zip
Fixed an issue with parsing < inside a search term.
Fixed an issue with repeatedly indexing an encrypted volume.
Changes in previous nightly build:
-
Latest public Beta:
http://www.voidtools.com/Everything-1.4.1.782b.x86.zip
http://www.voidtools.com/Everything-1.4.1.782b.x64.zip
Changes:
Tuesday, 25 October 2016: Version 1.4.1.782b
fixed an issue with namepartdupe:
fixed exclude hidden files
fixed a dual display search history positioning issue
fixed an issue with file:
fixed an issue with indexing hidden or system folders/files
fixed an issue when re-indexing an existing NTFS/ReFS index when "Include Only" is set.
added shell: function support.
added millisecond support to time format
I think that in the first post it is important to be clear:
what's new in the current last nightly build,
what was added in the previous nightly builds,
and what was the last public Beta.
Something like:
Latest nightly build:
http://www.voidtools.com/Everything-1.4.1.783b.x86.zip
http://www.voidtools.com/Everything-1.4.1.783b.x64.zip
Fixed an issue with parsing < inside a search term.
Fixed an issue with repeatedly indexing an encrypted volume.
Changes in previous nightly build:
-
Latest public Beta:
http://www.voidtools.com/Everything-1.4.1.782b.x86.zip
http://www.voidtools.com/Everything-1.4.1.782b.x64.zip
Changes:
Tuesday, 25 October 2016: Version 1.4.1.782b
fixed an issue with namepartdupe:
fixed exclude hidden files
fixed a dual display search history positioning issue
fixed an issue with file:
fixed an issue with indexing hidden or system folders/files
fixed an issue when re-indexing an existing NTFS/ReFS index when "Include Only" is set.
added shell: function support.
added millisecond support to time format
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Currently there are 2 files in the zip of the Nightly Builds:
Everything.exe
Everything.lng
Consider to add another file "Everything.exe.lnk" that include "-instance <current version>" so that we will have 3 files in the zip of the Nightly Builds:
Everything.exe
Everything.exe.lnk
Everything.lng
I find myself always do it manually after extracting the zip:
Create a shortcut of the EXE.
Properties.
C:\Everything\Everything.exe -instance 787
Everything.exe
Everything.lng
Consider to add another file "Everything.exe.lnk" that include "-instance <current version>" so that we will have 3 files in the zip of the Nightly Builds:
Everything.exe
Everything.exe.lnk
Everything.lng
I find myself always do it manually after extracting the zip:
Create a shortcut of the EXE.
Properties.
C:\Everything\Everything.exe -instance 787
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
That would assume that the only location for everything.exe is C:\everything.
That is not the case. The shortcut would depend on the location chosen by the user and thus could not be packaged in the .zip.
That is not the case. The shortcut would depend on the location chosen by the user and thus could not be packaged in the .zip.
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
3 kinds of solutions:
1. %windir%\explorer.exe ".\Everything.exe" - This should work for the exe but I've no knowledge how get it work with "-instance <current version>"
2. We can make a fake .lnk. Windows has a self-fix mechanism, if Windows doesn't find the path when lunching the .lnk (the path was changed), it will check if the exe is found in the same folder of the .lnk.
3. Thanks to RaMMicHaeL I have this VBS script for similar problem
1. %windir%\explorer.exe ".\Everything.exe" - This should work for the exe but I've no knowledge how get it work with "-instance <current version>"
2. We can make a fake .lnk. Windows has a self-fix mechanism, if Windows doesn't find the path when lunching the .lnk (the path was changed), it will check if the exe is found in the same folder of the .lnk.
3. Thanks to RaMMicHaeL I have this VBS script for similar problem
Code: Select all
Dim objShell
Set objShell = WScript.CreateObject( "WScript.Shell" )
objShell.Run(""".\7+ Taskbar Tweaker.exe"" -hidewnd")
Set objShell = Nothing
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
How about just using the Send command to put a shortcut on the desktop:
http://www.basiccomputerinformation.ca/ ... -shortcut/
http://www.basiccomputerinformation.ca/ ... -shortcut/
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
I would rather avoid having a lnk or bat in the zip. I assume you wish to run Everything directly from the zip.
I'm thinking about having the beta releases run in their own unique instance by default..
might cause more trouble than its worth..
Maybe holding down a special set of keys while running Everything..
Maybe if everything is run from the temp folder it automatically runs in its own instance.
I'm thinking about having the beta releases run in their own unique instance by default..
might cause more trouble than its worth..
Maybe holding down a special set of keys while running Everything..
Maybe if everything is run from the temp folder it automatically runs in its own instance.
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Thinking he just wants an easier way to get a desktop shortcut with the "-instance 1.4.x" already filled in (to more easily run different versions for comparison reasons, or whatever).
(Plus likely wouldn't work, even if the OS will "search" for the .exe...)
Likewise making "special" for beta...
If a user is going to use something in "beta" (like the current ongoing, changing beta, rather then one of the older, relatively static, & well tested "betas"), then you sort of have to expect the user to have some clue.
(Firefox might have done something like that for its "nightlies" or whatever, but I find the concept ridiculous.)
I'd also think you could automate any instance you'd want with a batch file?
Maybe even so far as setting up a desktop shortcut, if that floats your boat.
I'd think that to be highly non-standard.a lnk ... in the zip
(Plus likely wouldn't work, even if the OS will "search" for the .exe...)
Likewise making "special" for beta...
If a user is going to use something in "beta" (like the current ongoing, changing beta, rather then one of the older, relatively static, & well tested "betas"), then you sort of have to expect the user to have some clue.
(Firefox might have done something like that for its "nightlies" or whatever, but I find the concept ridiculous.)
I'd also think you could automate any instance you'd want with a batch file?
Maybe even so far as setting up a desktop shortcut, if that floats your boat.
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
I'm downloading a nightly version of Everything just for testing.
My way to make the testing fast is:
Download the Zip
Extract
Creating a shortcut within the folder > Properties > adding manually -instance 789 (My stable version of Everything is running in background, and I want to use the stable while testing. So to avoid a conflict I'm using the "-instance 789")
Running the shortcut > set the program to run as administrator
I'm open to new ideas
My way to make the testing fast is:
Download the Zip
Extract
Creating a shortcut within the folder > Properties > adding manually -instance 789 (My stable version of Everything is running in background, and I want to use the stable while testing. So to avoid a conflict I'm using the "-instance 789")
Running the shortcut > set the program to run as administrator
I'm open to new ideas
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
EGO.BAT
Run Everything, prompting for an -instance name
EGO.BAT 123
Run Everything with the specified -instance name, 123
EGO.BAT:
Adjust as needed.
Run Everything, prompting for an -instance name
EGO.BAT 123
Run Everything with the specified -instance name, 123
EGO.BAT:
Code: Select all
REM EGO, Everything_"GO.BAT" SjB 11-02-2016
@echo off
UNZIP Everything*.zip
set userid=
if NOT [%1]==[] goto userid:
set /p userid=Enter USERID:
goto set_usr:
:userid
set userid=%1
shift
:set_usr
START .\Everything.exe -instance %userid%
:exit
SET
PAUSE
set userid=
exit
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
therube, the code needs to be fixed...
David, What about to change the behaviour of the default -instance, where there is no name, it will get the version number? something like:
Everything (798)
Then user can make one .bat file for using its copy in each extracted ZIP.
David, What about to change the behaviour of the default -instance, where there is no name, it will get the version number? something like:
Everything (798)
Then user can make one .bat file for using its copy in each extracted ZIP.
Code: Select all
Everything.exe -instance
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
For having auto fill name of instance (version), Does it require to add new parameter?
It doesn't matter to me what the version Format will be:
798
798b
1.4.1.798b
1.4.1.798b.x64
1.4.1.798b.x86
Code: Select all
Everything.exe -instanceVersion
798
798b
1.4.1.798b
1.4.1.798b.x64
1.4.1.798b.x86
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Please try:
Everything.exe -instance "%cd%"
%cd% = current working directory.
%~dp0 could also be used from batch files:
Everything.exe -instance "%~dp0"
Everything.exe -instance "%cd%"
%cd% = current working directory.
%~dp0 could also be used from batch files:
Everything.exe -instance "%~dp0"
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Tested. The solution can't probably come from a .lnk, it must be a .bat.
Everything.exe -instance "%cd%" gives
Everything (Path)
Everything.exe -instance "%~dp0" gives
Everything (Path\)
I found more closer solutions here and here but it gives like this format:
Everything (Everything-1.4.1.789b.x64)
or
2 questions:
1. Can I have somehow just the version number?
2. Can I hide the bat window?
Everything.exe -instance "%cd%" gives
Everything (Path)
Everything.exe -instance "%~dp0" gives
Everything (Path\)
I found more closer solutions here and here but it gives like this format:
Everything (Everything-1.4.1.789b.x64)
Code: Select all
for %%a in (.) do set currentfolder=%%~nxa
Everything.exe -instance "%currentfolder%"
exit
Code: Select all
call set PARENT_DIR=%CD%
set PARENT_DIR=%PARENT_DIR:\= %
set LAST_WORD=
for %%i in (%PARENT_DIR%) do set LAST_WORD=%%i
Everything.exe -instance "%LAST_WORD%"
exit
1. Can I have somehow just the version number?
2. Can I hide the bat window?
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Try a START "" (I think it is), so:Everything.exe -instance "%LAST_WORD%"
Code: Select all
START "" Everything.exe -instance "%LAST_WORD%"
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
If Everything had a -version (-V) command line option...
If an Everything -V set %errorlevel% to its version number (I guess that might be kind of a non-standard thing to do)
Then you could do something like:
Otherwise, if Everything had a -version (-V) command line option...
You could send that to a file, Everything -V > instance
And then use SETX (maybe Win7 & later), or some other means, to get the value from the file, instance...
(I'm not really sure how to do that?)
Or if Everything set "-version" internally, then maybe something as simple as, Everything -instance -version (which would then result in something like Everything.exe -instance 1.4.1.816b-x86).
If an Everything -V set %errorlevel% to its version number (I guess that might be kind of a non-standard thing to do)
Then you could do something like:
Code: Select all
Everything -V
Everything -instance %errorlevel%
Otherwise, if Everything had a -version (-V) command line option...
You could send that to a file, Everything -V > instance
And then use SETX (maybe Win7 & later), or some other means, to get the value from the file, instance...
(I'm not really sure how to do that?)
Or if Everything set "-version" internally, then maybe something as simple as, Everything -instance -version (which would then result in something like Everything.exe -instance 1.4.1.816b-x86).
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Added -version-instance and -path-instance to Everything 816b.1. Can I have somehow just the version number?
Everything.exe -version-instance
- Will launch Everything with the version as the instance name
- Will launch Everything with the executable path as the instance name
START Everything.exe2. Can I hide the bat window?
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
therube and void
Thank you both.
Thank you both.
-
- Posts: 52
- Joined: Tue Dec 28, 2010 4:54 pm
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
THANK YOU for making the new "instance" flags! This has been my biggest annoyance with ES since 1.3. I have portable ES folders on every pen drive and I, inevitably, forget to change the shortcut every time I open it on another computer.
A couple of suggestions: Maybe the -path-instance (or -version-instance) should be the default in the new .ini files. That way new people (and distracted people!) don't waist a bunch of time fixing the problem when their additional instances act "weird."
Second, if you make a startup dialog for this eventually I'd like to suggest that you include a prompt to use a unique icon (and maybe provide a couple?). Using unique icons for my various instances really makes my life a lot less confusing.
A couple of suggestions: Maybe the -path-instance (or -version-instance) should be the default in the new .ini files. That way new people (and distracted people!) don't waist a bunch of time fixing the problem when their additional instances act "weird."
Second, if you make a startup dialog for this eventually I'd like to suggest that you include a prompt to use a unique icon (and maybe provide a couple?). Using unique icons for my various instances really makes my life a lot less confusing.
-
- Posts: 52
- Joined: Tue Dec 28, 2010 4:54 pm
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
Please remind me, what is the reason that the "instance" option was made necessary in 1.3? I forget the reason but I'm sure it was good. I run all of my instances from portable folders so I didn't need to worry about shortcuts until the new version.
Re: Suggestion for the post - Everything 1.4.1 Beta Nightly Builds
I'll consider making each Everything.exe run in its own instance by default.A couple of suggestions: Maybe the -path-instance (or -version-instance) should be the default in the new .ini files. That way new people (and distracted people!) don't waist a bunch of time fixing the problem when their additional instances act "weird."
It's not as easy as it sounds because of the Everything service and IPC.
You can customize the Everything icon per instance by placing an icon in your Everything.exe location with the filename:I'd like to suggest that you include a prompt to use a unique icon
Everything-<instance name>.ico
Where <instance name> is the instance name of Everything.
Added icons with different colors
It's not necessary if you only run one instance.Please remind me, what is the reason that the "instance" option was made necessary in 1.3?
Everything was designed for only one running instance and one Everything service.
It might be useful if you want to run different versions simultaneously.