aVd wrote on 2026-04-03, 20:25:

I just start DOSBox, go to TEDIT version 0.68 (the one without recursion protection) directory ("cd tedit"), start TEDIT 0.68 wi […]
Show full quote

cookertron wrote on 2026-04-03, 19:06:

aVd wrote on 2026-04-03, 17:50:

After a quick first test of TEDIT version 0.68 (in DOSBox as usually), now it seems like now using the <F1> keyboard shortcut causes the same problem even if no file is opened from the command line.

Can you explain that issue a little more please?

I just start DOSBox, go to TEDIT version 0.68 (the one without recursion protection) directory ("cd tedit"), start TEDIT 0.68 with no text file opened ("tedit"), then press <F1>, and get this with lock:

The attachment drop_to_prompt_with_lock_in_dosbox.jpg is no longer available

With DOSBox-X the lock happens a bit earlier, as I don't see the "colored prompt".

With the previous version 0.65 I got similar problems, but when I was using SHROOM and open at least one text file with TEDIT's start from the command prompt ("shroom tedit text.txt").

P.S. Just tried other key combo for the menu navigation with keyboard only: <Alt>+<V>, then <D> or <Enter> and the locking bug appears.

Forgot to mention - it happen often, but not on every tryout and only the mouse cursor can be moved after.

cookertron wrote on 2026-04-03, 19:06:

The answer is to prevent a new instance of TEDIT from spawning similar to how a TSR prevents multiple versions of itself loading […]
Show full quote

The answer is to prevent a new instance of TEDIT from spawning similar to how a TSR prevents multiple versions of itself loading into memory. Either create a TEDIT.LCK file when dropping to DOS and check it exists on start up when the user tries to invoke new instance of TEDIT - if it exists then notify and terminate. The other method is to use INT 2Fh Multiplex Instance Detection, which is what the TSR's use. MDI basically allows programs in memory to talk to each other, TEDIT can talk to TEDIT and ask, "Are you here" - if nothing comes back then it's OK to start up.

Re-release v0.68 https://github.com/cookertron/TEDIT

• Spawning a new instance of TEDIT after shelling to DOS results in detection, notification, termination. (see attached image)

Nice! I hope you're using the second method, so no more new temporary files are generated 😀

WOW! That's a pretty major bug right there. I'll get on that straight away 😒

EDIT: FIXED!

cookertron wrote on 2026-04-04, 03:19:

WOW! That's a pretty major bug right there. I'll get on that straight away 😒

EDIT: FIXED!

Yes, this one now seems like to be fixed, but I found a new bug with the latest revision of version 0.68 after some "shelling" with "/d" switch:

I didn't open any COMMAND.COM or other "ghost" files from TEDIT. And they can not be chosen from the <F1> opened file menu.

aVd wrote on 2026-04-04, 06:43:

Yes, this one now seems like to be fixed, but I found a new bug with the latest revision of version 0.68 after some "shelling" w […]
Show full quote

cookertron wrote on 2026-04-04, 03:19:

WOW! That's a pretty major bug right there. I'll get on that straight away 😒

EDIT: FIXED!

Yes, this one now seems like to be fixed, but I found a new bug with the latest revision of version 0.68 after some "shelling" with "/d" switch:

The attachment more_ghost_files_after_shelling.jpg is no longer available

I didn't open any COMMAND.COM or other "ghost" files from TEDIT. And they can not be chosen from the <F1> opened file menu.

Thank you for finding that aVd. Can you reproduce the bug consistently? I managed to do it once but since then I've not been able to.

Process:

1. cd TEDIT
2. TEDIT ori.txt thechair.txt
3. F1 - open side panel, all documents ok, no ghosts or garbage
4. F8 - shell to DOS
5. execute a few things including another instance of TEDIT (fails because of self-awareness)
6. EXIT out of DOS back into TEDIT
7. F1 - open side panel

As I mentioned, I've only seen garbage once and can't seem to get it back. If you could share your method I'd be very grateful 💪

cookertron wrote on 2026-04-04, 09:39:

Thank you for finding that aVd. Can you reproduce the bug consistently? I managed to do it once but since then I've not been abl […]
Show full quote

Thank you for finding that aVd. Can you reproduce the bug consistently? I managed to do it once but since then I've not been able to.

Process:

1. cd TEDIT
2. TEDIT ori.txt thechair.txt
3. F1 - open side panel, all documents ok, no ghosts or garbage
4. F8 - shell to DOS
5. execute a few things including another instance of TEDIT (fails because of self-awareness)
6. EXIT out of DOS back into TEDIT
7. F1 - open side panel

As I mentioned, I've only seen garbage once and can't seem to get it back. If you could share your method I'd be very grateful 💪

Yes, this bug occurs consistently every time, when I test latest TEDIT 0.68 revision in DOSBox:
1. Start TEDIT with "tedit /d";
2. Open some text file;
3. "Shelling" to DOS prompt;
4. "Exit";
5. Open the side pane list with opened text files = ghost artifacts appear.

It happen even with no text file is opened (skip step 2.).

aVd wrote on 2026-04-04, 10:01:

Yes, this bug occurs consistently every time, when I test latest TEDIT 0.68 revision in DOSBox: 1. Start TEDIT with "tedit /d"; […]
Show full quote

cookertron wrote on 2026-04-04, 09:39:

Thank you for finding that aVd. Can you reproduce the bug consistently? I managed to do it once but since then I've not been abl […]
Show full quote

Thank you for finding that aVd. Can you reproduce the bug consistently? I managed to do it once but since then I've not been able to.

Process:

1. cd TEDIT
2. TEDIT ori.txt thechair.txt
3. F1 - open side panel, all documents ok, no ghosts or garbage
4. F8 - shell to DOS
5. execute a few things including another instance of TEDIT (fails because of self-awareness)
6. EXIT out of DOS back into TEDIT
7. F1 - open side panel

As I mentioned, I've only seen garbage once and can't seem to get it back. If you could share your method I'd be very grateful 💪

Yes, this bug occurs consistently every time, when I test latest TEDIT 0.68 revision in DOSBox:
1. Start TEDIT with "tedit /d";
2. Open some text file;
3. "Shelling" to DOS prompt;
4. "Exit";
5. Open the side pane list with opened text files = ghost artifacts appear.

It happen even with no text file is opened (skip step 2.).

Yes you're right, I should have used /d switch. I can reproduce this now thank you

The fix for v0.68 is done - https://github.com/cookertron/TEDIT

The problem was when TEDIT loaded the 'shell to DOS' swap file into memory there was garbage data in memory that filled the remaining buffer so TEDIT though that meant there were documents. Thank you to aVd for finding that one.

I'm glad I can help, @cookertron! 😉

I hope that, when some bug is fixed, it doesn't invoke some new bugs and also the fixed functionalities remain stable in the later versions 😀 Probably one major new functionality per test release will cause less bugs, than two or three brand new features implemented at once.

@cookertron: Just a question. Are you open for even more feature requests? You implemented already quitte a lot so I would feel guilty if I would overburden you with too many feature requests. 😀

Not so hurry, @Yoghoo, we're waiting for the "LF"<-> "CR,LF" converter and save settings functionalities 😁

P.S. I'm just kidding, so share what you have in mind 😉

Release 0.69 - https://github.com/cookertron/TEDIT

• Detects line ending, allows conversion between LF (UNIX/Linux) and CRLF (Windows/DOS) via the 'Options' menu.

NOTE: Conversion collapses undo for that document.

I've tried to debug this as much as possible and didn't find anything - no doubt aVd will find something in seconds 😁. Also I didn't feel as though this feature needed a keyboard shortcut but if I was going to add one it would probably be CTRL+SHFT+L (L for line).

cookertron wrote on 2026-04-04, 13:11:

Release 0.69 - https://github.com/cookertron/TEDIT […]
Show full quote

Release 0.69 - https://github.com/cookertron/TEDIT

• Detects line ending, allows conversion between LF (UNIX/Linux) and CRLF (Windows/DOS) via the 'Options' menu.

NOTE: Conversion collapses undo for that document.

I've tried to debug this as much as possible and didn't find anything - no doubt aVd will find something in seconds 😁. Also I didn't feel as though this feature needed a keyboard shortcut but if I was going to add one it would probably be CTRL+SHFT+L (L for line).

