#253 Hyperlinks: Defining own hyperlinks

open
nobody
None
3
2011-09-05
2011-09-05
Jarek Czekalski
No

Doc says only "other plugins can provide their own links". I guess it's done by means of services. Would be nice to be able to specify links' syntax in some simpler way, like xml definitions. I've been using an editor which could be configured to enable links for any external program, with arguments. I configured it to recognize patterns like: [program.exe arg1 arg2].

The XML definition could consist of 3 pieces:
link_regexp
link_type=<open|edit|command>
command - for command type, with references $1 allowed

I'm surprised currently links can only be opened in editor, not with Desktop.

Discussion

    • priority: 5 --> 3
    • summary: Defining own hyperlinks --> Hyperlinks: Defining own hyperlinks
     
  • Patrick Eibl
    Patrick Eibl
    2012-09-17

    Looks like I had the same idea, but only just found this now. I created a ConfigurableHyperlinks plugin which is in svn and has been submitted to the plugin tracker. Give it a try and let me know what you think.

     
  • I think I'll give it a try, when I feel the need for this feature again. But in general creating a new plugin to enhance another one is a bad idea. Think how many plugins will jEdit have in several years, if they all evolve this way. How is the user going to find something then? Open source software developers should cooperate in creating a common work, not many independent pieces.

    And I know there are obstacles on the way to achieve this common work: developers ignore others' patches, don't like other people to work on their code and finally everyone wishes to have a software of his own. Anyway we should try to work on a common goal, not divide the open source software into countless parts, even if it's much easier. We need to learn to cooperate efficiently.

     
  • Patrick Eibl
    Patrick Eibl
    2012-09-18

    Good point, I agree. I originally coded this within the Hyperlinks plugin, but was concerned about mucking with someone else's code, which is why I separated it.

    I'll check with Matthieu whether he would be fine with me merging this functionality into Hyperlinks.