How can I view man pages for apps installed via snaps?How to find out where $MANPATH is set?Does apps...
What is the use of 'de' preposition in 'Yo voy *de* compras todos los sábados'
Am I a Rude Number?
What incentives do banks have to gather up loans into pools (backed by Ginnie Mae)and selling them?
Absorbing damage with Planeswalker
What's a good word to describe a public place that looks like it wouldn't be rough?
Non-Cancer terminal illness that can affect young (age 10-13) girls?
Do theoretical physics suggest that gravity is the exchange of gravitons or deformation/bending of spacetime?
Use two 8s and two 3s to make the number 24
Is there a Linux system call to create a “view” of a range of a file?
What sets the resolution of an analog resistive sensor?
Is there a weight limit to Feather Fall?
Is there any risk in sharing info about technologies and products we use with a supplier?
Words and Words with "ver-" Prefix
Should I reinstall Linux when changing the laptop's CPU?
Citing paywalled articles accessed via illegal web sharing
Dilemma of explaining to interviewer that he is the reason for declining second interview
How old is the day of 24 equal hours?
Mathematics and the art of linearizing the circle
Increment each digit in a number to form a new number
What is a good reason for every spaceship to carry a weapon on board?
Why do neural networks need so many training examples to perform?
If I delete my router's history can my ISP still provide it to my parents?
Why would space fleets be aligned?
Is it possible to grant users sftp access without shell access? If yes, how is it implemented?
How can I view man pages for apps installed via snaps?
How to find out where $MANPATH is set?Does apps installed via “snap” has man page?Man pages offline for e-reader?Can I get man pages without installing the corresponding packages?How best to read the man pages?Man pages not finding entryHow do I view the man pages?How to view man pages without the unnecessary linefeeds?Where can I see beatifully formated online man pages?Installing the manual for getxattrMan pages for clang unavailableCan't open shared libraries (snap)
I have a fresh installation of Ubuntu 16.04 LTS, and tried to install a few apps using the new snap packages. The installation of those packages goes easy, but when I try to do man <package> I cannot open the man page. For example:
$ man tmux
No manual entry for tmux
See 'man 7 undocumented' for help when manual pages are not available.
The whereis command gives me this output:
$ whereis tmux
tmux: /snap/bin/tmux
But the truth is that the man page file exists:
$ ls -l $PWD/*
-rw-r--r-- 1 root root 100394 Abr 20 06:46 /snap/tmux/current/share/man/man1/tmux.1
How can I get this to work? Is there any problem with the snap package management?
package-management manpage snap
edited Apr 29 '16 at 10:32
muru
1
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
add a comment |
I have a fresh installation of Ubuntu 16.04 LTS, and tried to install a few apps using the new snap packages. The installation of those packages goes easy, but when I try to do man <package> I cannot open the man page. For example:
$ man tmux
No manual entry for tmux
See 'man 7 undocumented' for help when manual pages are not available.
The whereis command gives me this output:
$ whereis tmux
tmux: /snap/bin/tmux
But the truth is that the man page file exists:
$ ls -l $PWD/*
-rw-r--r-- 1 root root 100394 Abr 20 06:46 /snap/tmux/current/share/man/man1/tmux.1
How can I get this to work? Is there any problem with the snap package management?
package-management manpage snap
edited Apr 29 '16 at 10:32
muru
1
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
add a comment |
I have a fresh installation of Ubuntu 16.04 LTS, and tried to install a few apps using the new snap packages. The installation of those packages goes easy, but when I try to do man <package> I cannot open the man page. For example:
$ man tmux
No manual entry for tmux
See 'man 7 undocumented' for help when manual pages are not available.
The whereis command gives me this output:
$ whereis tmux
tmux: /snap/bin/tmux
But the truth is that the man page file exists:
$ ls -l $PWD/*
-rw-r--r-- 1 root root 100394 Abr 20 06:46 /snap/tmux/current/share/man/man1/tmux.1
How can I get this to work? Is there any problem with the snap package management?
package-management manpage snap
edited Apr 29 '16 at 10:32
muru
1
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
I have a fresh installation of Ubuntu 16.04 LTS, and tried to install a few apps using the new snap packages. The installation of those packages goes easy, but when I try to do man <package> I cannot open the man page. For example:
$ man tmux
No manual entry for tmux
See 'man 7 undocumented' for help when manual pages are not available.
The whereis command gives me this output:
$ whereis tmux
tmux: /snap/bin/tmux
But the truth is that the man page file exists:
$ ls -l $PWD/*
-rw-r--r-- 1 root root 100394 Abr 20 06:46 /snap/tmux/current/share/man/man1/tmux.1
How can I get this to work? Is there any problem with the snap package management?
package-management manpage snap
package-management manpage snap
edited Apr 29 '16 at 10:32
muru
1
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
edited Apr 29 '16 at 10:32
muru
1
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
edited Apr 29 '16 at 10:32
muru
1
edited Apr 29 '16 at 10:32
muru
1
edited Apr 29 '16 at 10:32
muru
1
1
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
asked Apr 29 '16 at 9:09
Ruben PedroRuben Pedro
436
436
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
A 'band-aid' solution is to run the following from the command line:
export MANPATH=":/snap/tmux/current/share/man"
and then the command man tmux will work as well as all of your pre-exisiting man pages. Bear in mind that Ubuntu does not normally use $MANPATH and the standard man pages PATH can be seen as follows:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man
After running the 'band-aid' solution suggested above you should see:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man:/snap/tmux/current/share/man
This setting can also be placed in ~/.bashrc for permanency, remembering that after placing it there either log out and then back in or simply run: source ~/.bashrc
Not very satisfactory I must say, especially if each package has a man page in a different location. Let us hope that as standards solidify this will be less of a problem...
References:
AskUbuntu: How to find out where $MANPATH is set? An excellent AskUbuntu question and answer that describes what the MANPATH is and how to manipulate it.
Snappy installed manpages aren't accessible through man Launchpad bug where the issue of viewing snap man pages is discussed.
Support for man pages Further discussion this time from the snapcraft forums.
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
1
Thank you for your comprehensive answer. I get surprised how a technology previously matured on Ubuntu Core comes to an LTS with this failure in mind, when the propose of those snaps is to bypass some deb's limitations (eg. to have an updated version of an app/tool regardless the dependencies present on the base system). Indeed, each snap package suffers from this problem, and it gets unmanageable to take care of each one. Canonical must address this problem.
– Ruben Pedro
Apr 29 '16 at 15:15
There is a case for a bug report on Launchpad for this issue, particularly if you can cite examples of multiple packages. Please 'accept' my answer if it has been useful btw...
– andrew.46
Apr 29 '16 at 20:08
Yep, you're right. Here's the link to the issue: Snappy installed manpages aren't inaccessible through man
– Ruben Pedro
Apr 30 '16 at 6:56
Here it is from the developer perspective: forum.snapcraft.io/t/support-for-man-pages/2299/7
– user535733
5 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
});
}
});
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%2f764835%2fhow-can-i-view-man-pages-for-apps-installed-via-snaps%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A 'band-aid' solution is to run the following from the command line:
export MANPATH=":/snap/tmux/current/share/man"
and then the command man tmux will work as well as all of your pre-exisiting man pages. Bear in mind that Ubuntu does not normally use $MANPATH and the standard man pages PATH can be seen as follows:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man
After running the 'band-aid' solution suggested above you should see:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man:/snap/tmux/current/share/man
This setting can also be placed in ~/.bashrc for permanency, remembering that after placing it there either log out and then back in or simply run: source ~/.bashrc
Not very satisfactory I must say, especially if each package has a man page in a different location. Let us hope that as standards solidify this will be less of a problem...
References:
AskUbuntu: How to find out where $MANPATH is set? An excellent AskUbuntu question and answer that describes what the MANPATH is and how to manipulate it.
Snappy installed manpages aren't accessible through man Launchpad bug where the issue of viewing snap man pages is discussed.
Support for man pages Further discussion this time from the snapcraft forums.
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
1
Thank you for your comprehensive answer. I get surprised how a technology previously matured on Ubuntu Core comes to an LTS with this failure in mind, when the propose of those snaps is to bypass some deb's limitations (eg. to have an updated version of an app/tool regardless the dependencies present on the base system). Indeed, each snap package suffers from this problem, and it gets unmanageable to take care of each one. Canonical must address this problem.
– Ruben Pedro
Apr 29 '16 at 15:15
There is a case for a bug report on Launchpad for this issue, particularly if you can cite examples of multiple packages. Please 'accept' my answer if it has been useful btw...
– andrew.46
Apr 29 '16 at 20:08
Yep, you're right. Here's the link to the issue: Snappy installed manpages aren't inaccessible through man
– Ruben Pedro
Apr 30 '16 at 6:56
Here it is from the developer perspective: forum.snapcraft.io/t/support-for-man-pages/2299/7
– user535733
5 hours ago
add a comment |
A 'band-aid' solution is to run the following from the command line:
export MANPATH=":/snap/tmux/current/share/man"
and then the command man tmux will work as well as all of your pre-exisiting man pages. Bear in mind that Ubuntu does not normally use $MANPATH and the standard man pages PATH can be seen as follows:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man
After running the 'band-aid' solution suggested above you should see:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man:/snap/tmux/current/share/man
This setting can also be placed in ~/.bashrc for permanency, remembering that after placing it there either log out and then back in or simply run: source ~/.bashrc
Not very satisfactory I must say, especially if each package has a man page in a different location. Let us hope that as standards solidify this will be less of a problem...
References:
AskUbuntu: How to find out where $MANPATH is set? An excellent AskUbuntu question and answer that describes what the MANPATH is and how to manipulate it.
Snappy installed manpages aren't accessible through man Launchpad bug where the issue of viewing snap man pages is discussed.
Support for man pages Further discussion this time from the snapcraft forums.
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
1
Thank you for your comprehensive answer. I get surprised how a technology previously matured on Ubuntu Core comes to an LTS with this failure in mind, when the propose of those snaps is to bypass some deb's limitations (eg. to have an updated version of an app/tool regardless the dependencies present on the base system). Indeed, each snap package suffers from this problem, and it gets unmanageable to take care of each one. Canonical must address this problem.
– Ruben Pedro
Apr 29 '16 at 15:15
There is a case for a bug report on Launchpad for this issue, particularly if you can cite examples of multiple packages. Please 'accept' my answer if it has been useful btw...
– andrew.46
Apr 29 '16 at 20:08
Yep, you're right. Here's the link to the issue: Snappy installed manpages aren't inaccessible through man
– Ruben Pedro
Apr 30 '16 at 6:56
Here it is from the developer perspective: forum.snapcraft.io/t/support-for-man-pages/2299/7
– user535733
5 hours ago
add a comment |
A 'band-aid' solution is to run the following from the command line:
export MANPATH=":/snap/tmux/current/share/man"
and then the command man tmux will work as well as all of your pre-exisiting man pages. Bear in mind that Ubuntu does not normally use $MANPATH and the standard man pages PATH can be seen as follows:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man
After running the 'band-aid' solution suggested above you should see:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man:/snap/tmux/current/share/man
This setting can also be placed in ~/.bashrc for permanency, remembering that after placing it there either log out and then back in or simply run: source ~/.bashrc
Not very satisfactory I must say, especially if each package has a man page in a different location. Let us hope that as standards solidify this will be less of a problem...
References:
AskUbuntu: How to find out where $MANPATH is set? An excellent AskUbuntu question and answer that describes what the MANPATH is and how to manipulate it.
Snappy installed manpages aren't accessible through man Launchpad bug where the issue of viewing snap man pages is discussed.
Support for man pages Further discussion this time from the snapcraft forums.
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
A 'band-aid' solution is to run the following from the command line:
export MANPATH=":/snap/tmux/current/share/man"
and then the command man tmux will work as well as all of your pre-exisiting man pages. Bear in mind that Ubuntu does not normally use $MANPATH and the standard man pages PATH can be seen as follows:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man
After running the 'band-aid' solution suggested above you should see:
andrew@athens:~$ man -w
/usr/local/man:/usr/local/share/man:/usr/share/man:/snap/tmux/current/share/man
This setting can also be placed in ~/.bashrc for permanency, remembering that after placing it there either log out and then back in or simply run: source ~/.bashrc
Not very satisfactory I must say, especially if each package has a man page in a different location. Let us hope that as standards solidify this will be less of a problem...
References:
AskUbuntu: How to find out where $MANPATH is set? An excellent AskUbuntu question and answer that describes what the MANPATH is and how to manipulate it.
Snappy installed manpages aren't accessible through man Launchpad bug where the issue of viewing snap man pages is discussed.
Support for man pages Further discussion this time from the snapcraft forums.
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
edited 9 mins ago
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
answered Apr 29 '16 at 11:05
andrew.46andrew.46
21.9k1469149
21.9k1469149
1
Thank you for your comprehensive answer. I get surprised how a technology previously matured on Ubuntu Core comes to an LTS with this failure in mind, when the propose of those snaps is to bypass some deb's limitations (eg. to have an updated version of an app/tool regardless the dependencies present on the base system). Indeed, each snap package suffers from this problem, and it gets unmanageable to take care of each one. Canonical must address this problem.
– Ruben Pedro
Apr 29 '16 at 15:15
There is a case for a bug report on Launchpad for this issue, particularly if you can cite examples of multiple packages. Please 'accept' my answer if it has been useful btw...
– andrew.46
Apr 29 '16 at 20:08
Yep, you're right. Here's the link to the issue: Snappy installed manpages aren't inaccessible through man
– Ruben Pedro
Apr 30 '16 at 6:56
Here it is from the developer perspective: forum.snapcraft.io/t/support-for-man-pages/2299/7
– user535733
5 hours ago
add a comment |
1
Thank you for your comprehensive answer. I get surprised how a technology previously matured on Ubuntu Core comes to an LTS with this failure in mind, when the propose of those snaps is to bypass some deb's limitations (eg. to have an updated version of an app/tool regardless the dependencies present on the base system). Indeed, each snap package suffers from this problem, and it gets unmanageable to take care of each one. Canonical must address this problem.
– Ruben Pedro
Apr 29 '16 at 15:15
There is a case for a bug report on Launchpad for this issue, particularly if you can cite examples of multiple packages. Please 'accept' my answer if it has been useful btw...
– andrew.46
Apr 29 '16 at 20:08
Yep, you're right. Here's the link to the issue: Snappy installed manpages aren't inaccessible through man
– Ruben Pedro
Apr 30 '16 at 6:56
Here it is from the developer perspective: forum.snapcraft.io/t/support-for-man-pages/2299/7
– user535733
5 hours ago
1
1
Thank you for your comprehensive answer. I get surprised how a technology previously matured on Ubuntu Core comes to an LTS with this failure in mind, when the propose of those snaps is to bypass some deb's limitations (eg. to have an updated version of an app/tool regardless the dependencies present on the base system). Indeed, each snap package suffers from this problem, and it gets unmanageable to take care of each one. Canonical must address this problem.
– Ruben Pedro
Apr 29 '16 at 15:15
Thank you for your comprehensive answer. I get surprised how a technology previously matured on Ubuntu Core comes to an LTS with this failure in mind, when the propose of those snaps is to bypass some deb's limitations (eg. to have an updated version of an app/tool regardless the dependencies present on the base system). Indeed, each snap package suffers from this problem, and it gets unmanageable to take care of each one. Canonical must address this problem.
– Ruben Pedro
Apr 29 '16 at 15:15
There is a case for a bug report on Launchpad for this issue, particularly if you can cite examples of multiple packages. Please 'accept' my answer if it has been useful btw...
– andrew.46
Apr 29 '16 at 20:08
There is a case for a bug report on Launchpad for this issue, particularly if you can cite examples of multiple packages. Please 'accept' my answer if it has been useful btw...
– andrew.46
Apr 29 '16 at 20:08
Yep, you're right. Here's the link to the issue: Snappy installed manpages aren't inaccessible through man
– Ruben Pedro
Apr 30 '16 at 6:56
Yep, you're right. Here's the link to the issue: Snappy installed manpages aren't inaccessible through man
– Ruben Pedro
Apr 30 '16 at 6:56
Here it is from the developer perspective: forum.snapcraft.io/t/support-for-man-pages/2299/7
– user535733
5 hours ago
Here it is from the developer perspective: forum.snapcraft.io/t/support-for-man-pages/2299/7
– user535733
5 hours ago
add a comment |
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%2f764835%2fhow-can-i-view-man-pages-for-apps-installed-via-snaps%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
