.desktop suffix vanishes
I followed the advice in https://askubuntu.com/a/1037153/701356
and created a .desktop file, gave it execute permissions and moved it to ~/.local/share/applications
Three things I notice:
The .desktop suffix vanishes in Caja (although other files in the folder keep theirs).
It is no longer possible to edit the file by right-clicking the icon and hoping to see an "Open with Pluma" option.
If the file is copied elsewhere and renamed, Caja still thinks it is of type "desktop configuration file", and opening it launches the program.
Is all this behaviour correct?
16.04 .desktop
add a comment |
I followed the advice in https://askubuntu.com/a/1037153/701356
and created a .desktop file, gave it execute permissions and moved it to ~/.local/share/applications
Three things I notice:
The .desktop suffix vanishes in Caja (although other files in the folder keep theirs).
It is no longer possible to edit the file by right-clicking the icon and hoping to see an "Open with Pluma" option.
If the file is copied elsewhere and renamed, Caja still thinks it is of type "desktop configuration file", and opening it launches the program.
Is all this behaviour correct?
16.04 .desktop
Sounds like the correct behaviour.
– pomsky
Feb 10 at 23:31
add a comment |
I followed the advice in https://askubuntu.com/a/1037153/701356
and created a .desktop file, gave it execute permissions and moved it to ~/.local/share/applications
Three things I notice:
The .desktop suffix vanishes in Caja (although other files in the folder keep theirs).
It is no longer possible to edit the file by right-clicking the icon and hoping to see an "Open with Pluma" option.
If the file is copied elsewhere and renamed, Caja still thinks it is of type "desktop configuration file", and opening it launches the program.
Is all this behaviour correct?
16.04 .desktop
I followed the advice in https://askubuntu.com/a/1037153/701356
and created a .desktop file, gave it execute permissions and moved it to ~/.local/share/applications
Three things I notice:
The .desktop suffix vanishes in Caja (although other files in the folder keep theirs).
It is no longer possible to edit the file by right-clicking the icon and hoping to see an "Open with Pluma" option.
If the file is copied elsewhere and renamed, Caja still thinks it is of type "desktop configuration file", and opening it launches the program.
Is all this behaviour correct?
16.04 .desktop
16.04 .desktop
asked Feb 10 at 22:03
desconocidodesconocido
11
11
Sounds like the correct behaviour.
– pomsky
Feb 10 at 23:31
add a comment |
Sounds like the correct behaviour.
– pomsky
Feb 10 at 23:31
Sounds like the correct behaviour.
– pomsky
Feb 10 at 23:31
Sounds like the correct behaviour.
– pomsky
Feb 10 at 23:31
add a comment |
0
active
oldest
votes
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1117227%2fdesktop-suffix-vanishes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2faskubuntu.com%2fquestions%2f1117227%2fdesktop-suffix-vanishes%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
Sounds like the correct behaviour.
– pomsky
Feb 10 at 23:31