Messages in this thread | | | From | "Robert White" <> | Subject | RE: UTF-8 and case-insensitivity | Date | Tue, 17 Feb 2004 17:03:11 -0800 |
| |
P.S. Given that the GUI libraries (almost invariably) already deal with displaying things in a case insensitive way, the "best place to cut" to add case insensitivity to the user command-line experience would be adding a flag to file name completion in bash. Bash is already doing file name finds and lookups when you press tab; and the user is actively looking at the correctness and singularity/duality of the results.
So the proverbial "vi makef{tab}" would, if the flag was set, show you makefile, Makefile, and MakeFile (etc) as existent or just switch makef to "Makefile" if the name were unique.
It doesn't make lives easier for the API level project programmer people (c.f. samba), but it could uber-happy the incoming newbies, and people like me who have to interoperate within a vast wasteland of directories full of inconsistently named files created by windows programmers (like SOCKET.C, Socket.H, constants.h, and ss_switch.c all in one directory tree with hundreds of their friends. 8-)
I would however, be forced to throttle myself with my own intestine if kernel started doing this magic mapping "for me", especially "in some calls/contexts but not in others". (Not that I want to provide my possible death as a strong motivation for adding the feature. 8-)
Rob.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |