Re: [StrongED] StrongED 4.69b5 C mode bracket (mis)match freezing

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <mpro.mqie5n0050okp02uw@xxxxxxxxxxxxxxxxxxxx.invalid>
          Jeremy Nicoll - ml stronged <jn.ml.sed45@xxxxxxxxxxxxxxxxxxxx> wrote:

> pdmiller@xxxxxxxxxxxxxxxxxx wrote:
>
> >On another, more specialised, topic - were External Edit file data type
> >extensions ever implemented in a standard way?

You can add a rule to the desired mode's ModeWhen file to capture the
file. To have the file opened in C mode you'd add this to its ModeWhen:

  Rules Include
  - fff, (DrWimpC**
  End

Unfortunately that doesn't work due to the external edit code sending
the wrong rule type to the routine that applies the ModeWhen rules.

After fixing, a file opened from DrWimpC goes into C mode as intended.

> I don't know anything about External Edit, but I used to put appropriate
> literals into various files (eg log files each time a programme opened a new
> one) so that they'd always be opened the way I wanted in SE, eg writing:
>
> yyyymmdd hhmmss - StrongED$Mode=modename  StrongED$WrapWidth=1024

Yes, that would force the right mode too. Mind you, only one StrongED$
variable is allowed per line.

> at the top of such files.  IIRC it's not necessary that these are on the
> first line of a file, SE looks in the first few lines - I can't remember
> just how many 'few' is though.

StrongED scans the first 1024 bytes of a file.

Cheers,
Fred.

-- 
StrongED Developer
http://www.stronged.iconbar.com/

-- 
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx