Default .bashrc not used on Manjaro Linux
See original GitHub issueVersion: 1.0.172 Platform: Linux x64 5.15.21-1-MANJARO Plugins: none Frontend: xterm
Hi,
I use Tabby on my MacBook Air M1 at home and on a Manjaro Linux at work.
I noticed that using “bash” as default terminal on Mac it loads the .profile
file but on Linux it ignore the .bashrc
configuration. I need to manually execute source ~/.bashrc
to use my configuration and aliases every time.
I solved at the moment removing the -l
option on a custom profile.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Terminal does not source .bashrc by default - Gnome
Hello, I added some lines to my .bashrc recently, sourced the .bashrc and everything worked fine. However, after rebooting, my modifications ...
Read more >Manjaro default .bashrc explained - for dummies?
Hey there, just wondering if anyone has any material at hand that breaks down the default additions to the Manjaro .bashrc, explaining what ......
Read more >How I can customize .bashrc in Manjaro? - Support
How I can customize .bashrc in Manjaro? I did it on linuxmint by writing “gedit .bashrc”. But, in Manjaro it's not working.
Read more >User's bashrc ignored - Support - Manjaro Linux Forum
Hi! It seems my bashrc file is ignored. I've made several changes and none take effect. What I type to change it is...
Read more >Updates done to .bashrc do not hold across Terminal sessions
However, in manjaro-gnome-21.2.2 when I add the above mentioned function and do source .bashrc, the change does not stick across terminals.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you @erichlf. I will use my workaround because I prefer the “non login shell”. I close the issue.
Hi @erichlf @nuncio-bitis as I wrote, I solved (on Linux) by removing the
-l
option used by default to launch a bash shell. My “request” was to understand if the-l
option it is mandatory or could be removed by default to solve this very small issue.