On 17 Aug 2023, Christian Sacks said the following...
CS> On 17 Aug 2023, Paul Hayton said the following...
CS>
CS> PH> Mmm have a look in text or data dir and see if you can find
CS> PH> msg_index.ini I *think* that may be the file you're after?
CS> PH>
CS>
CS> I think I did try adjusting that one, but became under the impression
CS> that was for the listing of bases rather than listing of messages inside
CS> a base, but I could be wrong. Will have another look at that and see how
CS> it goes.
CS>

So in 132x37 this is what my msg_index.ini makes my message index list look
like in practice;
https://erb.pw/i/7742a07532ae808daa00b181f68fda1c.png

And this is what my message list looks like;
https://erb.pw/i/383599277491de31bb98e04d8de1f118.png

I've looked over msg_index.c132x36.ini again and can't see what to change (I
made the filename msg_index.c132x36.ini so as the wider screen resolution would
work, and in all other things it does, but I wonder if the message list
function doesn't know about this or I'm just missing a file that needs to be
created.

Hope this helps.

.... THE fIRST sTEP iS tO tAKE oFF tHE cAPS lOCK

On 17 Aug 2023, Christian Sacks said the following...
CS> I've looked over msg_index.c132x36.ini again and can't see what to
CS> change (I made the filename msg_index.c132x36.ini so as the wider screen

since both examples there were bodged. i'll retry this:

http://kirin.dcclost.com/~alex/derp.txt

On 17 Aug 2023, Christian Sacks said the following...
CS> On 17 Aug 2023, Christian Sacks said the following...
CS>
CS> CS> On 17 Aug 2023, Paul Hayton said the following...
CS> CS>
CS> CS> PH> Mmm have a look in text or data dir and see if you can find
CS> CS> PH> msg_index.ini I *think* that may be the file you're after?
CS> CS> PH>
CS> CS>
CS> CS> I think I did try adjusting that one, but became under the impression
CS> CS> that was for the listing of bases rather than listing of messages ins
CS> CS> a base, but I could be wrong. Will have another look at that and see
CS> CS> it goes.
CS> CS>
CS>
CS> So in 132x37 this is what my msg_index.ini makes my message index list
CS> look like in practice;
CS> https://erb.pw/i/7742a07532ae808daa00b181f68fda1c.png
CS>
CS> And this is what my message list looks like;
CS> https://erb.pw/i/383599277491de31bb98e04d8de1f118.png
CS>
CS> I've looked over msg_index.c132x36.ini again and can't see what to
CS> change (I made the filename msg_index.c132x36.ini so as the wider screen
CS> resolution would work, and in all other things it does, but I wonder if
CS> the message list function doesn't know about this or I'm just missing a
CS> file that needs to be created.

|$R36|&1 <- right justify in a 36-wide line &1
|$L20|&2 <- left justify in a 20 wide line &2

On 17 Aug 2023, Alexander Grotewohl said the following...
AG> |$R36 <- right justify in a 36-wide line &1
AG> |$L20 <- left justify in a 20 wide line &2

great scott!

left column:
<PIPE>$R36<ampersand>1
<PIPE>$L20<ampersand>2

On 17 Aug 2023, Alexander Grotewohl said the following...
AG> since both examples there were bodged. i'll retry this:
AG>
AG> http://kirin.dcclost.com/~alex/derp.txt

Thanks for this, I know how to left/right/centre justify text, that's not the
issue, see my previous screenshots. I just want to make the message list (not
the message base list) look nice on a 132x37 or bigger terminal.

.... System halted - Press all keys at once to continue

On 18 Aug 2023, Christian Sacks said the following...
CS> Thanks for this, I know how to left/right/centre justify text, that's
CS> not the issue, see my previous screenshots. I just want to make the
CS> message list (not the message base list) look nice on a 132x37 or bigger
CS> terminal.

okay i have a potential solution:

399, 400, and 401 display the text for each line. (seems to be first display,
selected, and unselected)

you create a .mps file for each: 399.mps, 400.mps, 401.mps

and change each to: (bar being the actual vertical bar)

!399 <bar><ampersand>1 <bar><amp>2 <bar><amp>6 ... whichever of them you use

and inside 399.mps et al you do something like

Begin
if ACS('X132') then
// for this one paramstr(3) would be <amp>6 from above
write(paramstr(1)+' ... '+paramstr(2)+' etc.. ')
else
write(...);
end;

and format it how you want with the correct widths.

the other option is to copy your entire prompts file and protect the wide one
with ACS X132 .. and the other with !X132 or something.

On 17 Aug 2023, Alexander Grotewohl said the following...
AG> okay i have a potential solution:
AG>
AG> 399, 400, and 401 display the text for each line. (seems to be first
AG> display, selected, and unselected)
AG>
AG> you create a .mps file for each: 399.mps, 400.mps, 401.mps
AG>
AG> and change each to: (bar being the actual vertical bar)
AG>
AG> !399 <bar><ampersand>1 <bar><amp>2 <bar><amp>6 ... whichever of them you
AG> use
AG>
AG> and inside 399.mps et al you do something like
AG>
AG> Begin
AG> if ACS('X132') then
AG> // for this one paramstr(3) would be <amp>6 from above
AG> write(paramstr(1)+' ... '+paramstr(2)+' etc.. ')
AG> else
AG> write(...);
AG> end;
AG>
AG> and format it how you want with the correct widths.
AG>
AG> the other option is to copy your entire prompts file and protect the
AG> wide one with ACS X132 .. and the other with !X132 or something.

Hmm this is an interesting idea, I will give it some thought. Thank you =)

.... When cheese gets its picture taken, what does it say?