Hi David,

On 2024-11-19 12:00:30, you wrote to All:

I compiled Linux version and it works fine, issue I have is basically
when accessing from windows SecureCRT or Putty, I cannot seem to find
the right emulation setting or terminal mode.

Does anyone have any experience running Golded rmeotely and showing up properly?

Can you do a rescan of this area (about 300 messages back will do)? In Februari and March I had a long thread with a few other people to get this right on my linux konsole, and remotely with Putty. Maybe it contains some useful clues for you...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello David!

19 Nov 24 12:00, you wrote to all:

I compiled Linux version and it works fine, issue I have is basically

[...]

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 4/0 90/0 103/705 124/5016 153/757 154/10 30 203/0 221/0

It actually isn't working fine. There is no Origin or Tear lines on all of your messages.



Stephen


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Hello David,

On Wed, Nov 20 2024 07:38:50 -0600, you wrote:

Erm ok, I noticed, but no idea why it happens when I use a TPL file
looking into that, and this is windows version LoL

Because it's not part of the template file. It's something you need to define in your config file.

TEARLINE <tearline>
ORIGIN <origin>

Do a search for GOLD_REF.TXT, as I said on a couple of occasions already, it will be your best friend (and tell you every option available to you, with descriptions on what they do).

SEEN-BY: 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1 SEEN-BY: 2320/105 3634/12 5020/400

While they don't seem to show up in Golded (Golded must still filter this), I'm seeing your SEEN-BYs in every message you post, too. These don't look like they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the "@" or something?

Regards,
Nick

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

Hi Nicholas,

On 2024-11-20 19:38:57, you wrote to David Gonzalez:

SEEN-BY: 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26
930/1
SEEN-BY: 2320/105 3634/12 5020/400

While they don't seem to show up in Golded (Golded must still filter this),
I'm seeing your SEEN-BYs in every message you post, too. These don't look like
they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the "@" or
something?

His seen-bys look fine here? Maybe your reader gets confused when the origin line is missing?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Thu, Nov 21 2024 05:32:21 -0600, you wrote:

While they don't seem to show up in Golded (Golded must still filter this),
I'm seeing your SEEN-BYs in every message you post, too. These don't look like
they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the "@" or
something?

His seen-bys look fine here? Maybe your reader gets confused when the origin line is missing?

I just got done saying it works fine in Golded, which is what you're using.. so it would look fine there.

Maybe it is my reader, I don't know. It also displays these SEEN-BYs on my BBS, which does indeed know what FTN kludges are, and shouldn't matter if there is an origin line or not.

