Otdfbt

Salesforce bug enabled "Modify All"

List of lists elementwise greater/smaller than

Does George B Sperry logo on fold case for photos indicate photographer or case manufacturer?

Is there any mention of ghosts who live outside the Hogwarts castle?

How can I use 400 ASA film in a Leica IIIf, which does not have options higher than 100?

Warped chessboard

Is it wise to pay off mortgage with 401k?

Gambler's Fallacy Dice

How did Arya and the Hound get into King's Landing so easily?

Connecting circles clockwise in TikZ

Can dirty bird feeders make birds sick?

Why "strap-on" boosters, and how do other people say it?

Filter a file list against an integer array?

Simple Arithmetic Puzzle 7. Or is it?

Do seaplanes need to get clearance for takeoff?

Farthing / Riding

How could the B-29 bomber back up under its own power?

How would a physicist explain this starship engine?

Vehemently against code formatting

How do we explain the use of a software on a math paper?

Difference in 1 user doing 1000 iterations and 1000 users doing 1 iteration in Load testing

What does it mean to "take the Cross"

Why was Houston selected as the location for the Manned Spacecraft Center?

Department head said that group project may be rejected. How to mitigate?

How to append code verbatim to .bashrc?

Change Gsetting with script on LogoutHow to set bashrc shell environmentTangoWithDjango .bashrc edit causing errorsupdating my path not workingChanging the value of $HOME in .bashrc.bashrc - if statement helpunexpected end of file bashrcError while installing Oracle 12c on Ubuntu 17.04.bashrc Error- command not foundHow return from .bashrc if not run interactively?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

5

As an example: When installing pyenv, you're required to add

export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"

to your .bashrc file.

However, the usual echo '..' >> ~/.bashrc will evaluate the statements before appending. How do you properly append such statements to a file using the command line without evaluation?

command-line bash bashrc

share|improve this question

asked May 7 at 15:36

bhnnbhnn

1314

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  This will not evaluate the commands, it will only print them into your ~/.bashrc. Either provide more information about your system and setup, or open ~/.bashrc in a text editor and write the lines by hand
  
  – j-money
  May 7 at 17:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @j-money This was merely meant as an example. I have noticed that there may be a discrepancy between the results of using echo '..' vs echo .. and as such, simply piping line by line into the file may indeed solve the issue. Nevertheless, steeldriver has provided a concise and scalable solution.
  
  – bhnn
  May 7 at 23:13
  

  
  
  
  

add a comment | 

5

As an example: When installing pyenv, you're required to add

export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"

to your .bashrc file.

However, the usual echo '..' >> ~/.bashrc will evaluate the statements before appending. How do you properly append such statements to a file using the command line without evaluation?

command-line bash bashrc

share|improve this question

asked May 7 at 15:36

bhnnbhnn

1314

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  This will not evaluate the commands, it will only print them into your ~/.bashrc. Either provide more information about your system and setup, or open ~/.bashrc in a text editor and write the lines by hand
  
  – j-money
  May 7 at 17:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @j-money This was merely meant as an example. I have noticed that there may be a discrepancy between the results of using echo '..' vs echo .. and as such, simply piping line by line into the file may indeed solve the issue. Nevertheless, steeldriver has provided a concise and scalable solution.
  
  – bhnn
  May 7 at 23:13
  

  
  
  
  

add a comment | 

As an example: When installing pyenv, you're required to add

export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"

to your .bashrc file.

However, the usual echo '..' >> ~/.bashrc will evaluate the statements before appending. How do you properly append such statements to a file using the command line without evaluation?

command-line bash bashrc

share|improve this question

asked May 7 at 15:36

bhnnbhnn

1314

export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"

share|improve this question

asked May 7 at 15:36

bhnnbhnn

1314

share|improve this question

asked May 7 at 15:36

bhnnbhnn

1314

asked May 7 at 15:36

bhnnbhnn

1314

asked May 7 at 15:36

bhnnbhnn

1314

3 Answers
3

active

oldest

votes

16

I'd suggest a here document

$ cat >> .bashrc <<'EOF'
export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
EOF

So long as the EOF word (which can be anything) is quoted, no shell expansion of the body takes place.

share|improve this answer

answered May 7 at 15:51

steeldriversteeldriver

72.8k11118192

add a comment | 

5

However, the usual echo '..' >> ~/.bashrc will evaluate the statements before appending. How do you properly append such statements to a file using the command line without evaluation?

No it won't. Anything inside of single-quotes is completely un-evaluated. You can use
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc without any worry that anything will be interpreted. The only character of any significance in a single-quoted string is a single-quote (which ends the string, and cannot be escaped.)

