source bash string instead of file
0
I want to source a bash function from a string instead of a file at the command line, so instead of this:
source file.sh
I want to do something like:
source `cat <<EOF
some_func(){
echo "nodejs version: $(node --version)"
echo "r2g version: $(r2g --version)"
echo "npm version: $(npm --version)"
}
export -f some_func;
EOF`
is this possible somehow?
bash shell source
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
add a comment |
0
I want to source a bash function from a string instead of a file at the command line, so instead of this:
source file.sh
I want to do something like:
source `cat <<EOF
some_func(){
echo "nodejs version: $(node --version)"
echo "r2g version: $(r2g --version)"
echo "npm version: $(npm --version)"
}
export -f some_func;
EOF`
is this possible somehow?
bash shell source
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
Why jump through so many hoops? Just put the text into the code right there?
– Jeff Schaller
Dec 19 '18 at 2:12
yeah actually what might be convenient is to send it all to the clipboard
– Alexander Mills
Dec 19 '18 at 2:14
Why not define your function in a shell startup file?
– Erwan
Dec 19 '18 at 2:19
because the user is going to copy the code and paste in their terminal, but the code will be in a readme file or Github issue template
– Alexander Mills
Dec 19 '18 at 2:35
1
source <( cat <<END ... ), but it seem like an awfully fragile and awkward workflow. I won't write this as an answer because I think it's ugly.
– Kusalananda
Dec 19 '18 at 8:29
add a comment |
0
0
0
I want to source a bash function from a string instead of a file at the command line, so instead of this:
source file.sh
I want to do something like:
source `cat <<EOF
some_func(){
echo "nodejs version: $(node --version)"
echo "r2g version: $(r2g --version)"
echo "npm version: $(npm --version)"
}
export -f some_func;
EOF`
is this possible somehow?
bash shell source
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
I want to source a bash function from a string instead of a file at the command line, so instead of this:
source file.sh
I want to do something like:
source `cat <<EOF
some_func(){
echo "nodejs version: $(node --version)"
echo "r2g version: $(r2g --version)"
echo "npm version: $(npm --version)"
}
export -f some_func;
EOF`
is this possible somehow?
bash shell source
bash shell source
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
asked Dec 19 '18 at 1:16
Alexander Mills
2,15911442
2,15911442
Why jump through so many hoops? Just put the text into the code right there?
– Jeff Schaller
Dec 19 '18 at 2:12
yeah actually what might be convenient is to send it all to the clipboard
– Alexander Mills
Dec 19 '18 at 2:14
Why not define your function in a shell startup file?
– Erwan
Dec 19 '18 at 2:19
because the user is going to copy the code and paste in their terminal, but the code will be in a readme file or Github issue template
– Alexander Mills
Dec 19 '18 at 2:35
1
source <( cat <<END ... ), but it seem like an awfully fragile and awkward workflow. I won't write this as an answer because I think it's ugly.
– Kusalananda
Dec 19 '18 at 8:29
add a comment |
Why jump through so many hoops? Just put the text into the code right there?
– Jeff Schaller
Dec 19 '18 at 2:12
yeah actually what might be convenient is to send it all to the clipboard
– Alexander Mills
Dec 19 '18 at 2:14
Why not define your function in a shell startup file?
– Erwan
Dec 19 '18 at 2:19
because the user is going to copy the code and paste in their terminal, but the code will be in a readme file or Github issue template
– Alexander Mills
Dec 19 '18 at 2:35
1
source <( cat <<END ... ), but it seem like an awfully fragile and awkward workflow. I won't write this as an answer because I think it's ugly.
– Kusalananda
Dec 19 '18 at 8:29
Why jump through so many hoops? Just put the text into the code right there?
– Jeff Schaller
Dec 19 '18 at 2:12
Why jump through so many hoops? Just put the text into the code right there?
– Jeff Schaller
Dec 19 '18 at 2:12
yeah actually what might be convenient is to send it all to the clipboard
– Alexander Mills
Dec 19 '18 at 2:14
yeah actually what might be convenient is to send it all to the clipboard
– Alexander Mills
Dec 19 '18 at 2:14
Why not define your function in a shell startup file?
– Erwan
Dec 19 '18 at 2:19
Why not define your function in a shell startup file?
– Erwan
Dec 19 '18 at 2:19
because the user is going to copy the code and paste in their terminal, but the code will be in a readme file or Github issue template
– Alexander Mills
Dec 19 '18 at 2:35
because the user is going to copy the code and paste in their terminal, but the code will be in a readme file or Github issue template
– Alexander Mills
Dec 19 '18 at 2:35
1
1
source <( cat <<END ... ), but it seem like an awfully fragile and awkward workflow. I won't write this as an answer because I think it's ugly.– Kusalananda
Dec 19 '18 at 8:29
source <( cat <<END ... ), but it seem like an awfully fragile and awkward workflow. I won't write this as an answer because I think it's ugly.– Kusalananda
Dec 19 '18 at 8:29
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489798%2fsource-bash-string-instead-of-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489798%2fsource-bash-string-instead-of-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why jump through so many hoops? Just put the text into the code right there?
– Jeff Schaller
Dec 19 '18 at 2:12
yeah actually what might be convenient is to send it all to the clipboard
– Alexander Mills
Dec 19 '18 at 2:14
Why not define your function in a shell startup file?
– Erwan
Dec 19 '18 at 2:19
because the user is going to copy the code and paste in their terminal, but the code will be in a readme file or Github issue template
– Alexander Mills
Dec 19 '18 at 2:35
1
source <( cat <<END ... ), but it seem like an awfully fragile and awkward workflow. I won't write this as an answer because I think it's ugly.– Kusalananda
Dec 19 '18 at 8:29