If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
I can't find a file I need, and when I search for "job", windows includes every freaking file in ever freaking DIRECTORY which has those three letters in them. forty eleven Cat pictures - because they are in the directory Jobby! something having to do with the flowers because the directory contains "jobola" How, or is it even possible, to get Windows to just search for "job" in filenames. This is one more thing which Windows 7 does, which I do not recall Win XP not doing. tschus pyotr Yes, I'm furious, I'm out of time and the presentation is not going to happen. -- pyotr filipivich The question was asked: "Is Hindsight overrated?" In retrospect, it appears to be. |
Ads |
#2
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_names?
On 05/02/2018 11:04 AM, pyotr filipivich wrote:
I can't find a file I need, and when I search for "job", windows includes every freaking file in ever freaking DIRECTORY which has those three letters in them. forty eleven Cat pictures - because they are in the directory Jobby! something having to do with the flowers because the directory contains "jobola" How, or is it even possible, to get Windows to just search for "job" in filenames. This is one more thing which Windows 7 does, which I do not recall Win XP not doing. tschus pyotr Yes, I'm furious, I'm out of time and the presentation is not going to happen. Install Everything.exe then under search menu tick Whole word, See if that works. Rene |
#3
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote:
I can't find a file I need, and when I search for "job", windows includes every freaking file in ever freaking DIRECTORY which has those three letters in them. forty eleven Cat pictures - because they are in the directory Jobby! something having to do with the flowers because the directory contains "jobola" How, or is it even possible, to get Windows to just search for "job" in filenames. This is one more thing which Windows 7 does, which I do not recall Win XP not doing. tschus pyotr Yes, I'm furious, I'm out of time and the presentation is not going to happen. Double quote the search term. e.g.: "job" Instead of just: job |
#4
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_names?
On 02/05/2018 17:04, pyotr filipivich wrote:
I can't find a file I need, and when I search for "job", windows includes every freaking file in ever freaking DIRECTORY which has those three letters in them. Did you actually include the quotes, and if not what happens if you do? In other words, if you haven't already, try searching for something like "job.*" (including the quotes), not job (without them). |
#5
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
pyotr filipivich wrote:
I can't find a file I need, and when I search for "job", windows includes every freaking file in ever freaking DIRECTORY which has those three letters in them. forty eleven Cat pictures - because they are in the directory Jobby! something having to do with the flowers because the directory contains "jobola" How, or is it even possible, to get Windows to just search for "job" in filenames. AQS (Advanced Query Syntax) for Windows Search is pretty rich but takes a while to learn. In short, to search on only files (aka documents) with "job" somewhere in their name, use: job kind:document You'll notice when type "kind:" that a drop-down list appears of available values of which "document" is one. I'm assuming you are using the searchbox in Windows Explorer. https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx Else, you could use Search Everything but you'll have to learn regex to let you exclude certain characters, like the backslash (which must be escaped by using \\ to differentiate from special characters, like \n for newline and \S for a non-whitespace char), where to anchor the string (if anchored rather than as a substring not at the start or end of the string), etc. Advanced Query Syntax https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx Yes, I'm furious, I'm out of time and the presentation is not going to happen. So you are here to vent instead of getting help? Microsoft doesn't visit any newsgroups (aka Usenet). You're venting to your peers. You don't plan ahead to prepare AND PRACTICE for your presentations? |
#6
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
VanguardLH on Wed, 2 May 2018 13:01:46 -0500 typed in
alt.windows7.general the following: pyotr filipivich wrote: I can't find a file I need, and when I search for "job", windows includes every freaking file in ever freaking DIRECTORY which has those three letters in them. forty eleven Cat pictures - because they are in the directory Jobby! something having to do with the flowers because the directory contains "jobola" How, or is it even possible, to get Windows to just search for "job" in filenames. AQS (Advanced Query Syntax) for Windows Search is pretty rich but takes a while to learn. In short, to search on only files (aka documents) with "job" somewhere in their name, use: job kind:document You'll notice when type "kind:" that a drop-down list appears of available values of which "document" is one. I'm assuming you are using the searchbox in Windows Explorer. Yes. I just found that filename:job does the trick as well. https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx Else, you could use Search Everything but you'll have to learn regex to let you exclude certain characters, like the backslash (which must be escaped by using \\ to differentiate from special characters, like \n for newline and \S for a non-whitespace char), where to anchor the string (if anchored rather than as a substring not at the start or end of the string), etc. Advanced Query Syntax https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx Yes, I'm furious, I'm out of time and the presentation is not going to happen. So you are here to vent instead of getting help? No Microsoft doesn't visit any newsgroups (aka Usenet). You're venting to your peers. You don't plan ahead to prepare AND PRACTICE for your presentations? In this case,the presentation was a simple resume. Yes, I should have sent it to the printers last week, but then I would have been searching for these files last week. And Microsoft would still have been "tagging" everything which has J O B in the title, the directory name, or inside the file itself. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#7
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
pyotr filipivich wrote:
In this case,the presentation was a simple resume. Yes, I should have sent it to the printers last week, but then I would have been searching for these files last week. And Microsoft would still have been "tagging" everything which has J O B in the title, the directory name, or inside the file itself. Agent Ransack https://www.mythicsoft.com/agentransack/ supports "regex" and to find files beginning with job, you'd use ^job If I knew the end of the file name, and I escaped the dot to make it literal, I could do job\.doc$ which says "look for job.doc right at the very end of the file name". If Windows Search supports this sort of thing, it's by approximation and not actual Regex or PCRE. There will be some Windows Search commands that have an equivalent effect to a proper search. One advantage of Agent Ransack, is it's more likely to look everywhere. It cannot look inside "C:\System Volume Information" because that is Access Denied for virtually any tool. Everything.exe can potentially look in there (because it reads the $MFT directly), except Everything.exe will run into trouble when attempting to stat() the contents and get size and date info. It's hard to say whether Everything.exe could list just the file names of the files in there, even though you have no way to look at them. Windows Search does a poor job, because occasionally you don't realize how some Windows permission or attribute has blocked your search attempt. Third-party tools are your friend, in this regard. Even if you choose not to use the third party ones all that often, you should keep them installed for "emergency search tasks" such as this case. Paul |
#8
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote:
How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* -- Stan Brown, Oak Road Systems, Tompkins County, New York, USA http://BrownMath.com/ http://OakRoadSystems.com/ Shikata ga nai... |
#9
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
In message , Stan Brown
writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] 3 -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf If you're playing a killer monster, be very quiet. - Anthony Hopkins, RT 2016/10/22-28 |
#10
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote:
In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. -- Stan Brown, Oak Road Systems, Tompkins County, New York, USA http://BrownMath.com/ http://OakRoadSystems.com/ Shikata ga nai... |
#11
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Thu, 3 May 2018 18:36:00 -0400, Stan Brown
wrote: On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. He seems to want to exclude directory (folder) names, so I think an additional parameter might be required: dir /s /b /a-d search_target -- Char Jackson |
#12
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Stan Brown on Wed, 2 May 2018 22:36:10
-0400 typed in alt.windows7.general the following: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* That's DOS, i.e. the command line. (I have many copies of _cmdprmt.bat scattered all round the place. For just hat reason.) Windows is not DOS. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#13
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
"J. P. Gilliver (John)" on Thu, 3 May 2018
09:50:41 +0100 typed in alt.windows7.general the following: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] I'm sure it was job{something}.3le. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#14
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_names?
On 5/3/2018 6:59 PM, Char Jackson wrote:
On Thu, 3 May 2018 18:36:00 -0400, Stan Brown wrote: On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. He seems to want to exclude directory (folder) names, so I think an additional parameter might be required: dir /s /b /a-d search_target Damn, don't they ever test these search procedures on the "vast wasteland" of non-computer-geeks? -- == Later... Ron C -- |
#15
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
pyotr filipivich wrote:
Stan Brown typed the following: pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* That's DOS, i.e. the command line. (I have many copies of _cmdprmt.bat scattered all round the place. For just hat reason.) Windows is not DOS. 'dir' is an internal DOS-mode command (i.e., internal to the command shell program). You run those in a command shell whether it was back in MS/IBM-DOS days or nowadays inside of Windows (which also has a command shell via cmd.exe). You NEVER ran a machine-coded 'dir' program. It is an internal command defined within the command shell. You do know how to load a command shell in Windows, right? Just run cmd.exe to load a command shell. Then you can run its internal functions, like 'dir', or have it load other programs. Actually, Windows is a DOS. DOS = Disk Operating System. Yep, Windows loads from a disk whether an HDD, SDD, flash drive, or whatever. A change in kernel does not obviate an OS is still a DOS. It is a pity that Gates chose "DOS" for his operating system name, like calling "dog" your pet dog. Maybe he should've stayed with Seattle DOS which he purchased as quick step up to get into producing an OS, and dropped off the "DOS" which was redundant, like saying you have a leek onion. However, what you want is the command *shell* which either calls it internal functions (those within cmd.exe) or a loader of external programs. When you were using MS/IBM-DOS, you were using command.com as the command shell with its command-line parser and interpreter. Nowadays in Windows, yep, you can still use a command shell (cmd.exe). Just because Microsoft changed the shortcut to "Command Prompt" does not alter that the shortcut is loading a command shell. You can use command shells from other sources, too. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|