I checked in Golded as well, and the "@" (which I think is just a translation of a CTRL character) was missing before all SEEN-BY lines, yet Golded still hides them (which is great for Golded, but my current reader and BBS software is treating it like regular text, because there is no CTRL character before it, as far as I can tell.

So I can only guess that something is stripping the CTRL character before that specific kludge, as that "@" character is still there on all the other kludges of his message (and I don't see any of those in my reader, either), and it doesn't happen with anyone else that I've read in the past few weeks.

Regards,
Nick

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

Hi Nicholas,

On 2024-11-21 16:05:45, you wrote to me:

While they don't seem to show up in Golded (Golded must still

filter
this),

I'm seeing your SEEN-BYs in every message you post, too. These don't

look like

they start with a CTRL character to be a proper kludge, either.

Are trying to invalidate these in your Golded config by removing the

"@" or

something?

His seen-bys look fine here? Maybe your reader gets confused when the origin
line is missing?

I just got done saying it works fine in Golded, which is what you're using..
so it would look fine there.

Maybe it is my reader, I don't know. It also displays these SEEN-BYs on my BBS, which does indeed know what FTN kludges are, and shouldn't matter if there is an origin line or not.

I checked in Golded as well, and the "@" (which I think is just a translation
of a CTRL character) was missing before all SEEN-BY lines, yet Golded still
hides them (which is great for Golded, but my current reader and BBS software
is treating it like regular text, because there is no CTRL character before
it, as far as I can tell.

SEEN+BY lines normally don't have a CTRL character in front of them!

So I can only guess that something is stripping the CTRL character
before that specific kludge, as that "@" character is still there on
all the other kludges of his message (and I don't see any of those in
my reader, either), and it doesn't happen with anyone else that I've
read in the past few weeks.

So I still think the SEEN-BY lines in this case are treated as normal text, because the origin line is missing...

They will only be treated special if they come after the origin line, which normally is the last readable line in a message, so it triggers your reader, to hide the lines comming after the origin line (my guess).

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Thu, Nov 21 2024 16:26:44 -0600, you wrote:

SEEN+BY lines normally don't have a CTRL character in front of them!

Ok.

So I still think the SEEN-BY lines in this case are treated as normal
text, because the origin line is missing...

Maybe.

They will only be treated special if they come after the origin line,
which normally is the last readable line in a message, so it triggers
your reader, to hide the lines comming after the origin line (my
guess).

I've let Rob know, as this reader is just accessing my Synchronet message bases via NNTP, and those SEEN-BYs are also displayed when logged into the BBS via telnet, so it's not just this reader.

Granted, if there was an origin line, I probably would have never seen this issue.

Regards,
Nick

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

Re: Re: Linux golded
By: Nicholas Boel to Wilfred van Velzen on Thu Nov 21 2024 04:46 pm

I've let Rob know, as this reader is just accessing my Synchronet message bases via NNTP, and those SEEN-BYs are also displayed when logged into the BBS via telnet, so it's not just this reader.

SBBSecho requires a tear line and/or an origin line in the message text before it'll start parsing SEEN-BYs and placing them in the message header (where FTN seen-bys are properly stored in a Synchronet Message Base). That's by design.
--
digital man (rob)

Steven Wright quote #33:
Everyone has a photographic memory; some just don't have film.
Norco, CA WX: 77.8°F, 11.0% humidity, 2 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Rob,

On Thu, Nov 21 2024 17:07:00 -0600, you wrote:

I've let Rob know, as this reader is just accessing my Synchronet message bases via NNTP, and those SEEN-BYs are also displayed when logged into the BBS via telnet, so it's not just this reader.

SBBSecho requires a tear line and/or an origin line in the message
text before it'll start parsing SEEN-BYs and placing them in the
message header (where FTN seen-bys are properly stored in a Synchronet Message Base). That's by design.

Ok. Thanks for the response!

Regards,
Nick

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

Hola David!

19 Nov 24 12:00, David Gonzalez dijo a All:

Hola All!, saludo cordial

I compiled Linux version and it works fine, issue I have is basically when accessing from windows SecureCRT or Putty, I cannot seem to find the right emulation setting or terminal mode.

Does anyone have any experience running Golded rmeotely and showing up properly?

I do. I use this line:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -Cpath_to_cfg

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hello David,

On Sun, Nov 24 2024 16:42:24 -0600, you wrote ..

Thanks Angel, I tried your suggestion and Fernando Toledo's sample
config with no luck my golded still looks like this:

You should probably start over with your config. Start as minimal as you possibly can (I think someone posted a command line option to create a
very basic golded.conf).

"LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -Cpath_to_cfg"

Definitely does NOT go in your golded.conf. That's something you type on
the Linux console in order to run Golded.

With that said, I'd be willing to guess you don't have 'luit' installed, either.

Are you new to Linux? If so, you should probably mention that so people
can be a lot lighter on their explanations to you, which you currently
aren't seeming to understand any of. It also seems like you're
completely missing a lot of the help people are already trying to give you.

Regards,
Nick

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

Hello David!

24 Nov 24 17:42, you wrote to Angel Ripoll:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target encoding is the same for my installation (I use Fidian for GoldEd through ttyd and tmux), I have a export TERM=screen.xterm-256color

where you can start that like (in a bin/bash script like) TERM=screen.xterm-256color /usr/bin/golded -T600

without that I have similar like you. Ie, if you run it directly in a shell
you possible have the incorrect encoding.

The 'lining' does have have really (imho) something to do withe the encoding for the characters in
messages ..


Dennis


... Why document it? I'll be here forever.
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Deputy Nodelist Police (2:280/2060)

Hola Dennis!

25 Nov 24 07:27, Dennis Slagers dijo a David Gonzalez:

Hello David!

24 Nov 24 17:42, you wrote to Angel Ripoll:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target encoding is the same for my installation (I use Fidian for GoldEd through ttyd and tmux), I have a export TERM=screen.xterm-256color

I have my system in UTF8 and I use ISO8859-1 with golded. That's why I use that line. Before using this I had to manually change the encoding of my terminal to see the golded screen correctly. If I didn't make that change, I saw more or less the screen as David says.

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hello David!

25 Nov 24 07:44, you wrote to Dennis Slagers:

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

I believe that this line has no use as source and target encoding
is the same for my installation (I use Fidian for GoldEd through
ttyd and tmux), I have a export TERM=screen.xterm-256color

In my case (using specific czech codepage):

1) How to start golded:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3
LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f

2) In .bash_profile:

export TERM=vt220

3) In putty:

UTF8

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hello David,

On Mon, Nov 25 2024 06:39:16 -0600, you wrote ..

With that said, I'd be willing to guess you don't have 'luit'
installed, either.

Guessing I do not, why?, well I based my install on the Git repo
instructions

Because if you are putting something you would normally run on the
command line in your Golded configuration file, people here should
probably be aware you're not very knowledgeable in Linux so they can
slow down a bit and explain things much more specific so you understand.
You seem to be missing a LOT of valuable information, as well as where
you should be looking for answers to most, if not all of your questions.

New... well, I don't consider myself new but I'm a self-proclaimed
expert, so yeah I might be missing some concepts.

Thank you for letting the people trying to help you know that.

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30
50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426
240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1
310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280
712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 2320/105
3634/12 5020/400

You've also missed the fact that multiple people, including myself, have
asked you multiple times to add a tearline and origin line via your
config file in networked messages, so that the above lines don't display
(ie they shouldn't, and wouldn't if you had the lines necessary).

So, please put these two lines in your Golded config file:

TEARLINE @longpid @version
ORIGIN "This is an example origin line."

In the quotes, you can put the name of your BBS or mailer, and maybe
even some kind of connection information to it, like mine below.

Regards,
Nick

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

Hi David,

On 2024-11-26 08:21:43, you wrote to Angel Ripoll:

Tried this but Ubuntu reports luit not found, triued intalling it but
no install candidate

# apt search luit
Sorting... Done
Full Text Search... Done
x11-utils/jammy,jammy,jammy,jammy 7.7+5build2 amd64
X11 utilities

xterm/jammy,jammy,jammy,jammy 372-1ubuntu1 amd64
X terminal emulator

# apt show x11-utils
Package: x11-utils
Version: 7.7+5build2
...
This package provides a miscellaneous assortment of X utilities
that ship with the X Window System, including:
- appres, editres, listres and viewres, which query the X resource database;
- luit, a filter that can be run between an arbitrary application and a
UTF-8 terminal emulator;
...
The luit program requires locale information from
the libx11-data package.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hola David!

26 Nov 24 08:21, David Gonzalez dijo a Angel Ripoll:

Hola Angel!, saludo cordial

LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg

Tried this but Ubuntu reports luit not found, triued intalling it but no install candidate

Package luit

oracular (24.10) (utils): locale and ISO 2022 support for Unicode terminals
2.0.20221028-1: amd64 arm64 armhf ppc64el riscv64 s390x
also provided by: luit
plucky (utils): locale and ISO 2022 support for Unicode terminals
2.0.20240910-1: amd64 arm64 armhf ppc64el riscv64 s390x
also provided by: luit

Luit is on Ubuntu 24.10

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hola David!

26 Nov 24 13:06, David Gonzalez dijo a Wilfred van Velzen:

Installed ok, still when I try the suggested command line, golded doesn't even try to start just nothing happens, no blank screen or error.

Are you sure you put -C/path_to_goldedconfig on the command line? I forgot that line a while ago and golded didn't do anything like you say it does. That's why I made a bash program to start golded (for that and more things)

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hola David!

27 Nov 24 14:20, David Gonzalez dijo a Angel Ripoll:

Yup!, just tried it:

