Re: Scripts

["Richard Torrens (lists)" <Lists@xxxxxxxxxxx>]

In article <6b29a64058.fjgraute@xxxxxxxxx>,
   Fred Graute <fjgraute@xxxxxxxxx> wrote:
> In message <584003b48bLists@xxxxxxxxxxx>
>           "Richard Torrens (lists)" <Lists@xxxxxxxxxxx> wrote:

> > Another point I have noticed is that the relevant directory is either
> > - or. If you leave !ScriptsSED in !StrongED then scripts added to
> > !StrED_cfg get ignored. I can see why this is - but it is not normal
> > StrongED style.

> ScriptSED looks in both StrED_cfg and StrongED with scripts in the former
> overriding homonymous scripts in the latter.

> > It's easy enough to move the whole !ScriptsSED to !StrED_cfg but you
> > then have to delete it again if you upgrade. 

> There's no need to move ScriptSED to StrED_cfg, just create a skeleton
> !ScriptSED with inside it 3 directories: Languages, Scripts and Tools.

> You can then add your languages, scripts and tools to it without having
> to worry about them when you upgrade StrongED.

I have 
SCSI::SSD.$.!Boot.Choices.!StrED_cfg.UserPrefs.Tools.!ScriptsSED
within are indeed Languages, Scripts and Tools but the extra scripts do
not appear in the menu. Opening the directory opens the !StrongED version -
as StrongED_Read:Tools.!ScriptSED.Scripts 

I tried moving it to  SCSI::SSD.$.!Boot.Choices.!StrED_cfg.!ScriptsSED
with te same results!

Is something wrong or are your instructions open to misinterpretation?

I suggest you supply !StrED_cfg with the appropriate directories in future.

-- 
Richard Torrens.
http://StrongED.Torrens.org for StrongEDinstructions (in preparation) and mailing list archives