Recent Posts

91

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.

92

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.

93

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?

94

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.

95

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)

96

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.

97

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

« Last post by joecar on September 14, 2023, 10:52:33 pm »

Appears to be happening in a few C files only, the other C files are ok.

I'm trying to create a chopped down version of the file where it's happening to post here.

98

SlickEdit® / Re: How does SE determine the document type for XML files?

« Last post by patrick on September 14, 2023, 07:51:08 pm »

Yes, that gets saved with your configuration, so you should only need to do it once.

I'll take a look at improving that detection later this afternoon.  The top level project tag is one of the things the detection code is looking at.  For this specific case, I think we should rule out Ant just because of the supplied DOCTYPE. 

99

SlickEdit® / Re: How does SE determine the document type for XML files?

« Last post by rjpontefract on September 14, 2023, 07:34:00 pm »

Thanks for the replies. 

If I use set-var-def-antmake-identify 0, is that remembered across restarts of SE?

Here's a small example that is identified as an ant file.  Is it the top level <project> tag that is being used to identify the file?

Code: [Select]

<!DOCTYPE ProjectAttributes SYSTEM "XML/platforms.dtd">
<project>

  <projectattributes name="TestAttributes">
  </projectattributes>

</project>


100

SlickEdit® / Re: How does SE determine the document type for XML files?

« Last post by Clark on September 14, 2023, 04:42:36 pm »

Please post a small sample file which reproduces this problem.