Sunday, April 5, 2020

Re: gx strange behavior

On Sunday, April 5, 2020 at 10:48:08 AM UTC+2, Manfred Lotz wrote:
>
> Hi all, 
> I have Fedora 31 and Fedora 32. Happens on both systems. 
>
> I want to open an URL in my browser and type `gx` when the cursor is 
> over an URL in vim resp. gvim 
>
>
> Doing this for example in an markdown document it works fine for vim but 
> nothing happens when doing the same in gvim. 
>
> When debugging (i.e. starting vim resp. gvim with `-V9vim.log`) I see: 
>
> line 2: sourcing "/usr/share/vim/vim82/autoload/netrw.vim" 
> finished sourcing /usr/share/vim/vim82/autoload/netrw.vim 
> continuing in <SNR>67_VersionAwareNetrwBrowseX 
> :!setsid xdg-open 'https://realpython.com/python-data-types/'>/dev/null 
> 2>&1 
>
> Calling shell to execute: "setsid xdg-open 
> 'https://realpython.com/python-data-types/'>/dev/null 2>&1" 
>
>
> Any idea how to find out why gvim behaves differently? 
>
>
> -- 
> Manfred 
>

A solution (or workaround?) to (the root cause of) this issue has been posted in this group a few weeks back in this discussion:
"netrw#BrowseX fails when invoked from gvim on Ubuntu"

The trick is to use:
:!xdg-open http://www.vim.org &

instead of:
:!xdg-open http://www.vim.org

Note the ampersand at the end of the first command. See the original discussion for more details.

I didn't look into the netrw plugin but I suppose there is a way to configure it so that the gx command launches xdg-open via a background job (the ampersand form).

Tom


--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/cd194c31-b64f-426f-bf64-5238cca6049e%40googlegroups.com.

No comments: