[Freedos-devel] New libfp-0.0!
I first mentioned libfp a few years ago, and I thought I could enhance its development by releasing what I have so far. The library libfp is the complement to libmpi. It handles floating-point math and complex math as part of the C runtime library. Version 0.0 is incomplete, and I hope that people out there can help in its development. Parts of it were borrowed from libm and libmpi as it was supposed to not be dependent on libm and on the same level as libmpi. Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] New libm-0.8!
Unto an unsuspecting world filled with innumerate people, I have submitted unto Jim Hall the latest version of libm, libm-0.8. I fixed a couple of things in csqrt and tanh. If anyone is brave enough to test my math, go ahead, I could use the feedback! Gregory Pietsch___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Email test
You failed because you didn't use the approved editor. -- Gregory > On 05/28/2024 12:20 AM EDT Jim Hall via Freedos-devel > wrote: > > > My email to the list bounced as undeliverable, but I'm sending this test just > in case it was a temporary hiccup. > > Can someone reply to this thread if you can see this message? > > *sent May 27 11:20pm > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS Edlin 2.24 is out!
Okay. Fixed. -- Gregory > On 05/16/2024 3:02 PM EDT Jim Hall via Freedos-devel > wrote: > > > On Thu, May 16, 2024 at 1:49 PM Jim Hall wrote: > > > > On Thu, May 16, 2024 at 1:36 PM Gregory Pietsch via Freedos-devel > > wrote: > > > > > > FreeDOS Edlin 2.24 has been released to an unsuspecting world! Jim Hall > > > sent me some edits that moved the copyright to the help screen and > > > changed "Abort edit" to "Really quit". It's available on SourceForge > > > and Jim should mirror it very soon now! > > > > > > > > > Thanks! Unfortunately, this still advertises itself as 2.23. Can you > > fix it on SF and I can re-mirror that? > >[..] > > FYI: I've fixed the source files on my end and mirrored that version > to Ibiblio. It's at: > > https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.24/ > > > I've also uploaded a compiled version of EDLIN16.EXE (compiled using OW.BAT) > > > Jim > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] FreeDOS Edlin 2.24 is out!
FreeDOS Edlin 2.24 has been released to an unsuspecting world! Jim Hall sent me some edits that moved the copyright to the help screen and changed "Abort edit" to "Really quit". It's available on SourceForge and Jim should mirror it very soon now! Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Edlin [was: libm-0.7 Released!]
Adding a /QUIET option would be extraneous, as it wasn't in the original Edlin and could easily be achieved by "edlin > NUL:". The copying message is important! The original Edlin had a /b option but I don't know how much of an improvement it is. Gregory > On 04/14/2024 12:43 PM EDT Jim Hall via Freedos-devel > wrote: > > > Tom Ehlert wrote: > > > btw: do you have a lot of communication about EDLIN? > > Gregory Pietsch wrote: > > > > I did have a lot of communication about Edlin when it was first released, > > but not as much anymore. > > > I actually use Edlin, and I do so without irony. It's great if you run > a command and want to make a quick BAT file out of it. I don't need > Edit for that, I can just as easily tap out a few lines in Edlin and > save it. > > One thing that would make that easier is a command line option to > suppress Edlin output. Something like /QUIET or /Q to not display the > "welcome" message (copyright & license). Because if I run a command > and want to make a BAT file out of it, the extra text might push some > interesting stuff off the top of the screen. > > Also, it would be nice if Edlin supported the /? option on DOS to > display the usage. Right now, it assumes any command line parameter is > a file: > > > C:\> edlin /? > > edlin 2.23, copyright (c) 2003 Gregory Pietsch > > This program comes with ABSOLUTELY NO WARRANTY. > > It is free software, and you are welcome to redistribute it > > under the terms of the GNU General Public License -- either > > version 2 of the license, or, at your option, any later > > version. > > > > /?: New file. > > * > > Here's an idea: if Edlin supported /? for usage, Edlin might only > display the "welcome" screen there and *not* display it during normal > program startup. That would remove my need for a /QUIET command line > option. > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] libm-0.7 Released!
I did have a lot of communication about Edlin when it was first released, but not as much anymore. -- Gregory > On 04/13/2024 2:53 PM EDT tom ehlert via Freedos-devel > wrote: > > > > Surprisingly, I have not received any communication whatsoever regarding > > libm. > > possibility 1) libm orks exactly as laid out in the documentation. > > poosibility 2) nobody cares about libm > > > btw: do you have a lot of communication about EDLIN? > > Tom > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.7 Released!
Submitted for your approval, the latest version of libm, FreeDOS's public domain math library, has been released! For this version, I have worked on edge cases regarding complex numbers and dug deep into the C99 Standard. Surprisingly, I have not received any communication whatsoever regarding libm. Where are the math nerds out there? Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
I don't keep track of whether changes had been made, but if someone wants to
hack it in, be my guest and send me an e-mail. I still have to check on what
hysterical historical behavior was for this, so I winged it.
Gregory
> On 02/05/2024 4:50 PM EST Jim Hall via Freedos-devel
> wrote:
>
>
> Not really about internationalization, so I'll make it a separate email:
>
>
> Whenever you quit Edlin, you always get this prompt:
>
> > *q
> > Abort edit (Y/n)? y
>
> I always find it a little concerning when I've already saved my file
> and Edlin asks if I want to "abort" my edit. It always makes me answer
> "n" and then write the file with "w" anyway before I use "q" again to
> quit. You get the same message with "e" ("end" : write and quit) which
> also makes me feel weird, which is why I prefer "w" then "q" to write
> then quit with individual steps so I know it's been saved.
>
> So this one is really a suggestion: can we not display "Abort edit
> (Y/n)?" if the file has been saved and no changes made? Or if that
> "change detection" would be too much to add, then maybe don't display
> that message with "e" because the program is supposed to write before
> quitting anyway.
>
>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
> On 02/05/2024 4:48 PM EST Jim Hall via Freedos-devel > wrote: > > > Gregory Pietsch wrote: > > Believe me, I've had a few headaches over the years regarding NLS. This > > led to the myriad of ways to do NLS in Edlin. Anyway, all the strings > > that would need to be translated are #defines in msgs.h, and I included > > a simple filter program to generate msgs.h files from the NLS files. I > > don't know if NLS was done the right way from the start (POSIX sus4, > > anyone?) but you shouldn't have to put a hundred FreeDOS programmers > > into a room and get 101 ways of doing NLS in a program. > > > > Edlin is supposed to be TINY, and I've turned into the guardian of bloat. > [..] > > I suppose one option is to go the ed(1) route and minimize the output > it produces. But that starts to tilt dangerously into "user > aggressive" territory. > > That said, maybe Edlin uses a bit too much text. For example, when you > start Edlin, it produces this copyright message (which should be > translated) > > edlin 2.23, copyright (c) 2003 Gregory Pietsch > > This program comes with ABSOLUTELY NO WARRANTY. > > It is free software, and you are welcome to redistribute it > > under the terms of the GNU General Public License -- either > > version 2 of the license, or, at your option, any later > > version. > > > > * > > ..where "*" is the prompt. > > Does it need to produce that much text? Or could Edlin just start with > a "*" prompt? Normally, that kind of text is produced on a "show version" option. That's boilerplate for the GNU license. I wanted to have enough space for translations. > > When you ask for help with "?" Edlin produces this text: > > *? > > > > edlin has the following subcommands: > > > > # edit a single line[#],[#],#mmove > > a append[#][,#]p page > > [#],[#],#,[#]ccopy q quit > > [#][,#]d delete[#][,#][?]r$,$replace > > e<> end (write & quit)[#][,#][?]s$ search > > [#]i insert[#]t<>transfer > > [#][,#]l list [#]w<>write > > > > where $ above is a string, <> is a filename, > > # is a number (which may be .=current line, $=last line, > > or either number + or - another number). > > I don't know if the first "edlin has the following subcommands" line > needs to be there. That saves 1 line of translation, which isn't much. > But every little bit, right? I wanted the help text to be thorough! Gregory > > Jim > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
Believe me, I've had a few headaches over the years regarding NLS. This led to the myriad of ways to do NLS in Edlin. Anyway, all the strings that would need to be translated are #defines in msgs.h, and I included a simple filter program to generate msgs.h files from the NLS files. I don't know if NLS was done the right way from the start (POSIX sus4, anyone?) but you shouldn't have to put a hundred FreeDOS programmers into a room and get 101 ways of doing NLS in a program. Edlin is supposed to be TINY, and I've turned into the guardian of bloat. I've tried to make it so that someone who is not in the priesthood could easily compile the thing with the right compiler, and I've tried to be broad about the compiler to use. Instead of tight 80x86 assembler, I made it portable as hell. It runs on Linux! It runs on Windows! It runs on Homer Simpson's brain! (Maybe...) Someone compiled it on a smartphone! Now I'm ranting Gregory > On 02/04/2024 2:55 PM EST Ralf Quint via Freedos-devel > wrote: > > > On 2/4/2024 11:32 AM, Jerome Shidel via Freedos-devel wrote: > > Hi, > > > >> On Feb 4, 2024, at 2:16 PM, Ralf Quint via Freedos-devel > >> wrote: > >> > >> On 2/4/2024 10:17 AM, Gregory Pietsch via Freedos-devel wrote: > >>> I made recompiling Edlin easy for non-programmers, so that shouldn't be a > >>> problem. You don't have to know a lick of C to recompile it. > >> Well, part of the problem is that in order to recompile, you need to have > >> the compiler (toolchain) installed, which isn't necessarily easy for a > >> non-programmer. > >> > >> > >> Ralf > > I have occasionally compiled edlin to provide an updated version for > > FreeDOS. > > > > As compile from source goes, EDLIN is not that bad. If I recall correctly, > > It just needs our Watcom-C to compile. Plus a little knowledge on options > > and such things. > > > > In general, it is extremely cumbersome to acquire all the exact required > > pieces to accomplish. An fairly often after spending a few hours on trying > > to get a successful compile, I will end up giving up. Therefore, I do that > > very rarely anymore for almost anything. > The problem with the whole NLS/i18n thing is that it is not only done > with just translating some text extruded from the sources. And > recompiling some programs which don't lend themselves well to the whole > "kitten" shebang. It would require a lot of testing, which needs to be > done by someone with those native language skills (plus some technical > knowledge what it is all about). A lot of command line tools might be > fairly easy to do, but for anything that is using a more formatted > screen output, this also requires to check where things are > "overflowing" (for lack of a better term right now)/misalignment... > And we have a very limited number of people that would have ALL the > required skills. > IMHO, before getting too much wound up with everything that is involved, > I think we need to make sure to have a proper English version, for > everything, > > > > As discussed in the online meeting, it would be nice to include dependency > > requirements in the package metadata. This makes me think we could possibly > > include the build-dependency requirements as well. Plus a per package > > universal build batch. That would be a lot of work and probably require > > frequent updating when packages change. > I see that there would be some effort initially to add that info, but > seriously, how much are dependencies as such changing for any given > program after that? > > > > But on the other hand, it would be very nice if all programs (excluding > > those made with commercial compilers like Turbo Pascal) could be built from > > source simply by installing the required build packages. > > > > This leads me to think, maybe we should go back to the old days when > > sources were in their own separate package and not included in the binaries > > package. > > > That was a move that I have never understood in the first place, as the > vast majority of people downloading FreeDOS are likely just interested > in getting it running, rather than doing any development. Specially if > things aren't as simple anymore as they (mostly) used to be in the days > of DOS, too many Linuxisms have crept in, which makes it so much harder > for people that are just trying to get back into DOS and haven't done > anything programming wise for the last 20-30 years, and then in things > like BASIC or Turbo Pascal, which are all "programma non grata" for a > lot of OSS license minded folks... > > > Ralf > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
I tried to make Edlin portable enough so that multiple toolchains would work on it. I normally use Cygwin with GCC and make to compile it, but FreeDOS is a DOS, so I tried to make it so that multiple compilers could compile it. Forgive my wording here... Anyway, tweaking config.h should take care of the differences in compilers. That file can also be generated through the configure script (as well as the makefile), but DOS wants things as simple as they can be. ;-) The files edlin.en and msgs-en.h in the distro are the English-language versions of the catalog and msgs.h, respectively. If I submitted a set of files for every language and compiler in existence, the politics of multiplication would come in, and I would be old and grey (or possibly dead from old age) before that project would be completed. Gregory > On 02/04/2024 1:32 PM EST Eric Auer wrote: > > > > I made recompiling Edlin easy for non-programmers, > > so that shouldn't be a problem. You don't have to > > know a lick of C to recompile it. > > One would still need the toolchain, so it would > be great if there could be somebody who already > has it (and does know C, just in case) who would > volunteer as the "send me your NLS updates for > EDLIN and I will make sure an updated EDLIN zip > will get published" person. Or, as said, a CI way. > > Eric > > PS: As mentioned on BTTR in the Book8088 compat thread > (which found out that SYS CONFIG GLOBALENABLELBASUPPORT=0 > can work around some crash in XT-IDE BIOS!) even seemingly > easy to use compiles fail in *unexpected* ways, e.g. OW > 2.0 compiles kernels in Linux, but only 1.9 does in DOS? ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
I made recompiling Edlin easy for non-programmers, so that shouldn't be a problem. You don't have to know a lick of C to recompile it. Gregory > On 02/04/2024 12:59 PM EST Eric Auer via Freedos-devel > wrote: > > > Hi! > > > Willi Spiegl said in the meeting that there is no NLS in Edlin. I beg to > > differ! > > As with the HTMLHELP versus AMB issue, the problem, as far as > I have understood Willi, is the lack of a process, possibly > an automated pipeline, which will take updated translations > and spread them to the right places. As a non-programmer, he > would not recompile EDLIN to submit updated translations, so > we have to figure out whom and how to give the files so the > updates get published to the right, easy to use places :-) > > Eric > > PS: The same probably applies to CTMOUSE and similar tools > with compile time translations. Could be put into continuous > integration pipelines, but then updates are rather rare here. > > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] NLS in Edlin
Willi Spiegl said in the meeting that there is no NLS in Edlin. I beg to differ! There are two different ways of supporting NLS in Edlin. The first (easy) way is that in the source code, all the message strings are in a file called msgs.h, so by translating the strings, putting the translations in a msgs.h file, and recompiling, you have a version of Edlin with translated strings. When I discovered how the rest of FreeDOS was doing NLS, I put a small program in the Edlin distribution called kit2msgs that translated a message catalog into a msgs.h file with a minimum of fuss. So, to translate all the messages to German, just download edlin.de from Github, add the three new missing messages, use kit2msgs to translate that into a msgs.h file, and compile! WAY TOO EASY! The second way was to read the message catalogs in real time. There's a file called msgscats.h in the Edlin source that uses catgets to get the messages, so using that as msgs.h and compiling in catgets.c should also work. This is a bag on the side of Edlin, and to keep Edlin as small as possible, I don't recommend this way, but it's doable. This needs more debugging, though. I tried to write a version of catgets that follows the POSIX specifications and uses the same format of files as FreeDOS and fits in with the string functionality that the rest of Edlin uses, but I could use some feedback. Hopefully this clarifies things. Gregory (not George) Pietsch___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Virtual get-together?
Isn't there a virtual get-together happening now?___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Question about edlin
Of course, quotes can be escaped. -- Gregory
> On 01/22/2024 5:18 PM EST Bret Johnson via Freedos-devel
> wrote:
>
>
> That solves the problem with commas, but it looks like you may still have
> issues if there are quotes in the file.
>
> I know one thing I've done in the past with some of my programs is allow the
> use of either a double-quote ("), single-quote ('), or grave-quote (`) as
> string demarkers, which allows strings to contain any two of the three
> quote-types and still be able to identify them properly. Of course, it will
> still fail if a string contains all three quote types, but that is a rare
> situation.
>
> EDLIN's solution (at least for MS-DOS 7.1) solves all potential problems with
> Ctrl-Z since Ctrl-Z (end-of-file) should never appear in the middle of the
> kinds of files (plain text) that EDLIN works with.
>
>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Question about edlin
I haven't shipped the NLS stuff since version 2.20 or so because I thought Jerome was handling that. -- Gregory > On 01/22/2024 2:11 PM EST Wilhelm Spiegl via Freedos-devel > wrote: > > > It would be great when edlin could support the 20 NLS files that are shipped > with it some day. > At least 1.24 till 1.29 of the NLS files are not supported. And I do not > speak about Chinese. > > Willi > > > > > Sent: Monday, January 22, 2024 at 6:23 PM > From: "Gregory Pietsch via Freedos-devel" > > To: "Technical discussion and questions for FreeDOS developers." > > Cc: "Gregory Pietsch" > Subject: Re: [Freedos-devel] Question about edlin > > FD edlin ignores a leading space. If you want the leading space to be > searched for, put the string in quotes; e.g. > > 1r"written"," written" > > The reason why I didn't stick a ^Z there is because I wanted to get away from > control characters in the commands, and a comma just looks better, IMHO. > > Gregory > > > On 01/22/2024 12:06 PM EST Bret Johnson via Freedos-devel > > wrote: > > > > > > > I'm using the "r" (replace) instruction correctly: 1rfrom,to will > > > start at line 1 and replace "from" with "to". > > > > > > But it looks like a leading space is ignored, so edlin treats my > > > "1rwritten, written" as just "1rwritten,written" and seems to ignore > > > it because the "from" and "to" strings are the same. > > > > > > FYI: I can add a space in the middle of a replaced word, such as: > > > > > > *1rtext,te xt > > > 1: This is a plain te xt file,written in edlin. > > > > > > Is "ignore leading spaces after the comma in the 'r' command" the > > > expected behavior from MS-DOS edlin? > > > > I haven't used EDLIN in a LONG time (decades), but just did an experiment > > with MS-DOS 7.1 EDLIN. Your problem doesn't seem to be unrecognized spaces, > > it seems to be that you're not using any sort of "escape" character to > > separate your input and output strings. I believe you think the comma > > should be the "escape" character and it isn't. There's a similar issue with > > programs like SED and AWK/GAWK. > > > > When I'm in EDLIN (at least the one with comes with MD-SOD 7.1) and I type > > "?" to get help, the syntax for the Replace command looks like this: > > > > Replace [startline][,endline][?]R[oldtest][CTRL+Znewtest] > > > > It expects you to use a Ctrl-Z (end-of-file character) as the "escape" > > character. > > If I use the Ctrl-Z "trick" I can replace things like you're wanting to do. > > > > I do not remember if earlier versions of EDLIN did this or not, nor do I > > know how FD-EDLIN works. > > > > > > ___ > > Freedos-devel mailing list > > Freedos-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-devel > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > > ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Question about edlin
FD edlin ignores a leading space. If you want the leading space to be searched for, put the string in quotes; e.g. 1r"written"," written" The reason why I didn't stick a ^Z there is because I wanted to get away from control characters in the commands, and a comma just looks better, IMHO. Gregory > On 01/22/2024 12:06 PM EST Bret Johnson via Freedos-devel > wrote: > > > > I'm using the "r" (replace) instruction correctly: 1rfrom,to will > > start at line 1 and replace "from" with "to". > > > > But it looks like a leading space is ignored, so edlin treats my > > "1rwritten, written" as just "1rwritten,written" and seems to ignore > > it because the "from" and "to" strings are the same. > > > > FYI: I can add a space in the middle of a replaced word, such as: > > > > *1rtext,te xt > > 1: This is a plain te xt file,written in edlin. > > > > Is "ignore leading spaces after the comma in the 'r' command" the > > expected behavior from MS-DOS edlin? > > I haven't used EDLIN in a LONG time (decades), but just did an experiment > with MS-DOS 7.1 EDLIN. Your problem doesn't seem to be unrecognized spaces, > it seems to be that you're not using any sort of "escape" character to > separate your input and output strings. I believe you think the comma should > be the "escape" character and it isn't. There's a similar issue with > programs like SED and AWK/GAWK. > > When I'm in EDLIN (at least the one with comes with MD-SOD 7.1) and I type > "?" to get help, the syntax for the Replace command looks like this: > > Replace [startline][,endline][?]R[oldtest][CTRL+Znewtest] > > It expects you to use a Ctrl-Z (end-of-file character) as the "escape" > character. > If I use the Ctrl-Z "trick" I can replace things like you're wanting to do. > > I do not remember if earlier versions of EDLIN did this or not, nor do I know > how FD-EDLIN works. > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Simplified Chinese Edlin?
While perusing Github, I noticed that the NLS project hasn't upgraded Edlin, which has three new messages to be translated. I also noticed that recently, many of the downloads of Edlin from SourceForge are from Hong Kong, which I found amusing. I also found a "fork" of Edlin in Github where the guy translated the messages into Simplified Chinese. This begs the question of what I should do to get Edlin to work with Simplified Chinese (I know very little about how an Asian language with 50,000 characters is used on a PC) and can we include it in NLS. I think searching for "edlin.zh-hans" on Github will find it. Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS Edlin 2.23 is out on Sourceforge!
Oops! I keep forgetting to change the version numbers in the config.h and batch files. Fixed and re-uploaded the files to SourceForge. -- Gregory > On 11/12/2023 11:07 AM EST Jim Hall via Freedos-devel > wrote: > > > Thanks! I always love a new Edlin release. :-) > > I've mirrored it on the FreeDOS Files Archive at Ibiblio. Here's the link: > https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.23/ > > > For anyone interested, the video Gregory mentioned is here: > https://www.youtube.com/watch?v=yapAepxbaT4 > > The compile warning is at 2:47 (yes, this is confirmed fixed in Edlin > 2.23 using OpenWatcom C) > > > FYI that if you compile this on FreeDOS, Edlin 2.23 will actually > advertise itself as "2.22". To fix, you'll need to edit config-h.bc or > config-h.ow (depending on your compiler .. I used config-h.ow to > compile with OpenWatcom C) and change all occurrences of "2.22" to > "2.23" (3 occurrences in each file). > > > On Sun, Nov 12, 2023 at 9:50 AM Gregory Pietsch via Freedos-devel > wrote: > > > > When Jim compiled Edlin 2.22 for the video, I noticed that the > > OpenWatcom compiler emitted a warning. Of course, this caused a > > disturbance in the Force. The new version 2.23 cleans up that warning, > > and therefore FreeDOS Edlin can now be thrown into the gladiatorial > > arena and slay the software demons called Fear, Doubt, Uncertainty, > > and Proprietary. > > > > Gregory > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] New FreeDOS Edlin 2.23 is out on Sourceforge!
When Jim compiled Edlin 2.22 for the video, I noticed that the OpenWatcom compiler emitted a warning. Of course, this caused a disturbance in the Force. The new version 2.23 cleans up that warning, and therefore FreeDOS Edlin can now be thrown into the gladiatorial arena and slay the software demons called Fear, Doubt, Uncertainty, and Proprietary. Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.6 and libmpi-0.2
In a world where mathematicians are the lowest of the low, I have sent Jim the latest versions of these low-level libraries. These versions contain mostly bug fixes. I am still wondering if someone out there can check the math. -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Meetup?
Isn't there a meet-up that's supposed to be happening now? -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Virtual get-together?
Wasn't a virtual get-together supposed to happen about now? -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
