Skip to content

Commit

Permalink
Minimal vimrc please
Browse files Browse the repository at this point in the history
  • Loading branch information
@liuchengxu
liuchengxu committed Jun 20, 2020
1 parent dffbb04 commit b940914
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,11 @@ _Instructions: Replace the template text and remove irrelevant text (including t

**Environment (please complete the following information):**
- OS: ???

- (Neo)Vim version: ???
<!-- Output of `git rev-parse --short HEAD` in vim-which-key directory. -->
- vim-which-key version: ???
<!-- Without a minimal vimrc, this issue might be closed directly. -->
- Have you reproduced with a minimal vimrc: ???

**Describe the bug**
Expand All @@ -29,6 +32,8 @@ set nocompatible
set runtimepath^=/path/to/vim-which-key
syntax on
filetype plugin indent on

This comment has been minimized.

Sign in to view

Copy link
@mmrwoods

mmrwoods Aug 27, 2023

Contributor

Might be worth adding set noloadplugins be added after filetype plugin indent on here, otherwise plugins installed as vim packages may be loaded automatically.

This comment has been minimized.

Sign in to view

Copy link
@liuchengxu

liuchengxu Aug 27, 2023

Author Owner

Good to know that, feel free to send a PR!

This comment has been minimized.

Sign in to view

Copy link
@mmrwoods

mmrwoods Aug 27, 2023 •
edited
Loading

Contributor

ok, scratch that, using noloadplugins will actually prevent vim-which-key from being loaded (unless it is loaded using packadd), but you could use set packpath=$VIMRUNTIME after set runtimepath^=/path/to/vim-which-key to avoid automatically loading other plugins installed as vim packages.

This comment has been minimized.

Sign in to view

Copy link
@liuchengxu

liuchengxu Aug 27, 2023

Author Owner

If I read it correctly, set noloadplugins is equivalent to the command line argument --noplugin here from :h 'noloadplugins'. That being said, it should work the same as vim -u min.vim --noplugin. No big deal anyway, it shouldn't be a blocker to reproduce the issue in most cases.
" Here place the configuration that can cause this issue.
```

2. Start (neo)vim with command: `vim -u min.vim`
Expand Down

0 comments on commit b940914

Please sign in to comment.