Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 68:30:45 |
| Calls: | 12 |
| Files: | 12,938 |
| Messages: | 99,147 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
Those warnings are "normal". In terms like they better be fixed, by they are expected especially in new compiler. They mostly safe and you may ignore them.
Do you use following parameters when build it:
USE_NCURSES
WIDE_NCURSES
BUGGY_NCURSES
And which ncurses library version do you have?
That is interesting. It shall work totally fine without screen multiplexor.
Would be interesting to understand how screen or tmux makes a difference.
BTW, what do you have for $TERM env variable?
My last commit rollback some change I made previously because it was found to be buggy in some cases. So it could be some other change actually.
If you familiar with git, would be nice if you hunt down which commit makes
things worse in your setup. You may use git bisect for that.
https://git-scm.com/docs/git-bisect
It is very good actually. Golded writes errors in that file and if it empty
- it's a good sign.
Moved to next line is OK. It's just for messages, which has lines longer than your terminal width.
To use cp437 you need to change Putty config for sure. And I'd recommend you to use one byte locale for golded if you don't need many different encodings. That will solve many issues for you right away.
Some people do experience issues like you. And would be really great to find and fix root cause.
Could you also try to remove file goldxlat.gel? Golded will generate it on start.
That "q" reference sounded familiar. I found a setting in putty that mentions this:
https://paste.opensuse.org/pastes/6fc707014110
Btw: With these settings your messsages look OK in putty. But now my 'mc' linedrawing characters look totally borked. When I set putty to use utf-8,
'mc' looks ok, but your messages in golded look like this:
https://paste.opensuse.org/pastes/13f114dba16c
Not as it should be, but usable...
It is pitty...
My last commit rollback some change I made previously because it was found to be buggy in some cases. So it could be some other change actually.
If you familiar with git, would be nice if you hunt down which commit makes
things worse in your setup. You may use git bisect for that.
https://git-scm.com/docs/git-bisect
Would be interesting to understand how screen or tmux makes a
difference.
It wasn't much, it just displayed the above mentioned things correctly without any additional PuTTY settings.
BTW, what do you have for $TERM env variable?
TERM="xterm"
Moved to next line is OK. It's just for messages, which has lines
longer than your terminal width.
Is there a way to change the line length in Golded? If it is set for something like 78 by default, maybe changing it to 79 would help as it could be one extra character that's causing it to wrap to the next
line. Although, I don't know how replies and quotes coming from here
would look on others' systems then.. I'd rather break things on my
end, not others. :)
To use cp437 you need to change Putty config for sure. And I'd
recommend you to use one byte locale for golded if you don't need
many different encodings. That will solve many issues for you
right away.
Honestly, I have no interest in using CP437 in a terminal. I don't
mind some irregularities, but this time there were just more than
usual.
I don't like things easy. For some reason I enjoy making things
extremely difficult for myself.
Some people do experience issues like you. And would be really
great to find and fix root cause.
I agree! Then again, if/when you get iconv working properly I think
many of these issues will probably disappear since iconv > old crusty translation tables.
Could you also try to remove file goldxlat.gel? Golded will
generate it on start.
I did, and it didn't change anything. I'll use 'git bisect' and see if
I can figure out if a recent commit changes it back to the way it was.
My last commit rollback some change I made previously because it
was found to be buggy in some cases. So it could be some other
change actually.
If you familiar with git, would be nice if you hunt down which
commit makes things worse in your setup. You may use git bisect
for that.
https://git-scm.com/docs/git-bisect
I'm not very familiar with it, but I was able to figure it out with
the link you provided. Thank you!
$ git bisect start
$ git bisect bad
$ git bisect good f7be1e97e251ee2be20f63abdcf2a18f93c880b9
I chose this commit because it was just prior to the 'revert "zero conversion" workaround', where things were definitely looking more
towards 'normal'.
$ make BUILD=minimal (this compiled version 20231112 for some reason I don't yet understand)
It was back to normal with this compile.
$ git bisect good
$ make BUILD=minimal (this compiled version 20240206)
It was still good.
$ git bisect good
https://pharcyde.org/git-bisect-result.png
It seems as though I'm back to the way it was in version GoldED+/LNX 1.1.5-b20240206. Here is an example:
https://pharcyde.org/golded-20240206.png
$ git bisect reset (to go back to the master branch 20240209)
$ make BUILD=minimal
https://pharcyde.org/golded-20240209.png
Same configuration in golded.conf:
[ start paste ]
# Character translation path
xlatpath /home/axisd/src/golded-plus/cfgs/charset
include /home/axisd/src/golded-plus/cfgs/config/charsets.cfg
# UTF-8 Configuration
#
xlatcharset utf-8 utf-8 utf_utf.chs
xlatimport cp437
xlatexport utf-8
xlatlocalset utf-8
[ end paste ]
For bisect you better chose wider range. Like a year or so. With bisect you
only need ln(N) tries to find broken commit. It could be broken earlier actually.
You have xlatimport cp437.
Does that message with broken pseudo-graphics have CHRS kludge? If not - is
it really in cp437 encoding? Pseudo-graphics characters located in second half of charset table and it's different for different charsets.
Just make your terminal wider and then start golded. It will use whole window width unless you use "Dispmargin" parameter in your config. As for quotes, they will be broken down to "Quotemargin" columns.
Sure. That's your choice. :) I just want to tell that GoldEd was designed to work with one byte encodings and UTF-8 may work incorrectly.
I'm working on some refactoring now in charset conversions now. When that is done, then iconv integration will be very simple.
Got it. What is weird, last commit fixed issue for one sysop and broken it for you.
Could you try to build from commit 372220588c6f17cd3f709dcb721a9144169d988c
? It was before all my changes. If it will have same behavior, then it's something wrong with setup on your side and we'll try to figure that out.
It is pitty...
It looks like the two of you that have this similar issue are using a
form of LATIN codepage (you with LATIN-2, and Al with LATIN-1). Just
an observation. Hope you figure it out!
It looks like the two of you that have this similar issue are using a
form of LATIN codepage (you with LATIN-2, and Al with LATIN-1). Just
an observation. Hope you figure it out!
I will try to get more data about that.
That "q" reference sounded familiar. I found a setting in putty that
mentions this:
https://paste.opensuse.org/pastes/6fc707014110
That doesn't seem to work very well for me.
Just make your terminal wider and then start golded. It will use
whole window width unless you use "Dispmargin" parameter in your
config. As for quotes, they will be broken down to "Quotemargin"
columns.
My terminal during that session is already 160 wide, so that's not the issue with the random wrapping of those characters, then.
Sure. That's your choice. :) I just want to tell that GoldEd was
designed to work with one byte encodings and UTF-8 may work
incorrectly.
Definitely understood. However, it worked _better_ before, and I'm
just trying to figure out what happened and why.
With that said, I'm not ruling out the possibility something was
actually "fixed" that broke my utf-8 hackery, either. :)
Got it. What is weird, last commit fixed issue for one sysop and
broken it for you.
Yes, I know. I've had some side discussions with Wilfred about this
exact issue. However, it seems he's using a bit more of a single-byte setup than I am. So, it's possible that he is doing less translation
from cp437 to utf-8 (as far as I know, he isn't using any xlat
settings whatsoever in golded.conf) .
Could you try to build from commit
372220588c6f17cd3f709dcb721a9144169d988c ? It was before all my
changes. If it will have same behavior, then it's something wrong
with setup on your side and we'll try to figure that out.
I can, but as I'm not super experienced with git, so I have some questions.
When I use 'git bisect' with these steps:
$ git bisect start
$ git bisect bad
$ git bisect good 372220588c6f17cd3f709dcb721a9144169d988c
I get this:
Bisecting: 29 revisions left to test after this (roughly 5 steps) [f535cc792abd5d254da57a2f5b70d5b02cbd7abf] Add github actions badge
This is a much later revision after quite a few of your changes, so
'git bisect' didn't seem to take me back as far as you wanted me to
go.. unless I'm doing something wrong.
I did see this after typing 'git bisect --help':
" Once you have specified at least one bad and one good commit, git
bisect selects a commit in the middle of that range of history, checks
it out, and outputs something similar to the following: "
So am I actually able to specify which commit I would like to go back
to with 'git bisect' or should I use 'git checkout'? If checkout is
the answer, I won't be able to keep track of good or bad commits any
more.
Hello Nicholas!
16 Feb 24 08:30, I wrote to you:
Symptom in Subject:
4 characters from position 13 copied to position 9
  correct: 123456789ABCDEFGHIJKL
will look: 12345678DEFGDEFGHIJKL
(no matter if EDITREPLY is setup and how)
Happening if:
- If subject is longer than 16 characters (better to say, short ones can not see)
- CHRS is missing
- CHRS is one of: LATIN-1 2, UTF-8 2
-- but - not always
- where CHRS look ok: CP850 2, UTF-8 4
-- again - not always...
Karel
--- GoldED+/LNX 1.1.5-b20180707
 * Origin: Plast DATA (2:423/39)
So do you have terminal 160 chars wide, but message displayed narrower?
So how bisect works.
You start process with git bisect start as you already did.
First you mark some commit which is good for sure with git bisect good. Then mark "bad" commit with git bisect bad. That will be last commit in repo.
git will checkout commit in the middle of those two for you. Then you build
it and test. If it's good, run git bisect good, if it's bad, git bisect bad. Build it and test again.
So do you have terminal 160 chars wide, but message displayedYes, the message itself was created by a script and was only 78
narrower?
characters wide to begin with when it was created, and is posted to
the message base with 'hpt post'.
I just think that my utf-8 hackery may be moving some of those line drawing characters to the next line when it shouldn't be doing so.
Maybe there are some soft CRs in there I should be looking for (I
don't know how to spot those)?
So how bisect works.
You start process with git bisect start as you already did.
First you mark some commit which is good for sure with git bisect
good. Then mark "bad" commit with git bisect bad. That will be
last commit in repo. git will checkout commit in the middle of
those two for you. Then you build it and test. If it's good, run
git bisect good, if it's bad, git bisect bad. Build it and test
again.
That's how I understand it. However, you asked me to roll back to a specific version, and git bisect is not able to do that.
So without going that route, I can say ever since you've started
updating Golded I haven't had any display issues, until this latest version. What you seemed to have fixed for Wilfred, did the opposite
for me. :)
Then most probably it has 'soft CR'. You may dump message hex codes with 'I'.
If you just want to use specific commit, then use git checkout. If you want
to do binary search for broken commit - use git bisect interactively. Here's a tutorial, how to use it:
And that's is very strange. I'd not be surprised if it was broken when I made first change (which was reverted by last commit), but looks like it worked fine.
Then most probably it has 'soft CR'. You may dump message hex
codes with 'I'.
I assume I'm looking for 8D somewhere? If so, there are none in the
entire message.
I did notice a question mark in the message body:
00B0 C4 C4 C4 C4 C4 BF 20 C4 C4 C4 C4 C4 C4 C4 C4 C4 ?
But that's about it as far as anomolies.
If you just want to use specific commit, then use git checkout.
If you want to do binary search for broken commit - use git
bisect interactively. Here's a tutorial, how to use it:
I used checkout to get the specific commit you asked me to grab (372220588c6f17cd3f709dcb721a9144169d988c), and it is indeed exactly
how the latest version is. So you were right.
And that's is very strange. I'd not be surprised if it was broken
when I made first change (which was reverted by last commit), but
looks like it worked fine.
It did not. Whatever first change you made actually kind of helped me,
I suppose. Hopefully this helps narrow things down better and we can figure out what's going on.
Code 20 is a space. So wrapping caused by that.
Also check if you have DispMargin parameter in your config. If you do - comment it out or remove. Then GoldEd will use all window width.
You said that before you started to experiment - all worked fine. Have you used same compiler? Now I suspect that issue caused by something in your setup. Because it's quite opposite from others have.
That's why would be interesting to use bisect from 372220588c6f17cd3f709dcb721a9144169d988c to master and find specific commit
which made it bad in your specific case.
Your mail editor seems to insert an unnecessary utf-8 character, I can't read, in front of these quoted lines. :-(
Your mail editor seems to insert an unnecessary utf-8 character,
I can't read, in front of these quoted lines. :-(
I looked back on a few previous messages, and it seems to only add it
once the quote level gets to 3. (>>>). I will take a look, thanks!
I looked back on a few previous messages, and it seems to only
add it once the quote level gets to 3. (>>>). I will take a look,
thanks!
Also with level 2.
Thunderbird seems to replace some normal spaces by non-breaking spaces (UTF-8: C2 A0) in quotes. I intended to investigate this...
Also with level 2.
Code 20 is a space. So wrapping caused by that.I doubt it.
Also check if you have DispMargin parameter in your config. If
you do - comment it out or remove. Then GoldEd will use all
window width.
Most likely whatever the default settings is, since I don't use it in
my config.
You said that before you started to experiment - all worked fine.I said before that it has looked fine for quite some time. I didn't go back to the version you asked me too until I got the answer to use 'checkout' instead of 'bisect'. Now that I was able to go back that
Have you used same compiler? Now I suspect that issue caused by
something in your setup. Because it's quite opposite from others
have.
far, I was able to give you a better answer.
That's why would be interesting to use bisect from
372220588c6f17cd3f709dcb721a9144169d988c to master and find
specific commit which made it bad in your specific case.
I did this, sort of. Instead of bisect, I used checkout and tried
every version after 372220588* until I got to the one that changed the display.
8e9f3518ac9b3b32676e7b7563e92cc44e7b5ba7 is the commit that changes
things for the better in my case.
It stayed that way until you reverted the commit in the latest
version.
My only thoughts is that I am using PuTTY to connect with utf-8
settings to a utf-8 linux terminal. I include golded-plus/cfgs/config/charsets.cfg so I basically translate to and
from everything currently possible.
Maybe Wilfred had issues with this commit because he's not actually
using any xlat configuration? He had told me he's using some kind of
half and half utf-8/cp437 terminal and not using any xlat* settings in
his configuration. If he can view that stat screen I posted as well as view Michiel's tearline and origin line over in the UTF-8 echo during
the same golded session and no configuration changes, I would be surprised.
This is with 8e9f3518*:
https://pharcyde.org/golded-stats.png
https://pharcyde.org/golded-utf8.png
As you can see the only issue I seem to have with this version (and everything up till the 20240206 release) is a few line wraps on the
stat screen that shouldn't be happening - and I don't have a very extensive golded.conf where I could see anything in there that would
be causing that, except the translation tables themselves.
Default is to use whole window. Then it's weird, that line is broken.
That's something. Thanks for doing that.
Have you tried to run it in local terminal emulator? Do you have any GUI on
that computer?
Putty may be pain in the ass to configure correctly.
Would be cool if you may share your config and message base with message containing pseudo-graphics for me to play with. If I reproduce it internally - then I may find the cause very quickly! By config I mean not only golded.cfg, but all included files, including charset tables.
Sure. I will netmail you a link to the zip file. You will most likely have the directory structure in the config to make things work, but otherwise all pertinent information should be there.
Sure. I will netmail you a link to the zip file. You will most
likely have the directory structure in the config to make things
work, but otherwise all pertinent information should be there.
"You will most likely have *to change* the directory structure."
It was not a Golded bug, it was user error. ;)
Are you referring to having these issues with a version from 2018? If
so, I would suggest you upgrade to the latest version and see if you
have any of the same issues you have now.
Are you referring to having these issues with a version from 2018? If
so, I would suggest you upgrade to the latest version and see if you
have any of the same issues you have now.
Just did and same result (= same issues).
If that is the case, and you have the sources, try including 'golded-plus/cfgs/config/charsets.cfg' in your golded.conf and see if
that helps or not.
For that group I have:
GROUP B
XLATPATH /home/fido/golded/xlat
XLATCHARSET CP437 LATIN-2 asc_il2.chs
XLATCHARSET LATIN-2 CP437 il2_asc.chs
XLATIMPORT CP437
XLATIMPORT CP437
XLATLOCALSET LATIN-2
MSGLISTWIDESUBJ YES
ENDGROUP
If that is the case, and you have the sources, try including
'golded-plus/cfgs/config/charsets.cfg' in your golded.conf and
see if that helps or not.
Already have that since ever.
For that group I have:
GROUP B
XLATPATH /home/fido/golded/xlat
XLATCHARSET CP437 LATIN-2 asc_il2.chs
XLATCHARSET LATIN-2 CP437 il2_asc.chs
XLATIMPORT CP437
XLATIMPORT CP437
XLATLOCALSET LATIN-2
MSGLISTWIDESUBJ YES
ENDGROUP
Using UTF-8 in putty, having LANG=cs_CZ.utf8 in bash, startin golded:
luit -encoding 'ISO-8859-2' ./gedlnx -f
(because GROUP A we have ISO-8859-2 as agreed coding)
As I wrote, I have issue in GROUP B, GOLDED here...
For that group I have:
GROUP B
XLATPATH /home/fido/golded/xlat
XLATCHARSET CP437 LATIN-2 asc_il2.chs
XLATCHARSET LATIN-2 CP437 il2_asc.chs
XLATIMPORT CP437
XLATIMPORT CP437
XLATLOCALSET LATIN-2
MSGLISTWIDESUBJ YES
ENDGROUP
Are you using the wrong translation table? I think you should be using cp437 -> il2, rather than ascii -> il2.
Are you using the wrong translation table? I think you should be using
cp437 -> il2, rather than ascii -> il2.
Most probably he does because it works for him prior to my last changes. So I assume that text conversion performed correctly.
Try to set LANG to cs_CZ.ISO8859-2 and that will solve your issue! No
need to set it for the whole system. Just for golded session.
$ LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f
Your problem is that luit converts symbols from 8859-2 to UTF, but
ncurses tries to work in UTF-8 mode because you have LANG=cs_CZ.utf8.
Are you using the wrong translation table? I think you should be using cp437 -> il2, rather than ascii -> il2.
Are you using the wrong translation table? I think you should be using
cp437 -> il2, rather than ascii -> il2.
I do not have xlat file like that.
Point is that in group B there I expect only English and old fashioned ascii 127 anyway.
You might want to try iso-8859-2 in PuTTY, also, rather than UTF-8.
Then try the command line that Vitaliy recommended to use?
xlatcharset cp437 utf-8 437_u8.chs
If that .chs file isn't in your xlat directory, I believe you can grab
it from Golded sources on github.
Try to set LANG to cs_CZ.ISO8859-2 and that will solve your
issue! No need to set it for the whole system. Just for golded
session.
$ LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f
Just did, but no improvement. Would it be possible that old messages
are alreadu scrambled and I have to wait for new examples?
Your problem is that luit converts symbols from 8859-2 to UTF,
but ncurses tries to work in UTF-8 mode because you have
LANG=cs_CZ.utf8.
I am not sure that is just my XLAT setup or BASH env. Interesting is,
that it is only subject (message is OK). What is difference for XLAT
in Subj and in Message? Why one UTF-8 is OK a different is not (UTF-8
4 against UFT-8 2)?
And there was another collegue who has same issue (assume different setup).
Could you please make sure that your system actually has such locale?
What does it show if you run:
LANG=cs_CZ.ISO8859-2 locale
Also try to run:
locale -a
It could be both. Could you please show your xlat setup?
BTW, luit works for me. Only difference is that my FidoNet charset is KOI8-r.
As for UTF - it's not supported and might "work" if you do some weird setup, but I'd not count on it. Better work in one-byte locales like
cp437 or ISO8859-2 in your case.
I totally understand you. I spend several days before my system
started to work OK. Will try to resolve your issues. :)
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-b20240302SEEN-BY: 4/0 80/1 90/0 103/705 124/5016 153/757 154/10 30 203/0 218/700 221/0 SEEN-BY: 221/1 6 229/426 240/1120 5832 280/464 5003 5006 5555 292/854 8125 SEEN-BY: 301/1 113 123 812 310/31 335/364 341/66 234 396/45 423/120 460/58 SEEN-BY: 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1
* 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?
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
x 2 REGION93 0 REGION93 FPick New Area: lqAreaqDescriptionqqqqqqqqqqqMsgsqqqqNewqqEchoIDqqqqqqqqGqkxqqqqqqGrupo de Echomailsqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq x 1 Area de pruebas 0 ESP.PRUEBAS 27 0 ESP.PRUEBAS F
Thanks Angel, I tried your suggestion and Fernando Toledo's sample
config with no luck my golded still looks like this:
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,
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)
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
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
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.SEEN-BY: 80/1 103/705 124/5016 153/757 154/10 30 203/0 218/700 221/0 1 6 SEEN-BY: 240/1120 280/464 301/1 113 123 812 335/364 341/66 200 234 460/58 SEEN-BY: 712/848 5020/1042 229/426 103/705 218/720 102/401 103/1 218/215 840 SEEN-BY: 218/860 880 214/22 218/870 930 601 124/5016 218/700 1 10/1 218/0 10/0
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
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,
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.
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!
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.
x 1 NETMAIL 0 0 Netmail - xqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqxPick New Area: lqAreaqDescriptionqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqMsgsqqqqNewqqEchoIDqqqk
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.
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)
Love your charming ways
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)
LANG=es_ES.ISO8859-1 luit -encoding 'ISO-8859-2' gedlnx -C ./
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 (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
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
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
X terminal emulator
Whatever the error I'm making... I cannot seem to find it
Nobody told you to put 'set' in front of that command line! Blank
lines is what you get when you do that.
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)
SBBS is not there, as per the path /home/sbbs is $HOME for sbbs user,
SBBS lives under /sbbs
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
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
USERNAME David Gonzalez
ADDRESS 4:930/10
AREADEF Netmail "NETMAIL" 0 Net OPUS /sbbs/fido/netmail
AREAFILE AreasBBS /sbbs/data/areas.bbs
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
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.
Sorry but I'm confused about this
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
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.
virtualCommand '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
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.SEEN-BY: 4/0 80/1 90/0 103/705 154/10 218/700 221/1 6 229/426 240/1120 280/464 SEEN-BY: 301/1 113 123 812 335/364 341/66 200 234 460/58 712/848 900/0 102 106 SEEN-BY: 902/0 19 26 930/1 10 5020/1042 229/426 103/705 218/720 102/401 103/1 SEEN-BY: 218/215 840 860 880 214/22 218/870 930 601 124/5016 218/700 1 10/1 SEEN-BY: 218/0 10/0
--- 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,SEEN-BY: 4/0 80/1 90/0 103/705 154/10 218/700 221/1 6 229/426 240/1120 280/464 SEEN-BY: 301/1 113 123 812 335/364 341/66 200 234 460/58 712/848 900/0 102 106 SEEN-BY: 902/0 19 26 930/1 10 5020/1042 229/426 103/705 218/720 102/401 103/1 SEEN-BY: 218/215 840 860 880 214/22 218/870 930 601 124/5016 218/700 1 10/1 SEEN-BY: 218/0 10/0
Nick
... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
(1:154/700)
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:
- This is my working setup WIndows+Mystic+Golded, tat's why you see mystic.
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.
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.
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.SEEN-BY: 4/0 80/1 90/0 103/705 124/5016 153/757 154/10 30 203/0 218/700 221/0 SEEN-BY: 221/1 6 229/426 240/1120 5832 280/464 5003 5006 5555 292/854 8125 SEEN-BY: 301/1 113 123 812 310/31 335/364 341/66 234 396/45 423/120 460/58 SEEN-BY: 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1 10 SEEN-BY: 5020/400 1042 229/426 103/705 218/720 102/401 103/1 218/215 840 860 SEEN-BY: 218/880 214/22 218/870 930 601 124/5016 218/700 1 10/1 218/0 10/0
--- 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.
RegardsSEEN-BY: 4/0 80/1 90/0 103/705 124/5016 153/757 154/10 30 203/0 218/700 221/0 SEEN-BY: 221/1 6 229/426 240/1120 5832 280/464 5003 5006 5555 292/854 8125 SEEN-BY: 301/1 113 123 812 310/31 335/364 341/66 234 396/45 423/120 460/58 SEEN-BY: 467/888 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1 10 SEEN-BY: 5020/400 1042 229/426 103/705 218/720 102/401 103/1 218/215 840 860 SEEN-BY: 218/880 214/22 218/870 930 601 124/5016 218/700 1 10/1 218/0 10/0
Kai
--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)
Environment=LC_ALL=en_US.UTF-8
Without it a lot of things went wrong on display with my Debian ..
It's difficult as a number of settings can cause golded not to
function properly with its display
O pulled the GoldED+ (/home/sbbs/golded-plus) repo
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?
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 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 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'renot
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)
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.
I may derail a bit here but, would you recommend other message editor,
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)
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?.
Hello David!
02 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?.
There is none. The Fidonet Technology Standard is old.
Fidonet Technology Networks are build on old standards.
Modern moved forward to UTF and Unicode and left Fidonet behind.
Regards
Kai
--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)
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
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 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
Hello Nick!
01 Dec 24 09:18, you wrote to David Gonzalez:
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
This did work, basic setup plus these and my unction keys to force
mail processing are working (on windows+mystic+golded)
Strange thing if you notice now my origin doesn't contain bbs.skynetbbs.com, I'm not really sure if mystic's areaas.bbs takes
care of that or if I should add an Origin line manually w/out screwing what already works.
This happened after I removed all AREADEF lines from *this* golded.cfg
and included the areas.bbs, strange.
Looking into it tho.
Regards,
Nick
David
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: (4:930/1)
Sure, looks better but still missing a tagline and some more info I
would like to put, but that'll do for now.
!d:\bbs\mystic\msgs\rberrypi RBERRYPI 4:902/26 4:930/1.10 4:930/10
Thanks will try and let yall know.
Thanks for your help and suggestion, I definitely could not get luit installed/working, I put you commands on a bash script but again luit
is teb issue.
