• Manual

    From Chris Jacobs@2:280/5555.11 to All on Wed Sep 2 20:38:05 2026

    Hello everybody!

    I downloaded golded-plus-1.1.5-20260825-win64-msvc18.zip
    In it I found

    gold_ref.txt Copyright (C) 1990-1999 by Odinn Sorensen
    gold_usr.txt Copyright (C) 1990-1998 by Odinn Sorensen

    These seem a little outdated.

    Chris


    --- Binkd, FMail, Golded+
    * Origin: https://drschrisjacobs.nl (2:280/5555.11)
  • From Vincent Coen@2:250/1 to Chris Jacobs on Thu Sep 3 16:35:28 2026

    Hello Chris!

    02 Sep 26 20:38, you wrote to all:


    Hello everybody!

    I downloaded golded-plus-1.1.5-20260825-win64-msvc18.zip
    In it I found

    gold_ref.txt Copyright (C) 1990-1999 by Odinn Sorensen
    gold_usr.txt Copyright (C) 1990-1998 by Odinn Sorensen

    These seem a little outdated.

    Bit like the code - the people doing updates have not been adding update changelogs that revise manual and in some cases not including anything in the log.





    Vincent


    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20240604
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Nick Boel@1:154/10 to Vincent Coen on Thu Sep 3 10:55:18 2026
    Hey Vincent!

    On Thu, 03 Sep 2026 16:35:28 +0100, you wrote:

    Bit like the code - the people doing updates have not been adding update changelogs that revise manual and in some cases not including anything
    in the log.

    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20240604

    Seeing as though you haven't updated in 2+ years, how would you know what you are saying is true? Have you been following any of the work done in 2026; or 2025 for that matter?

    Is anything that you are aware of that needs updating in either of the manuals? If not, everything in them still holds true for the current code.

    The "log" is used for logging issues with Golded once started/running. It's not used for revising or updating progress on the code.

    All recent updates have been written to docs/notework.txt. Not only in the master branch, but in a newly made "unicode" fork, as well. If you followed along with any current progress, you would know that.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20260830
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Vincent Coen@2:250/1 to Nick Boel on Thu Sep 3 18:23:04 2026

    Hello Nick!

    03 Sep 26 10:55, you wrote to me:

    Hey Vincent!

    On Thu, 03 Sep 2026 16:35:28 +0100, you wrote:

    Bit like the code - the people doing updates have not been adding
    update changelogs that revise manual and in some cases not
    including anything in the log.

    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20240604

    Seeing as though you haven't updated in 2+ years, how would you know
    what you are saying is true? Have you been following any of the work
    done in 2026; or 2025 for that matter?

    Is anything that you are aware of that needs updating in either of the manuals? If not, everything in them still holds true for the current
    code.

    The "log" is used for logging issues with Golded once started/running.
    It's not used for revising or updating progress on the code.

    All recent updates have been written to docs/notework.txt. Not only in
    the master branch, but in a newly made "unicode" fork, as well. If you followed along with any current progress, you would know that.

    I update when I can find a copy that will compile but not found any for 2 years
    or so and yes I run under Linux and now have to hit return to get the echo list
    page.


    Vincent


    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20240604
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Chris Jacobs@2:280/5555.11 to Nick Boel on Thu Sep 3 19:47:01 2026

    Hello Nick!

    03 Sep 26 10:55, you wrote to Vincent Coen:

    Is anything that you are aware of that needs updating in either of the manuals? If not, everything in them still holds true for the current
    code.

    A list of ALT keys Golded uses would be nice.
    My sysop boss advised me RTFM but asked where in the FM it was could not find it either.

    Chris

    --- Binkd, FMail, Golded+
    * Origin: https://drschrisjacobs.nl (2:280/5555.11)
  • From Nick Boel@1:154/10 to Vincent Coen on Thu Sep 3 15:02:28 2026
    Hey Vincent!

    On Thu, 03 Sep 2026 18:23:04 +0100, you wrote:

    I update when I can find a copy that will compile but not found any for
    2 years or so

    Did you try the current source on github? Seems to compile just fine for anyone else that has tried recently..?

    and yes I run under Linux and now have to hit return to get the echo
    list page.

    Are you saying you have to hit enter when starting Golded to get to the area list?

    .. that means you probably have a bad option set in your config. What does your golded.log say?

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20260830
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Nick Boel@1:154/10 to Chris Jacobs on Thu Sep 3 15:06:34 2026
    Hey Chris!

    On Thu, 03 Sep 2026 19:47:00 +0200, you wrote:

    A list of ALT keys Golded uses would be nice.
    My sysop boss advised me RTFM but asked where in the FM it was could not find it either.

    Try taking a look at cfgs/config/goldkeys.cfg, which is mentioned and shown, with examples, how to use in both gold_ref.txt and gold_usr.txt. It gives you lists of what is set by default, as well as directions on how to create your own new customized ones.

    Maybe you can give that info to your boss, so the next time someone asks at least he knows where in the FM it is, now. ;)

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20260830
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Vincent Coen@2:250/1 to Nick Boel on Thu Sep 3 21:22:38 2026

    Hello Nick!

    03 Sep 26 15:02, you wrote to me:

    Hey Vincent!

    On Thu, 03 Sep 2026 18:23:04 +0100, you wrote:

    I update when I can find a copy that will compile but not found any
    for 2 years or so

    Did you try the current source on github? Seems to compile just fine
    for anyone else that has tried recently..?

    and yes I run under Linux and now have to hit return to get the
    echo list page.

    Are you saying you have to hit enter when starting Golded to get to
    the area list?

    .. that means you probably have a bad option set in your config. What
    does your golded.log say?

    Nothing.


    Vincent


    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20240604
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Vincent Coen@2:250/1 to Nick Boel on Thu Sep 3 21:42:30 2026

    Hello Nick!

    03 Sep 26 15:02, you wrote to me:

    Hey Vincent!

    On Thu, 03 Sep 2026 18:23:04 +0100, you wrote:

    I update when I can find a copy that will compile but not found any
    for 2 years or so

    Did you try the current source on github? Seems to compile just fine
    for anyone else that has tried recently..?

    and yes I run under Linux and now have to hit return to get the
    echo list page.

    Are you saying you have to hit enter when starting Golded to get to
    the area list?

    Downloaded copied old mygolded.h to folder ran dist-gpl.sh and that prduces lots
    of warnings and errors

    Running GCC 15.2


    Vincent


    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20240604
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Sean Dennis@1:18/200 to Vincent Coen on Thu Sep 3 21:55:40 2026
    Vincent Coen wrote to Nick Boel:

    I update when I can find a copy that will compile but not found any for 2 years
    or so and yes I run under Linux and now have to hit return to get the echo

    list
    page.

    I recently downloaded the GitHub GED+ and it compiled just fine on my
    Slackware 15 system. Perhaps if you are having issuing compiling, you could provide a compile log to the current developer to assist in improving GED+?

    What I compiled: https://github.com/golded-plus/golded-plus/

    I also successfully compiled the same code under a FreeBSD 15.1 VM.

    -- Sean

    --- MBSE BBS v1.1.7.2 (Linux-x86_64)
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Sean Dennis@1:18/200 to Chris Jacobs on Thu Sep 3 21:56:57 2026
    Chris Jacobs wrote to Nick Boel:

    A list of ALT keys Golded uses would be nice.
    My sysop boss advised me RTFM but asked where in the FM it was could not find it either.

    I'd look in goldkeys.cfg to find what you're looking for.

    -- Sean

    --- MBSE BBS v1.1.7.2 (Linux-x86_64)
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Sean Dennis@1:18/200 to Vincent Coen on Thu Sep 3 22:04:43 2026
    Vincent Coen wrote to Nick Boel:

    Downloaded copied old mygolded.h to folder ran dist-gpl.sh and that prduces lots of warnings and errors

    Whenever I compile GED+, I get a lot of warnings and errors, but that's GCC being picky. You can stop the warnings by modifying CMakeLists.txt at the
    top level (before defining the targets): add_compile_options(-w) -- that usually works for me.

    Running GCC 15.2

    I'm using 11.2, but Slackware is very slow to update...

    -- Sean

    --- MBSE BBS v1.1.7.2 (Linux-x86_64)
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Dennis Slagers@2:280/2060 to Sean Dennis on Fri Sep 4 07:39:04 2026

    Hello Sean!

    03 Sep 26 22:04, you wrote to Vincent Coen:

    Downloaded copied old mygolded.h to folder ran dist-gpl.sh and
    that prduces lots of warnings and errors

    Whenever I compile GED+, I get a lot of warnings and errors, but
    that's GCC being picky. You can stop the warnings by modifying CMakeLists.txt at the top level (before defining the targets): add_compile_options(-w) -- that usually works for me.

    I m using Debian 12, compiled it, gets a a lot of warnings, but someone many years told me
    as long as it compiles and does not exit before creating the final binaries are made you are just fine
    Run it and if it works .. it works..

    And it does .. Running the new version now.

    (and I only used 'make')


    Dennis


    ... The system is perfect; humans are flawed.
    --- GoldED+/LNX 1.1.5-b20260830
    * Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)
  • From Vincent Coen@2:250/1 to Sean Dennis on Fri Sep 4 14:08:04 2026

    Hello Sean!

    03 Sep 26 22:04, you wrote to me:

    Vincent Coen wrote to Nick Boel:

    Downloaded copied old mygolded.h to folder ran dist-gpl.sh and
    that prduces lots of warnings and errors

    Whenever I compile GED+, I get a lot of warnings and errors, but
    that's GCC being picky. You can stop the warnings by modifying CMakeLists.txt at the top level (before defining the targets): add_compile_options(-w) -- that usually works for me.

    Running GCC 15.2

    I'm using 11.2, but Slackware is very slow to update...


    Well I added that line near the top in CMakeLists.txt as :

    --
    CMAKE_MINIMUM_REQUIRED(VERSION 2.8...3.19)
    add_compile_options(-w)

    find_program(CCACHE_PROGRAM ccache)

    --

    and used the command :

    ./dist-gpl.sh > build.log 2> build.err

    which produced via ll -h build.*

    -rw-r--r-- 1 mbse bbs 385K Sep 4 14:05 build.err
    -rw-r--r-- 1 mbse bbs 15K Sep 4 14:05 build.log

    So still produced a lot of warnings and as it is still a large file just showing the top few lines produced below :

    --
    gdbgtrk.cpp: In function ‘void __gftrk_track(const char*)’: gdbgtrk.cpp:110:26: warning: operation on ‘__gftrk_curr’ may be undefined [-Wsequence-point]
    110 | __gftrk_curr = (++__gftrk_curr) % __gftrk_max;
    | ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gdbgtrk.cpp:110:26: warning: operation on ‘__gftrk_curr’ may be undefined [-Wsequence-point]
    gftnaddr.cpp: In member function ‘char* ftn_addr::set(const char*, char*, int)’:
    gftnaddr.cpp:175:28: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
    175 | static char* nulchar = "";
    | ^~
    gftnnlfd.cpp: In member function ‘virtual bool ftn_frontdoor_nodelist_index::find(const char*)’:
    gftnnlfd.cpp:724:12: warning: ‘char* strncpy(char*, const char*, size_t)’ specified bound 16 equals destination size [-Wstringop-truncation]
    724 | strncpy(tmp, lookup_name, sizeof(tmp));
    | ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    gkbdunix.cpp: In function ‘int find_the_key(char*, gkbd_key_type**)’: gkbdunix.cpp:538:25: warning: the address of ‘gkbd_key_type::str’ will never be NULL [-Waddress]
    538 | if(key and key->str)
    | ~~~~~^~~
    gkbdunix.cpp:366:10: note: ‘gkbd_key_type::str’ declared here
    366 | char str[7];
    | ^~~
    glog.cpp: In member function ‘void glog::printf(const char*, ...)’: glog.cpp:172:38: warning: ‘%s’ directive writing up to 253 bytes into a region of size 248 [-Wformat-overflow=]
    172 | sprintf(logbuf, "%c %s %4.4s %s", *buf, strftimei(timebuf, 20, "%d-%b %H:%M:%S", &time_now), shortprogname, buf+2);
    | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    glog.cpp:172:16: note: ‘sprintf’ output 9 or more bytes (assuming 262) into
    a destination of size 256
    172 | sprintf(logbuf, "%c %s %4.4s %s", *buf, strftimei(timebuf, 20, "%d-%b %H:%M:%S", &time_now), shortprogname, buf+2);
    | ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    glog.cpp:168:38: warning: ‘%s’ directive writing up to 253 bytes into a region of size 248 [-Wformat-overflow=]
    168 | sprintf(logbuf, "%c %s %4.4s %s", *buf, strftimei(timebuf, 20, "%d %b %H:%M:%S", &time_now), shortprogname, buf+2);
    | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    glog.cpp:168:16: note: ‘sprintf’ output 9 or more bytes (assuming 262) into
    a destination of size 256
    168 | sprintf(logbuf, "%c %s %4.4s %s", *buf, strftimei(timebuf, 20, "%d %b %H:%M:%S", &time_now), shortprogname, buf+2);

    --

    Also within the files are a lot of these :

    --
    eline.cpp: In function ‘void ScanKludges(GMsg*, int)’:
    geline.cpp:1699:33: warning: ISO C++ forbids converting a string constant to ‘cha
    r*’ [-Wwrite-strings]
    1699 | "GoldED",
    | ^~~~~~~~
    geline.cpp:1700:33: warning: ISO C++ forbids converting a string constant to ‘cha
    r*’ [-Wwrite-strings]
    1700 | " GED ",
    | ^~~~~~~
    --


    Now I program as well although using the GnuCobol compiler that traslates into C and compiles to binary etc AND I do not get warning or errors and if I do I fix them as a matter of course. I do not accept any warning or error messages as acceptable.

    Pity the Golded programmers do not feel the same way.


    There again I have been a professional (gets paid for it) for some 60+ years from m/f, mini's and micros.


    Vincent


    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20260304
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Nick Boel@1:154/10 to Vincent Coen on Fri Sep 4 10:05:34 2026
    Hey Vincent!

    On Thu, 03 Sep 2026 21:42:30 +0100, you wrote:

    Downloaded copied old mygolded.h to folder ran dist-gpl.sh and that
    prduces lots of warnings and errors

    Running GCC 15.2

    I'm unaware of what "dist-gpl.sh" does or if it has been modified in the last decade or more. You could just try "make" and see what happens. Works for me. and I'm using gcc (GCC) 16.2.1 20260810. See the latest version in my tearline, compiled about 15 minutes ago with "make GOLD_UTF8=1".

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20260904
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Nick Boel@1:154/10 to Dennis Slagers on Fri Sep 4 10:09:14 2026
    Hey Dennis!

    On Fri, 04 Sep 2026 07:39:04 +0200, you wrote:

    And it does .. Running the new version now.

    (and I only used 'make')

    --- GoldED+/LNX 1.1.5-b20260830

    FYI, there's a newer version already. ;)

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20260904
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Eugene Subbotin@2:5075/35 to Nick Boel on Fri Sep 4 18:41:02 2026
    Hello Nick!

    Friday September 04 2026 10:05, you wrote to Vincent Coen:

    I'm unaware of what "dist-gpl.sh" does or if it has been modified in
    the last decade or more. You could just try "make" and see what
    happens. Works for me. and I'm using gcc (GCC) 16.2.1 20260810. See
    the latest version in my tearline, compiled about 15 minutes ago with "make GOLD_UTF8=1".

    That's right. This script is outdated; it hasn't changed in years and isn't used in current builds, so I'm not even sure if it still works. The entire build system is based on GNU Makefile or CMake and doesn’t require any separate scripts. The script in question clearly hasn’t been updated in decades and was migrated to GitHub from the old SourceForge repository.

    Eugene

    ... It's full of stars!
    --- GoldED+/BSD 1.1.5-b20260904 (NetBSD 11.0 Intel Core Haswell)
    * Origin: FireFox Station (2:5075/35)
  • From Sean Dennis@1:18/200 to Dennis Slagers on Fri Sep 4 12:35:27 2026
    Dennis Slagers wrote to Sean Dennis <=-

    I m using Debian 12, compiled it, gets a a lot of warnings, but someone many years told me
    as long as it compiles and does not exit before creating the final binaries are made you are just fine
    Run it and if it works .. it works..

    Turning off warnings can occasionally speed things up considerably which is
    why I do it.

    -- Sean

    ... What does a nosey pepper do? It gets jalapeno business.

    --- MultiMail/Win
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Sean Dennis@1:18/200 to Nick Boel on Fri Sep 4 13:13:19 2026
    Nick Boel wrote to Vincent Coen <=-

    I'm unaware of what "dist-gpl.sh" does or if it has been modified in
    the last decade or more.

    It's the script that resides in the main directory of the source code
    directory that compiles GoldEd+ for Linux.

    I don't use it; I manually install it using cmake and it works fine under
    Linux and FreeBSD.

    I did just try it in a Slackware 15 VM and the script works for me, even as outdated as it is.

    -- Sean

    --- MultiMail/Win
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Sean Dennis@1:18/200 to Vincent Coen on Fri Sep 4 13:21:08 2026
    Vincent Coen wrote to Sean Dennis <=-

    Now I program as well although using the GnuCobol compiler that
    traslates into C and compiles to binary etc AND I do not get warning or errors and if I do I fix them as a matter of course. I do not accept
    any warning or error messages as acceptable.

    That's just the nature of running 35-year-old C code through a modern compiler—-it's going to shout, but it is what it is. Since we can't change how GCC behaves much with old code, there's not much use worrying about it unless you want to refactor the whole codebase for free...which is something
    I don't think anyone wants to do on their own time.

    -- Sean


    --- MultiMail/Win
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Eugene Subbotin@2:5075/35 to Sean Dennis on Fri Sep 4 22:21:54 2026
    Hello Sean!

    Friday September 04 2026 13:21, you wrote to Vincent Coen:

    @CHRS: CP850 2
    compiler—-it's going to shout, but it is what it is. Since we can't
    ^^^
    Looks like wrong charset selected: UTF-8 sequence under CP850 CHRS kludge :)

    Eugene

    ... It's full of stars!
    --- GoldED+/BSD 1.1.5-b20260904 (NetBSD 11.0 Intel Core Haswell)
    * Origin: FireFox Station (2:5075/35)
  • From Michiel van der Vlist@2:280/5555 to Sean Dennis on Fri Sep 4 21:28:50 2026
    Hello Sean,

    On 04 Sep 26 13:21, you wrote to Vincent Coen:

    @MSGID: 1:18/200@fidonet 66966797
    @PID: MBSE-BBS 1.1.7.2 (Linux-x86_64)
    @CHRS: CP850 2

    The CHRS kludge in your messade says CP850

    That's just the nature of running 35-year-old C code through a modern compiler—-it's going to shout, but it is what it is. Since we can't
    ^
    But the first "dash" here is UTF-8. There is a misconfigution in your setup.

    Luckily this gives me an opportunity to test the "XLATUTFAUTODETECT override" option. It works as expected! ;-)


    Cheers, Michiel

    --- GoldED+/W32-MINGW 1.1.5-b20260904
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Vincent Coen@2:250/1 to Sean Dennis on Fri Sep 4 21:14:39 2026

    Hello Sean!

    04 Sep 26 13:21, you wrote to me:

    Vincent Coen wrote to Sean Dennis <=-

    Now I program as well although using the GnuCobol compiler that
    traslates into C and compiles to binary etc AND I do not get
    warning or errors and if I do I fix them as a matter of course. I
    do not accept
    any warning or error messages as acceptable.

    That's just the nature of running 35-year-old C code through a modern compiler—-it's going to shout, but it is what it is. Since we can't
    change how GCC behaves much with old code, there's not much use
    worrying about it unless you want to refactor the whole codebase for free...which is something I don't think anyone wants to do on their
    own time.

    If you are referring to age of sources, my site of programs that is over 500k lines of code in Cobol started life around 1970 odd. Some sections before and others later. The compiler at the time was Micro Focus Workbench but I discontinued that after the later new version of its successor went to 6k pounds and now that yet another company has bought it it is ever more expensive
    with even less support, even for obtaining the personal edition (as I now
    offer all the sources FOC as O/S on SF.

    So switched to using GnuCobol which is free to obtain and use.
    Just took some time to migrate it but not that long - under 40 hours.


    Vincent


    --- Mageia Linux v10 X64/Mbse v1.1.7.2/GoldED+/LNX 1.1.5-b20260304
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Sean Dennis@1:18/200 to Eugene Subbotin on Fri Sep 4 18:05:07 2026
    Hello Eugene,

    04 Sep 26 22:21, you wrote to me:

    Looks like wrong charset selected: UTF-8 sequence under CP850 CHRS
    kludge :)

    Yep, been dealing with that for 30 years from Windows boxes.

    - Sean

    ... Complex problems have simple, easy to understand wrong answers.
    --- GoldED+/LNX 1.1.5-b20260304
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Sean Dennis@1:18/200 to Vincent Coen on Fri Sep 4 18:22:05 2026
    Hello Vincent,

    04 Sep 26 21:14, you wrote to me:

    If you are referring to age of sources

    No, I was not. I was referring to the GoldEd source code, not whatever 'sources' you are talking about. To repeat what I said more succinctly: don't look a gift horse in the mouth. The developers are spending their own free time and effort to help the community. If you aren't going to use your 'decades of professional experience' to submit a code fix for them, complaining about the warnings is just wasting everyone's time.

    -- Sean

    ... "It compiles? Ship it!" -- Bill Gates, probably
    --- GoldED+/LNX 1.1.5-b20260304
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Sean Dennis@1:18/200 to Eugene Subbotin on Fri Sep 4 18:50:20 2026
    Hello Eugene,

    04 Sep 26 22:21, you wrote to me:

    Looks like wrong charset selected: UTF-8 sequence under CP850 CHRS
    kludge :)

    Just built your binary successfully here using the instructions I gave Vince.

    My system info for you:

    mbse@bbs.outpostbbs.net
    -----------------------
    OS: Slackware 15.0 x86_64 x86_64
    Host: Wistron Corporation HPE ProLiant ML110 G6
    Kernel: 5.15.209
    Shell: bash 5.1.16
    CPU: Intel Xeon X3430 (4) @ 2.395GHz
    GPU: Matrox Electronics Systems Ltd. ProLiant
    Memory: 592MiB / 7938MiB

    Thanks for bringing GED forward!

    -- Sean

    ... The slowest checker is always at the quick check-out lane.
    --- GoldED+/LNX 1.1.5-b20260304
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Dennis Slagers@2:280/2060 to Nick Boel on Sat Sep 5 08:33:02 2026

    Hello Nick!

    04 Sep 26 10:09, you wrote to me:

    (and I only used 'make')

    --- GoldED+/LNX 1.1.5-b20260830

    FYI, there's a newer version already. ;)

    You were saying?

    .. damn those timezones .. When I looked when I had time yesterday there was no new release yet
    Now 17 hours later there was ..

    still ? why the binaries are executable and golded not after the 'make' where my system needs golded to be executable
    LOL ;)

    Dennis


    ... I don't have a solution, but I admire the problem.
    --- GoldED+/LNX 1.1.5-b20260904
    * Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)
  • From Dennis Slagers@2:280/2060 to Sean Dennis on Sat Sep 5 08:36:02 2026

    Hello Sean!

    04 Sep 26 12:35, you wrote to me:

    I m using Debian 12, compiled it, gets a a lot of warnings, but
    someone many years told me as long as it compiles and does not
    exit before creating the final binaries are made you are just
    fine Run it and if it works .. it works..

    Turning off warnings can occasionally speed things up considerably
    which is why I do it.

    Check! ;)
    I am just a silly user sometimes forced into 'make' where he prefers ready to use systems ;)


    Dennis


    ... That feature isn't broken; it's "dynamic."
    --- GoldED+/LNX 1.1.5-b20260904
    * Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)