share|improve this answer

answered May 8 at 0:56

hobbshobbs

952611

add a comment | 

2

You can add in front of special characters.

For example:

echo export PATH="/home/user/.pyenv/bin:$PATH"

gives the following result:

export PATH="/home/user/.pyenv/bin:$PATH"

so the quotation marks and the $PATH are still there.

share|improve this answer

answered May 7 at 15:46

EliasElias

276112

add a comment | 

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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1141273%2fhow-to-append-code-verbatim-to-bashrc%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

16

I'd suggest a here document

$ cat >> .bashrc <<'EOF'
export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
EOF

So long as the EOF word (which can be anything) is quoted, no shell expansion of the body takes place.

share|improve this answer

answered May 7 at 15:51

steeldriversteeldriver

72.8k11118192

add a comment | 

16

I'd suggest a here document

$ cat >> .bashrc <<'EOF'
export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
EOF

So long as the EOF word (which can be anything) is quoted, no shell expansion of the body takes place.

share|improve this answer

answered May 7 at 15:51

steeldriversteeldriver

72.8k11118192

add a comment | 

I'd suggest a here document

$ cat >> .bashrc <<'EOF'
export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
EOF

So long as the EOF word (which can be anything) is quoted, no shell expansion of the body takes place.

share|improve this answer

answered May 7 at 15:51

steeldriversteeldriver

72.8k11118192

$ cat >> .bashrc <<'EOF'
export PATH="/home/user/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
EOF

share|improve this answer

answered May 7 at 15:51

steeldriversteeldriver

72.8k11118192

answered May 7 at 15:51

steeldriversteeldriver

72.8k11118192

answered May 7 at 15:51

steeldriversteeldriver

72.8k11118192

5

However, the usual echo '..' >> ~/.bashrc will evaluate the statements before appending. How do you properly append such statements to a file using the command line without evaluation?

No it won't. Anything inside of single-quotes is completely un-evaluated. You can use
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc without any worry that anything will be interpreted. The only character of any significance in a single-quoted string is a single-quote (which ends the string, and cannot be escaped.)

share|improve this answer

answered May 8 at 0:56

hobbshobbs

952611

add a comment | 

5

However, the usual echo '..' >> ~/.bashrc will evaluate the statements before appending. How do you properly append such statements to a file using the command line without evaluation?

No it won't. Anything inside of single-quotes is completely un-evaluated. You can use
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc without any worry that anything will be interpreted. The only character of any significance in a single-quoted string is a single-quote (which ends the string, and cannot be escaped.)

share|improve this answer

answered May 8 at 0:56

hobbshobbs

952611

add a comment | 

However, the usual echo '..' >> ~/.bashrc will evaluate the statements before appending. How do you properly append such statements to a file using the command line without evaluation?

No it won't. Anything inside of single-quotes is completely un-evaluated. You can use
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc without any worry that anything will be interpreted. The only character of any significance in a single-quoted string is a single-quote (which ends the string, and cannot be escaped.)

share|improve this answer

answered May 8 at 0:56

hobbshobbs

952611

share|improve this answer

answered May 8 at 0:56

hobbshobbs

952611

answered May 8 at 0:56

hobbshobbs

952611

answered May 8 at 0:56

hobbshobbs

952611

2

You can add in front of special characters.

For example:

echo export PATH="/home/user/.pyenv/bin:$PATH"

gives the following result:

export PATH="/home/user/.pyenv/bin:$PATH"

so the quotation marks and the $PATH are still there.

share|improve this answer

answered May 7 at 15:46

EliasElias

276112

add a comment | 

2

You can add in front of special characters.

For example:

echo export PATH="/home/user/.pyenv/bin:$PATH"

gives the following result:

export PATH="/home/user/.pyenv/bin:$PATH"

so the quotation marks and the $PATH are still there.

share|improve this answer

answered May 7 at 15:46

EliasElias

276112

add a comment | 

You can add in front of special characters.

For example:

echo export PATH="/home/user/.pyenv/bin:$PATH"

gives the following result:

export PATH="/home/user/.pyenv/bin:$PATH"

so the quotation marks and the $PATH are still there.

share|improve this answer

answered May 7 at 15:46

EliasElias

276112

echo export PATH="/home/user/.pyenv/bin:$PATH"

export PATH="/home/user/.pyenv/bin:$PATH"

share|improve this answer

answered May 7 at 15:46

EliasElias

276112

answered May 7 at 15:46

EliasElias

276112

answered May 7 at 15:46

EliasElias

276112