05-09-2011
It seems that every shell you run is a login shell. Bash reads and executes the ~/.bashrc file only if it is started as an interactive, but not login shell. When Bash starts as an interactive login shell, it reads and executes the ~/.bash_profile file. What you could do is to source the ~/.bashrc file from the ~/.bash_profile file. Something like this:
# .bash_profile
# sourcing .bashrc:
. ~/.bashrc
this way every interactive shell you start will read and execute the ~/.bashrc file, be it a loging shell or not.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
what is the command to connect to remote terminals? (1 Reply)
Discussion started by: sendtorohitgupt
1 Replies
2. UNIX for Advanced & Expert Users
Hi, I am working in huge environment, I do type commands from my terminal window repeadly in all same setup unix environments. I am looking some kind of a terminal emulator or some simple program that will help me?
basically if type command like 'ls' in one unix terminal window it should echo... (5 Replies)
Discussion started by: rgmekala
5 Replies
3. Shell Programming and Scripting
i want the shell script to open the terminal and in that terminal i want to run a command specified in the script...
how can it be done... (2 Replies)
Discussion started by: chandrabhushan
2 Replies
4. AIX
I just wondering if there are ways to open multiple virtual terminal to a single LPAR.
After I have use putty to login to the VIOS. I will use mkvt -id <LPAR id> to open console but if my friend want to open 2 second one, it will say, VT already connected.
IS there a way to work this around ? ... (1 Reply)
Discussion started by: wingcross
1 Replies
5. Shell Programming and Scripting
I have written a simple script to show battery life remaining. I would like to be able to quickly view it with a predefined keybinding or launcher.
xterm -e scriptname should do the trick but the xterm closes when the script finishes, not giving me chance to read the output. How can I keep... (3 Replies)
Discussion started by: spoovy
3 Replies
6. Linux
OK this is a bit messy.
I run Fedora with gnome on a compiz desktop, I have a script (userstart) that opens my 'standard' environment for all my machines when I login. userstart flips to a specific workspace and then opens the required applications in that workspace then flips to the next... (2 Replies)
Discussion started by: Bashingaway
2 Replies
7. Shell Programming and Scripting
hi,
how to write shell script that runs different commands(like:ls,ps,ls-l) in differnt terminals(each command should run in different terminal).
my main motive is to run different 'c' program exe's available in different locations in different terminals.
thanks
sai (2 Replies)
Discussion started by: saidopdf
2 Replies
8. Shell Programming and Scripting
( sleep 3
echo ${LOGIN}
sleep 2
echo ${PSWD}
sleep 2
while read line
do
echo "$line"
PID=$?
sleep 2
kill -9 $PID
done < temp
sleep 5
echo "exit" ) | telnet ${HOST}
while is executing only command and exits. (5 Replies)
Discussion started by: sooda
5 Replies
9. Shell Programming and Scripting
Hi All ,
i am trying to create an alias to open a new gnome-terminal and run some commands in each tab & to have a specific name for each tab
i am using csh ,
tried this command
gnome-terminal --tab -t "s1" --tab -t "s2" --tab -t "s3" --tab -t "s4"
it opened 4 tabs but the title didn't... (0 Replies)
Discussion started by: Assem
0 Replies
VI(1) General Commands Manual VI(1)
NAME
vi - screen oriented (visual) display editor based on ex
SYNOPSIS
vi [ -t tag ] [ -r ] [ +command ] [ -l ] [ -wn ] name ...
DESCRIPTION
Vi (visual) is a display oriented text editor based on ex(1). Ex and vi run the same code; it is possible to get to the command mode of ex
from within vi and vice-versa.
The Vi Quick Reference card and the Introduction to Display Editing with Vi provide full details on using vi.
FILES
See ex(1).
SEE ALSO
ex (1), edit (1), ``Vi Quick Reference'' card, ``An Introduction to Display Editing with Vi''.
AUTHOR
William Joy
Mark Horton added macros to visual mode and is maintaining version 3
BUGS
Software tabs using ^T work only immediately after the autoindent.
Left and right shifts on intelligent terminals don't make use of insert and delete character operations in the terminal.
The wrapmargin option can be fooled since it looks at output columns when blanks are typed. If a long word passes through the margin and
onto the next line without a break, then the line won't be broken.
Insert/delete within a line can be slow if tabs are present on intelligent terminals, since the terminals need help in doing this cor-
rectly.
Saving text on deletes in the named buffers is somewhat inefficient.
The source command does not work when executed as :source; there is no way to use the :append, :change, and :insert commands, since it is
not possible to give more than one line of input to a : escape. To use these on a :global you must Q to ex command mode, execute them, and
then reenter the screen editor with vi or open.
3rd Berkeley Distribution April 29, 1985 VI(1)