"This bash shell is now fully operational!"

[glyf]

For many years, I have been a fan of the Z shell. In particular, I loved its programmable completion and many hookable interactive events.

As the years have gone by, however, Bash has slowly re-taken the ground that ZSH originally claimed. Programmable completion, ever more elaborate prompts, and so on became as commonplace in bash configurations

Comments

[jes5199]

This is extremely cool. Thanks. (Now I have my GNU SCREEN title and my XTERM title set together using readable commands, rather than using screen's terribly conceived auto-titles)

[glyf]

Glad you enjoyed it. Spread the word! I have been looking for a way to do this in bash for years, and others looking for a similar hack will likely have a hard time finding it from google... (how did you run across it, anyway?)

[jes5199]

I googled for preexec() bash
because I had seen the zsh preexec example in the Screen infodocs, and I didn't see any good reason why that hadn't been ported to bash. I was about to install the patch when I found your post.

[rawy]

Cool news cool ideas! and cool you also

Awesome

[georgiajosh]

Thanks this is an awesome find, I never would have found this out on my own, Congrats on the discovery.
Thanks for the post.

Josh King Atlanta Center for Cosmetic Dentistry

Re: Awesome

[glyf]

Hi there,

I am going to go out on a limb here and assume your post is legit, but I almost deleted it as spam; you tripped almost every one of my triggers. Just some pointers for next time, your post looks like spam because:

• it's short
• it doesn't mention the content of the article specifically
• it includes a hyperlink to a completely unrelated commercial site

Question about preexec.bash

[lmjog]

Thanks for a great hack to bash!

I've tried to use the precmd & preexec functions used at the bottom of your script, but it seems that I need to setup the variables $SCREEN_RUN_HOST and $SCREEN_HOST somewhere in my .bashrc to get it work correctly.

Could you please share what how you set up those?

TIA
/LM

Re: Question about preexec.bash

[glyf]

Oh. That's unfortunate. Those variables are part of some pretty gratuitous hacks in my overall setup; I'll try to correct this "module" so that it doesn't require them.

Re: Question about preexec.bash

[lmjog]

If possible if you could just share the info on how you set them. I use a setup with a couple of nested screens myself, and if I can read your script correctly, I like the idea how it presents itself.

Re: Question about preexec.bash

[glyf]

Sorry for the long delay; I keep thinking I'll have time to eventually clean everything up and do a real release of my whole config.

In the meanwhile, just do this in your shell startup somewhere:
export SCREEN_HOST=`hostname -s`then in your screenrc,

setenv SCREEN_RUN_HOST $SCREEN_HOST
setenv SCREEN_RUN_USER $USER

# Many sshd configurations accept "LC_*" environment variables. Take advantage
# of that to sneak our environment variables over there.
setenv LC_SCREEN_RUN_HOST $SCREEN_HOST
setenv LC_SCREEN_RUN_USER $USER

very very cool!

[corporal_touchy]

no not cool
plain f**king awesome!

this should totally be incorporated into bash by a patch instead of hack

but meanwhile
thanks for the hack! ;)

cool trick with the LC_ vars to shorten the prompts, too!