Re: SciTE 5.2.3 released

Le 17/07/2022 à 01:16, 'Neil Hodgson' via scite-interest a écrit :
> [Note, any ” in this mail should be " but Mail.app tries to correct quotes]
>
> Philippe Lhoste:
>
>> And it looks more like a system problem than one with SciTE: even a v. 3
>> doesn't work.
>
>     OK. Let’s try to narrow down the possibilities.
>
>     First check the values used for default and user by typing in the output pane:
>
> echo Default="$(SciteDefaultHome)" User="$(SciteUserHome)"
>
>     The quotes are to try to detect extra spaces. The result on my just-now test (after setting SciTE_HOME=D:\usr\wscite) were:
>
>> echo Default="D:\usr\wscite" User="D:\usr\wscite"
> Default="D:\usr\wscite" User="D:\usr\wscite"
>
>      Then open User Options from the Options menu and show the path:
>
> echo "$(FilePath)"
>
>      With the result
>
> "D:\usr\wscite\SciTEUser.properties"
>
>     Now this file contains the "import PhiLho/SciTEUser" and that file exists. Now at the end of the Options menu is "Open PhiLho/SciTEUser". Is that entry present? If selected does it open the correct file?
>
>     With "PhiLho/SciTEUser" open, what does 'echo "$(FilePath)"' produce:
>
> "D:\usr\wscite\PhiLho\SciTEUser.properties"

After setting SciTE_UserHome, I could load the main user properties
files, but the imports didn't work. But at least, I had all these
variables in the statusbar, so I could examine them.

>     Ah! Just realized that setting "imports.include" may filter it out unless it includes "PhiLho/SciTEUser".

That's it!
I had imports.exclude of most languages I don't use (or event know…),
and an imports.include=markdowwn (it was excluded in the previous one),
probably an experiment made a long time ago…
After I commented out the latter, my include loading the position of
SciTE worked, but not my language properties files.
I removed the last line in imports.include, which excluded these too.
I wanted to remove them from being imported in the main properties
files, to take in account only the properties I set. The idea was to
avoid defining properties I didn't want to have and didn't want to disable.

To be clearer, previous settings were:

imports.exclude=\
abaqus asciidoc asl [... more ...] markdown verilog vhdl visualprolog \
\
abbrev cpp css html lua others pov sql vb

imports.include=markdown

# Properties I customized
import abbrev
import cpp
import css
import html
import lua
import others
import pov
import sql
import vb

I am pretty sure this worked at some time… (except perhaps for the
imports.include ? Not sure anymore). Ie. perhaps at some time, it worked
in a linear way, the import statements overriding the imports.exclude,
no longer now?

I removed markdown from imports.exclude, removed the imports.include,
and now it works!

Anyway, thanks for pushing me in the right direction!

Regards.

--
Philippe Lhoste
--  (near) Paris -- France
--  http://PhiLhoSoft.github.io/about/
--  --  --  --  --  --  --  --  --  --  --  --  --  --

-- 
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/scite-interest/d0b0a890-fc17-c04f-05e7-65784694777e%40GMX.net.