Recent Posts

91

SlickEdit 2023 v28 Beta Discussion / Re: Directory diff seg faults

« Last post by astromme on September 18, 2023, 05:18:25 PM »

Incidentally, I switched to qt5 version (via softlinks) we talked about here: https://community.slickedit.com/index.php/topic,19267.msg76904.html#msg76904 and it doesn't crash.. I switched back to to the "original" 2023 beta 2 and it crashes again.

Would you still like me to try the debug version you created?

92

SlickEdit 2023 v28 Beta Discussion / Re: Directory diff seg faults

« Last post by Clark on September 17, 2023, 01:15:16 PM »

I built an installer with added debug in vsdiff that hopefully will tell us something. Please install and test with this debug vsdiff.

vsdiff may be crashing when diffing a particular file. If so, this test will let us know which file. I removed the theading (this uses only 1 thread), so that the debug info will be much easier to figure out.

The debug will be written to /home/<username>/.slickedit/28.0.0/logs/vs.log

After vsdiff crashes, dump the contents of vs.log. If it looks like it crashed on a particular file. Run it again and see if it still crashes on the same file. Keep me posted.

v28 beta 2 installer with debug for vsdiff:

https://support.slickedit.com/outbound/2800/se_28000002_linux64qt5_beta2_vsdiff_debug1.tar.gz

93

SlickEdit 2023 v28 Beta Discussion / Re: Slick-C Error inPython when typing "printf("

« Last post by JeppeOland on September 15, 2023, 10:09:26 PM »

Best kind of bug there is (for the guy fixing it)

94

SlickEdit 2023 v28 Beta Discussion / Re: Slick-C Error inPython when typing "printf("

« Last post by Dennis on September 15, 2023, 09:54:52 PM »

The original problem will be fixed in the next beta.  The proportion of "easy to reproduce" / "easy to fix" for this one was out of this world.

95

SlickEdit 2023 v28 Beta Discussion / Re: Slick-C Error inPython when typing "printf("

« Last post by JeppeOland on September 15, 2023, 03:02:09 PM »

Yeah those are pretty common.
Stuff like matplotlib.pyplot is also pretty frequently used.

96

SlickEdit 2023 v28 Beta Discussion / Re: Slick-C Error inPython when typing "printf("

« Last post by Dennis on September 15, 2023, 02:51:22 PM »

Looks like our automatic Python tagging only gets the standard Python packages.  Numpy is an add-on.

It is a pretty commonly used package, I might look into adding information for it to our "python.tagdoc". 
It might be a good idea to add PyTorch too.  I will look into it.

97

SlickEdit 2023 v28 Beta Discussion / Re: Slick-C Error inPython when typing "printf("

« Last post by JeppeOland on September 15, 2023, 02:40:57 PM »

Is "numpy" not being automatically tagged?

98

SlickEdit 2023 v28 Beta Discussion / Re: Slick-C Error inPython when typing "printf("

« Last post by Dennis on September 15, 2023, 02:16:56 PM »

You can turn off the auto-correct feature by going to Document > Python Options... > Completion Options > | | Auto-correct identifier before operator.  The same option applies both to "." operators and function argument help / open paren.

I might be able to tweak things to handle the "numpy" case, I assume that the reason that it tries to replace with "sin" is because it can not find numpy.sign.  You could try creating a language specific tag file for Python in order to have the numpy module tagged.

99

SlickEdit 2023 v28 Beta Discussion / Re: Slick-C Error inPython when typing "printf("

« Last post by JeppeOland on September 15, 2023, 07:30:54 AM »

Similarly, typing "numpy.sign(" replaces with "sin()" and gives the same error.
(replacing in this case is wrong since there IS a sign function)

100

SlickEdit 2023 v28 Beta Discussion / Re: View->New Line Chars

« Last post by Dennis on September 14, 2023, 11:18:18 PM »

Keep an eye on the file encoding.  Maybe it is a difference between your Unicode and non-Unicode editor font.