Skip to content

Conversation

lithammer
Copy link
Contributor

Open the Vim help file instead of man when pressing K in normal mode.

@lithammer
Copy link
Contributor Author

I guess this should have the defaults label.

@fmoralesc fmoralesc added defaults Nvim defaults for options, colorscheme/theme, autocmds/events, etc. runtime funtime labels Jul 26, 2015
@vheon
Copy link
Contributor

vheon commented Jul 26, 2015

I would prefer this behaviour from tpope/vim-scriptease as a default for vim files.

@justinmk
Copy link
Member

Yeah, I was thinking scriptease should be a default plugin, actually. (Please don't send a PR for that, though...)

@vheon Any reason this PR would be a problem in the meantime? If users have scripttease they won't notice, and users that don't have scriptease get some benefit.

@lithammer
Copy link
Contributor Author

What does that scriptease snippet actually do? It wasn't immediately obvious to me.

@fmoralesc
Copy link
Contributor

@Renstrom It adjusts the help-topic depending on what's under the cursor.

@lithammer
Copy link
Contributor Author

Ah, so it's just a bit more intelligent than this solution?

@vheon
Copy link
Contributor

vheon commented Jul 26, 2015

@Renstrom yes

@justinmk no, absolutely. I was just thinking to do it right once, since the solution is already available.

@ghost ghost changed the title Set 'keywordprg' for vim and help filetypes. [RFC] Set 'keywordprg' for vim and help filetypes. Jul 26, 2015
@ghost
Copy link

ghost commented Jul 26, 2015

This should be mentioned in vim_diff.txt.

Besides that I've used this for a while, and while it mostly works fine I've always had the following issue:

  • open empty buffer, :setf help
  • create the buffer contents |help-context|
  • put cursor on first letter and press K, taken to *help* tag
  • put cursor on c and press K, taken to *:syn-context* tag

I just tried :set iskeyword+=- and it seems to fix it, but I'm not sure if it will work in all cases.

@marvim marvim added the RFC label Jul 26, 2015
@fmoralesc
Copy link
Contributor

@pyrohh It's weird you had to do that, since the help on 'iskeyword' says:

For a help file it is set to all non-blank printable characters except
'*', '"' and '|' (so that CTRL-] on a command finds the help for that
command).

I think that is not true.

@lithammer
Copy link
Contributor Author

In the case of using the scriptease version, where would one put the s:helptopic() function?

@fmoralesc
Copy link
Contributor

I would suggest you put it in some file in runtime/autoload, so you can call it from both vim and help files, and it only gets defined on demand.

You'll also need to modify it so it can work standalone, as it stands it uses some other stuff from scriptease.

@lithammer lithammer force-pushed the set-keywordprg-for-vim-and-help branch 2 times, most recently from 949e950 to 34b9794 Compare September 16, 2015 19:57
@lithammer
Copy link
Contributor Author

Ported the functionality from vim-scriptease.

return reverse(map(synstack(line, col), 'synIDattr(v:val,"name")'))
endfunction

function! HelpTopic()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since you are using autoload file you must use help#topic() (help is because file is named {rtp}/autoload/help.vim).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also missing abort.

@ZyX-I
Copy link
Contributor

ZyX-I commented Sep 16, 2015

@neovim/core Also what about tests? In #3270 I assumed that it is bad idea to add any code without testing and put tests for runtime files into test/functional/plugin. I think it is needed to establish an agreement on this matter. E.g. for this issue it needs to test that K opened in help and vim files opens right topics.

let post = getline('.')[col : -1]
let syn = get(synnames(), 0, '')
let cword = expand('<cword>')
if syn ==# 'vimFuncName'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The entire function is for .vim files: this and the following conditions will never match in a help file. I think this needs to be altered: topic for functions should be opened if current word is immediately followed by a parenthesis in addition to syn check.

return ':'.cword
elseif pre =~# '\<v:$'
return 'v:'.cword
elseif cword ==# 'v' && post =~# ':\w\+'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same.

