On Mon, 6 Apr 2020 22:51:04 -0400 Charles E Campbell <[email protected]> wrote:
> Manfred Lotz wrote: > > On Mon, 6 Apr 2020 12:27:58 -0400 > > Charles E Campbell <[email protected]> wrote: > > > >> Manfred Lotz wrote: > >>> On Sun, 5 Apr 2020 11:52:42 -0400 > >>> Charles E Campbell <[email protected]> wrote: > >>> > >>>> 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? > >>>>> > >>>>> > >>>> Try looking at :help netrw-debug . The trace will tell you more > >>>> about what was actually done. > >>>> > >>> I tried but did not see any debug messages. > >>> > >> Did you turn debugging on in netrw? As in, vi netrw.vim, :DechoOn, > >> :wq . > >> > > I think I am not smart enough to get debugging on. > > > > I ran > > > > vim netrw.vba.gz > > :so % > > :q > > > > vim Decho.vba.gz > > :so % > > :q > > > > Both times there came a message about a duplicate tag "netrw-cd" in > > file /home/manfred/.vim/doc/pi_netrw.txt > > > > > > Then I started netrw.vimc, and typed > > :DechoOn > > > > Here I got error messages > > > > Error detected while processing function DechoOn: > > line 7: > > this file<netrw.vimrc> does not contain any Decho/Dfunc/Dret > > commands or function calls. > > > > which is true as netrw.vimc only has > > > > set nocp > > so /home/manfred/.vim/plugin/netrwPlugin.vim > > > Yes, that's why you should turn debugging on in netrw.vim, not > something else. netrw.vim should be in your > $HOME/.vim/autoload/netrw.vim directory. > Yes, it is. The newest one from your website. > vim netrw.vim > :DechoOn > :wq > Yep, works now. > Then try gx or whatever; you should get a trace. > > The trace is time consuming; FYI: to turn debug tracing off: > Hm, my cursor is onto an url and I type gx. There is a message at the bottom: DEBUG: start up DECHOREMOTE server and a separate gvim window opened. Now pressing enter I get the debug info which is 99 lines. I send it to you with a separate mail. Thanks a lot for your patience. -- Manfred -- -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200407063521.5718f7c6%40hogwart.
