Every day I work using Stata and the new UDL is super useful for Stata syntax; beautiful, easy to use and to understand. Before NP++ 6.2 the previous UDL worked fine for Stata syntax but with a lot of limitations that UDL 2.0 does not have now. Although, I am having two different kinds of problem with the new UDL:
1. Folding in code is not working properly
For working with loops I need to use curly braces {} for open and close the loop, respectively. This is precisely what I need to fold. With the new UDL the folding in code is not working fine and it is opening and closing on anywhere different than the lines with the curly braces. Sometime to temporally solve the problem I type and erase immediately a “comment character” (which in Stata is the star or asterisk *) at the beginning of the line with the open folding brace “{“ and it rearranges the folding line in the left side of the screen, but not always works. Additionally, sometimes when I type something in the middle of the loop, the “folding in code” structure stops working.
2. Delimiters using double quotes (“”) are not working fine
In Stata, double quotes (“”) delimit string characters. In occasions the delimiter stops working and assigns the same style to the whole program. One way I found to fix this is cut the first line in the code just after the delimiter style start working wrong and I paste it then at the end of the last line working correctly. Finally I reverse the procedure above and the delimiter works fine again.
My officemate has the same problems and we two think this makes very uncomfortable to work with NP++.
Any help is highly appreciated.
Best,
Pablo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding the two issues discussed yesterday, these are the examples of the problems:
Example 1: As I told you before, my open and close characters for folding in code are { and }, respectively. In this example the folding should not start in line 21 but in line 22; it should start a new folding in line 23 but it doesn’t; it should open a new folding in line 35 and close it in line 37. Instead it starts in line 34, close in line 36 and open a new folding in line 38 when it should not do so.
I am trying to get for you an example of the other issue about the double quotes (“”) but it happened suddenly and right now it seems to be working fine. I’ll send it to you as soon as I get.
Finally, you can see my userDefineLang.xml file attached.
Please, let me know if this enough or you need anything else. I am completely willing to help with this issue.
Regarding the problems with the double quotes, this is an example;
Figure 1 shows the way the highlight is supposed to work properly. In figure 2 you can see the delimiters (“”) are working reversely and the comments line are not working. As you can see also, the way I found to fix the problem was moving up and then down all the lines until it fix by itself. Although it might happen that suddenly, while I am typing some code below, it starts working wrong way again.
Figure1
Figure 2
Thank you,
Pablo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
both issues were already reported and both were solved. Unfortunately, code got lost when I had a HDD failure last week. So, until I re-write the same thing (it might take weeks) you should try your luck with last beta version that I updated to github: https://github.com/Loreia/UDL2/downloads
I believe it contains solution for both problems.
Please report here if it helps.
BR
Loreia
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you so much for your response. Although, what am I supposed to do with the file “SciLexer2.dll”? I copied it in the NotePad ++ folder (C:\Program Files\Notepad++) and now NP++ is not opening. Do I have to do something with the file “SciLexer.dll”? Perhaps, should I replace it for “SciLexer2.dll”? Can you please guide me on this?
Thank you.
Pablo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First of all thanks all of you for your great job, I'm an studen and I hope soon know enought to help you (If I may help you to translate the new buttons, menus, etc from English to Spanish please tell me how and I'll do).
I'm trying to define my own language but I'm having trouble with Folding In Code Styles with spaces like in the image attached (Sorry, I didn't know how to show it here)
In the first "Fin si" it doesn't close right, but the second "FIN SI" yes and I have checked the Ignore MAY./min.
In the first it just mark it as the Open but not as the close correct word.
Unfortunately SciLexer2.dll file didn’t solve the bugs that we discussed few days ago. I am very sorry for your loss; I think it should be very frustrating to lose all the information, and I completely understand that you will take some time to fix this again. Although, I would really like to encourage you to solve this issues soon because, as I told you before, I am promoting NP++ among all my coworkers who work in Stata and I cannot do it now because of this issue. Believe me, we are more or less 20 people working with Stata daily and it could be expanded to many more.
I am very interesting on this, and if you think that I can help you to fix this in any way, please don’t hesitate and let me know. Keep me posted.
Have a nice thanksgiving day.
Pablo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sorry about slow reply, Sourceforge stopped notifying me about new posts on this thread so I was out of loop for a while.
You should download ZIP file and extract it to installation directory. Than close NPP (if it is open) and start Notepad2++.exe (notice number 2 in file name). That will start beta instead of regular version.
Thanks for reporting "ignore case" problem, it will be fixed in next revision of UDL.
About the speed of updating UDL. There isn't much that can be done about it. I am already working on it as hard as I can. You will just have to wait until it is finished.
BR
Loreia
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your reply. I have not been available to try beta version because I am using a corporative desktop and people from IT do not have time for coming to my office (I think they are king of tired of me for making them come so often few weeks before :P ), so I’ll wait until they come and I’ll let you know whether beta version worked or at least solved some or none of the problems.
all the best,
Pablo.
PS: Thank you for working so hard updating the UDL. I am looking forward to use it :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your userDefineLang.xml file is awesome! I hope you don't mind if I use it. However, I have the same problem that you described: open and close characters for folding in code are { and } are floating around on wrong places. Have you been able to solve this problem in the meantime?
Thank you and all the best,
Joze
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am glad you liked it. You are more than welcome to use it. I am sure that as soon as Loreia find the way to solve the folding issue everything will work fine.
Best,
Pablo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After trying to figure out why multipart keywords weren't working for a few minutes, I eventually discovered that multipart keywords don't work if "Ignore case" is enabled.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've found another issue where the highlighting will go away when i do a compare between two files. I've to go back and re apply the UDL to get the highlighting back.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm currently trying to make a custom language formatting, but I keep on bumping into problems.
It seems the language I use (a programming part of the Creo and Pro/E 3D CAD drawing program) uses some strange syntax.
Most parameters exist out of 2 words with a whitespace inbetween
IF --> END IF
ADD FEATURE --> END ADD
ADD SUBASSEMBLY --> END ADD
INPUT --> END INPUT
RELATIONS --> END RELATIONS
Is it possible to make this foldable?
In the keywords I can put these parameters between "" to recognize it as 1 part. But it seems this doesn't work for folding...
An example of the code:
ADD FEATURE (initial number 4)
INTERNAL FEATURE ID 7
TYPE = COORDINATE SYSTEM
NAME = ASM_DEF_CSYS
FEATURE IS IN LAYER(S) :
05__ASM_ALL_DTM_CSYS - OPERATION = SHOWN
05__ASM_DEF_DTM_CSYS - OPERATION = SHOWN
END ADD
ADD SUBASSEMBLY ZADEL_LINKS
INTERNAL COMPONENT ID 40
END ADD
ADD SUBASSEMBLY ZADEL_RECHTS
INTERNAL COMPONENT ID 41
END ADD
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
Finally I got it.
we must used Folding in code 2 style to solve this problem.
Thanks
Hi mahtav,
yes, that would be the solution.
There are two folding in code styles precisely so users could solve this kind of problem.
BR
Loreia
Dear all,
Every day I work using Stata and the new UDL is super useful for Stata syntax; beautiful, easy to use and to understand. Before NP++ 6.2 the previous UDL worked fine for Stata syntax but with a lot of limitations that UDL 2.0 does not have now. Although, I am having two different kinds of problem with the new UDL:
1. Folding in code is not working properly
For working with loops I need to use curly braces {} for open and close the loop, respectively. This is precisely what I need to fold. With the new UDL the folding in code is not working fine and it is opening and closing on anywhere different than the lines with the curly braces. Sometime to temporally solve the problem I type and erase immediately a “comment character” (which in Stata is the star or asterisk *) at the beginning of the line with the open folding brace “{“ and it rearranges the folding line in the left side of the screen, but not always works. Additionally, sometimes when I type something in the middle of the loop, the “folding in code” structure stops working.
2. Delimiters using double quotes (“”) are not working fine
In Stata, double quotes (“”) delimit string characters. In occasions the delimiter stops working and assigns the same style to the whole program. One way I found to fix this is cut the first line in the code just after the delimiter style start working wrong and I paste it then at the end of the last line working correctly. Finally I reverse the procedure above and the delimiter works fine again.
My officemate has the same problems and we two think this makes very uncomfortable to work with NP++.
Any help is highly appreciated.
Best,
Pablo
Hi Pablo,
can you share your userDefineLang.xml file?
BR
Loreia
Sure, How can I do that?? Last time I tried to attached an image and I did not get it…. sorry, so bad using computers.
Pablo.
Dear Loreia,
I am more that willing to share my userDefineLang.xml file with you. How can I do that using this forum? Do you want me to send it to you via email???
In the same sense how can I paste a picture in this forum. As I understand I need to add a link that contains the image, right?? how can I do that??
Thank you,
Pablo.
Dear Loreia,
Regarding the two issues discussed yesterday, these are the examples of the problems:
Example 1: As I told you before, my open and close characters for folding in code are { and }, respectively. In this example the folding should not start in line 21 but in line 22; it should start a new folding in line 23 but it doesn’t; it should open a new folding in line 35 and close it in line 37. Instead it starts in line 34, close in line 36 and open a new folding in line 38 when it should not do so.
I am trying to get for you an example of the other issue about the double quotes (“”) but it happened suddenly and right now it seems to be working fine. I’ll send it to you as soon as I get.
Finally, you can see my userDefineLang.xml file attached.
Please, let me know if this enough or you need anything else. I am completely willing to help with this issue.
Thank you,
Pablo
Last edit: Pablo Bonilla 2012-11-14
Dear Loreia,
Regarding the problems with the double quotes, this is an example;
Figure 1 shows the way the highlight is supposed to work properly. In figure 2 you can see the delimiters (“”) are working reversely and the comments line are not working. As you can see also, the way I found to fix the problem was moving up and then down all the lines until it fix by itself. Although it might happen that suddenly, while I am typing some code below, it starts working wrong way again.
Figure1
Figure 2
Thank you,
Pablo
Hi Pablo,
both issues were already reported and both were solved. Unfortunately, code got lost when I had a HDD failure last week. So, until I re-write the same thing (it might take weeks) you should try your luck with last beta version that I updated to github:
https://github.com/Loreia/UDL2/downloads
I believe it contains solution for both problems.
Please report here if it helps.
BR
Loreia
Dear Loreia,
Thank you so much for your response. Although, what am I supposed to do with the file “SciLexer2.dll”? I copied it in the NotePad ++ folder (C:\Program Files\Notepad++) and now NP++ is not opening. Do I have to do something with the file “SciLexer.dll”? Perhaps, should I replace it for “SciLexer2.dll”? Can you please guide me on this?
Thank you.
Pablo
Hi..., I'm not sure if I found a Bug.
First of all thanks all of you for your great job, I'm an studen and I hope soon know enought to help you (If I may help you to translate the new buttons, menus, etc from English to Spanish please tell me how and I'll do).
I'm trying to define my own language but I'm having trouble with Folding In Code Styles with spaces like in the image attached (Sorry, I didn't know how to show it here)
In the first "Fin si" it doesn't close right, but the second "FIN SI" yes and I have checked the Ignore MAY./min.
In the first it just mark it as the Open but not as the close correct word.
Dear Loreia,
Unfortunately SciLexer2.dll file didn’t solve the bugs that we discussed few days ago. I am very sorry for your loss; I think it should be very frustrating to lose all the information, and I completely understand that you will take some time to fix this again. Although, I would really like to encourage you to solve this issues soon because, as I told you before, I am promoting NP++ among all my coworkers who work in Stata and I cannot do it now because of this issue. Believe me, we are more or less 20 people working with Stata daily and it could be expanded to many more.
I am very interesting on this, and if you think that I can help you to fix this in any way, please don’t hesitate and let me know. Keep me posted.
Have a nice thanksgiving day.
Pablo
Hi Pablo,
sorry about slow reply, Sourceforge stopped notifying me about new posts on this thread so I was out of loop for a while.
You should download ZIP file and extract it to installation directory. Than close NPP (if it is open) and start Notepad2++.exe (notice number 2 in file name). That will start beta instead of regular version.
Thanks for reporting "ignore case" problem, it will be fixed in next revision of UDL.
About the speed of updating UDL. There isn't much that can be done about it. I am already working on it as hard as I can. You will just have to wait until it is finished.
BR
Loreia
Dear Loreia,
Thanks for your reply. I have not been available to try beta version because I am using a corporative desktop and people from IT do not have time for coming to my office (I think they are king of tired of me for making them come so often few weeks before :P ), so I’ll wait until they come and I’ll let you know whether beta version worked or at least solved some or none of the problems.
all the best,
Pablo.
PS: Thank you for working so hard updating the UDL. I am looking forward to use it :)
Dear Pablo,
Your userDefineLang.xml file is awesome! I hope you don't mind if I use it. However, I have the same problem that you described: open and close characters for folding in code are { and } are floating around on wrong places. Have you been able to solve this problem in the meantime?
Thank you and all the best,
Joze
Dear Joze,
I am glad you liked it. You are more than welcome to use it. I am sure that as soon as Loreia find the way to solve the folding issue everything will work fine.
Best,
Pablo
After trying to figure out why multipart keywords weren't working for a few minutes, I eventually discovered that multipart keywords don't work if "Ignore case" is enabled.
Hi everyone,
bugs reported on this thread are now solved.
You can get latest RC and test for yourself.
I would appreciate feedback (both confirmation that bugs are fixed and notification if they were fixed).
https://sourceforge.net/p/notepad-plus/discussion/331753/thread/01f8c28f/?page=19
https://github.com/Loreia/UDL/downloads
BR,
Loreia
Hi Loreia
I've found another issue where the highlighting will go away when i do a compare between two files. I've to go back and re apply the UDL to get the highlighting back.
Hi Celvin,
If you are using compare plugin, you should report this problem to plugin maintainer.
BR,
Loreia
Hello Loreia,
I'm currently trying to make a custom language formatting, but I keep on bumping into problems.
It seems the language I use (a programming part of the Creo and Pro/E 3D CAD drawing program) uses some strange syntax.
Most parameters exist out of 2 words with a whitespace inbetween
IF --> END IF
ADD FEATURE --> END ADD
ADD SUBASSEMBLY --> END ADD
INPUT --> END INPUT
RELATIONS --> END RELATIONS
Is it possible to make this foldable?
In the keywords I can put these parameters between "" to recognize it as 1 part. But it seems this doesn't work for folding...
An example of the code:
ADD FEATURE (initial number 4)
INTERNAL FEATURE ID 7
TYPE = COORDINATE SYSTEM
NAME = ASM_DEF_CSYS
END ADD
ADD SUBASSEMBLY ZADEL_LINKS
INTERNAL COMPONENT ID 40
END ADD
ADD SUBASSEMBLY ZADEL_RECHTS
INTERNAL COMPONENT ID 41
END ADD
Hi Jeroen,
please upgrade to Notepad++ 6.3, and try to define those keywords as "Folding in code 2 " type. It should look something like this:
Direct link in case picture is cut off by sourceforge.
http://i.snag.gy/FGy8b.jpg
BR,
Loreia
Hi,
That works like a charm, thank you!
Hi,
i got a problem with the nested comments like shown in the picture. I also tried your start: '#' end: '((EOL))', but nothing works. Can you help me?
BR Robert
Hi Robert,
where is the problem? You define one delimiter as
start:solution
end:)
and the second one:
start: ?
end: ?
Now, I don't know this:
1. Did you define nesting?
2. What are you trying to achieve?
BR,
Loreia