- Try files with non word char in it's name, like "PHP (HTML)", "Tcl/Tk" "ActionScript 2.0" no idea if this is a problem when used as config group name
- Reply the comments in the diff
Details
Diff Detail
- Repository
- R40 Kate
- Lint
Lint Skipped - Unit
Unit Tests Skipped
It would add a some code complexity, but I'm not sure it adds so much value that it would be worth it.... If you want the tree-mode for one file type, the probability is quite high that you want it for the other types too. I don̈́'t remember any bug report that would request that feature... Are you asking for it? ;)
Sorry to hear that you are not interested any more :(
Thanks for your work so far!
I would still would want to integrate get your Normal parser as a Markdown parser if you are OK with that.
I would still would want to integrate get your Normal parser as a Markdown parser if you are OK with that.
Feel free to do as you like.
But consider that I intend to offer in a couple of days/weeks my own version of your plugin to the attention of Kate developers. These will have a "Normal" and a "Markdown" parser besides of a couple of other modifications.
The probability that this is unchanged accepted is of cause not very large. And my willingness to follow some modification request is pretty limited when it sounds for me incomprehensible or overwhelmed my abilities.
So, in the near future I must make a decision where to host my plugin. Any suggestions? Is there a place below KDE where I can upload it which give the Kate developers some benefit but I have still full control?
In case of a refusal I like to make it available to the public as independent compilable addon, so that new home of my plugin must offer this possibility.
Regards, Lothar