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

Specially-named scripts aren't found #19

Open
Kebap opened this issue Jul 4, 2021 · 0 comments
Open

Specially-named scripts aren't found #19

Kebap opened this issue Jul 4, 2021 · 0 comments

Comments

@Kebap
Copy link

Kebap commented Jul 4, 2021

In addition to #9 I now tested the following names (for triggers highlighting web-links etc.)

  1. http(s) und www.lua (edit: My bad, this file 1 needed underscores and not space characters (stupid caveat))
  2. mud@mg.mud.de.lua

Muddler finds the triggers.json and creates the objects alright, only they have no scripts inside.
Seems like muddler didn't find the corresponding lua files after all? Because of the @ character maybe?

Here is the relevant triggers.json excerpt for your comparison:

[
  {
    "name": "http(s) und www",
    "highlight": "no",
    "patterns": [ 
      {
        "pattern": "(?i:https?:\\/\\/\\S*)",
        "type": "regex",
        "comment": "accepted trigger types are 'substring', 'regex', 'startOfLine', 'exactMatch', 'lua', 'spacer', 'color', 'colour', and 'prompt'"
      },
      {
        "pattern": "(?i:www\\.\\S*)",
        "type": "regex"
      }
    ]
  },
  {
    "name": "mud@mg.mud.de",
    "patterns": [
      {
        "pattern": "mud@mg.mud.de",
        "type": "substring"
      }
    ]
  }
]

Am I doing it wrong?

Workaround: - renamed file 2 to not use "@" and now it works as expected

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

No branches or pull requests

1 participant