Using windows "TEMP" or "TMP" directory on HDD for all the swap files is a smart idea, but what if there's no HDD in the system? Probably switching to "one file edit mode only" and ignoring SHROOM-like settings and command line switch "/d"?

aVd wrote on 2026-04-17, 09:14:

Using windows "TEMP" or "TMP" directory on HDD for all the swap files is a smart idea, but what if there's no HDD in the system? Probably switching to "one file edit mode only" and ignoring SHROOM-like settings and command line switch "/d"?

They are all valid issues, which I very much agree with, they need to be addressed, as I briefly explained in points 1 and 2, which you further expanded upon, on the comment you just made.

I found an issue that tedit will create the config file in your current directory and not in the directory where the executable resides. So it creates those config files all over your drive.

So say the executable is in c:\utils but you call tedit from the root (c:\) then it will create it in the root. If you go to c:\temp and run tedit there it will create another one there as well etc.

Release 0.72 (https://github.com/cookertron/TEDIT)

• TEDIT.CFG now saves in the location of TEDIT.COM no matter which directory has been explored, either through file browser or shell.

Release 0.72.1

File dialog box now supports:-

• A:
• A:\
• A:*.txt
• A:\*.txt
• a: (lower case)
• *.txt
• *.*
• mytext.txt

Agent86 has a new feature stemming from the config file issue (I haven't released the update yet). Now it can handle virtual disk drives to remove dependency from the host file system which can be incompatible with DOS based programs.

The floppy disk issue is a huge problem that still needs to be addressed and I'm looking into it but it'll take time to get it right.

cookertron wrote on 2026-04-22, 09:37:

The floppy disk issue is a huge problem that still needs to be addressed and I'm looking into it but it'll take time to get it right.

No problem, I will keep an eye open.
Thanks for your continued effort.

Currently all buffers are dumped to disk when switching documents, this reduces the memory footprint of TEDIT and allows editing of document with virtually unlimited size. It also dumps, all memory to disk when dropping to shell, again to free up memory. This can cause significant disk writes making TEDIT pretty much unusable when working off a floppy disk. The strategy of dumping memory to disk has become the core architecture of TEDIT so bypassing it to a lite version within itself would be an undertaking and a half.

I propose this:

1. We keep TEDIT as is, and highlight working from floppy disk as a limitation.

or

2. Fork TEDIT and create TEDIT LITE - remove multi-document editing with it's memory dump architecture. Text files completely reside in memory, as does clip, undo, piece table. Disk writes only occur when saving the document and saving/updating config file. Shelling to DOS keeps everything in memory, unloading can be the choice of the user via SHROOM etc.

and/or

3. Your suggestion here...

I wouldn't fork TEDIT (maintaining/testing multiple projects is a hassle). I would just disable the Shell and multi edit function if run from floppy. Or even keep it as is. What I basically do with my programs is looking for a TMP, TEMP variable and put the temp files there. That is in most of the cases a HDD. If that doesn't exists I put it on the C: drive. If that fails than I reduce the functionality. If that's not possible than error out. Sometimes it is just not worth it to support all edge cases (how many pc's, that are using your program, do not have an HDD for example).

cookertron wrote on 2026-04-23, 08:05:

3. Your suggestion here...

Hi,
No need of fork. We still have this version and it's usable from floppy disks. I don't think, that someone will use TEDIT started from floppy disk to write some code for big software projects.

Just one question. Can we rebuild it with newer Agent86 version? The modified source code is included in the attached archive.

aVd wrote on 2026-04-23, 09:21:

Hi, No need of fork. We still have this version and it's usable from floppy disks. I don't think, that someone will use TEDIT st […]
Show full quote

cookertron wrote on 2026-04-23, 08:05:

3. Your suggestion here...

Hi,
No need of fork. We still have this version and it's usable from floppy disks. I don't think, that someone will use TEDIT started from floppy disk to write some code for big software projects.

Just one question. Can we rebuild it with newer Agent86 version? The modified source code is included in the attached archive.

The Agent86 update doesn't effect how TEDIT compiles. It basically allows the COM program to operate within a simulated DOS file system for testing purposes. Currently the new features only exists in the Linux branch of the repo as I haven't been into Windows for about 3 weeks. The Linux branch needs porting and testing in Windows to make sure everything works correctly as the two OS's have different handlers agent86 uses.

@cookertron

In my case, I was using it as a replacement for MS-DOS EDIT, as TEDIT is smaller and is more feature rich. I have used it as a general purpose text editor for batch files, assembler projects and a bit of text here and there to tweak some configurations.

If it does not work out of read-only media or restricted storage space, it won't be much use to me, as flexibility in it is what I appreciate most. I often use bootable DOS CD-ROM images and have a set of bootable DOS disks for my machines which I usually update with the newest stuff I find or build myself.

For word processing I use other beasts (WordPerfect 6.2 and rarely MS-Word 5.5).

For high level language development I use their own integrated/built-in editors which are always better customized for the job at hand.

In the end it depends what YOU want TEDIT to become.

Trying run TEDIT.COM from a USB running FreeDOS created by with Rufus.

What is going on? Is the project dead already?