The file: /etc/csh.env sets: setenv PAGER '/usr/bin/less' so that the search in less is case insensitive. This can be annoying when the command names in man pages have capital or mixed case letters. Unsetting "PAGER" fixes the problem, as well as using "less -i". Please make either of these changes.
Of course I meant that "less" is currently being case sensitive. Being case insensitive is preferred.
The case insensitivity of less isn't dictated by the PAGER environment variable, but you can set it in the LESS environment variable if you use LESS as the pager. There are reasons why you shouldn't assume case insensitivity. Historically, the programs "mail" and "Mail" are often different, and on systems where both are installed, may even have different man pages. Similar for "head" and "HEAD" which are very different programs, and makefile/Makefile, and finally .z (pack) and .Z (compress) extensions. Linux is not Windows, and should not try to adjust to the case insensitive world of Windows users. If man pages list a command with the wrong case, that should be fixed in the man page. That said, I agree that it's wrong to set PAGER (and VISUAL and EDITOR, for that matter) in a global env file. They do have default fallbacks, and users who don't agree with the defaults can set the variables to whatever they like. In your case, if you want less to be case sensitive, add "setenv LESS '-i'" to your ~/.cshrc (or add it to the LESS setting in /etc/csh.env)
The setting of PAGER or LESS, or whatever from csh.env is not a tcsh-specific problem, the same happens for any shell that reads the environment settings from portage. Editting csh.env is a bad thing, it is generated. csh.env is sourced early in the process, only for login shells, meaning their settings can be overridden by any configuration lateron without a problem. They /are/ defaults/fallbacks. I believe the solution to your problem is to either unsetenv PAGER in your .tcshrc or set LESS env variable accordingly to get the behaviour you want.
