Comments on: Set Your zsh Prompt http://blog.bstpierre.org/zsh-prompt Software Development, version 3.0 Thu, 22 Dec 2011 21:52:32 -0700 hourly 1 http://wordpress.org/?v=3.0.4 By: kiviuq http://blog.bstpierre.org/zsh-prompt/comment-page-1#comment-7599 kiviuq Fri, 05 Mar 2010 15:01:53 +0000 http://blog.bstpierre.org/?p=264#comment-7599 My fault. Actually ambiguities *are* resolved if a is declared local infunction title(). So putting "local" as an identifier in front of the first occurance of a in function title() and you may again use a as a variable in the command line independently from a in titlel(). Sorry about the confusion. To auto detect global declarations in the future one can add setopt warncreateglobal to .zshrc My fault. Actually ambiguities *are* resolved if a is declared local infunction title(). So putting “local” as an identifier in front of the first occurance of a in function title() and you may again use a as a variable in the command line independently from a in titlel(). Sorry about the confusion. To auto detect global declarations in the future one can add

setopt warncreateglobal

to .zshrc

]]> By: kiviuq http://blog.bstpierre.org/zsh-prompt/comment-page-1#comment-7596 kiviuq Fri, 05 Mar 2010 14:35:38 +0000 http://blog.bstpierre.org/?p=264#comment-7596 There's only one problem in that code. When you hapen to use a as variable in the command line it will collide with a defined globally in function title(). Even after turning a into local a you still won't be able to say things like a="x x x// /" .. next line.. echo $a in the console. Any ideas how to fix that besides of renaming a into something less "common" like ZEWTGASDG1233 to avoid potential ambiguities. There’s only one problem in that code. When you hapen to use a as variable in the command line it will collide with a defined globally in function title(). Even after turning a into local a you still won’t be able to say things like a=”x x x// /” .. next line.. echo $a in the console. Any ideas how to fix that besides of renaming a into something less “common” like ZEWTGASDG1233 to avoid potential ambiguities.

]]> By: Justin http://blog.bstpierre.org/zsh-prompt/comment-page-1#comment-7351 Justin Thu, 25 Feb 2010 01:16:32 +0000 http://blog.bstpierre.org/?p=264#comment-7351 I ripped that from somewhere else on the net with comments and all. It was by far the best out of a few. I think it was from http://dotfiles.org/ which is a decent resource for quickly obtaining different solutions to common interactive shell problems. I'm always tempted to make a more flashy $PROMPT with colors and what not, because face it -- you're going to be stuck on busybox at times. It seems like a good idea that custom zsh hosts be easily distinguishable from minimal shells. I still don't do the color prompt though. I ripped that from somewhere else on the net with comments and all. It was by far the best out of a few. I think it was from http://dotfiles.org/ which is a decent resource for quickly obtaining different solutions to common interactive shell problems.

I’m always tempted to make a more flashy $PROMPT with colors and what not, because face it — you’re going to be stuck on busybox at times. It seems like a good idea that custom zsh hosts be easily distinguishable from minimal shells. I still don’t do the color prompt though.

]]>