hiphish / info.vim Goto Github PK

This family of commands is used for navigating to related neighbouring nodes. Here are my suggestions, keep in mind that these commands will only be available in info buffers:

" append node (currently in use)
:UpNode
:NextNode
:PrevNode

" Prepend info
:InfoUp
:InfoNext
:InfoPrev

The variants with Info prefix are guaranteed to have at least four suggestions for the first four letters when tab-completing, and unlikely to have more. On the other hand, the suffix versions are unpredictable, they might complete immediately or the user might get a lot of suggestions if other plugins use a similar naming scheme.

Opinions?

To supplement the built-in info reader, how about proposing in the docs a function, named say vinfo in .bash/zshrc that calls :Info, for example

vinfo() {
  vim +"Info "$@"" +only
}

Thanks for this plugin.

Executing e.g. :Info ls returns the error Info.vim: falling back to manpage. Running info ls on the regular command line shows the expected page.

Executing :Info works without issues, and following a couple of links I am able to reach that page about ls (info:coreutils.info#ls%20invocation).

By the way, the tutorial mentions :InfoGoto XRef-Navigation. I think this should be :Goto XRef-Navigation.

I noticed that the <Plug>Info* mappings do not use the "parentheses trick". <Plug>InfoFoo will trigger a wait for mapping to complete if there is also a <Plug>InfoFoo2 mapping defined.

The wait would be avoided if they were defined as <Plug>(InfoFoo) and <Plug>(InfoFoo2) . In other words, it's a good practice to always wrap <Plug>(...) mappings in parentheses.

Just FYI in case you didn't already know.

It seems this repo is "deprecated" in favor of the one on Gitlab. It would be good if you made this clear on the README and/or description.

The README mentions there is both a :Menu command and a :InfoMenu command. But when I load the plugin, I only get a :Menu option.

I'm working around right now with custom commands, but having :InfoMenu and other aliases like :InfoFollow etc built-in would be nice to have. A common style I use to for Vim plugins is to type the command prefix (e.g. :Info) and use tab-completion to quickly see what's available.

Useful plugin though, thanks!

For example, :Info git init falls back to the default git page, while :Man git init shows the right page.

Thanks for nice plugin!

Currently, info.vim uses info:... format for buffer names. I suggest changing it to the standard info://... format, following many other plugins, e.g. fugitive://, man://, fern://.

Vim always interprets a filename that starts with scheme:// as an absolute path, so it removes ambiguity. For example, there can be a file named info:... in cwd. This is why :h Cmd-event recommends this format. This also allows ignoring the info buffers in :oldfiles with set viminfo+=rinfo://.

When inside an Info documentation, I can move around without any problems and follow link to and from different Info nodes without any problems. However, during normal Vim usage, I usually like to go back to my previous point using , which inside an Info document seem to freeze Vim completely.

I don't know if that's a problem coming from my side, or from the plug-in itself (I haven't tested it without any other plug-ins yet, I could try that if needed).

Otherwise thanks for providing this plug-in, I haven't had any other problems using it and it looks great!

I added these mappings:

nmap gg K

"use fzf for the menu
nmap gm :call fzf#vim#buffer_lines('* ', 0)

There's probably a much better way to find the nodes names than just searching for "* "

Info supports looking up indices that are not Nodes.
For a list of what indices you could look up you could run info --apropos=

I added support for this on my fork, but it's more of a crud quick hack than something nice, hence I won't be creating a PR, but you could look at it here:
https://github.com/mburz/info.vim