doganalper/template.nvim

File template plugin based on buffer filetype

Hi 👋 I'm Alper

Curious Frontend Developer

• 🌍  I'm based in Istanbul, Turkey currently
• ✉️  You can contact me at [email protected]
• 🧠  I'm learning Go and Typescript 🥽
• ⚡  I might bore you with my questions!

Skills

Socials

Badges

My GitHub Stats

template.nvim's Issues

Better README file

An option to switch templates

• User may switch templates if current filetype has multiple templates.
• Switching template will cause to delete content of current buffer.
• Possible telescope extension here would be good.

Modularization of functions/templates

• Currently all code is on same file.
• Separate codes into chunks

Feature for jumping locations after setting template

• Example for this feature is LuaSnip

When I created the file and wrote the file template, an error occurred

Thank you for your work. This plugin is what I need, but I encountered the following error while using it:

msg_show.lua_error Error executing vim.schedule lua callback: ...share/nvim/lazy/template.nvim/lua/template/internals.lua:76: attempt to yield across C-call boundary
stack traceback:
[C]: in function 'yield'
...share/nvim/lazy/template.nvim/lua/template/internals.lua:76: in function 'cb'
...ocal/share/nvim/lazy/dressing.nvim/lua/dressing/util.lua:206: in function <...ocal/share/nvim/lazy/dressing.nvim/lua/dressing/util.lua:202>

Do I need to install other supporting plugins for this?

only the Vue filetype are triggered

Thank you so much for your help!
After fixing it, I found that when there are multiple file types, only the Vue files are triggered. Is it because my config file is not configured properly, or is there something else?

return {
  { "stevearc/dressing.nvim", event = "VeryLazy" },

  {
    "doganalper/template.nvim",
    event = "VeryLazy",
    config = function()
      require("template").setup({
        -- custom config
        mappings = {
          switch_template = "<leader>cg",
        },
        templates = {
          vue = {
            {
              name = "Vue 2 JS",
              template = {
                "<template>",
                "<div>",
                "</div>",
                "<template>",
                "",
                "<script>",
                "export default {}",
                "</script>",
              },
            },
            {
              name = "Vue 2 Ts",
              template = {
                "<template>",
                "<div>",
                "</div>",
                "</template>",
                "",
                '<script lang="ts">',
                "import Vue from 'vue';",
                "export default Vue.extend({})",
                "</script>",
              },
            },
            {
              name = "Vue 3",
              template = {
                '<script lang="ts" setup></script>',
                "",
                "<template></template>",
              },
            },
          },
          markdown = {
            {
              name = "bast template",
              template = {
                "---",
                "title:",
                "categories: [ ]",
                "tags: [ ]",
                "date:",
                "---",
              },
            },
            {
              name = "bas1 template",
              template = {
                "---",
                "title:",
                "categories: [ ]",
                "tags: [ ]",
                "date:",
                "---",
              },
            },
          },
          Java = {
          {
              name = "Java template",
              template = {
                "// java template",
              },
            }
          }
        },
      })
    end,
  },
}

Option for extending templates

• Currently whenever user passes templates on options for plugin, it will replace any existing templates for that filetype.
• Instead of replacing all, this feature will add given templates to existing templates on default opts.
• If any names collides, user given template will be prioritized.