PhpED is marking the file as changed (with that "*" near the name in the file tab) even if I make no changes in file.

As an example, after saving all open files in a debug workspace, when I get into one file openned by the debugger in a step-into(F7) mode, the file openned is marked as changed. When I close it, phped asks me if I want to save it.

This also occur sometimes when I just select text in the file.

This is annoying, because I loose control of files altered when I compare directoies from my local machine and the remote server.

Dear HotShot, could you please supply more details - I checked it on my 4.0.1 build 4051 and couldn't reproduce it at all. Are there any particluar steps or actions that you are taking?
Here is what I did:
Loaded two scripts, one calls another via include.
Changed both of them
Saved both of them
Started debugging the first one (local debugging)
Steped into the second one - it still opens up as saved file.

is that the scenario you were talking about?

Yes, it is. This happens when you uncheck the "Make editor readonly while debug session" in Tools>Settings>Tools>Debugger.

H-m. Mine is unchecked and i did try changing the files while debugging and saving it. Let me play some more with that - are there any other tricks to get this to show up? Maybe ddmitrie knows something about it. BTW, whcih build of PhpED are you using?

Build 4048

Actually it all was discussed there many times

opening-a-file-wants-me-to-save-t717.html
editor-changed-flag-and-undo-operations-t896.html
marking-as-modified-t1660.html

In short, when Optimal Fill checkbox is checked, editor _modifies_ the file for you to get all indented spaces optimally filled with tabs (if enabled with Use Tab character) or not. Additioanlly, when "Keep trailing blanks" is not checked, editor does also _modify_ the file for you when removes these trailing blanks

Yes, my "optimall fill" was enabled. Solved now

I didn't find those posts the way I searched. Since it's a so common complaint and is so simple to solve, may be it should be in the FAQs.

sure
post7021.html