Source zshrc/bashrc in all open terminals

trap "source ~/.zshrc" USR1
Put this in your zshrc, source it, then run 'pkill -usr1 zsh' to source it in all open terminals. Also works with bash. More info: http://www.reddit.com/r/commandline/comments/12g76v/how_to_automatically_source_zshrc_in_all_open/

5
By: ppaschka
2012-11-03 07:24:03

These Might Interest You

  • alias for editing .bashrc and sourcing it with a quick command, very useful for quickly adding and modifying alias' and functions in bashrc, create lots of alias from commandlinefu very quickly, use nano vim or any other edit if you want, very useful if you have a barcode scanner and you want to run commands quickly with barcodes Show Sample Output


    -19
    alias sbrc="source ~/.bashrc" && alias nbrc="nano ~/.bashrc"
    professoralex · 2009-05-13 02:41:37 5
  • Place the line above in your ~/.bahsrc file. Now every time you issue the 'vb' command, you invoke the vim editor to edit it, then source it so the changes take effect immediately. Notes: * This mechanism is not working well if your .bashrc contains commands that should not be sourced more than once. * This trick also work for your csh or tclsh users: place the following line in your ~/.cshrc file: alias vc 'vim ~/.cshrc; source ~/.cshrc Thank you adzap for pointing out the missing quote


    2
    alias vb='vim ~/.bashrc; source ~/.bashrc'
    haivu · 2009-03-02 21:01:49 4
  • Any changes to BASH shell made in .bashrc will be active in the current terminal window from the moment you execute this command, ie. aliases, prompt settings etc. No need to restart terminal. (In BASH 'source' simile to 'eval' lets you generally execute any bunch of commands stacked in a text file).


    5
    source ~/.bashrc
    knoppix5 · 2012-10-01 08:30:19 0
  • This could be added to .bashrc. Background: Linux usually saves history only on clean exit of shell. If shell ends unclean, history is lost. Also numerous terminals might confuse their history. With this variable set, history is immedeately written, accessible to all other open shells.


    2
    PROMPT_COMMAND="history -a"
    danam · 2009-10-21 12:33:25 0

What Others Think

If you put this only into your local .zshrc, use pkill -u `id -u` if you want to restrict the reloading to the terminals attached to your current user if he owns a unique user ID. You may kill zsh sessions for other users/executions otherwise as USR1 (and USR2) defaults to kill the zsh process. Also beware if you are running X servers started from a zsh as this would not reload this and be killed too on the first try inside X. For me it's: trap "source ~/.zshrc && rehash && echo 'Config OK'" USR1 alias re="pkill -u `id -u` -USR1 zsh"
Testuser_01 · 293 weeks and 2 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: