Menu

#367 Two wrong editing behaviors and bugs of the editor FED.EXE (Folding Text Editor)

freedos14
closed
nobody
fed (1)
5
2025-08-11
2022-08-01
Oliver
No

Create a TXT File with with the following 2 lines and 2 words without pressing the return key at the end of the second line:

TEST1
TEST2

The TXT file must have the following HEX Code (when opened with a HEX Editor):

54 45 53 54 31 0D 0A 54 45 53 54 32

Save the file and close the Editor. This is an important step, do not forget it, even if you think it doesn't make much sense to end an editor and restart it again! It this case it does make sense.

Now open the file with FED.EXE again.

When the file is opened, the cursor is in the top left position of the file.
Now press the SHIFT-key and hold it and then press the cursor-down key 2 times to mark the line.

And here's the bug. Because FED can't move the cursor in the not existing third line, you can't mark both lines.

It will only mark the first line, not the second.
This is a wrong behavior.
All modern editors, including EDIT.EXE from MS-DOS, will move the cursor into the third line and allows the user that way to mark both lines.
You can use the Cursor right key or the END key as a work around to mark the complete second line, but this is not the nicest way to do it.
Thus this bug should be fixed.

Then there is another bug related to the above one.

If you want to add a new line below the other 2 lines, you can't move the cursor into the 3rd line to do so.
If you move the cursor key down by using the cursor down key 2 times, the cursor will stay at the first T of the word TEST2 in the second line.
You can put the cursor to the most right by pressing the END key and then press the RETURN key as a work around to create a third line, but this is not the same as just being able to move the cursor key to the next line by pressing the cursor down key just 2 times.

Modern editors will always allow you to move into the next line behind the last line to make editing easier and more comfortable, even when an empty third line does not exist in the file.
This bug should be fixed too.

Discussion

  • Robert Riebisch

    Robert Riebisch - 2022-08-09

    FED just behaves different from what you expect.
    So it's by design, but no bug.
    You issue is a feature request then.

     
  • Robert Riebisch

    Robert Riebisch - 2022-08-19

    You can't mark the last line with the cursor as described above and this is a bug.

    Yes, you can't mark it that way, but it never was the intention of FED to support such behavior. -> Not a bug.

     
  • Jim Hall

    Jim Hall - 2025-08-11
    • labels: --> fed
    • status: open --> closed
     
  • Jim Hall

    Jim Hall - 2025-08-11

    Marking as closed because this is not a bug, just behavior that the user did not expect:

    FED just behaves different from what you expect.
    So it's by design, but no bug.

    For what it's worth, I use FED all the time, and I prefer that it not go to a nonexistent "third" line in the file when the file has no third line (i.e. only 2 lines, no newline after line 2). Editors act differently, especially in DOS. This is how FED works.

     

Log in to post a comment.

MongoDB Logo MongoDB