@ZyX-I
Copy link
Contributor

ZyX-I commented Sep 16, 2015

By the way, why using help#topic() for help files at all? Simple nnoremap <buffer> K <C-]> should be enough here.

@justinmk
Copy link
Member

what about tests? In #3270 I assumed that it is bad idea to add any code without testing and put tests for runtime files into test/functional/plugin

Yes, we prefer tests. And test/functional/plugin/help_spec.lua would be a good place for it.

@lithammer lithammer mentioned this pull request Sep 23, 2015
6 tasks
@lithammer lithammer force-pushed the set-keywordprg-for-vim-and-help branch from eaa1533 to ce6d317 Compare October 18, 2015 10:15
@josephholsten
Copy link
Contributor

@justinmk @ZyX-I @Renstrom what's remaining to get this completed? I'm personally happy with autocmd Filetype vim setlocal keywordprg=:help, but this fancier impl seems close.

Peter Renström added 5 commits July 8, 2017 00:20
Open the Vim help file instead of 'man' when pressing 'K' in normal
mode.

Credits to Tim Pope for the original implementation in vim-scriptease.
@lithammer lithammer force-pushed the set-keywordprg-for-vim-and-help branch from 759316d to a13ea1d Compare July 7, 2017 22:20
@lithammer
Copy link
Contributor Author

lithammer commented Jul 7, 2017

I tried to address some comments and rebased since this was two years old. Unfortunately I'm quite bad a Vimscript.

return "'" . cword . "'"
elseif pre =~# '&$' || pre =~# '&[lg]:$'
return "'" . cword . "'"
elseif pre =~# 'set\s\+$' || pre =~# '\vsetl(ocal)?\s+$' || pre =~# '\vsetg(lobal)?\s+$'
Copy link
Member

@mhinz mhinz Jul 8, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This matches setl and setlocal, but not setloc. Use this instead:

elseif pre =~# '\vset?\s+$' || pre =~# '\vsetl%[ocal]\s+$' || pre =~# '\vsetg%[lobal]\s+$'

endif
let g:loaded_help = 1

function! help#topic() abort
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this function obvious enough that it doesn't need a comment? I'm too green to judge. Would it qualify as obvious if it had tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly, I barely know myself since this was blatantly copied from https://github.com/tpope/vim-scriptease/blob/59a73a2415ea1b006ae3e91163ddde24e8540844/autoload/scriptease.vim#L693-L723. Initially this pull request only contained a simple keywordprg=:help, but then it was suggested to use vim-scriptease's more intelligent lookup.

But in short, this function looks at the word under the cursor (e.g. what syntax group it has), and on the word(s) coming before and after.

@justinmk
Copy link
Member

justinmk commented Jul 8, 2017

Contrary to #3104 (comment) I think it's now a good time to include scriptease as a standard plugin. @tpope do you have any objection to that?

@lithammer
Copy link
Contributor Author

What does it really mean to include as a standard plugin?

@justinmk
Copy link
Member

justinmk commented Jul 8, 2017

@Renstrom It means include the plugin in runtime/pack/dist/start/scriptease

@justinmk
Copy link
Member

justinmk commented Jul 8, 2017

6720fe2 includes a minimal version of this change.

