Re: [StrongED] "wrapwidth" setting

[Peter Young <pnyoung@xxxxxxxxxxxx>]

On 18 Oct 2013  Fred Graute <fjgraute@xxxxxxxxx> wrote:

> In message <20857c9c53.pnyoung@xxxxxxxxxxxxxxxxxxxx>
>           Peter Young <pnyoung@xxxxxxxxxxxx> wrote:

>> On 16 Oct 2013  Fred Graute <fjgraute@xxxxxxxxx> wrote:
>>
>>> In message <c1120f9b53.old_coaster@old_coaster.yahoo.co.uk>
>>>           Tony Moore <old_coaster@xxxxxxxxxxx> wrote:
>>
>>>> On 15 Oct 2013, Jim Nagel <stred@xxxxxxxxxxxxxxxx> wrote:
>>>>
>>>>> Please can someone tell me:
>>>>>
>>>>> How do I cause a certain textfile to open at width 132, without my
>>>>> having to manually tweak "wrapwidth" at the bottom of the StrongEd
>>>>> window every time?
>>>>>
>>>>> Can't find anything relevant in iconbar Choices.
>>>>>
>>>>> (The file in question is a logfile that I am opening frequently while
>>>>> monitoring something.  MPro's Msgserve log, as it happens.)
>>>>
>>>> The log should open in SysLog mode, if you have that installed. Then
>>>> Mode Choices > Wrapping > Softwrap width > Fixed number of characters >
>>>> 132. However the width of the display is set via Global Choices >
>>>> Windows, so 132 characters will not be displayed, unless your default is
>>>> 132, and you will still have to click the toggle-size button.
>>
>>> You could tie the FullView function to the OnLoad keyword to force the
>>> view to full size. Simply add this line to the SysLog ModeFile:
>>
>>>    OnLoad   FullView
>>
>>> Doing it this way has the advantage that it affects one mode only rather
>>> than all modes which may be more desirable.
>>
>> That would be useful for me, in viewing SyncDisc's logfiles, which
>> open in Base Mode, and also WimpLog's logs, which open in SysLog
>> modes, but it doesn't seem to work for me.

> There are two reasons that I can think of why this isn't working for
> you.

>  - You have copies of these modes in UserPrefs but modified the ones in
>    Defaults. Open the ModeFile by clicking Adjust on the iconbar icon
>    and then Shift click on the mode name in the menu. This will open the
>    ModeFile in use, check that it has the OnLoad line.

>  - The permission for OnLoad is set to 'N' in the ModeLock file. Open
>    the ModeLock file (Ctrl-Select on iconbar icon) to check and alter if
>    necessary.

Fred, you are a master at remote diagnosis; many thanks once again. In 
fact it was a bit of both of those. The ModeFile for BaseMode was 
indeed the wrong one, the ModeFile for SysLog was the right one, but 
in ModeLock I had to change the setting for OnLoad for SysLog but not 
for BaseMode.

I can never remember the shortcuts for accessing these files, so I 
have access to them in <plug> the excellent StrongMen </plug>. I must 
now check that StrongMen is indeed pointing to the right BaseMode 
ModeFile, the one in StrED_cfg, as I think it isn't.

With best wishes,

Peter.

-- 
Peter Young (zfc W) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@xxxxxxxxxxxx

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