I wonder if using s:lencompare on the list from s:find / s:runtime_globpath would make sense.

I am having an issue with neobundle where it adds itself to the &rtp and has a copy of all help files in a doc directory therein (Shougo/neobundle.vim#269).

Then I've tried to use :Vedit doc/foo.txt to get to the original help file as a workaround, and noticed that it does not appear to prefer the shorter path.

Unfortunately, when navigating to any link to another vim manual entry and uppercase K doesn't work. But a usual :h %entry% works. What am I doing wrong?

I prefer to use screenspace conservatively, so I use a single-line guard.
For example, I do the following in Node.js for Vim's node.vim file:

if exists("g:loaded_node") || &cp || v:version < 700 | finish | endif
let g:loaded_node = 1

I have a feeling Scriptease doesn't unlet that Guard and thereby fails to reload the code.

Particularly I mean the preview window triggered by :Verbose ...

I think it would be even more convenient to have a command (something in the spirit of :Vfind or $ which -a vim) which searches all vim recognized subfolders:

This is a list of directories which will be searched for runtime
files:
  filetype.vim  filetypes by file name |new-filetype|
  scripts.vim   filetypes by file contents |new-filetype-scripts|
  autoload/ automatically loaded scripts |autoload-functions|
  colors/   color scheme files |:colorscheme|
  compiler/ compiler files |:compiler|
  doc/      documentation |write-local-help|
  ftplugin/ filetype plugins |write-filetype-plugin|
  indent/   indent scripts |indent-expression|
  keymap/   key mapping files |mbyte-keymap|
  lang/     menu translations |:menutrans|
  menu.vim  GUI menus |menu.vim|
  plugin/   plugin scripts |write-plugin|
  print/    files for printing |postscript-print-encoding|
  spell/    spell checking files |spell|
  syntax/   syntax files |mysyntaxfile|
  tutor/    files for vimtutor |tutor|

Occasionally, it is not clear whether the file you have in mind is in ftplugin, plugin, autoload or you know that there is only a scriptease.vim in the folder plugin so you do not have to prepend the expected foldername. Instead of typing :Ve plugin/scriptease.vim you can enter :Vf scriptease.vim.

Do you have a plan for supporting dictionary functions for :Breakadd?
Script using dictionary functions is often long and difficult to understand, so adding this feature will be incredibly helpful for us.

I often :verb map or :verb set to find out which file is responsible for configuration – but need to manually go the file itself. :Verbose map is better – at least I can jump to the file – but still have to handle the line number manually.

It would be great if :Verb map and :Verb set loaded results in the quickfix list.

Consider the following simple foo.vim file:

function! s:Foo()
    let x = 2
    return x + 1
endfunction

echo s:Foo()

Now if I open nvim and do Breakadd here inside the s:Foo function I get and error saying

Could not determine script id

If I now run :Runtime on that file and repeat the process of setting the breakpoint inside the function then the breakpoint is correctly set. So my question is: is it possible to set a breakpoint within an s: function without having to run :Runtime first? I guess the answer is no but any pointer/explanation is appreciated. Thanks in advance.

I found myself wanting to look through all my autocmds and the only way I could think to do it was redirecting the output of autocmds to a register and pasting that into a new buffer. Any chance you'd consider adding a command to handle that more easily for arbitrary commands? Something like :Redir autocmds. I think it matches the intent of e.g. :Messages.

Hi,
when I saw vim-scriptease supports projections I thought they would automatically work for any vim project. Here's the use-case:

$ cd vim-ruby
$ vim
:Eftp<tab> # doesn't work ??

This scenario works:

:Vedit ftplugin/ruby
:Esyntax ruby

Are there plans for supporting the first use case?

Thanks!

Ok, I have dived (diven? dove?) headfirst into pimping [g]Vim into the code editor I need it to be. I do node/javascript. I have the start of a javascript.vim indent module from https://github.com/nikmartin/vim-javascript. But it has bugs. I want to fix those bugs. You appear to be a Vim god among men. Do you have a recommendation for a reference on getting started debugging vim scripts? I got :help debug-scripts but there has to be something better than step step step step to wade through an indent script every f-ing time I hit a right bracket to try to debug why my brackets indenting sucks. Any suggestions?

For example, try running :Scriptnames followed by :cfdo echo % - nothing happens. I'd expect the filenames to be echoed.

Hello,

Some commands in vim-scriptease are defined with the -range=N attribute, and can be prefixed with a count. This is the case, as an example, for the :Verbose command, to temporarily increase Vim's verbosity level.

Since Vim's patch 8.1.1241, the command doesn't always work anymore. That is, if you prefix :Verbose with a count greater than 1, in an empty buffer, Vim complains with the error E16: Invalid range.

I think that's because the range is interpreted as the line of an address, and there's no line whose address is greater than 1 in an empty buffer.

Here's a MWE:

com! -range=1 Cmd echo 'test'

Run :3Cmd in an empty buffer, and E16 will be raised.

I think the solution is to specify that the type of the range is other (which doesn't exist yet in Nvim):

com! -range=1 -addr=other Cmd echo 'test'
              ^^^^^^^^^^^

At least, it does fix the issue on my machine.

Do you think that Vim's patch 8.1.1241 introduced a regression, or is it working as intended, and you're now expected to use -addr=other whenever you want to use -range for some arbitrary count, not tied to any specific type (line address, buffer number, window number, ...)?

Hi, I was playing around with the <K> mapping and there may be a bug for Plug in these contexts:

Plug 'tpope/vim-scriptease'  # 1st column
  Plug 'tpope/vim-scriptease'  # with tab

Not sure if it's my setup, but maybe someone can verify. I guess it has to do with scriptease#helptopic() and an uppercase char as the 1st char of the line.

Sorry if this is just uninformed, but I am having a really hard time wrapping my head around what the workflow is supposed to be with this.

In trying to debug a vim plugin which is active for a certain filetype (vimwiki, .wiki files).

Upon certain keyboard actions (pressing o or Enter on a specific line in the .wiki file), some vimwiki-specific functions are invoked which cause a noticeable slowdown.

I was able to get the following to work so far, using Vim's standard debug functionality:

:123  "go to specific line
:debug normal o  "Insert a new line. This command is very slow.
:breakadd func vimwiki#lst#kbd_o

This makes the debugger break on kbd_o and I can step and echo variables.

But all the action happens in some other local "s:" functions, for which :breakadd apparently does not work.
This is what :Breakadd (according to the documentation) supports, but it is only available when inside a vimscript file.

Since these "s:" functions are not pure functions, but work on some non-trivial buffer contents, I (believe I) can't just call them with their arguments while inside the Vimscript file where they are defined.

Is it possible to add a breakpoint for this local function and still start debugging like described above?

Sometimes I just want to grep through the vim plugins, I can easily write something on my own but feel like this plugin might be a good place for this.

If you think there's value, I can work on a PR.

I've found that vim-scriptease removes the colon from iskeyword:

It mentions that this would break tags, but for me removing : breaks tags, since a colon is included with script-local functions (s:foo).

You are not using https://github.com/universal-ctags/ctags then, are you?

I'd like to add some behavior to the Verbose preview window. Please consider adding a (scriptease specific filetype to the preview window scriptease#verbose_command() to give a hook to trigger modifications off of.
Among other things, I'd add a <nowait> to the q mapping, but I'd consider some personal navigation commands etc.
I'd expect it could be as simple as adding another command, set ft=scripteaseverbose, into the exe chain.

You might want to add the following mappings to your plugin. It's pretty handy I think.

https://github.com/sjl/dotfiles/blob/master/vim/vimrc#L368-L370
https://github.com/rainerborene/dotfiles/blob/master/vimrc#L380-L381

What do you think?

Hi tpope, I wrote a small plugin that greps through &rtp & scriptnames, which I've found useful for hacking on vim.

When I shared it on r/vim, it was suggested to me that I should turn it into a PR for scriptease, which makes sense to me, especially since I used a couple of your functions (scriptease#capture & scriptease#scriptnames_qflist) anyway.

So if you think these 2 features are good additions, just let me know.

in the spirit of :Messages, :Scriptnames.

Right now I do following to the see full report which is usually longer than the screen.

:syntime on
" scroll in file with slow syntax file (e.g. tex with vimtex and fontawesome5 latex syntax)
:redir > syntimereport.txt
:syntime report
:e syntimereport.txt

I am not sure if it is possible to get the actual lines of the syntax groups in the syntax file. Vim help mentions that the name is not necessarily unique:

			NAME		Name of the syntax item.  Note that
					this is not unique.

Maybe loading the report into the preview window for full view and easy navigation would be a first step.

I see that the plugin define some mappings, is there a way to disable them to make sure they are not clashing with other plugins or definitions?