sbbs@bbs:~$ LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx -C ./ Command 'luit' not found, did you mean:
command 'lfit' from deb fitsh (0.9.4-1)
command 'lut' from deb tracetuner (3.0.6~beta+dfsg-3)
Try: sudo apt install <deb name>

And as previously suggested I installed the luit package or what you guys suggested, yet this is what I get.

Try just gedlnx -C/path_to_goldedcfg without a space between -C and the path. And remember that the path is the full path with the config file. Let's see if golded starts.

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hi David,

On 2024-11-28 09:42:57, you wrote to Angel Ripoll:

Try just gedlnx -C/path_to_goldedcfg without a space between -C
and the path. And remember that the path is the full path with the
config file. Let's see if golded starts.

sbbs@bbs:~$ set LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2' gedlnx -C/home/sbbs
sbbs@bbs:~$ set LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2'
gedlnx -C/home/sbbs/golded.cfg
sbbs@bbs:~$ set LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2'
gedlnx -C /home/sbbs/golded.cfg
sbbs@bbs:~$ set LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2'
gedlnx -C /home/sbbs
sbbs@bbs:~$ set LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2'
gedlnx

Tried all of these, nothing just another blank line.

Nobody told you to put 'set' in front of that command line! Blank lines is what you get when you do that.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hi David,

On 2024-11-28 15:57:29, you wrote to me:

Love your charming ways

Well maybe you notice a pattern here, when over time, people get less cordial, when you don't seem to read and follow their well meant instructions too well...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello David,

On Thu, Nov 28 2024 16:44:56 -0600, you wrote ..

LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2' gedlnx -C ./

This command is wrong.

sbbs@bbs:~$ LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2' gedlnx -C/home/sbbs/

This one is closer, though you need to actually specify the config file,
not just point it to a directory it might reside in.

Why in the world would you put your Golded config file in your
Synchronet directory? You know what? Never mind. You should focus on one
thing at a time.

LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2' gedlnx -C/path/to/
golded.conf

This probably won't work, though, see below.

If you don't know where your golded config files is, you have even
bigger problems.

Command 'luit' not found, did you mean:
command 'quit' from snap quit (1.0+git)
command 'lfit' from deb fitsh (0.9.4-1)
command 'lut' from deb tracetuner (3.0.6~beta+dfsg-3)
See 'snap info <snapname>' for additional versions.
sbbs@bbs:~$ sudo apt info luit
Package: luit
State: not a real package (virtual)
N: Can't select candidate version from package luit as it has no candidate
N: Can't select versions from package 'luit' as it is purely virtual
N: No packages found
sbbs@bbs:~$ sudo apt search luit
Sorting... Done
Full Text Search... Done
xterm/noble,now 390-1ubuntu3 amd64 [installed]
X terminal emulator

Whatever the error I'm making... I cannot seem to find it

Everything above definitely means that the package 'luit' is NOT
installed. Maybe it is not available via your package manager, or you do
not have the proper repo enabled that this package resides in.

So with that said, forget about luit and change your command line to this:

LANG=es_ES.ISO8859-2 gedlnx -C/path/to/golded.conf

See how that works for you.

While you're at it, here is like the 4th or 5th (and final) time I'll
say that you should add these two lines to your golded.conf before you
even try to start it:

TEARLINE @longpid @version
ORIGIN "I'm very new to all this, so please forgive me."

SEEN-BY: 4/0 90/0 103/705 104/119 120/616 124/5016 153/757 154/10 30 50 700 SEEN-BY: 203/0 220/20 90 221/0 6 226/18 44 50 229/426 240/1120 5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 341/66 234 396/45 SEEN-BY: 423/120 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 SEEN-BY: 902/26 930/1 10 2320/105 3634/12 5020/400

Regards,
Nick

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

Hello David!

28 Nov 24 17:44, you wrote to Wilfred van Velzen:

sbbs@bbs:~$ LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2' gedlnx -C/home/sbbs/ Command 'luit' not found, did you mean: command 'quit'
from snap quit (1.0+git) command 'lfit' from deb fitsh

if luit cannot be found you have to install it
as far as I know luit is part of x11-utils

luit is not a standalone package in most modern Debian or Ubuntu distributions. It is part of the X.Org project and typically included in the x11-utils package.

apt install x11-utils

Hoever in my tests and in my terminal this was not a solution for your issue
to fix it I had to add (I use fidian with goldED, which is ran under tmux and ttyd)
(as per example):

Environment=LC_CTYPE=en_US.UTF-8
Environment=LANG=en_US.UTF-8
Environment=LC_ALL=en_US.UTF-8

Without it a lot of things went wrong on display with my Debian .. with this .. its working ok
btw . .sometimes you have to reboot and/or logout/login to make it work correctly.

But in general above would even not solve the issue

X terminal emulator

Whatever the error I'm making... I cannot seem to find it

It's difficult as a number of settings can cause golded not to function properly with its display

if in your normal shell you still get the qqqqqq your standard encoding within your shell is not ok
But .. you have to take care on the config

for instance I start my golded from a bin/bash script, but when I do not use


export TERM=screen.xterm-256color

this line .. I do not get the 'lines' but I get the qqqqqqq ..

so please first try to get it running correctly without Luit . .as that should be possible
eliminate as much encoding/decoding stuff as that could cause issues ..

Try to make a bin/bash to make encoding sometimes easier rather than being busy with .bashrc etc.
but I do not know how well experienced you are in linux. (On certain levels I lack serious knowledge, so I try a lot of things and I also sometimes use chatgpt or co-pilot to check what direction to go ..

not always direct an answer but it gives you guidelines/hints/tips you could try.

Dennis


... I don't troubleshoot; I blame the vendor.
--- GoldED+/LNX 1.1.5-b20240309
* Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)

Hello Wilfred!

28 Nov 24, Wilfred van Velzen wrote to David Gonzalez:

Nobody told you to put 'set' in front of that command line! Blank
lines is what you get when you do that.

A well known AI method can't be wrong: Just try any combination.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello David,

On Fri, Nov 29 2024 06:42:22 -0600, you wrote:

SBBS is not there, as per the path /home/sbbs is $HOME for sbbs user,
SBBS lives under /sbbs

This doesn't match the location of your config file below.

Command 'luit' not found, did you mean:
command 'quit' from snap quit (1.0+git)
command 'lfit' from deb fitsh (0.9.4-1)
command 'lut' from deb tracetuner (3.0.6~beta+dfsg-3)
See 'snap info <snapname>' for additional versions.
sbbs@bbs:~$ sudo apt info luit
Package: luit
State: not a real package (virtual)
N: Can't select candidate version from package luit as it has no
candidate
N: Can't select versions from package 'luit' as it is purely virtual
N: No packages found
sbbs@bbs:~$ sudo apt search luit
Sorting... Done
Full Text Search... Done
xterm/noble,now 390-1ubuntu3 amd64 [installed]
X terminal emulator

Weird thing and I guess it's Ubuntu's fault here, hwy does it report
the package intsalled and then report no such command

Where in the above quoted text does it say "luit is installed"? I see things like "'luit' not found", "State: not a real package (virtual)", and "N: No packages found."

The only place it actually says something is installed is "xterm/noble,now 390-1ubuntu3 amd64 [installed]" but that has nothing to do with the package "luit".

This one worked, like gedlnx by itself with no other viriables or declarations, but I still get wrong key mappings

- NETMAIL (4:930/10) ------------------------------------------------ Netmail -
Msg : 1 of 1 Uns Loc
From : David Gonzalez 4:930/10 29 Nov 24 07:41:24
To : hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh 29 Nov 24 07:41:24
Subj :
------------------------------------- F10: Addressbook -- Shift-F10: Nodelist -

TEARLINE @longpid @version
ORIGIN "I'm very new to all this, so please forgive me."

Look at my golded.cfg which I've posted before:

<sbip>
sbbs@bbs:~$ cat golded.cfg

This right here. The "home" directory you speak of above is not "sbbs", it is "bbs". So try this:

---------[ THIS ONE ]--------
LANG=es=ES.ISO8859-1 gedlnx -C/home/bbs/golded.cfg -----------------------------

NOTE: I change the above line to use ISO-8859-1, since every reference I've seen -2 is used in Central and Eastern Europe, which has nothing to do with South America. This may fix your key binding issue as well.

You may not be using the correct config file.

