Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
SlickEdit® / Re: Colored build output - a simple solution?
« Last post by emmenlau on Today at 11:31:36 am »
Dear Graeme,
thanks a lot for your help again! I feel bad about my rant, and also feel bad for you to spend time on this. My frustration is that Slickedit makes a seemingly simple task too hard. I can not understand why this functionality is not part of the base package. I've tried CLion and other IDE's and this is one of the first things that "just work".

I've now also contacted Slickedit support with this question. I think this is such a broadly relevant question that there should be either a ready-made settings file for download, or a detailed PDF with the steps required, or this should be part of the core distribution. If you don't have something ready-made, please do not spend too much time on it!

Thanks a lot Graeme and all the best, Mario
22
SlickEdit® / Re: Colored build output - a simple solution?
« Last post by Graeme on Today at 11:05:44 am »
Hi
I don't work for SlickEdit.  However, maybe this is not so easy, I will need some time to investigate.  I guess you know GCC can produce coloured output so it might make sense to use what GCC generates as suggested by Clark here (one of your links)
https://community.slickedit.com/index.php/topic,408.msg1615.html#msg1615

It looks like GCC lets you customize the colours
https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html
and it looks like it is ANSI escape sequences e.g.
BRIGHT_RED "\x1b[0;1;31m"

Do you know if any of these escape sequences make it into the build window when you run GCC?  If so, can you copy and paste it to a file and post the file here.

In Slick C you can colour a line of text like this
Code: [Select]
      p_col = 1; _SetTextColor(CFG_FILENAME, _line_length(), false);
so the easiest way might be to write a macro that searches for errors etc and colours the whole line.  Can you capture a few lines or error and warning output from GCC and post it here?



23
SlickEdit® / Re: Colored build output - a simple solution?
« Last post by emmenlau on Today at 07:10:48 am »
Dear @Graeme,
thanks for your reply. But I'm not sure what to do next.

I understand that for you its not hard to color the buffer. But for me it's hard. And I found at least the following other topics about this question, without a detailed solution:
  * https://community.slickedit.com/index.php?topic=408.0
  * https://community.slickedit.com/index.php?topic=15761.0
  * https://community.slickedit.com/index.php?topic=7750.0
  * https://community.slickedit.com/index.php?topic=14235.0

Can you explain step by step what would need to be done on a vanilla Slickedit install to get colored build output from gcc? I do not care what kind of colors or what kind of font, really! Maybe errors in red, warnings in orange and diagnostic gcc messages in green, but really I would not care. Just help me discriminate diagnostic messages from the standard build output. And please make this a default option for Slickedit.
24
My tag file had beta 5 files in it so I did rebuild all and got an error.
It worked the second time without an error.

Code: [Select]
Incorrect version
slickc.ex 6395 slickc:removeOldFiles(C:\SlickConfig\23.0.0\tagfiles\slickc.vtg,C:\Program Files\SlickEdit\Pro-23-0-0\\macros\)   p_window_id: 455   p_object: OI_EDITOR   p_name:
slickc.ex 7027 copyInstalledSlickCTagFile()   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
slickc.ex 5880 _e_MaybeBuildTagFile(0,1,1)   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
tags.ex 8939 MaybeBuildTagFile(e,1,1)   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
tagform.ex 11993 TagRebuildAnyTagFile(C:\SlickConfig\23.0.0\tagfiles\slickc.vtg,e,0)   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file
tagform.ex 12625 _tag_form.ctlrebuild_tag_file.lbutton_up()   p_window_id: 459   p_object: OI_COMMAND_BUTTON   p_name: ctlrebuild_tag_file

26
I started to make a Java Project so I can see Live Errors. I think I ran into what you (Patrick) mentioned before:

Quote
I have found a bug with live error's jdk detection for openjdk 1.8 on linux that I need to work through.

In "JDK installation directory", I put the "bin" directory of my 1.8 JDK and also tried the parent dir of bin, and I get error: "Path to JDK 1.6 or later must be specified in order to use Live Errors". Is this the same problem you are tracking down?

I'm on RC1, Linux x64, CentOS 7.2
27
Fixed for RC2. This problem seems to occur with more than just Delete.
28
SlickEdit 2018 v23 Beta Discussion / Re: Bad crash with search
« Last post by Clark on Today at 12:47:04 am »
I just tried this on a couple of my Windows systems. Looks like whatever algorithm Windows previously used is different now. I was able to allocate 16gig on my 16gig Windows 7 system. On my 8gig Windows 10 system, I was able to allocate 27gig. On older Windows OSes the OS would never let you allocate more than 1/3 of the total memory available.

In any case, it would be a good idea to try a much smaller buffer cache size to see if that fixes the problem. I'm still very suspicious.
29
Following up to say that my case was also fixed in RC1.  I've been using it all day without any issues so far.  Thanks!
30
Untar attached file.

With a clean config, go to Smart Open, right click at the top and check "Date modified" so that the date modified is showing.

Now go to the directory containing the hi.txt directory. Notice this directory has a date - 181012-1602.

Right click on hi.txt and choose "Delete". It gets the filename wrong in the dialog box, says: "Delete file '.../deletefileissue/181012-1602   2018-10-16T20:00:58hi.txt'". The delete then fails because smart open got the file name wrong.

Similar issue occurs when trying to rename the file. The filename populated in the Move/Rename Files dialog box is not correct.

RC1, Linux x64, CentOs 7.2
Pages: 1 2 [3] 4 5 ... 10