Put . ~/.bashrc and now prompts 2 files to edit indefinitely

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








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"









share|improve this question



















  • 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














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"









share|improve this question



















  • 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












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"









share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








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












  • 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










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"





share|improve this answer




















  • 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











  • 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











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















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






























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"





share|improve this answer




















  • 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











  • 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















up vote
0
down vote



accepted










Delete the line:



alias alias="vi ~/.bash_aliases"


Also probably delete the line:



alias compile=". ~/.bashrc"





share|improve this answer




















  • 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











  • 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













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"





share|improve this answer












Delete the line:



alias alias="vi ~/.bash_aliases"


Also probably delete the line:



alias compile=". ~/.bashrc"






share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 18 at 1:54









WinEunuuchs2Unix

35.7k759133




35.7k759133











  • 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











  • 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










  • @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


















 

draft saved


draft discarded















































 


draft saved


draft discarded














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













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491