Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Carryover Tags are not functioning as expected. #1571

Open
2 tasks done
evpeople opened this issue Sep 5, 2024 · 0 comments
Open
2 tasks done

The Carryover Tags are not functioning as expected. #1571

evpeople opened this issue Sep 5, 2024 · 0 comments
Labels
bug Issues related to bugs. Please attach a severity, a priority and category with this label.

Comments

@evpeople
Copy link

evpeople commented Sep 5, 2024

Prerequisites

  • I am using the latest stable release of Neovim
  • I am using the latest version of the plugin

Neovim Version

NVIM v0.10.1 Build type: Release LuaJIT 2.1.1724512491

Neorg setup

      require("neorg").setup({
        load = {
          ["core.defaults"] = {},
          ["core.export"] = {},
          ["core.export.markdown"] = {},

          ["core.ui"] = {},
          ["core.completion"] = { config = { engine = "nvim-cmp", name = "[Norg]" } },
          ["core.integrations.nvim-cmp"] = {},
          ["core.ui.calendar"] = {},
          ["core.summary"] = {},
          ["core.concealer"] = {
            config = {
              icon_preset = "diamond",
              icons = {
                code_block = { conceal = true },
              },
            },
          }, -- Adds pretty icons to your documents
          ["core.dirman"] = {
            config = {
              workspaces = {
                my_ws = "~/code/my_neorg/", -- Format: <name_of_workspace> = <path_to_workspace_root>
              },
              default_workspace = "my_ws",
              index = "index.norg", -- The name of the main (root) .norg file
            },
          },
          ["external.templates"] = {
            config = {
              templates_dir = "/users/evpeople/code/my_neorg/templates",
              default_subcommand = "fload", -- or "fload", "load"

              keywords = { -- Add your own keywords.
                YESTERDAY_OF_ORG = function() -- detect date from filename and return in org date format
                  local ls = require("luasnip")
                  local s = require("neorg.modules.external.templates.default_snippets")
                  return ls.text_node(s.parse_date(-1, s.file_name_date(), [[../../%Y/%m/%d]])) -- 2006/11/01
                end,
                TODAY_OF_ORG = function() -- detect date from filename and return in org date format
                  local ls = require("luasnip")
                  local s = require("neorg.modules.external.templates.default_snippets")
                  return ls.text_node(s.parse_date(0, s.file_name_date(), [[%Y/%m/%d]])) -- 2006/11/01
                end,
                TOMORROW_OF_ORG = function() -- detect date from filename and return in org date format
                  local ls = require("luasnip")
                  local s = require("neorg.modules.external.templates.default_snippets")
                  return ls.text_node(s.parse_date(1, s.file_name_date(), [[../../%Y/%m/%d]])) -- 2006/11/01
                end,
              },
            },
          },
        },
      })

Actual behavior

    #name awesome quotes
    > This is a quote.
    > We can talk about anything we like

    This quote now has a /name/! You can link to it with the magic char: {# awesome quotes}!

When I press <CR> on {# awesome quotes} , it doesn't jump to the #name awesome quotes above, but instead reports an error: "link not found".

Expected behavior

core.esupports.hop can find the link

Steps to reproduce

create a file with

**** Name

    #name awesome quotes
    > This is a quote.
    > We can talk about anything we like

     This quote now has a /name/! You can link to it with the magic char: {# awesome quotes}!

then press <CR> on {# awesome quotes}

Potentially conflicting plugins

No response

Other information

No response

Help

None

Implementation help

No response

@evpeople evpeople added the bug Issues related to bugs. Please attach a severity, a priority and category with this label. label Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues related to bugs. Please attach a severity, a priority and category with this label.
Projects
None yet
Development

No branches or pull requests

1 participant