How to remove a bash script that runs at launch?

I recently setup the following command:

echo “export DISPLAY=:0.0” >> ~/.bashrc

in my Ubuntu on windows distribution to save time on setting up the virtual desktop when I launch the program, but it doesn't ever work correctly when run at runtime, giving this:

Command '“export' not found, did you mean:



command 'mexport' from deb mblaze

This seems to be a result of the quotation marks that I used in the command from the guide that I followed, so I should be able to fix those by removing the quotes, but I need to remove the script first.

So I would like to remove it from running at launch, how would I go about this?

edited 11 hours ago

asked 12 hours ago

Rhett Flanagan

New contributor

1

Looks like you used wrong kind of quotation marks. Are any quotation marks needed at all? Where did you find the command?

– pomsky
11 hours ago

@pomsky I realized that, I had followed a guide to setup the desktop and it had the quotes, so that needs to be rectified when I try to set that up again. I don't think the quotes are needed from what I've seen about setting up commands like it, hence wanting to remove the command.

– Rhett Flanagan
11 hours ago

edit ~/.bashrc manually and remove "export....". nano ~/.bashrc should be simple enough

– j-money
11 hours ago

add a comment |

I recently setup the following command:

echo “export DISPLAY=:0.0” >> ~/.bashrc

in my Ubuntu on windows distribution to save time on setting up the virtual desktop when I launch the program, but it doesn't ever work correctly when run at runtime, giving this:

Command '“export' not found, did you mean:



command 'mexport' from deb mblaze

So I would like to remove it from running at launch, how would I go about this?

edited 11 hours ago

asked 12 hours ago

Rhett Flanagan

New contributor

1

Looks like you used wrong kind of quotation marks. Are any quotation marks needed at all? Where did you find the command?

– pomsky
11 hours ago

@pomsky I realized that, I had followed a guide to setup the desktop and it had the quotes, so that needs to be rectified when I try to set that up again. I don't think the quotes are needed from what I've seen about setting up commands like it, hence wanting to remove the command.

– Rhett Flanagan
11 hours ago

edit ~/.bashrc manually and remove "export....". nano ~/.bashrc should be simple enough

– j-money
11 hours ago

add a comment |

I recently setup the following command:

echo “export DISPLAY=:0.0” >> ~/.bashrc

in my Ubuntu on windows distribution to save time on setting up the virtual desktop when I launch the program, but it doesn't ever work correctly when run at runtime, giving this:

Command '“export' not found, did you mean:



command 'mexport' from deb mblaze

So I would like to remove it from running at launch, how would I go about this?

edited 11 hours ago

asked 12 hours ago

Rhett Flanagan

New contributor

I recently setup the following command:

echo “export DISPLAY=:0.0” >> ~/.bashrc

in my Ubuntu on windows distribution to save time on setting up the virtual desktop when I launch the program, but it doesn't ever work correctly when run at runtime, giving this:

Command '“export' not found, did you mean:



command 'mexport' from deb mblaze

So I would like to remove it from running at launch, how would I go about this?

command-line bash

edited 11 hours ago

asked 12 hours ago

Rhett Flanagan

New contributor

edited 11 hours ago

asked 12 hours ago

Rhett Flanagan

New contributor

edited 11 hours ago

asked 12 hours ago

Rhett Flanagan

New contributor

asked 12 hours ago

Rhett Flanagan

asked 12 hours ago

Rhett Flanagan

New contributor

Rhett Flanagan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

1

Looks like you used wrong kind of quotation marks. Are any quotation marks needed at all? Where did you find the command?

– pomsky
11 hours ago

@pomsky I realized that, I had followed a guide to setup the desktop and it had the quotes, so that needs to be rectified when I try to set that up again. I don't think the quotes are needed from what I've seen about setting up commands like it, hence wanting to remove the command.

– Rhett Flanagan
11 hours ago

edit ~/.bashrc manually and remove "export....". nano ~/.bashrc should be simple enough

– j-money
11 hours ago

add a comment |

1

Looks like you used wrong kind of quotation marks. Are any quotation marks needed at all? Where did you find the command?

– pomsky
11 hours ago

@pomsky I realized that, I had followed a guide to setup the desktop and it had the quotes, so that needs to be rectified when I try to set that up again. I don't think the quotes are needed from what I've seen about setting up commands like it, hence wanting to remove the command.

– Rhett Flanagan
11 hours ago

edit ~/.bashrc manually and remove "export....". nano ~/.bashrc should be simple enough

– j-money
11 hours ago

Looks like you used wrong kind of quotation marks. Are any quotation marks needed at all? Where did you find the command?

– pomsky
11 hours ago

@pomsky I realized that, I had followed a guide to setup the desktop and it had the quotes, so that needs to be rectified when I try to set that up again. I don't think the quotes are needed from what I've seen about setting up commands like it, hence wanting to remove the command.

– Rhett Flanagan
11 hours ago

edit ~/.bashrc manually and remove "export....". nano ~/.bashrc should be simple enough

– j-money
11 hours ago

add a comment |

2 Answers
2

active

oldest

votes

You could remove the line

“export DISPLAY=:0.0”

in the file .bashrc.
The file would be in your user's home.

edited 11 hours ago

pomsky

31.2k1194127

answered 11 hours ago

Ubunter

464

New contributor

add a comment |

The problem is that you used the character “ and not the normal double quotes ("):

$ uniprops “

U+201C ‹“› N{LEFT DOUBLE QUOTATION MARK}

    pP p{Pi}

    All Any Assigned Punct Is_Punctuation Common Zyyy Pi P General_Punctuation

       InPunctuation Gr_Base Grapheme_Base Graph X_POSIX_Graph GrBase Initial_Punctuation

       Pat_Syn Pattern_Syntax PatSyn Print X_POSIX_Print Punctuation QMark Quotation_Mark

       Unicode X_POSIX_Punct

$ uniprops "

U+0022 ‹"› N{QUOTATION MARK}

    pP p{Po}

    All Any ASCII Assigned Basic_Latin Punct Is_Punctuation Common Zyyy Po P Gr_Base

       Grapheme_Base Graph X_POSIX_Graph GrBase Other_Punctuation Pat_Syn Pattern_Syntax

       PatSyn POSIX_Graph POSIX_Print POSIX_Punct Print X_POSIX_Print Punctuation QMark

       Quotation_Mark Unicode X_POSIX_Punct

If you had used the regular quotes, it would have worked as you expected:

echo "export DISPLAY=:0.0" >> ~/.bashrc

echo 'export DISPLAY=:0.0' >> ~/.bashrc

answered 11 hours ago

terdon♦

66.2k12138221

1

or no quotes at all: echo export DISPLAY=:0.0 >> ~/.bashrc :)

– dessert
8 hours ago

@dessert indeed, in this case the quotes aren't needed, but it's good practice to use them anyway. Next time, you might want to do something like echo "alias foo='ls bar*'" >> ~/.bashrc for example and that would fail without the double quotes.

– terdon♦
8 hours ago

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
});

}
});

Rhett Flanagan is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

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

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119161%2fhow-to-remove-a-bash-script-that-runs-at-launch%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

You could remove the line

“export DISPLAY=:0.0”

in the file .bashrc.
The file would be in your user's home.

edited 11 hours ago

pomsky

31.2k1194127

answered 11 hours ago

Ubunter

464

New contributor

add a comment |

You could remove the line

“export DISPLAY=:0.0”

in the file .bashrc.
The file would be in your user's home.

edited 11 hours ago

pomsky

31.2k1194127

answered 11 hours ago

Ubunter

464

New contributor

add a comment |

You could remove the line

“export DISPLAY=:0.0”

in the file .bashrc.
The file would be in your user's home.

edited 11 hours ago

pomsky

31.2k1194127

answered 11 hours ago

Ubunter

464

New contributor

You could remove the line

“export DISPLAY=:0.0”

in the file .bashrc.
The file would be in your user's home.

edited 11 hours ago

pomsky

31.2k1194127

answered 11 hours ago

Ubunter

464

New contributor

edited 11 hours ago

pomsky

31.2k1194127

edited 11 hours ago

pomsky

31.2k1194127

edited 11 hours ago

pomsky

31.2k1194127

answered 11 hours ago

Ubunter

464

New contributor

answered 11 hours ago

Ubunter

464

answered 11 hours ago

Ubunter

464

New contributor

Ubunter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment |

The problem is that you used the character “ and not the normal double quotes ("):

$ uniprops “

U+201C ‹“› N{LEFT DOUBLE QUOTATION MARK}

    pP p{Pi}

    All Any Assigned Punct Is_Punctuation Common Zyyy Pi P General_Punctuation

       InPunctuation Gr_Base Grapheme_Base Graph X_POSIX_Graph GrBase Initial_Punctuation

       Pat_Syn Pattern_Syntax PatSyn Print X_POSIX_Print Punctuation QMark Quotation_Mark

       Unicode X_POSIX_Punct

$ uniprops "

U+0022 ‹"› N{QUOTATION MARK}

    pP p{Po}

    All Any ASCII Assigned Basic_Latin Punct Is_Punctuation Common Zyyy Po P Gr_Base

       Grapheme_Base Graph X_POSIX_Graph GrBase Other_Punctuation Pat_Syn Pattern_Syntax

       PatSyn POSIX_Graph POSIX_Print POSIX_Punct Print X_POSIX_Print Punctuation QMark

       Quotation_Mark Unicode X_POSIX_Punct

If you had used the regular quotes, it would have worked as you expected:

echo "export DISPLAY=:0.0" >> ~/.bashrc

echo 'export DISPLAY=:0.0' >> ~/.bashrc

answered 11 hours ago

terdon♦

66.2k12138221

1

or no quotes at all: echo export DISPLAY=:0.0 >> ~/.bashrc :)

– dessert
8 hours ago

@dessert indeed, in this case the quotes aren't needed, but it's good practice to use them anyway. Next time, you might want to do something like echo "alias foo='ls bar*'" >> ~/.bashrc for example and that would fail without the double quotes.

– terdon♦
8 hours ago

add a comment |

The problem is that you used the character “ and not the normal double quotes ("):

$ uniprops “

U+201C ‹“› N{LEFT DOUBLE QUOTATION MARK}

    pP p{Pi}

    All Any Assigned Punct Is_Punctuation Common Zyyy Pi P General_Punctuation

       InPunctuation Gr_Base Grapheme_Base Graph X_POSIX_Graph GrBase Initial_Punctuation

       Pat_Syn Pattern_Syntax PatSyn Print X_POSIX_Print Punctuation QMark Quotation_Mark

       Unicode X_POSIX_Punct

$ uniprops "

U+0022 ‹"› N{QUOTATION MARK}

    pP p{Po}

    All Any ASCII Assigned Basic_Latin Punct Is_Punctuation Common Zyyy Po P Gr_Base

       Grapheme_Base Graph X_POSIX_Graph GrBase Other_Punctuation Pat_Syn Pattern_Syntax

       PatSyn POSIX_Graph POSIX_Print POSIX_Punct Print X_POSIX_Print Punctuation QMark

       Quotation_Mark Unicode X_POSIX_Punct

If you had used the regular quotes, it would have worked as you expected:

echo "export DISPLAY=:0.0" >> ~/.bashrc

echo 'export DISPLAY=:0.0' >> ~/.bashrc

answered 11 hours ago

terdon♦

66.2k12138221

1

or no quotes at all: echo export DISPLAY=:0.0 >> ~/.bashrc :)

– dessert
8 hours ago

@dessert indeed, in this case the quotes aren't needed, but it's good practice to use them anyway. Next time, you might want to do something like echo "alias foo='ls bar*'" >> ~/.bashrc for example and that would fail without the double quotes.

– terdon♦
8 hours ago

add a comment |

The problem is that you used the character “ and not the normal double quotes ("):

$ uniprops “

U+201C ‹“› N{LEFT DOUBLE QUOTATION MARK}

    pP p{Pi}

    All Any Assigned Punct Is_Punctuation Common Zyyy Pi P General_Punctuation

       InPunctuation Gr_Base Grapheme_Base Graph X_POSIX_Graph GrBase Initial_Punctuation

       Pat_Syn Pattern_Syntax PatSyn Print X_POSIX_Print Punctuation QMark Quotation_Mark

       Unicode X_POSIX_Punct

$ uniprops "

U+0022 ‹"› N{QUOTATION MARK}

    pP p{Po}

    All Any ASCII Assigned Basic_Latin Punct Is_Punctuation Common Zyyy Po P Gr_Base

       Grapheme_Base Graph X_POSIX_Graph GrBase Other_Punctuation Pat_Syn Pattern_Syntax

       PatSyn POSIX_Graph POSIX_Print POSIX_Punct Print X_POSIX_Print Punctuation QMark

       Quotation_Mark Unicode X_POSIX_Punct

If you had used the regular quotes, it would have worked as you expected:

echo "export DISPLAY=:0.0" >> ~/.bashrc

echo 'export DISPLAY=:0.0' >> ~/.bashrc

answered 11 hours ago

terdon♦

66.2k12138221

The problem is that you used the character “ and not the normal double quotes ("):

$ uniprops “

U+201C ‹“› N{LEFT DOUBLE QUOTATION MARK}

    pP p{Pi}

    All Any Assigned Punct Is_Punctuation Common Zyyy Pi P General_Punctuation

       InPunctuation Gr_Base Grapheme_Base Graph X_POSIX_Graph GrBase Initial_Punctuation

       Pat_Syn Pattern_Syntax PatSyn Print X_POSIX_Print Punctuation QMark Quotation_Mark

       Unicode X_POSIX_Punct

$ uniprops "

U+0022 ‹"› N{QUOTATION MARK}

    pP p{Po}

    All Any ASCII Assigned Basic_Latin Punct Is_Punctuation Common Zyyy Po P Gr_Base

       Grapheme_Base Graph X_POSIX_Graph GrBase Other_Punctuation Pat_Syn Pattern_Syntax

       PatSyn POSIX_Graph POSIX_Print POSIX_Punct Print X_POSIX_Print Punctuation QMark

       Quotation_Mark Unicode X_POSIX_Punct

If you had used the regular quotes, it would have worked as you expected:

echo "export DISPLAY=:0.0" >> ~/.bashrc

echo 'export DISPLAY=:0.0' >> ~/.bashrc

answered 11 hours ago

terdon♦

66.2k12138221

answered 11 hours ago

terdon♦

66.2k12138221

answered 11 hours ago

terdon♦

66.2k12138221

answered 11 hours ago

terdon♦

66.2k12138221

1

or no quotes at all: echo export DISPLAY=:0.0 >> ~/.bashrc :)

– dessert
8 hours ago

@dessert indeed, in this case the quotes aren't needed, but it's good practice to use them anyway. Next time, you might want to do something like echo "alias foo='ls bar*'" >> ~/.bashrc for example and that would fail without the double quotes.

– terdon♦
8 hours ago

add a comment |

1

or no quotes at all: echo export DISPLAY=:0.0 >> ~/.bashrc :)

– dessert
8 hours ago

@dessert indeed, in this case the quotes aren't needed, but it's good practice to use them anyway. Next time, you might want to do something like echo "alias foo='ls bar*'" >> ~/.bashrc for example and that would fail without the double quotes.

– terdon♦
8 hours ago

or no quotes at all: echo export DISPLAY=:0.0 >> ~/.bashrc :)

– dessert
8 hours ago

@dessert indeed, in this case the quotes aren't needed, but it's good practice to use them anyway. Next time, you might want to do something like echo "alias foo='ls bar*'" >> ~/.bashrc for example and that would fail without the double quotes.

– terdon♦
8 hours ago

add a comment |

Rhett Flanagan is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Rhett Flanagan is a new contributor. Be nice, and check out our Code of Conduct.

Thanks for contributing an answer to Ask Ubuntu!

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');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

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

Post as a guest

Name

Required, but never shown

Sign up or log in

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

Post as a guest

Name

Required, but never shown

Sign up or log in

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

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Ngtjyty