Function List: Is file extension of User Defined Language still working?
-
. It seems the function list parser is not triggered by the file’s extension but by the language type
I’m doing this ticket:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/4896With ext it makes new implementation more complex so less easy to maintain. Since ext part doesn’t work, I will remove this part.
-
@donho see also #298 and Function List known issue #4
-
@MAPJe71
Hmm… I think the file ext to apply function list is not necessary anymore. Users can set several exts in UDL, and once the file is recognized as UDL, function list will work on it if its parser is present. -
So to have working list we need two things, a parser and a UDL file (even without styles)?
-
Although in the case of UDL it’s obvious. There was no question.
-
@donho
The problem of FL ext not working is that it requires an UDL i.e. you can’t use an FL parser without an UDL. -
@ArkadiuszMichalski appearently beat me to it.
You need both FL parser and UDL (can be a “dummy” i.e. with name and extension but without styles) because FL ext does not work. -
Furthermore, for every UDL FunctionList parser deployed with Notepad++ you would also have to include the UDL definition in order for those parsers to work.
-
So to have working list we need two things, a parser and a UDL file (even without styles)?
Yes. Set an empty UDL with the exts + the name via the UDL dialog - it took me 5 seconds only.
Furthermore, for every UDL FunctionList parser deployed with Notepad++ you would also have to include the UDL definition in order for those parsers to work.
Not necessary. A simple explanation in npp-user-manual will be enough.
-
@donho But few UDL is not problem, what if someone has to make a lot of them and gets a trash on the menu?
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/4896#issuecomment-706421610
