In /etc/profile.d/tcsh-settings, there are two things that extremely annoy me. One is "set correct=all", which makes tcsh to correct file names as well. E.g. $ ./myexec > out1 is ok, but $ ./myexec > out2 pops up a suggesting to replace out2 with out1. If user is not cautios enough, he will accept the suggestion resulting in out1 overwritten. I strongly suggest to replace the setting with "set correct=cmd". Another one is "set complete=enhance". With its case mangling etc everything becomes confusing. While we're at that, I'd suggest the following additions to navigate the relevant history entries only: bindkey -k up history-search-backward bindkey -k down history-search-forward bindkey " " magic-space Reproducible: Always Steps to Reproduce:
I suggest using ~/.tcshrc for now to get over your annoyances! all in all your suggestions are a little more gentoo-like than the settings we currently have as default for tcsh-settings... I don't want to push through these changes though as the tcshrc.sourceforge.net "enhancements" are used as the basis for our settings... i'll talk to some other heavy tcsh users and see what they have to say about this. until then, ~/.tcshrc :)
As a heavy tcsh user, I agree with Evgeny. Multiple times in the past, I've had to add to my (already significant) .tcshrc to override some new Gentoo (or other distro) setting. It's as annoying as any other application or system that thinks it knows better than me what "improvements" should go on. Can I also suggest removing, or at least making less intrusive, some global behaviour which *cannot* be overridden in ~/.tcshrc? I'm "manually" maintaining the global csh.cshrc for now to avoid a forced ~/.tcsh.config file; also, in tcsh-settings, the following: alias cwdcmd 'echo "Directory: $cwd"' Results in noise upon login you can't get rid of using ~/.tcshrc (although you can get rid of it after that). In general, I think there's a lot of "advanced" options getting set that novices won't notice, and that power users (a) can find on their own, and (b) find annoying when sprung on them unexpectedly.
<Currently in tcsh-bindkeys...> # PAGE UP : search in history backwards for line beginning as current. bindkey ^[[5~ history-search-backward # PAGE DOWN : search in history forwards for line beginning as current. bindkey ^[[6~ history-search-forward </tcsh-bindkeys> magic-space i'm not so sure about... Why is this important? I have commented out "set complete=enhance" and changed "set correct=all" to "set correct=cmd" as those make sense to me. Any other comments before I commit? Please be specific.
Hmm, why to use esc sequences instead of well-understood key names? Regarding magic-space: when space added to a command being typed, it switches the history search to the subset of previous commands beginning with the text of the current one. Extremely convenient. See also my comments on http://bugs.gentoo.org/show_bug.cgi?id=47059. Regards, Evgeny
One more suggestion. limit coredumpsize 0 I believe this is what a vast majority of users need. "core"s littering $HOME are annoying. Especially when $HOME is NFS-mounted (i.e. relatively slow) and with quotas enabled. When such mastodonts as mozilla crash, one has to wait a lot of time until the bestia completes its 50-MB coredumping process.
Argh, another annoyance from the current tcsh-settings: set fignore=(.o \~ .bck) It indeed might be wise to skip object files from the completion list when invoking e.g. `vi', but not in general!!
I have added the coredumpsize entry commented out in the tcsh-settings file. I like the idea but I don't think it is something we want turned on by default. I have added the magic-space line commented out in the tcsh-bindkeys. And lastly I commented out the set fignore line.
Guys, not sure why this bug is mine but I don't use tcsh. People working on OOo should know this thing better than me.
please put a patch together as I'm not really a tcsh user. If anyone can answer bug 91725 and include a solution in your patch I'd appreciate it. Please reopen when patch attached.
