| Summary: | Having a file saved, creating a new one, and saving it as same name merges tab and shows dirty flag | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Shaun Reich <sreich> |
| Component: | All editors | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Shaun Reich
2013-09-16 14:37:10 UTC
Shouldn't that be the expected behaviour? You already confirmed the overwrite..so "Reload" loads the new data. But then how could I save a file into the place of another and save the other one into the first one's place without overwriting and going through a drawn out process? I tend to accidentally start making .h code in a .cpp file and vice versa. So no, this isn't the behavior I'd expect, especially since the tabs have merged and the file I just saved into now has a prompt to reload, which doesn't make sense because I just saved it. So yeah. I don't see how it could be expected behavior. I agree that the behavior with the reload button is odd, but otherwise this is expected behavior. You cannot have two different documents with the same url. Thus they are merged. You wrote: "But then how could I save a file into the place of another and save the other one into the first one's place without overwriting and going through a drawn out process?" I assume you mean swapping two files, yes? Personally I use copy'n'paste for that. You could e.g. copy the contents of A, then save B as A and paste the contents of A into a new file B. Note that imo this is such an uncommon thing to do that I'm perfectly fine with the way it is right now. But you mention a regression, the code in place for that did not change recently. So I have no idea what you mean by that comment. The behavior is like that for years already as far as I can see. Imo the bug is that there is no way to "restore" the old data which you confirmed to overwrite. Maybe eventually such functionality could be added to the undo buffer to restore the previous file contents somehow. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |