Skip to content
This repository has been archived by the owner on Jan 14, 2024. It is now read-only.

Check list for when opening a bug report issue #43

Open
fenetikm opened this issue Nov 6, 2020 · 3 comments
Open

Check list for when opening a bug report issue #43

fenetikm opened this issue Nov 6, 2020 · 3 comments

Comments

@fenetikm
Copy link
Collaborator

fenetikm commented Nov 6, 2020

First check the following:

  • Latest version of neuron
  • Latest version of this plugin
  • You have a neuron.dhall file in you zettelkasten directory

Helpful information to know when reporting a bug:

  • Vim or NeoVim
  • List of steps followed when you saw the bug including the zettel
@fenetikm fenetikm pinned this issue Nov 6, 2020
@fenetikm fenetikm changed the title New issue check list Check list for when opening a bug report issue Nov 6, 2020
@lehmacdj
Copy link

lehmacdj commented Jan 2, 2021

You should create a issue template for this list instead of just a issue, so that everyone sees it when creating an issue: https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/about-issue-and-pull-request-templates.

@fenetikm
Copy link
Collaborator Author

fenetikm commented Jan 3, 2021

Great idea @lehmacdj - @fiatjaf could you please do that or give me permission to do so?

@em429
Copy link

em429 commented Jan 23, 2021

First check the following:

* Latest version of neuron

* Latest version of this plugin

* You have a `neuron.dhall` file in you zettelkasten directory

Helpful information to know when reporting a bug:

* Vim or NeoVim

* List of steps followed when you saw the bug including the zettel

There have been some major breaking changes lately in neuron, e.g. tag querying moved to its own plugin, query command and json output completely changed..etc -- so current neuron doesn't work anymore with current neuron.vim.

Latest 'release' works, so I think the above can be a bit confusing for new users as neuron's install page recommends installing from master.

Probably should also be mentioned in the readme.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants