I've gotten a request from a user to deal with the tcsh/bash/zsh hack SHLVL:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500703 As said there, I'm not in favor of this feature, but people want to use it to keep track of subshells, or change behavior based on them. It came up that since trying to figure out how many shells have been started before the time you open your terminal window (console, ssh session...) is the problem, a terminal emulator could get around the problem (or the symptom, depending on how you look at it) by resetting SHLVL to 0. What do people think? I don't like it, since neither my /bin/sh nor my login shell use SHLVL at all, and this might encourage people to use it (and then complain loudly when they find themselves on another system). And then I have to explain why our /usr/bin/urxvtcd is different from the script suggested in the documentation. However, a general mechanism for having urxvt set environment variables before launching the shell/command (without resorting to -e env ...) might make everyone happy. Is this desirable, or just more kludging? I'd like to have a FAQ that says "you have to set this" but not "you have to write your own wrapper script". -- things change. [EMAIL PROTECTED] _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
