Please make find dialog case-sensitive

Thanks for the report.

What version of the mc package do you have installed? What version of Ubuntu are you running? Have you always had this problem?

I can confirm this issue on latest Dapper, mc 1:4.6.1-1ubuntu2. When trying to find a file using 'Command | Find file', the search is always case sensitive regardless of whether 'case Sensitive' is checked or not.

Yes, I always had this problem. I am running Ubuntu 6.06 Dapper Drake Flight CD 6 with current upgrades. Midnight Commander from Fedora Core 5 is working well (on Fedora host; on Ubuntu i did not test it) and has beautifull patch for disk free usage, UTF-8 ofcourse too.

OK, does the Fedora package have the same issue as the Ubuntu package? What version is the Fedora package?

I think there are: http://mirror.linux.duke.edu/pub/fedora/linux/core/5/x86_64/os/Fedora/RPMS/mc-4.6.1a-10.x86_64.rpm and http://mirror.linux.duke.edu/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/mc-4.6.1a-10.i386.rpm and http://mirror.linux.duke.edu/pub/fedora/linux/core/5/source/SRPMS/mc-4.6.1a-10.src.rpm. You can try it on Ubuntu and send report.

This issue is reported as fixed upstream:

https://savannah.gnu.org/bugs/?func=detailitem&item_id=5452

But, more interestingly:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351562

Apparently, this is the intended behaviour.

Very interesting, thanx for post. And beautifull patch for disk free usage will be insert too?

Ho, hooo "Case insesitive option in find dialog is broken" is broken in Fedora too. Excuse, i make mystake above, really do not working well on Fedora Core 5.

Upstream bug about that: https://savannah.gnu.org/bugs/?18977

Still broken in feisty and gutsy.

apparently this is the intended behaviour of the case sensitive option - in that, it refers specifically to the 'content' field and not to the file name. Personally i find this confusing - at the very least, the option should make it clear that it refers to the content field only.
However, from the debian and savannah discussions, it seems as if the developers do not intend to change this behaviour, regarding it as a feature, not a bug.

Should we therefore close this bug?

Seems the bug have been fixed in intrepid or hardy release. I can't reproduce.