Solved Yak Shaving Shell Hell

[ccammack]

I have just been reading this thread and am wondering if any of you use multiple shells and have a nice way to share their configurations?

I found this approach but I'm thinking about trying a single a .personal config file sourced at the bottom of .profile and .bashrc and .zshrc and the others, and make that single included file deal with all of the issues that come up:

• syntax differences
• multiple-entry idempotency
• interactive vs. non-interactive
• login vs non-login
• what else?
  

 

[mer]

For me it's simply easier to have separate config files, one for each shell.
Otherwise your single file has a bunch of lines that are similar.
But how do you know which section to source?
You need if/else if/else clauses, but you need a shell agnostic if construct.

 

[cracauer@]

I only use sh and bash. I have sh config files and libraries that are sourced by bash. If it's bash then it sources additional bash-only files.

The same trick doesn't work with zsh.

 

[SirDice]

wondering if any of you use multiple shells and have a nice way to share their configurations?

Shell - Share your .shrc, .kshrc or .mkshrc file segments: Bourne or Korn shell

Share your .shrc and/or .kshrc configuration file(s) or samples. .profile can also be used to set common configurations of Bourne and Korn shells. Samples from this file intended for Bourne and Korn can be shared too. There's not as many posts about use of Bourne shells and variant Korn shells...

forums.freebsd.org

Share your .tcshrc file

I decieded to start this thread after reading the thread 'Which shell do you use?'. I'll start, mine is below. # .cshrc - csh resource script, read at beginning of execution by each shell # # # -- Set up command aliases alias searchports 'find /usr/ports -type f -name pkg-descr | xargs...

forums.freebsd.org

Shell - Share your .zshrc file

I like the way how tcsh works, but it is outdated a little bit (only 1 update since 2012), also some nice features are available in zsh, like suggesting flags and other completions for cli and not only cli apps… But some of its features are distracting and annoying IMHO. I didn't find any...

forums.freebsd.org

 

[ccammack]

You need if/else if/else clauses, but you need a shell agnostic if construct.

Could you clarify this a little more for me? I found that the original Bourne shell didn't have elif, but Almquist does, and test condition syntax is different in different shells, of course, but if i stick to POSIX behavior, what other problems might I run into with if constructs?

 

[mer]

test condition syntax is different in different shells

That's basically what I was talking about.
If you try and have a single file to be sourced by all your different shells, you pretty much have to have different sections, selected by if's or tests.
csh/tcsh setenv wont' work in sh or bash
the way you define aliases in them are different
Back up to #3 by cracauer@ that works because bash can use sh syntax as a least common denominator.

If all the shells you are considering share lineage, you may be able to come close. If you are trying to do it across csh and sh, very hard to do. csh and tcsh, sure because of lineage.