I have found a bug in MicroGoldEd

[AmigaMance]

I'm using version "8 SP 4" which i believe that it's the latest one. Here's how to reproduce the bug:
- Create a new file in any directory with the name test, by typing in a CLI window "ed ram:testing" (without the quotes) or whatever. Write something random, save the file and then quit
- Now try to create a new file in the same directory by typing "ed ram:testing2".
Instead of a new file, the editor will load the previous file "testing".
 This is definitely a bug..

[dcr8520]

hmm, no idea.. but shouldn't you contact the author rather than posting it here?

[AmigaMance]

I would like to see if other people can reproduce it first..

[cha05e90]

I'm using version "8 SP 10", but it shows the same error. Furthermore the "ed" seem not to detach itself properly from the starting shell process - maybe this is related to the error (i.e. the first "testing"-file process is still active somehow and shows of course the "old" file...).

[AmigaMance]

I'm using version "8 SP 10", but it shows the same error.

 So it's not only me. Ok.

Furthermore the "ed" seem not to detach itself properly from the starting shell process.

 I can't reproduce this one. I don't see the process with the Status command after quitting, if this is what you mean. Perhaps a new bug of the newer version you are using? I haven't try this version yet. Thanks for the feedback.

[AmiKit]

Instead of a new file, the editor will load the previous file "testing".
 This is definitely a bug..

The same behavior here with AmiKit/microgolded 8 SP 10

[cha05e90]

I reproduced that error following your description (except using the files "RAM:Test" and "RAM:Test2" - lazy as i am ;-)
I did it twice:
1. Typing "ed RAM:Test", typing something, saving and closing MicroGoldED. But: I won't get my shell back - it is still blocked. So i had to open a new shell and type "ed RAM:Test2". Guess what happens? Right - the old file is opened (RAM:Test).
2. I used "RUN ed RAM:Test" etc. The starting shell in this case is of course usable after starting MicroGoldED, I can close the Editor after typing text in the first "RAM:Test" file and start it again in the same shell with "run ed RAM:Test2". And - yes - same error, it is opening the old file. When I close the editor again and then try to close the starting shell (which is still "usable", i have a prompt etc.) the shell WON'T CLOSE with a message saying "Process 4 is ending" ... for ever.

So, in both cases there seem to be problem with the detachment from the mother shell or general process handling of MicroGoldED - this is why i supposed it might be a part of that error. BTW: This is with OS4.1.

[Amile]

Also using GoldED 8 SP 10 here, this time on MorphOS 2.2.

The Ambient-Shell is given back, so this isn't reproduceable here, but the opening bug/feature. And in both Cubic IDE and microgolded. And even worse, the filename can be appended by one character (not limited to numbers, just any alphanumerical char fits) *or* can be reduced by one character *or* the last character can be changed to any alphanumerical character (also in reduced form), everything opens the same file.

So the file 'test' can be opend by all these filenames:

test
test1
testz
tes
tes1
tesz
te1
tez

[AmigaMance]

1. Typing "ed RAM:Test", typing something, saving and closing MicroGoldED. But: I won't get my shell back

 No, i can't reproduce it either, but yes, it may be relevant with the problem.
 Ok guys. I have notified the author about this thread.

[cha05e90]

Interesting - AmigaMance: which os version do you use? i suppose os3.5 or os3.9? so there seems to be a difference in behaviour between MorphOS/OS3.x and OS4.1 (the shell thingie). OS4.x is often known to behave ... erm ... not the same way ;-) - but maybe this might be a hint to the underlying error, as os4.x is sometimes more strictly in task and stack related issues...

[AmigaMance]

Interesting - AmigaMance: which os version do you use? i suppose os3.5 or os3.9? so there seems to be a difference in behaviour between MorphOS/OS3.x and OS4.1 (the shell thingie). OS4.x is often known to behave ... erm ... not the same way ;-) - but maybe this might be a hint to the underlying error, as os4.x is sometimes more strictly in task and stack related issues...

 What you reported doesn't occur with AmigaOS 3.x, MOS 1.4.5 tested myself and MOS 2.2 according to Amile. So, i think you are right. This behaviour has to be OS4 specific.

[AmigaMance]

Hey, everyone.
I want to thank Dietmar for replying to my PM. This isn't a bug. It's a filename typo correction feature. It can be disabled from the menu Extras -> Customize. Un-tick "Correct file names" and save.