/ search commands

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

/ search commands

Post by void »

Search commands are available in Everything 1.4.1.802b or later.

To use search commands, type in one of the following commands in the search box and press ENTER:
about:
  • Show the about dialog.
about:config
  • Open the user Everything.ini
about:credits
  • Show the Everything credits
about:license
about:licence
  • Show the Everything license
about:home
  • Load the home search
about:preferences
about:options
  • Show the options window
/command <ID>
  • Run the specified UI ID command
/debug
/console /debug_log
  • Start debug logging.
/verbose
  • Toggle the showing of verbose debugging information in the debug console.
/update <path>
  • rescan a folder index by path (if path is omitted, all folder indexes are rescanned).
/reindex [path]
/rebuild [path]
  • Reindex path (if path is omitted, all indexes are rebuilt).
/quit
/exit
  • Exit Everything.
/close
  • Close the Everything search window.
/closeall
  • Close all Everything search windows.
/help
  • Show Everything Help.
/config_save [filename]
  • Export all settings
/config_load [filename]
  • Import settings
/monitor_pause
  • Stop monitoring changes to indexes.
    Changes to folder indexes will be missed.
/monitor_resume
  • Resume monitoring changes to indexes.
/ini_option <value>, /ini_option=<value>
  • Set the ini_option, ini_option can be any ini key name.
/ini_option
  • Display the current setting for ini_option in the status bar.
For example:
To enable menu_folders without exiting Everything, changing the Everything.ini and restarting Everything, type in the following search and press Enter:
/menu_folders 1

Notes: changing certain ini options requires a restart.

TODO:
/script lua script ...
Stamimail
Posts: 1122
Joined: Sat Aug 31, 2013 9:05 pm

Re: / search commands

Post by Stamimail »

1. You gave an example of "menu_folders". I couldn't find it in ini_option help.
2. Why wouldn't it better to equalize the syntax to what is in INI:
/menu_folders=1
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

1. You gave an example of "menu_folders". I couldn't find it in ini_option help.
The ini page needs updating, I'm working on it for the final Everything 1.4 release.
2. Why wouldn't it better to equalize the syntax to what is in INI:
/menu_folders=1
Everything uses the standard console input:
/command parameters

I've added support for /command=parameters for the next release, thanks.
froggie
Posts: 300
Joined: Wed Jun 12, 2013 10:43 pm

Re: / search commands

Post by froggie »

If I understand correctly

Code: Select all

/ini_option <value>

    ini_option can be any ini key name.
is persistent (it updates the ini file)

How about adding "/ini_option ? " to display the current value of ini_option

How about putting the ini file in the same order as the ini page, with occasional comments in the file that match the ones in the page
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

The Everything.ini is updated on exit.

I would prefer if users changed these ini options in Everything now, as changing the Everything.ini can be daunting if you don't know how it works.
It's easier to ask a user to enter in the search: /command than to exit Everything, open their Everything.ini, find the ini option, change it, save changes and restart Everything..

What I would like ultimately is a about:config search command that lists all options, so you can see the current settings, default settings and the ability to change settings.

/ini_option ? is a good idea, I'm not sure how I would display this result. Maybe it could be shown in the result list until another search is performed.
Maybe it could be displayed in the status bar for a couple seconds.

I've added about:config to open the Everything.ini for the next beta update for now..
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

Added search commands in 806b:

about:
about:config
about:credits
about:license, about:licence
about:home
about:preferences, about:options
/debug, /console
/debug_log
/rebuild
/update <path>
/ini_option=<value>
/ini_option
therube
Posts: 4883
Joined: Thu Sep 03, 2009 6:48 pm

Re: / search commands

Post by therube »

Hmm.

/ conflicts with Options | Search -> Replace forward slashes with backslashes.

I'll take the latter any day over / search.

Option to disable /?
Maybe something like an /exit strategy
BTW, /exit strategy exits rather then searches for \exit strategy ;-).



Maybe an option to use some other character in place of / as the / ?

Was thinking some other illegal filename character, but even with that there could be situations where there could be oddities too, because if you used >, that could conflict with a "›" character (which is legal) that diacritics might pick up on (though that might be a very odd thing to run into?).
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

