You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
I've got a big .sql dump of 400MB in my project.
Opening it crashes Brackets immediately, which seems to be not only a flaw in error handling, but a usability problem too (aside of obviously loosing unsaved changes). One can learn not to open large files, but due to Brackets' behaviour, the same thing happens when I want to delete it - right clicking files in the sidebar opens up the file.
imo this would be solved if
left clicking large files would open a prompt window, alerting users, that this could take a while, and if choosing yes, opening files in a plain text mode, w/o codemirror plugin (hopefully that would allow to edit medium sized files)
large files wouldn't open on right click, only the popup should appear
The text was updated successfully, but these errors were encountered:
Reviewed medium priority, 1.0, "Project Management".
@MikeSpock We'll probably want to add a dialog that says that Brackets doesn't handle files bigger than X, with a preference that's able to change the threshhold.
I've been working on a new version of the file tree that does not automatically open the file when you right click on the it.
When #8788 is complete, right-clicking on an item in the file tree does not open the file, which is the second proposed solution in the original description.
I've got a big .sql dump of 400MB in my project.
Opening it crashes Brackets immediately, which seems to be not only a flaw in error handling, but a usability problem too (aside of obviously loosing unsaved changes). One can learn not to open large files, but due to Brackets' behaviour, the same thing happens when I want to delete it - right clicking files in the sidebar opens up the file.
imo this would be solved if
The text was updated successfully, but these errors were encountered: