jump in the file list

[nice_guy]

Problem:
In a file list with 5000 files I want to jump to the first file in the list that contains "1234" in the name.
And so on ... second file with "1234" ...

How to do?

[void]

Typing in the result list will jump to the file.

Make sure the result list has focus and type in: 1234

The jump to text is shown in the status bar.
The jump to text is cleared after 3 seconds.

After the jump to text is cleared, typing in 1234 again will jump to the next file starting with 1234.


To find files starting with 1234, search for:
startwith:1234
-or-
regex:^1234

[nice_guy]

"Typing in the result list will jump to the file."

No, not here.
No jump

"After the jump to text is cleared, typing in 1234 again will jump to the next file starting with 1234."

File name is not starting with 1234.
1234 is anywhere in the filename, at different places

Everything should move to the next file in the result list by pressing a key

[NotNull]

You can simply add 1234 to your search, like

*.txt 1234

that will find all txt files with 1234 in their name

You can browse through the list of found files using the Up/Down keys.

[therube]

It would be really nice to have (Vim-like) regex: in the file list.
Such that /1234 would go to the next 1234 - beginning or not.

1234, alone, taking you to ^1234 is fine, but /1234 to find 1234 anywhere in the name, or 1234$ to fine a name ending in 1234...
Then a (Vim-like) 'n' (or 'N') to take you to the 'n'ext, previous, occurrence (or F3, next, Shift+F3, previous).


Similarly a way to 'm'ark a spot in the list, such that you can easily jump back to that spot.
You're down at "line" 2100 of 5000 in your list, you mark that "a", 'ma', you errantly <sp> hit the Home key, so you're at line 1, you hit 'a (jump to the 'a' mark) & you're back at line 2100. (And you can mark multiple area, a-z... & jump to any of them...)


(You won't believe how many times I working in a long list of files, errantly <sp> hit a wrong key & up in lala land, then have to try to figure out where I was, & make my way back to it .)

[therube]

You can simply add 1234 to your search

But you don't want to change or filter your search itself.

You only want to be able to easily search within your results list.

[nice_guy]

You can simply add 1234 to your search, like

*.txt 1234

that will find all txt files with 1234 in their name

You can browse through the list of found files using the Up/Down keys.

No, that direction was not my point.

[NotNull]

But you don't want to change or filter your search itself.
You only want to be able to easily search within your results list.

Could you give an example when and how you search through the result list?
When I search, all my desired results show up on 'Page 1'.
Am I doing something wrong/inefficient here?

[therube]

You have a broad search, train.
You do not want anything more refined at that point, just train.

You're presented with a list of 50,000 hits.
red trains, blue trains, the little train that could...

You're sorted, alpha or otherwise, perhaps by size...

You're at the top of your list, 'a little train that can'.
You know that you have another similarly named file in there, 'should i delete this or not - a little train that can'.
You don't want to open a new search window, you don't want to lose you're current position in the results list.

You type in, /a little train that can, & Everything, being that train, jumps down to, 'should i delete this or not - a little train that can'.
You hit the Del key & delete it.
You hit the n (next) key, & you've now found in your results list, 'read-along story book, a little train that can'.
You hit F2, & change the file name to, 'read-along story book, the little train that could'.

You hit '' (that's two of "those" marks") & you're returned back towards the top where you started from 'a little that can'.
(Or had you, 'ma' [marked, 'a'], a 'a [return to 'a'] would return you back to that marked spot.)


IOW, it brings a FAYT feature to the results list.

[NotNull]

Thanks for explaining, therube.
Although I meant how people use this currently, I got your point.

Turns out I do use it differently: I typically search for a (1 or 2) file / folder. Either that or all files/folders that (don't) match a very specific pattern.

[therube]

(Would just like to bump this.)

Say you've got a list of files (& this is rather small as it is, & there is not an overflow [in the name, in particular, which I may often have]) & say you have a general search, & you want it to be general, "backr":

And you do not want to filter the search any further (for whatever reason), you simply want "backr".
So you have your list of results.
Given the the majority of results start with "backr", & we're sorted alpha, & say you want one of them,
you type: 'backr'
& you're taken to the first backr. And that's fine, you're in the neighborhood.
Now, at this point, you're kind of stuck.
Say you wanted the file name that contained "brice" in it. Well that is quite a ways down the list.
And again, you don't want to filter (the search) any further, so you scroll down... until you (perhaps) catch the letters "b r i c e", & you're like oh, that's what I need.
Suppose instead, you type:
backr/brice
The / here (taken from Salamander syntax) is a wildcard, akin to .*, so within the results list you are now searching for:
"b a c k r .* b r i c e"
& with that, you're presented with (i guess better said, cursor position is moved to) "BackR-Cover-AEBrice.doc".
(You do see that when you peruse the list, no?).
Now that you're there, you realize that while you are where you expect, what you found is not what you wanted.
So you press the <down-arrow> (in Salamander speak, or 'n' in VIM speak, or F3 in editor speak) & you are then presented with:
"BackR-Exec-AEBrice.doc"
& you say, ah, that's what I want. & you double-click it & it opens.
(Actually, you system presents you with a dialog that says, Which application do you want to open .doc with? [cause you don't have word ])

So we're done with "brice" & we want "herbert":
"backr/rfi/13/herbert"
Very quickly (faster then perusing that list, no?), you have "BackR-Fax-RFI-13-Conduits-Over-36RCP-Herbert-2.doc".
And if that's not the right one, <down-arrow>, & you hit, "BackR-Fax-RFI-13-Conduits-Over-36RCP-Herbert.doc", & with that, you smile.
(Note that that <down-arrow> took you to the next "backr/rfi/13/herbert", rather then [necessarily] then next sequential file.)

Again, I want my basic search "backr".
I do not want to filter it any further.
But being able to search within the results list itself (more so then simply the starting number of characters), would be of benefit, IMO.
(And you ask, how do I work around? In most cases, I open a new search window, type in "backr", then filter it to "backr herbert".
While that works, not as efficient, particularly.)
.
.

Everything FAYT.png (72.63 KiB) Viewed 21878 times

[void]

Thanks for the backr/brice suggestion therube,

I have put this on my TODO list.

I also have on my TODO list to add a Find dialog (Find text within the current results).

[void]

Everything 1.5.0.1322a adds support for "Quick Find".

To quickly find text in the results:

• In Everything, in the result list, press /
  ---/ is shown as the jump to text in the status bar---
• Continue typing in the text to find.
  ---/text is shown as the jump to text in the status bar---
  (Type quickly as the jump to text will time-out after 1 second)
• Everything will jump to the first file containing the typed in text.

Everything will treat / as a * wildcard card.
* and ? wildcards are also supported.



jump_to_forward_slash_action

[harryray2]

Is there a way to highlight all results or maybe a 'jump to next result' ?

[void]

No, that is planned for the Edit -> Find functionality.

"Quick Find" is just a quick way to jump to the first file containing...

[tuska]

2void
Thanks for this new function!

Everything 1.5.0.1322a adds support for "Quick Find".

To quickly find text in the results:

• In Everything, in the result list, press /
• Type in the text to find.
• Everything will jump to the first file containing the typed in text.

Unfortunately, it doesn't work for me at the moment:

1. Everything.ini -> jump_to_forward_slash_action=1 (default) <= This entry exists | Everything 1.5.0.1323a (x64)
2. Windows 11 Pro (x64) Version 22H2 (OS build 22621.674)
3. I have tried to check all shortcuts to see if / is already defined - no occurrence.
4. When I press the slash key / in the search result (focus in the search result), the cursor moves down one line.
   and in the status line I briefly see the following: (Jump to: /).
5. /jump_to_forward_slash_action=0 <ENTER> does the following for me:
   In the search result, pressing the / key several times changes the focus, i.e.
   / ... Focus on 1st file in the search result
   / ... Focus on 1st folder in search result
   The following is NOT displayed in the status bar: "(Jump to: /)".

On this occasion, I noticed the following (keyboard layout GERMAN), in an OTHER setting:
Tools > Options > Keyboard > Show commands containing: result list ev > Result List | Hot Item | Search in Everything: (ZEHNERTASTATUR) (Global) ... Here you cannot see which key on the numeric keypad was pressed, in this case it was the '*' star key.
(ZEHNERTASTATUR) ... current -> Press a key on the separate numeric keypad (without showing which key was pressed).
However, it is possible to press, for example, the digit 9 on the separate numeric keypad - in this case you get the following:
9 (ZEHNERTASTATUR) (Global). In this case, it is obvious that the digit 9 was pressed.
From this point of view, it is certainly not an urgent problem.


Please check.
Thank you!

[therube]

Working on my end.

1. ditto
2. Win7 x64, 1323a, x86

3. test with a newly created "test" -instance & see if you get different results

4. ditto
- but it does then advance to your (results list search) term, that being whatever you've typed after the /
so, /xyz should find the first instance of "xyz" in a file name in the results list that contains "xyz"
(in my case, "21.09.17 filename xyz".)

5. ditto

[therube]

The issue I see, is that the timeout is too quick (for us slow typer's) .

Does it need to have an automatic timeout, or can it be left "on" indefinitely, cancelled by an ESC (key) [or TAB to the search bar]?
And if "indefinitely", then I'd think an up-arrow / down-arrow, should then be equally doable to take you to the prev/next hit (aside from a Find GUI variety).
And all the while, while still "on", you can change the search as you want.

So while "on" (& in my sorted by Time list of) ...
/ev, takes you to "Everything.exe"
down-arrow, takes you to Everything-15.ini
/1.5 (so that is now actually, /ev/1.5), takes you to Everything-1.5a.db
down-arrow, takes you to Everything-1.5.0.1244a.x86.zip
<backspace> 3 times, so once again were at (solely) /ev
/.chm (so now we're at /ev/.chm), takes you to Everything.chm


Do you think a user would get "stuck" in that mode? Nah!

[therube]

slow typer's ... Does it need to have an automatic timeout, or can it be left "on" indefinitely

OK, so you can essentially do that already.

jump_to_timeout=

Set that to a larger value, say "999999".
(In my case, I set it to my ssn# .)
Doing that, at least temporarily, also gives you a longer period of time before the "Jump to:" (display) times out, giving you a better look at just what is being done.

[tuska]

2therube
Thanks for testing!

I must confess to my shame that I had mistakenly expected a small separate window to open,
where I can enter the search text.

When I use it correctly, everything works perfectly.
So my question has already been answered.

Thank you again.

[harryray2]

Ooohh, yes, increasing the timeout helps a lot. Is there a downside to increasing the timeout?

[void]

Thank you for the feedback,

I am considering a "quick find" bar.

Is there a downside to increasing the timeout?

No, it's easy to clear the timer by pressing up/down or clicking on an item.
The default timeout is 1 second.

[harryray2]

Thanks, a quick find bar sounds good.

[therube]

(As things stand now*...)

Should opening (double-clicking on) a file act as an ESC as far as the (FAYT aka jump) timeout is considered?

(As things stand now*...)

If current action were enhanced, like allow up/down-arrow to find prev/next match, I'd think one would not want it to cancel on open, necessarily.



BTW, this is a really nice feature .

[horst.epp]

slow typer's ... Does it need to have an automatic timeout, or can it be left "on" indefinitely

OK, so you can essentially do that already.

jump_to_timeout=

Set that to a larger value, say "999999".
(In my case, I set it to my ssn# .)
Doing that, at least temporarily, also gives you a longer period of time before the "Jump to:" (display) times out, giving you a better look at just what is being done.

The default was almost unusable for me
but with a timeout of 3000 its perfect

[void]

Thank you for the feedback.

Should opening (double-clicking on) a file act as an ESC as far as the (FAYT aka jump) timeout is considered?

Currently, Everything will clear the jump to text when you click on a result.
Are you looking for an option to not clear the jump to text?

If current action were enhanced, like allow up/down-arrow to find prev/next match, I'd think one would not want it to cancel on open, necessarily.

Quick find is designed to find the first item only (no next/prev)
I will consider a find next/prev option for quick find.
Thank you for the suggestion.

Finding the next/prev item will be supported in with the find bar which is in development.

[andymbody]

FYI... @nice_guy

I created a simple AHK tool that can be used with this quick-find feature (until void implements the 'find' functionality). You can specify the text to find and the script will send the request for you quickly without the need to manually type / + keys each time.

Setting the quick-find timeout does not eliminate the need to retype your / +keys request for each jump to the next item. And if the timeout is too long, you must use an extra keystroke to reset the quick-find for your next request. Using the AHK tool, you can set the timeout to minimal value (it won't matter). Using the tool, you can press a single custom hotkey which will clear the previous quick-find request and send it again to find the next match. This can be done as fast as you want.

Currently, the tool is at a very simplified stage, but could be modified to include other functionality such as...
* Storing commonly requested strings and assign hotkeys for each type of request
* it may even be able to be modified to simulate the "marks" that you mentioned

The tool could be used as an exe or script (for modification purposes).

Let me know if this tool would interest you...
Andy

[therube]

I created a simple AHK tool

Post the code?

[andymbody]

Post the code?

As requested...
This is a no-frills version. But features can be added or adjusted as desired. I may make a couple minor improvements myself if there is interest in the tool. Currently it is a limited temp solution for the request made by this thread. Once @void adds the find function to EverythingApp, it will be obsolete.

To use:
1. Set jump_to_timeout to 500 or less. Do this by typing /jump_to_timeout=500 within search bar of Everything.
2. Request your main search query within EverythingApp.
3. !! Make sure that the results-list has focus (tab to it or click top item in the list) !!
4. Run this script
5. Type in the phrase you would like to find within the results-list. The focus will jump to the EverythingApp and find first match.

Current Hotkeys (change as desired).
Ctrl+n - finds next match in the list from top to bottom
Ctrl+j - reactivates this app window so you can type in a new phrase as desired.
Escape - exits this app (be careful, or change this to something else like ctrl+q or ctrl+esc)

In it's current limited state, it will not move to previous match or jump around using any type of "mark". This would require more code to "simulate". The code is below, which requires the latest AHK to be installed on your system. If anyone would like the .exe instead, let me know.

I have only tested this on my system, so let me know if you see issues. FYI... I was able to get wildcards to work with this tool, but not the following type of expressions.

To find files starting with 1234, search for:
startwith:1234
-or-
regex:^1234

Enjoy!
Andy

Code: Select all

#Persistent
#NoEnv
SetWorkingDir %A_ScriptDir%
#SingleInstance Force
SetTitleMatchMode 2		; allows partial title matches
SetBatchLines -1

;#########################################################################################################################
global ThisApp, EditVal
global gTargetWinTitle := "Everything (1.5a)"

;#########################################################################################################################
; build/show this app window
Gui, +hWndThisApp
Gui Font, s9, Segoe UI
Gui Add, Edit, x96 y24 w196 h21 vEditVal ;gEditValue 
Gui Add, Text, x16 y24 w69 h23 +0x200, Search For:
Gui Add, Button, x16 y65 w80 h23 gJumpNext, &JumpNext
Gui Add, Button, x214 y65 w80 h23 gGuiClose, &Quit
Gui Show, w315 h100, ET Jump
return

;#########################################################################################################################
; CHANGE THESE HOTKEYS AS DESIRED

$^n::	; Ctrl+n	- jump to next match
	jumpNext()
	return

$^j::	; Ctrl+j	- show/activate this app window
	showJumpApp()
	return
	
;#########################################################################################################################
GuiEscape:
GuiClose:
    ExitApp

;#########################################################################################################################
JumpNext(CtrlHwnd := "", GuiEvent := "", EventInfo := "", ErrLevel := "")
{
; jumps to next match within EverythingApp results-list (if it has focus)

	static targ_hWnd
	
	; update variable for edit control
	Gui, Submit, NoHide

	; get window handle of target app (EverythingApp), as required
	; use hwnd for return calls, so we can be consistant about which window we target
	if (targ_hWnd=="")
	{
		; get win handle of target app (EverythingApp)
		WinGet, targ_hWnd, ID, % gTargetWinTitle	
	}
	
	; if target window is not loaded, exit
	if (targ_hWnd=="")
	{
		MsgBox % "The everything app window is not loaded!`nPlease open the app window and make sure that the result-list has mouse focus."
		Send, ^n	; pass trigger key to rest of system
		return
	}
	
	; target window is loaded, activate it as required
	WinActivate, % "ahk_id" targ_hWnd

	; **** NOTE - this does not make sure that the results-list has control - the user should do this manually !! ***
	
	; send search phrase to EverythingApp (hopefully to results-list control - SysListView321)
	Gui, Submit, NoHide
	Send, %EditVal%
	return
}
;#########################################################################################################################
showJumpApp()
{
; show/activate this app window

;       WinActivate, % "ahk_id" ThisApp		; alternate method
	Gui, show
	return
}

[void]

Everything 1.5.0.1332a adds a Findbar.

Quick find should behave exactly the same as before, except the quick find text is shown in the findbar.
The quick findbar will auto hide after 5 seconds.