/ conflicts with Options | Search -> Replace forward slashes with backslashes.
It is a concern of mine too, you can escape these commands with double quotes and they are only activated after pressing enter.
Option to disable /?
Letting the user choose the command character or to disable search commands would probably be the best option.
You might like to use :: or /: or > , I'll add an ini option so you can specify the search command prefix.
that could conflict with a "›" character (which is legal) that diacritics might pick up on (though that might be a very odd thing to run into?).
It's possible, unlikely, but possible.
It could be escaped with double quotes.
therube
Posts: 4883
Joined: Thu Sep 03, 2009 6:48 pm

Re: / search commands

Post by therube »

Oh, ">" could be potentially a problem too, because > is also used as greater then.

dm:>yesterday


(I wonder what the difference is between dm:today & dm>yesterday ?
Oh, files, generally purposely, dated sometime into the future.
dm:gt:tomorrow. Some funny constructs one can come up with.
And yes, some of this you'd be pushing things to actually run into a problem, but...)
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

dm:>yesterday
This would be fine, search commands must start with the search command prefix.
dm:>quit (+enter would search for dm:>quit, and find nothing)
>quit (+enter would quit)
froggie
Posts: 300
Joined: Wed Jun 12, 2013 10:43 pm

Re: / search commands

Post by froggie »

Nits:
To use search commands, enter in one of the following commands in the search box:
When you do the help for this It might be better as ".........enter in one of the following in the search box and then press ENTER", since enter is not usually used on the Everything command line.

Any About:.... command followed by a space does not work.


How about About:About to list all the About: & / search commands
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

Thanks for the nit picking.
When you do the help for this It might be better as ".........enter in one of the following in the search box and then press ENTER"
Changed from:
To use search commands, enter in one of the following commands in the search box
to:
To use search commands, type in one of the following commands in the search box and press ENTER:
Any About:.... command followed by a space does not work.
This is by design, commands must be entered exactly as they appear.
I'll consider eating about: even if there is no valid command.
How about About:About to list all the About: & / search commands
about:about is on my TODO list, I might open a voidtools support wiki page for now.
It will eventually be added as a help window similar to help -> search syntax, or possibly in the result window. I'm trying to avoid adding any text now as I've finalized the localization for Everything 1.4.

I'll improve these search commands more in Everything 1.5, for now I just want a simple way for users to change ini-settings in Everything.
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

The search command prefix / can now be changed in Everything 808b or later with the ini option: search_command_prefix

For example, to change the search_command_prefix to >
  • Type in the following search and press ENTER:
    /search_command_prefix=>
NotNull
Posts: 5416
Joined: Wed May 24, 2017 9:22 pm

Re: / search commands

Post by NotNull »

/monitor_pause
  • Pauses scanning for index updates
/monitor_resume
  • Resumes scanning for index updates

Regarding
/update <path>
/reindex [path]
/rebuild [path]

Testing with local NTFS volume C:, local NTFS volume T: (RAMdisk) and mapped network share M:
  • For folder indexing, only /update M:\ will update it; /reindex M:\ and /rebuild M:\ seem to have no effect.
  • For NTFS indexing, /reindex C:\ and /rebuild C:\ will have effect; /update C:\ has no effect
  • Not entirely sure, but it looks like - based on my interpretation of the debug logging - that none of these 3 variations (/reindex t:\ , etc) cause the T:-volume to be re-indexed.

therube wrote: Wed Nov 16, 2016 12:29 pm / conflicts with Options | Search -> Replace forward slashes with backslashes.
Workaround: start your search with a space ( /commands have to start with a / in the search bar):

Code: Select all

_/windows/
( _ is a space)
void
Developer
Posts: 16446
Joined: Fri Oct 16, 2009 11:31 pm

Re: / search commands

Post by void »

I've updated the documentation, thanks.

/update is for folder indexes only. It will schedule a rescan that should occur immediately.

/rebuild and /reindex are identical.
They will mark the specified index (any index) as out of date and perform a quick rebuild.
Any indexes marked as out of date will be rescanned.
If no index is specified, a complete rebuild is performed (same as deleting your Everything.db)
Post Reply