USERNAME David Gonzalez
ADDRESS 4:930/10
AREADEF Netmail "NETMAIL" 0 Net OPUS /sbbs/fido/netmail
AREAFILE AreasBBS /sbbs/data/areas.bbs

I'm also not sure Synchronet supports OPUS style netmail, so your "Netmail" areadef probably won't work currectly in this case.

NICKNAME David G.

USEPID yes
EMPTYTEARLINE no

CTRLINFOECHO TEARLINE, ORIGIN

// Your origin lines.
ORIGIN "Un BBS Más | sync.skynetbbs.com:10023"
TEARLINE @longpid @version

These should display properly if you were actually using this config file.

So please if you see te offending line, tell me because I do not see
those kludge lines you all seem to be seing and my Origin line is also gone... as you can see what you suggested is indeed there.

You are using Golded. As far as I can tell, Golded strips those kludge lines no matter if you have an origin line or not. However, most other software doesn't. So basically anyone that is NOT using Golded is seeing it.

Looks like you might be using a different config file, or one that was generated by mistake. Try the line I gave above and see if it works any better for you. As for the key bindings, that could be on the OS level. We can tackle that after your Golded works a bit better.

Sorry but I'm confused about this

People are willing to help you out, you just need to pay attention, and not try to setup 10 different things at once. Focus on getting one thing right, then move on to the next.

I also just noticed that you are accessing your Synchronet message bases with Golded. So if the above help doesn't work, the next place you should check is your settings in SCFG > MESSAGE AREAS > FIDONET > MESSAGE SUB-BOARDS > <any sub board> > NETWORK OPTIONS > APPEND TAG/ORIGIN LINE = YES, then make sure you have ECHOMAIL ORIGIN LINE set to what you want it to be, and FIDONET ECHOMAIL = YES.

Regards,
Nick

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

Hello David,

On Fri, Nov 29 2024 06:42:22 -0600, you wrote:

Look at my golded.cfg which I've posted before:

<sbip>
sbbs@bbs:~$ cat golded.cfg
USERNAME David Gonzalez
ADDRESS 4:930/10
AREADEF Netmail "NETMAIL" 0 Net OPUS /sbbs/fido/netmail
AREAFILE AreasBBS /sbbs/data/areas.bbs

Something else I noticed. The TID kludge of this message shows you're using Mystic BBS's tosser. So at this point, I have no idea what you're trying to do here by accessing Synchronet message bases with Golded, and tossing with Mystic (this should absolutely not work seeing at the two softwares use completely different message base formats).

So it seems you're leaving some valuable information out, unless you have Mystic BBS software installed in /sbbs. If so, then you're not only confusing yourself, but everyone else, too. :(

Regards,
Nick

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

Hello David,

On Fri, Nov 29 2024 08:41:18 -0600, you wrote:

Something else I noticed. The TID kludge of this message shows you're
using Mystic BBS's tosser. So at this point, I have no idea what
you're trying to do here by accessing Synchronet message bases with
Golded, and tossing with Mystic (this should absolutely not work
seeing at the two softwares use completely different message base
formats).

Yes!, you're correct but allow me to explain:

That would have been nice to know much earlier!

- This is my working setup WIndows+Mystic+Golded, tat's why you see mystic.

While it may be working, it's not currently working /correctly/. Let's get *THIS* setup working correctly first, as that is the one you're using to post here currently.

I'm currently on the "production" node 4:930/1, the Linux SBBS+GoldED
is where I'm setting or trying to get a second node working, sorry if
this all confused people. Even though this Goldd config also appears
to have issues.

Most definitely it confused everyone, and most definitely still has the same issues since the beginning, since you were modifying the wrong config file. THIS golded config needs to be modified to add your tearline and origin lines.

So it seems you're leaving some valuable information out, unless you have Mystic BBS software installed in /sbbs. If so, then you're not
only confusing yourself, but everyone else, too. :(

Yes and my apologies *all* of what you've seen has come from my Windwos+mystic+golded node, golded on linux is my side-node.

Many thanks and hope this clears the air a bit.

Yeah, much clearer. That gets rid of Synchronet out of this entire equasion at the moment. Let's get /this/ one working first, then the other one accessing Synchronet will have completely different settings.

Regards,
Nick

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

Hello Dennis!

29 Nov 24, Dennis Slagers wrote to David Gonzalez:

Environment=LC_ALL=en_US.UTF-8

Without it a lot of things went wrong on display with my Debian ..

Let's have a look at the display flow:

shell charset
(screen/tmux charset)
golded charset
golded charset translatation
remote terminal translation (putty xterm and charset)

It's difficult as a number of settings can cause golded not to
function properly with its display

Did i miss another location where the translation can be wrong?

If the system was build with the same random configuration method that is visible here then there could be modifications that knock out common functions. If x11-utils is installed but luit not found then there could be a path setup error, apparmor restrictions or anything else.

My favorite personal question is: Why does an CLI programm need x11 tools?

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Nick!

29 Nov 24, David Gonzalez wrote to Nick Boel:

O pulled the GoldED+ (/home/sbbs/golded-plus) repo

Btw, i noticed msged requires a correct termcap library definition during the complilation process. Is there anything similar that could break golded from the very beginning?

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello David!

29 Nov 24, David Gonzalez wrote to Kai Richter:

Nobody told you to put 'set' in front of that command line!
Blank lines is what you get when you do that.

A well known AI method can't be wrong: Just try any combination.

Meaning?

Just try any meaning. ;-)

Sorry. Back to be serious again. In my point of view the whole world is based on trial and error. It is fine if you try different ways. You don't need help this way because you learn the working way by yourself. But on your own there is a long list of fails that needs much time to be sorted out.

To reduce this time we are asking others if there is a known solution already. We receive others experience and the best thing is: There is a filter that sorts out known failures. If you read Wilfreds lines above than you see that he does know that the line with "set" in front will not work. That is why nobody told you to write "set...".

In this case "set..." may break things. You can set a previous correct working parameter to fail. If your helper doesn't notice that other screws are turned he will wonder why it does not work. Based on your outputs it have to work and he could confirm the working solution on his system. And all because of some missing communication.

Latest example: It took 11 days to sort out that you have two different machines with differnt setups. To us it looked like you have two problems on one machine. Nick found now that one software is not involved on one machine. This would reduce the possible failures making things easier.

In short: It's easier to stay on the bridge if you want to cross the river.
And it's no fun to build a bridge and see people walking through the water.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai!

30 Nov 24 10:29, you wrote to Nick Boel:

Hello Nick!

29 Nov 24, David Gonzalez wrote to Nick Boel:

O pulled the GoldED+ (/home/sbbs/golded-plus) repo

Btw, i noticed msged requires a correct termcap library definition
during the complilation process. Is there anything similar that could break golded from the very beginning?

I did grab termcap file but when I wsa doing the synchronet process, do not if it's related, also even when using Linux VCs it looks wrong "qqq" as lines.

Regards

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (4:930/1)

Hello Kai!

30 Nov 24 10:24, you wrote to Dennis Slagers:

Hello Dennis!

29 Nov 24, Dennis Slagers wrote to David Gonzalez:

Environment=LC_ALL=en_US.UTF-8

Without it a lot of things went wrong on display with my Debian
..

Let's have a look at the display flow:

shell charset
(screen/tmux charset)
golded charset
golded charset translatation
remote terminal translation (putty xterm and charset)

It's difficult as a number of settings can cause golded not to
function properly with its display

Did i miss another location where the translation can be wrong?

If the system was build with the same random configuration method that
is visible here then there could be modifications that knock out
common functions. If x11-utils is installed but luit not found then
there could be a path setup error, apparmor restrictions or anything
else.

My favorite personal question is: Why does an CLI programm need x11
tools?

Why and I wouldn't say that GoldED+ code is incompatible, it wouldn't build at all, to avoid that for my tests on the Linux alternate system, I'm using the BBS to post.

I may derail a bit here but, would you recommend other message editor, I remmeber back in the day when I used Red Hat, I had the same issues but I cannot figure this one.

Another note, By using TERM=v220 it loads ok, but lines are gree (my console colors).

I read Angel or someone else hada batch script adn I'm guessing ti contains variables to load properly, as my system doens't ahve desktop environment not sure if it would show properlky on a Desktop terminal emulator.

Chao

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (4:930/1)

Hello Nick!

29 Nov 24 09:35, you wrote to David Gonzalez:

Have a look at my sig.

I did delete everything form my golded.cfg and recreated it with -INSTALL, Origin shows and so does tearline, but origin is take from goldareas.txt from mystic.

Noty sure how to have golded read the messagebase directly which I know it's JAM but JAMPATH pointing to D:\BBS\MYSTIC\msgs does not load any message base. So my solution here is to copy/paste all AREADEFs to golded.cfg, dumb but is wat works for me ATM.

Cheers

Hello David,

On Fri, Nov 29 2024 08:41:18 -0600, you wrote:

Something else I noticed. The TID kludge of this message shows
you're using Mystic BBS's tosser. So at this point, I have no idea
what you're trying to do here by accessing Synchronet message bases
with Golded, and tossing with Mystic (this should absolutely not
work seeing at the two softwares use completely different message
base formats).

Yes!, you're correct but allow me to explain:

That would have been nice to know much earlier!

- This is my working setup WIndows+Mystic+Golded, tat's why you see
mystic.

While it may be working, it's not currently working /correctly/. Let's
get *THIS* setup working correctly first, as that is the one you're
using to post here currently.

I'm currently on the "production" node 4:930/1, the Linux
SBBS+GoldED is where I'm setting or trying to get a second node
working, sorry if this all confused people. Even though this Goldd
config also appears to have issues.

Most definitely it confused everyone, and most definitely still has
the same issues since the beginning, since you were modifying the
wrong config file. THIS golded config needs to be modified to add your tearline and origin lines.

So it seems you're leaving some valuable information out,

unless you

have Mystic BBS software installed in /sbbs. If so, then you're

not

only confusing yourself, but everyone else, too. :(

Yes and my apologies *all* of what you've seen has come from my
Windwos+mystic+golded node, golded on linux is my side-node.

Many thanks and hope this clears the air a bit.

Yeah, much clearer. That gets rid of Synchronet out of this entire equasion at the moment. Let's get /this/ one working first, then the
other one accessing Synchronet will have completely different
settings.

Regards,
Nick

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

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (4:930/1)

Hello David,

On Sun, Dec 01 2024 07:29:33 -0600, you wrote ..

Have a look at my sig.

Just so you have the correct terminology:

Your /sig/ is "David"
Your /tearline/ is "--- GoldED+/W32-MSVC 1.1.5-b20180707"
Your /Origin/ is " * Origin: " and what follows it.

I did delete everything form my golded.cfg and recreated it with -
INSTALL, Origin shows and so does tearline, but origin is take from goldareas.txt from mystic.

That's great news! The bottom of your messages look much better now.
Thank you.

Noty sure how to have golded read the messagebase directly which I
know it's JAM but JAMPATH pointing to D:\BBS\MYSTIC\msgs does not
load any message base. So my solution here is to copy/paste all
AREADEFs to golded.cfg, dumb but is wat works for me ATM.

The JAMPATH keyword is only for the location of echomail.jam and
netmail.jam files, which you probably aren't using at this point. It has nothing to do with where your message bases are.

If you'd like full access to your message bases, without having to do
multiple AREADEF lines, you probably need to create an AREAS.BBS from
Mystic, and then use AREAFILE to point to that..

1) Create areas.bbs from Mystic, and remember where you created it.
2) Comment out all of your AREADEF lines in /this/ golded.cfg.
3) When all AREADEF lines are commented out: In the same golded.cfg:

AREAFILE AREASBBS /path/to/areas.bbs

Regards,
Nick

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

Hello David!

01 Dec 24, David G wrote to Kai Richter:

I may derail a bit here but, would you recommend other message editor,

If you go for old fidonet software then all editors can have codepage issues.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai!

02 Dec 24 18:06, you wrote to me:

Hello David!

01 Dec 24, David G wrote to Kai Richter:

I may derail a bit here but, would you recommend other message
editor,

If you go for old fidonet software then all editors can have codepage issues.

And your recommended *more modern one* was?.

Thanks

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (4:930/1)