Hi,
I was "late to the party", so I missed to download the previous ver. 0.68 fourth bugfix revision at the time it was the latest version. I was able to trace it back from the github repo and tested it - seems to work fine with no more ghosting.

As for the new version 0.69 with LF <-> CR,LF convertor - seems to work fine. I didn't tested yet with text file with mixed line breaks (nowadays this happen when using windows and Linux).

I have no bugs to report, except one small keyboard misbehaving, which can be traced back to the version with <Alt> key menu (de)activation: For example when <Alt>+<F> is used to open "File" drop-down menu and then <Alt> is pressed again, the menu bar goes "inactive". But if <Esc> is pressed instead, the menu bar stays "active" and needs a second <Esc> press to be deactivated. It will be nice, if one <Esc> press acts like the <Alt> press in this particular case.

SHROOM still works nicely with TEDIT and gives some better results in memory saving, so I changed my mind for default behavior as if "/d" flag is used - better off to stay like it is now.

While I was digging for the previous 0.68 version, I saw some "clipboard" named files commit traces. So, I suppose, that the next TEDIT version will have the DOSBox clipboard sharing option implemented 😀

SHROOM works better than TEDIT because TEDIT doesn't unload itself from memory. SHROOM goes as far as to unload TEDIT too. There could be a workaround where TEDIT unloads itself from memory and leaves a stub to load itself back in 🤔

I'll look into that bug thank you for finding it.

I have no plans to add DOSBox clipboard sharing yet. Is it needed, probably not! When DOSBox allows shared disk space you could just edit a document on the host system.

I'm intrigued about @yoghoo's new feature request 😎

cookertron wrote on 2026-04-05, 07:53:

I have no plans to add DOSBox clipboard sharing yet. Is it needed, probably not! When DOSBox allows shared disk space you could just edit a document on the host system.

I fully agree with this.

cookertron wrote on 2026-04-05, 07:53:

I'm intrigued about @yoghoo's new feature request 😎

He already suggested one thing, that I also thought for: Configuration for tab spacing and SHROOM-like function settings ("/t" and "/d" switches still can override this) in "Options" menu with saving in configuration file.

For example If we have a TEDIT.INI it may be something like this:

1tabs=2    ; 0 or no value = default 8; 2, 4 or 8
2moreshellmem=1    ; 0 or no value = false; 1 = true = /d switch,

If the config file is missing, it could be auto-created on TEDIT start with the default values set in it.

cookertron wrote on 2026-04-05, 07:53:

I'm intrigued about @yoghoo's new feature request 😎

You ask and you'll receive. 😀 This is my list:

• Change case of selected word/lines
• Word select on double click
• Save file history
• Time in upper right corner (12h/24h)
• Create backups when saving

This is sorted by my humble priority. Change case of selected word/lines to lower or upper case is something I use regularly. Some options should be a configuration options of course like creating backups and time.

@Yoghoo, what do you mean with "save file history"?

Also, those backup files may be optional - set from "Options" menu in config file + command line switch.

aVd wrote on 2026-04-05, 09:35:

@Yoghoo, what do you mean with "save file history"?

Also, those backup files may be optional - set from "Options" menu in config file + command line switch.

It means: remember the files you had open in the past. See screenshots for an example.

Also included a screenshot for an option dialog from EditV to maybe give some inspirations how to handle an option dialog in TEDIT.

I get it. Seems like this "document history" will also need a config file to store the last n opened paths+filenames.

The priority is to create a settings file first. Also there are a lot of swap files - I think they should be bundled into a ".temp" (yes a period before the directory name 😁) directory that gets deleted on successful exit.

I don't mind the swap files for each of the opened, but not currently edited files. It will be nice, if they can be created with active "hidden" attribute, so not to be shown with standard "dir" command when "shelling" or in "Open file" select/dialog box.

aVd wrote on 2026-04-05, 11:04:

I don't mind the swap files for each of the opened, but not currently edited files. It will be nice, if they can be created with active "hidden" attribute, so not to be shown with standard "dir" command when "shelling" or in "Open file" select/dialog box.

I think the swaps are currently unavoidable with this current architecture but I like your idea of making them hidden.