Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search scope in services (or others) #2287

Open
Dboingue opened this issue Nov 18, 2024 · 1 comment
Open

Search scope in services (or others) #2287

Dboingue opened this issue Nov 18, 2024 · 1 comment

Comments

@Dboingue
Copy link

Dboingue commented Nov 18, 2024

In the ancestor processhacker, I routinely could filter per running process by just enterring "run" or running.

It seems that now the scope of the little search box is a lot more restricted, is that design or oversight? or is there a closed or open issue our it. I made a search and a similar issue but different motivation or specificity of the question is
Allow searching for exact string and/or in certain column #1876
#1876 (comment)

Here I am merely asking for what was there before. If it needs to be more complex, and join that issue, perhaps column hearder could be made target keywords, but I do enjoy the pan column search.. I wonder how it worked, though. Or if I am confused about having see that. Perhaps it had hidden values for small categorical columns, and "running" was dissected. Otherwise now to think of it, it would also have given the service names containing "run*". I hope not (that i dreamt this), but I don,t mind being told so. sorry to barge in then. but otherwise my question or prefernece to get that back stands. Thank you.

@dmex
Copy link
Member

dmex commented Nov 19, 2024

the scope of the little search box is a lot more restricted, i

It should be exactly the same? Can you describe what changed or provide more information?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants