DOS ain't dead

Hi all!

I wrote a simple editor for Windows , Linux , DOS. Perhaps it will be of interest to the DOS community.



Important:

1) Editor works when available CWSDPMI.EXE
2) The default editor highlights keywords for the freebasic programming language. To disable keyword highlighting, launch the editor. After the first launch, a settings file is created in the folder with the editor file. Turn off the backlight in it (you need to do this: highlight = 0)

The editor supports infinite UNDO|REDO

On other systems it also supports UNICODE.

More description is here: https://sourceforge.net/projects/console-edit/files/ . There is also an archive with source codes (for those interested).

Release download link: https://sourceforge.net/projects/console-edit/files/Bin/

Hi all!

Now, by default, the highlighting for the programming language is not enabled, that is, after the first launch - it will be a regular editor. If desired, highlighting can be enabled in the settings file. Also, the freebsd 64-bit platform is now supported.

> Now, by default, the highlighting for the programming language is not
> enabled, that is, after the first launch - it will be a regular editor. If
> desired, highlighting can be enabled in the settings file. Also, the
> freebsd 64-bit platform is now supported.

I noticed that to make this release, you replaced the previous cedit.zip file and the binary zip and tar.gz files in the "bin" directory on your SourceForge project:

https://sourceforge.net/projects/console-edit/files/

So this means:

(1) there's no indication what version this release is - for example, if someone wants to know if they've already downloaded this version

(2) no one can download the previous release - such as to compare features/bugs between builds

Could you use version numbers in future releases of CEDIT? When releasing on SourceForge, a common way to do this is to create a directory with the version number (such as 1.2) and then put releases under that, preferably with a version number as part of the filename too (cedit12.zip, linux32_cedit-1.2.tar.gz, etc)

It would also be helpful to create a few files in your source code:

HISTORY.TXT that includes a copy of the release notes for each version

LICENSE.TXT with a copy of your license (your SourceForge project page says MIT license, but I don't see a copy of the license in your source code)

CONTRIB.TXT with a list of the contributors' names and email addresses (if you want others to contribute to your project)

The following files have been added to the archive with the source code:

Contrib.txt
License.txt
History.txt

I understand about the version numbers and I will take note.
Thanks for the advice!

Since the last entry, I have released 2 updates. They are all about fixing bugs:

09.02.2023
Fixed bug Comments+UNDO|REDO in DOS
fixed incorrect save behavior for some operations (didn't display the save file dialog after changing the code using commenting and UNDO|REDO)

06.02.2023
Added checks for pointers when allocating memory
Improved UNICODE support:
a) in linux|freebsd all characters should be displayed and there should be correct cursor indexing
b) on windows it's hard to tell because the console has limited support for UNICODE. At least "Chinese Simplified" should work if Windows is set to "Chinese Simplified".
Flicker reduced in Windows
Comments are now also added to the undo buffer UNDO|REDO

Updated (actually it's several updates in one ad):

from 10.02.2023
1) fixed path setting
from 19.02.2023
2) Fixed unnecessary scrolling when commenting and deleting
3) Fixed cursor position after REDO (comment return)
4) Code corrected on Windows to be able to compile under Win9x
from 02.03.2023
5) Application optimization
from 05.03.2023
6) added key redefinitions for terminals rxvt, st
7) fixed key buffer full bug in Linux (appears on older machines)
8) on Linux, the editor is built with static libtinfo, and this allows you to work without the need to install libtinfo5 (in theory, it should work on any distribution, without the need to install dependencies)
from 09.05.2023
9) fixed bug with text output on Linux
10) on all platforms, the ability to run scripts (*.bat , *.sh) from the editor using the F5,F6 keys has been added. This allows you to compile|run or simply run any program. For correct configuration, read the readme.txt file