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 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
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: The File Bank BBS! https://tfb-bbs.org (3:712/1321)
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)
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
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
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?
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?
While they don't seem to show up in Golded (Golded must stillfilter
this),
I'm seeing your SEEN-BYs in every message you post, too. These don'tlook 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.
SEEN+BY lines normally don't have a CTRL character in front of them!
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).
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.
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.
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?
LANG=es_ES.ISO8859-1 luit -encoding ISO8859-1 gedlnx
-Cpath_to_cfg
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,* Origin: The File Bank BBS! https://tfb-bbs.org (3:712/1321)
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.* Origin: The File Bank BBS! https://tfb-bbs.org (3:712/1321)
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Deputy Nodelist Police (2:280/2060)
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
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
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
New... well, I don't consider myself new but I'm a self-proclaimed
expert, so yeah I might be missing some concepts.
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
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
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
* Origin: The File Bank BBS! https://tfb-bbs.org (3:712/1321)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)
Tried this but Ubuntu reports luit not found, triued intalling it but
no install candidate
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
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.
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,* Origin: The File Bank BBS! https://tfb-bbs.org (3:712/1321)
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)
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.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 47:11:58 |
Calls: | 161 |
Files: | 5,321 |
Messages: | 221,633 |