A new PR including runtime/pack/dist/start/scriptease would be welcome. We would like to establish a workflow for including more plugins as standard plugins in runtime/pack/dist/*, possibly as git subtrees. Help there is welcome.

@justinmk justinmk closed this Jul 8, 2017
@justinmk justinmk removed the RFC label Jul 8, 2017
justinmk pushed a commit that referenced this pull request Jul 8, 2017
@lithammer lithammer deleted the set-keywordprg-for-vim-and-help branch July 8, 2017 14:13
@tpope
Copy link
Contributor

tpope commented Jul 8, 2017

No objection. I would recommend sticking to stable releases rather than tracking master, though with Neovim still in development maybe that doesn't matter.

@ZyX-I
Copy link
Contributor

ZyX-I commented Jul 8, 2017

Neovim is indeed in development and here we at least wait for CI before merging patches, so I would rather suggest master.

justinmk added a commit to justinmk/neovim that referenced this pull request Nov 8, 2017
FEATURES:
0e873a3 Lua(Jit) built-in neovim#4411
5b32bce Windows: `:terminal` neovim#7007
7b0ceb3 UI/API: externalize cmdline neovim#7173
b67f58b UI/API: externalize wildmenu neovim#7454
b23aa1c UI: 'winhighlight' neovim#6597
17531ed UI: command-line coloring (`:help input()-highlight`) neovim#6364
244a1f9 API: execute lua directly from the remote api neovim#6704
45626de API: `get_keymap()` neovim#6236
db99982 API: `nvim_get_hl_by_name()`, `nvim_get_hl_by_id()` neovim#7082
dc68538 menu_get() function neovim#6322
9db42d4 :cquit : take an error code argument neovim#7336
9cc185d job-control: serverstart(): support ipv6 neovim#6680
1b7a9bf job-control: sockopen() neovim#6594
6efe84a clipboard: fallback to tmux clipboard neovim#6894
6016ac2 clipboard: customize clipboard with `g:clipboard` neovim#6030
3a86dd5 ruby: override ruby host via `g:ruby_host_prog` neovim#6841
16cce1a debug: $NVIM_LOG_FILE neovim#6827
0cba3da `:checkhealth` built-in, validates $VIMRUNTIME neovim#7399

FIXES:
105d680 TUI: more terminals, improve scroll/resize neovim#6816
cb912a3 :terminal : handle F1-F12, other keys neovim#7241
619838f inccommand: improve performance neovim#6949
04b3c32 inccommand: Fix matches for zero-width neovim#7487
60b1e8a inccommand: multiline, other fixes neovim#7315
f1f7f3b inccommand: Ignore leading modifiers in the command neovim#6967
1551f71 inccommand: fix 'gdefault' lockup neovim#7262
6338199 API: bufhl: support creating new groups neovim#7414
541dde3 API: allow K_EVENT during operator-pending
8c732f7 terminal: adjust for 'number' neovim#7440
5bec946 UI: preserve wildmenu during jobs/events neovim#7110
c349083 UI: disable 'lazyredraw' during ui_refresh. neovim#6259
51808a2 send FocusGained/FocusLost event instead of pseudokey neovim#7221
133f8bc shada: preserve unnamed register on restart neovim#4700
1b70a1d shada: avoid assertion on corrupt shada file neovim#6958
9f534f3 mksession: Restore tab-local working directory neovim#6859
de1084f fix buf_write() crash neovim#7140
7f76986 syntax: register 'Normal' highlight group neovim#6973
6e7a8c3 RPC: close channel if stream was closed neovim#7081
85f3084 clipboard: disallow recursion; show hint only once neovim#7203
8d1ccb6 clipboard: performance, avoid weird edge-cases neovim#7193
01487d4 'titleold' neovim#7358
01e53a5 Windows: better path-handling, separator (slash) hygiene neovim#7349
0f2873c Windows: multibyte startup arguments neovim#7060

CHANGES:
9ff0cc7 :terminal : start in normal-mode neovim#6808
032b088 lower priority of 'cursorcolumn', 'colorcolumn' neovim#7364
2a3bcd1 RPC: Don't delay notifications when request is pending neovim#6544
023f67c :terminal : Do not change 'number', 'relativenumber' neovim#6796
1ef2d76 socket.c: Disable Nagle's algorithm on TCP sockets neovim#6915
6720fe2 help: `K` tries Vim help instead of manpage neovim#3104
7068370 help, man.vim: change "outline" map to `gO` neovim#7405
@justinmk justinmk mentioned this pull request Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defaults Nvim defaults for options, colorscheme/theme, autocmds/events, etc. runtime funtime
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants