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

Find file dialog should have its own "Content" history #2144

Closed
mc-butler opened this issue Apr 15, 2010 · 2 comments
Closed

Find file dialog should have its own "Content" history #2144

mc-butler opened this issue Apr 15, 2010 · 2 comments
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress ver: 4.7.1 Reproducible in version 4.7.1
Milestone

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/2144
Reporter alex_sh (@ashaduri)
Keywords find, file, content

One of the things annoys me the most in mc 4.7 (after upgrading from 4.6.x) is that the Find File dialog always pre-fills the "Content:" field with whatever I was searching for in the editor or the viewer.

The thing is, 99.9% of the time I use the Find File dialog to search for file patterns, not the content in them. So now, each time I open the dialog, I have to remember to manually go to that field and clear it, which really gets in a way of the workflow. IMHO, this is usability regression.

So please, make that history separate. Or, if you want to have a single history, at least make the default value of that field an empty string, with whatever I may have searched in the editor/viewer simply accessible in the dropdown menu.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Apr 15, 2010 at 12:49 UTC

  • Status changed from new to closed
  • Resolution set to duplicate

Replying to alex_sh (#2144):

So please, make that history separate.

Sorry, but no.

Or, if you want to have a single history, at least make the default value of that field an empty string,

It's a duplicate of #2046.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Feb 21, 2025 at 7:32 UTC (comment 2)

  • Branch state set to no branch

Closed as duplicate of #2046.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress ver: 4.7.1 Reproducible in version 4.7.1
Development

No branches or pull requests

1 participant