Subj : Re: Golded Linux
To   : Sean Dennis
From : Nicholas Boel
Date : Sat Nov 16 2024 11:11 pm

Hello Sean,

On Sat, Nov 16 2024 22:13:30 -0600, you wrote:

>  NB> I will admit, having some kind of warning/error message in the Linux
>  NB> console letting you know that your golded.cfg has errors in it would
>  NB> be extremely beneficial, compared to a blank screen and going back to
>  NB> the command prompt without any information.

> Using 'tee' can help a lot.

Thanks for the tip! :)

There may have been some kind of warning message at one point, and maybe now that most distros default to UTF-8 consoles, it could be related. I would imagine there is probably a few things that can be used as a crutch. However, IMO none of them should be necessary.

> 'gedlnx | tee output.txt' works but ANSI color codes are captured so you'd 
> need to look at the output in an ANSI-capable viewer.

Here's a little gem I found a long time ago (if you haven't seen it already), maybe this simple script would work instead of a full fledged ansi-capable viewer?

https://github.com/keaston/cp437

> I'm using GoldEd+ under Slackware 15 without issues.

Latest golded installed (but not being used at this very second) here under Archlinux v.today, also without issues except that I would love to see ditching the cp437 stuff, getting rid of translation tables, and bringing in the iconv support. Unfortunately, I'm not a good programmer so all of that goes right in the suggestion box aka trash bin.

Did you switch back to Linux recently? I could have sworn I saw your old BBS software on OS/2 or DOS not too long ago. Or do you run multiple instances these days and switch them up on occasion just to confuse me?

Regards,
Nick

.... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

.