Put . ~/.bashrc and now prompts 2 files to edit indefinitely
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
1
down vote
favorite
I am a beginner Ubuntu user: I ran the command . ~/.bash_aliases
and now anytime I open Ubuntu on my windows laptop, it reads 2 files to edit, opens each of the files and I press quit every time to get back to the command line. I would initially be back in the command line, but would be brought back to edit the tiles indefinitely until I closed the prompt. Closing the prompt and reopening it, it would make me edit the 2 files and then let me go back to the command line.
How do I stop Ubuntu from doing this?
Edit: There is nothing in the bash_aliases file, I moved all the content to the bashrc file.
This is the contents of the bashrc file:
BASE16_SHELL=$HOME/.config/base16-shell/
[ -n "$PS1" ] && [ -s $BASE16_SHELL/profile_helper.sh ] && eval "$($BASE16_SHELL/profile_helper.sh)"
export PS1="e[95mwe[0m$ "
alias ls="ls --color=auto"
alias update="sudo apt-get install"
alias compile=". ~/.bashrc"
alias alias="vi ~/.bash_aliases"
alias thiscomp="cd /mnt/c/Users/name/Documents"
bashrc
add a comment |Â
up vote
1
down vote
favorite
I am a beginner Ubuntu user: I ran the command . ~/.bash_aliases
and now anytime I open Ubuntu on my windows laptop, it reads 2 files to edit, opens each of the files and I press quit every time to get back to the command line. I would initially be back in the command line, but would be brought back to edit the tiles indefinitely until I closed the prompt. Closing the prompt and reopening it, it would make me edit the 2 files and then let me go back to the command line.
How do I stop Ubuntu from doing this?
Edit: There is nothing in the bash_aliases file, I moved all the content to the bashrc file.
This is the contents of the bashrc file:
BASE16_SHELL=$HOME/.config/base16-shell/
[ -n "$PS1" ] && [ -s $BASE16_SHELL/profile_helper.sh ] && eval "$($BASE16_SHELL/profile_helper.sh)"
export PS1="e[95mwe[0m$ "
alias ls="ls --color=auto"
alias update="sudo apt-get install"
alias compile=". ~/.bashrc"
alias alias="vi ~/.bash_aliases"
alias thiscomp="cd /mnt/c/Users/name/Documents"
bashrc
2
Can we get the contents of your .bash_aliases file?
â RobertRSeattle
Apr 17 at 22:51
1
Please edit your original question above and add the contents of the.bash_aliases
file. Please use the icon above the edit window to format the code copied and pasted in the original question.
â user68186
Apr 17 at 22:55
Are you running Ubuntu on Bash on Windows? ie WSL?
â WinEunuuchs2Unix
Apr 18 at 2:01
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am a beginner Ubuntu user: I ran the command . ~/.bash_aliases
and now anytime I open Ubuntu on my windows laptop, it reads 2 files to edit, opens each of the files and I press quit every time to get back to the command line. I would initially be back in the command line, but would be brought back to edit the tiles indefinitely until I closed the prompt. Closing the prompt and reopening it, it would make me edit the 2 files and then let me go back to the command line.
How do I stop Ubuntu from doing this?
Edit: There is nothing in the bash_aliases file, I moved all the content to the bashrc file.
This is the contents of the bashrc file:
BASE16_SHELL=$HOME/.config/base16-shell/
[ -n "$PS1" ] && [ -s $BASE16_SHELL/profile_helper.sh ] && eval "$($BASE16_SHELL/profile_helper.sh)"
export PS1="e[95mwe[0m$ "
alias ls="ls --color=auto"
alias update="sudo apt-get install"
alias compile=". ~/.bashrc"
alias alias="vi ~/.bash_aliases"
alias thiscomp="cd /mnt/c/Users/name/Documents"
bashrc
I am a beginner Ubuntu user: I ran the command . ~/.bash_aliases
and now anytime I open Ubuntu on my windows laptop, it reads 2 files to edit, opens each of the files and I press quit every time to get back to the command line. I would initially be back in the command line, but would be brought back to edit the tiles indefinitely until I closed the prompt. Closing the prompt and reopening it, it would make me edit the 2 files and then let me go back to the command line.
How do I stop Ubuntu from doing this?
Edit: There is nothing in the bash_aliases file, I moved all the content to the bashrc file.
This is the contents of the bashrc file:
BASE16_SHELL=$HOME/.config/base16-shell/
[ -n "$PS1" ] && [ -s $BASE16_SHELL/profile_helper.sh ] && eval "$($BASE16_SHELL/profile_helper.sh)"
export PS1="e[95mwe[0m$ "
alias ls="ls --color=auto"
alias update="sudo apt-get install"
alias compile=". ~/.bashrc"
alias alias="vi ~/.bash_aliases"
alias thiscomp="cd /mnt/c/Users/name/Documents"
bashrc
bashrc
edited May 7 at 5:02
Jason Aller
44358
44358
asked Apr 17 at 20:57
hello1094
83
83
2
Can we get the contents of your .bash_aliases file?
â RobertRSeattle
Apr 17 at 22:51
1
Please edit your original question above and add the contents of the.bash_aliases
file. Please use the icon above the edit window to format the code copied and pasted in the original question.
â user68186
Apr 17 at 22:55
Are you running Ubuntu on Bash on Windows? ie WSL?
â WinEunuuchs2Unix
Apr 18 at 2:01
add a comment |Â
2
Can we get the contents of your .bash_aliases file?
â RobertRSeattle
Apr 17 at 22:51
1
Please edit your original question above and add the contents of the.bash_aliases
file. Please use the icon above the edit window to format the code copied and pasted in the original question.
â user68186
Apr 17 at 22:55
Are you running Ubuntu on Bash on Windows? ie WSL?
â WinEunuuchs2Unix
Apr 18 at 2:01
2
2
Can we get the contents of your .bash_aliases file?
â RobertRSeattle
Apr 17 at 22:51
Can we get the contents of your .bash_aliases file?
â RobertRSeattle
Apr 17 at 22:51
1
1
Please edit your original question above and add the contents of the
.bash_aliases
file. Please use the icon above the edit window to format the code copied and pasted in the original question.â user68186
Apr 17 at 22:55
Please edit your original question above and add the contents of the
.bash_aliases
file. Please use the icon above the edit window to format the code copied and pasted in the original question.â user68186
Apr 17 at 22:55
Are you running Ubuntu on Bash on Windows? ie WSL?
â WinEunuuchs2Unix
Apr 18 at 2:01
Are you running Ubuntu on Bash on Windows? ie WSL?
â WinEunuuchs2Unix
Apr 18 at 2:01
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Delete the line:
alias alias="vi ~/.bash_aliases"
Also probably delete the line:
alias compile=". ~/.bashrc"
Should isource ~/.bashrc
it after deleting it?
â hello1094
Apr 18 at 2:00
@hello1094 Don't delete~/.bashrc
. There is no need to source it, it is automatic when you open a terminal window.
â WinEunuuchs2Unix
Apr 18 at 2:01
Sorry, i meant after deleting the 2 alias lines
â hello1094
Apr 18 at 2:02
The existing alias will stay in place if you resource.bashrc
. Close the terminal and reopen it.
â WinEunuuchs2Unix
Apr 18 at 2:02
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Delete the line:
alias alias="vi ~/.bash_aliases"
Also probably delete the line:
alias compile=". ~/.bashrc"
Should isource ~/.bashrc
it after deleting it?
â hello1094
Apr 18 at 2:00
@hello1094 Don't delete~/.bashrc
. There is no need to source it, it is automatic when you open a terminal window.
â WinEunuuchs2Unix
Apr 18 at 2:01
Sorry, i meant after deleting the 2 alias lines
â hello1094
Apr 18 at 2:02
The existing alias will stay in place if you resource.bashrc
. Close the terminal and reopen it.
â WinEunuuchs2Unix
Apr 18 at 2:02
add a comment |Â
up vote
0
down vote
accepted
Delete the line:
alias alias="vi ~/.bash_aliases"
Also probably delete the line:
alias compile=". ~/.bashrc"
Should isource ~/.bashrc
it after deleting it?
â hello1094
Apr 18 at 2:00
@hello1094 Don't delete~/.bashrc
. There is no need to source it, it is automatic when you open a terminal window.
â WinEunuuchs2Unix
Apr 18 at 2:01
Sorry, i meant after deleting the 2 alias lines
â hello1094
Apr 18 at 2:02
The existing alias will stay in place if you resource.bashrc
. Close the terminal and reopen it.
â WinEunuuchs2Unix
Apr 18 at 2:02
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Delete the line:
alias alias="vi ~/.bash_aliases"
Also probably delete the line:
alias compile=". ~/.bashrc"
Delete the line:
alias alias="vi ~/.bash_aliases"
Also probably delete the line:
alias compile=". ~/.bashrc"
answered Apr 18 at 1:54
![](https://i.stack.imgur.com/2SXNl.jpg?s=32&g=1)
![](https://i.stack.imgur.com/2SXNl.jpg?s=32&g=1)
WinEunuuchs2Unix
35.7k759133
35.7k759133
Should isource ~/.bashrc
it after deleting it?
â hello1094
Apr 18 at 2:00
@hello1094 Don't delete~/.bashrc
. There is no need to source it, it is automatic when you open a terminal window.
â WinEunuuchs2Unix
Apr 18 at 2:01
Sorry, i meant after deleting the 2 alias lines
â hello1094
Apr 18 at 2:02
The existing alias will stay in place if you resource.bashrc
. Close the terminal and reopen it.
â WinEunuuchs2Unix
Apr 18 at 2:02
add a comment |Â
Should isource ~/.bashrc
it after deleting it?
â hello1094
Apr 18 at 2:00
@hello1094 Don't delete~/.bashrc
. There is no need to source it, it is automatic when you open a terminal window.
â WinEunuuchs2Unix
Apr 18 at 2:01
Sorry, i meant after deleting the 2 alias lines
â hello1094
Apr 18 at 2:02
The existing alias will stay in place if you resource.bashrc
. Close the terminal and reopen it.
â WinEunuuchs2Unix
Apr 18 at 2:02
Should i
source ~/.bashrc
it after deleting it?â hello1094
Apr 18 at 2:00
Should i
source ~/.bashrc
it after deleting it?â hello1094
Apr 18 at 2:00
@hello1094 Don't delete
~/.bashrc
. There is no need to source it, it is automatic when you open a terminal window.â WinEunuuchs2Unix
Apr 18 at 2:01
@hello1094 Don't delete
~/.bashrc
. There is no need to source it, it is automatic when you open a terminal window.â WinEunuuchs2Unix
Apr 18 at 2:01
Sorry, i meant after deleting the 2 alias lines
â hello1094
Apr 18 at 2:02
Sorry, i meant after deleting the 2 alias lines
â hello1094
Apr 18 at 2:02
The existing alias will stay in place if you resource
.bashrc
. Close the terminal and reopen it.â WinEunuuchs2Unix
Apr 18 at 2:02
The existing alias will stay in place if you resource
.bashrc
. Close the terminal and reopen it.â WinEunuuchs2Unix
Apr 18 at 2:02
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025936%2fput-bashrc-and-now-prompts-2-files-to-edit-indefinitely%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
Can we get the contents of your .bash_aliases file?
â RobertRSeattle
Apr 17 at 22:51
1
Please edit your original question above and add the contents of the
.bash_aliases
file. Please use the icon above the edit window to format the code copied and pasted in the original question.â user68186
Apr 17 at 22:55
Are you running Ubuntu on Bash on Windows? ie WSL?
â WinEunuuchs2Unix
Apr 18 at 2:01