Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fuse: mount failed: Permission denied when using neovim as MANPAGER #15590

Closed
Gelio opened this issue Sep 7, 2021 · 4 comments
Closed

fuse: mount failed: Permission denied when using neovim as MANPAGER #15590

Gelio opened this issue Sep 7, 2021 · 4 comments
Labels
closed:question issues that are closed as usage questions distribution packaging and distributing Nvim to users

Comments

@Gelio
Copy link
Contributor

Gelio commented Sep 7, 2021

Neovim version (nvim -v)

v0.6.0-dev+220-gdb695cc4c

Vim (not Nvim) behaves the same?

no clue

Operating system/version

Ubuntu 20.04 LTS

Terminal name/version

kitty 0.23.1

$TERM environment variable

xterm-kitty

Installation

appimage

How to reproduce the issue

  1. Install neovim appimage
  2. Set MANPAGER variable according to Following HEAD: breaking changes on master #14090 (comment)
  3. Run man ls

Expected behavior

Neovim opens with the man page for ls

Actual behavior

There is an error about mounting the appimage:

13:26 $ env | grep MANPAGER
MANPAGER=nvim +Man!
13:26 $ man ls
fuse: mount failed: Permission denied

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory
man: command exited with status 127: sed -e '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }' | LESS=-ix8RmPm Manual page ls(1) ?ltline %lt?L/%L.:byte %bB?s/%s..?e (END):?pB %pB\%.. (press h for help or q to quit)$PM Manual page ls(1) ?ltline %lt?L/%L.:byte %bB?s/%s..?e (END):?pB %pB\%.. (press h for help or q to quit)$ MAN_PN=ls(1) nvim +Man!

The same error occurs for other man pages (pwd, echo).

Using the :Man ls command after neovim is open works fine.

@Gelio Gelio added the bug issues reporting wrong behavior label Sep 7, 2021
@justinmk
Copy link
Member

justinmk commented Sep 8, 2021

has nothing to do with Nvim. Likely just a quirk of using any appimage with MANPAGER

@justinmk justinmk closed this as completed Sep 8, 2021
@justinmk justinmk added closed:question issues that are closed as usage questions distribution packaging and distributing Nvim to users and removed bug issues reporting wrong behavior labels Sep 8, 2021
@Gelio
Copy link
Contributor Author

Gelio commented Sep 8, 2021

Thanks for pointing that out. I switched to using a regular binary and it works fine

@jrowlingson
Copy link
Sponsor Contributor

jrowlingson commented May 9, 2023

Ran into this when attempting to use the nvim.appimage (since the .deb release was removed #22773). I was able to workaround w/ --appimage-extract and symlinking the bin.

$ man -V
man 2.9.4

@treequin
Copy link

Ran into this today. I got it to work by combining the two commands in this SE answer.
export MANPAGER='nvim.appimage --appimage-extract-and-run +Man!'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed:question issues that are closed as usage questions distribution packaging and distributing Nvim to users
Projects
None yet
Development

No branches or pull requests

4 participants