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

Failed to open image file with Image Viewer eog #1422

Open
cgbahk opened this issue Jun 21, 2024 · 0 comments
Open

Failed to open image file with Image Viewer eog #1422

cgbahk opened this issue Jun 21, 2024 · 0 comments
Labels

Comments

@cgbahk
Copy link

cgbahk commented Jun 21, 2024

Environment

  • Operating System: Ubuntu 22.04
  • Vim/Neovim version :version:
    NVIM v0.6.1
    Build type: Release
    LuaJIT 2.1.0-beta3
    Compiled by [email protected]
    
    Features: +acl +iconv +tui
    
  • NERDTree version, found on first line of quickhelp ?: 6.10.16
  • Are you using any of these NERDTree-dependent plugins?
    None of suggested plugins.
  • Provide a minimal .vimrc file that will reproduce the issue.
    It's too big... https://github.com/cgbahk/vimrc

Steps to Reproduce the Issue

  1. Given image file, say image.svg of image.png
  2. Using NerdTree menu feature, browse to the image file in Nerdtree, press m then o to execute the file with system editor

Current Behavior (Include screenshots where appropriate.)

No log, image viewer not opened

Expected Result

Image viewer (eog, https://en.wikipedia.org/wiki/Eye_of_GNOME) opens up to show image.

I recently migrate into nvim. I've used vim in combination with NerdTree for 5+ years without this issue. Configuration is totally same between vim and nvim.

In nvim with same environment, I can open other types of files as usual, like opening directories or libreoffice files. This issue only occurs to image files (or maybe I haven't met any other bug file types).

It is hard to find related issue or stackoverflow thread. Also as there is no log, there is hardly no point to start with for me.

What would be the source of the issue, or at least, how can I debug..?

@cgbahk cgbahk added the bug label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant