Date: Fri, 10 Feb 2012 09:21:33 -0800 From: Kevin Oberman <kob6558@gmail.com> To: Chuck Burns <break19@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Enhancing the user experience with tcsh Message-ID: <CAN6yY1s%2B4%2BkOUsT_wq91=r5yLqDtmqF0qajhYsd8g-hY4esJ-g@mail.gmail.com> In-Reply-To: <4F354ED1.3060307@gmail.com> References: <CAF6rxgnebQUY8azv8fovQPkB%2BGgsQjaByZ6JwnNWjrM1hB65eQ@mail.gmail.com> <1328887627.38277.68.camel@buffy.york.ac.uk> <CAF6rxgmjQX%2B8hZVdjYBHJfonegavYhY_22gyVszpPvxhAKbvTA@mail.gmail.com> <1328892101.38277.88.camel@buffy.york.ac.uk> <4F354ED1.3060307@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 10, 2012 at 9:07 AM, Chuck Burns <break19@gmail.com> wrote: > On 2/10/2012 10:41 AM, Gavin Atkinson wrote: >> >> On Fri, 2012-02-10 at 11:25 -0500, Eitan Adler wrote: >>> >>> Picking a random email to reply to. >>> >>> My goal with this email is to reduce the amount of "controversial" >>> changes. >> >> I applaud this. =A0I've often considered doing the same but avoided it >> because it was easier than fighting the bikeshed :) >> >>> commit 3ea4ea3a59d14cb060244618dd89d7dd0170bee1 >>> diff --git a/etc/root/dot.cshrc b/etc/root/dot.cshrc >>> --- a/etc/root/dot.cshrc >>> +++ b/etc/root/dot.cshrc >>> @@ -7,9 +7,10 @@ >>> >>> =A0alias h =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0history 25 >>> =A0alias j =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0jobs -l >>> -alias la =A0 =A0 =A0 ls -a >>> +alias la =A0 =A0 =A0 ls -aF >>> =A0alias lf =A0 =A0 =A0 ls -FA >>> -alias ll =A0 =A0 =A0 ls -lA >>> +alias ll =A0 =A0 =A0 ls -lAF >>> +alias ls =A0 =A0 =A0 ls -F >>> >>> Two people didn't like these changes but didn't explain why. This is >>> incredibly helpful, especially for a new user. =A0If you dislike the >>> alias change please explain what bothers you about it? >> >> I don't use the first two aliases, so I don't care about them at all. = =A0I >> do however disagree strongly with changing the default options on such a >> widely used command. >> >> This change is disruptive, and it can affect use of ls(1) in scripts. >> For example, it even sticks the extra characters in the output of >> "ls -1" (the number 1), which is specifically designed to be used when >> piping the output elsewhere. =A0Please do not break this. =A0It is also >> distracting - If I want to see what type of file a particular entry is, >> why not just run "ls -l"? >> >> It's like the tendency some Linux distributions have of >> "alias mv mv -i", although that can at least be overridden on the >> command line with "-f". =A0The "ls -F" change cannot be overridden witho= ut >> unaliasing. >> >>> =A0if ($?prompt) then >>> =A0 =A0 =A0 =A0# An interactive shell -- set some stuff up >>> - =A0 =A0 =A0 set prompt =3D "`/bin/hostname -s`# " >>> + =A0 =A0 =A0 set prompt =3D "[%n@%m]%c04%# " >>> + =A0 =A0 =A0 set promptchars =3D "%#" >>> >>> Many people had alternative suggestions for the prompt. Can you please >>> clarify why you believe your prompt should be the _default_ one? >> >> I can't comment as I didn't say my suggestion should be default - but >> for me the above isn't a bad choice. =A0I would however prefer: >> set prompt =3D "%n@%m:%c04 %# " >> and not >> set prompt =3D "[%n@%m]%c04%# " >> >> as that then gives you user@host:path in exactly the same format as you >> need to use with scp, etc. >> >> >>>> I use the $HOME/bin on my machines but I am not so sure to make this a >>>> general thing. >>> >>> Many people expect it, and given that it is the last item in the path >>> it won't affect all that much. >> >> It's been in there forever. =A0I think this should stay, it would just b= e >> too disruptive otherwise. >> >> > My $0.02 > > Instead of using -F to denote filetypes, why not use colors? -G -- it > shouldnt affect scripts at all, yet still provide the same sort of feedba= ck. > (Tho, I personally use csh's built-in "ls-F" instead of "ls", and actuall= y > tend to alias it to ls as well.) > > Just a thought. > > I do, however, like most of the other changes. Here's my stamp. "Approved= " > :) I want mine green with yellow trim. That said, if you really want to look at massive .tcshrc setup, look at shells/tcshrc. It's woefully out of date and the latest version upstream has a lot more cool stuff, but it takes a lot of hacking since it's written for Linux. (I still need to fix auto-complete for route(8).) It's really got all of the bells and whistles , but I don't think it's for everyone and I certainly tend to heavily modify my own. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1s%2B4%2BkOUsT_wq91=r5yLqDtmqF0qajhYsd8g-hY4esJ-g>