Issue with Acode Text Editor's File Management Behavior

[HeH-DG]

Issue with Acode Text Editor's File Management Behavior

I'm experiencing an issue with the Acode text editor regarding its file management behavior. While Acode supports multi-tab functionality and allows opening multiple files simultaneously, there's a significant workflow problem when creating new files.

The Issue: When attempting to create a new file, Acode forces me to save it immediately before I can even start editing. This behavior differs from standard text editors, which typically:

1. Allow creating new, unsaved files without immediate save prompts
2. Don't show any prompts when closing an empty, unmodified file
3. Only prompt to save when closing a file that contains modifications

The Current Behavior:

• Forces immediate file saving when creating a new file
• Requires file path and name before allowing any editing
• No option for temporary/unsaved files

Expected Behavior (Based on Standard Text Editors):

• Allow creation of new, unsaved files
• Only prompt for saving if the file contains modifications
• Provide the option to close unmodified files without prompts
• Show save/discard prompts only when closing modified files

Use Case Example: While working on a programming project, I often need to create temporary files for testing code snippets or making quick notes. With the current behavior, I'm forced to save these temporary files, leading to an accumulation of unnecessary files in my workspace. This is both impractical and counterintuitive to standard coding workflows.

Request: Is there a way to modify this behavior to align with standard text editor functionality? The current forced-save approach significantly hampers productivity and creates unnecessary file management overhead.

This issue needs addressing as it affects the basic workflow of the editor and creates unnecessary friction in the development process.

If applicable, add mockups / screenshots to help present your vision of the feature

No response

[bajrangCoder]

There's no need to save your file first. When you create a new file from the menu or using Ctrl + N, saving isn't required immediately—you can choose to save it later if needed. However, if you create a file from the sidebar workspace, you'll need to save it right away, as this action indicates your intent to store the file.

Regarding closing a tab with unsaved changes, the warning is there to prevent accidental data loss. While this might not align with your workflow, many users appreciate such safeguards. If you'd prefer a different experience, you may be able to customize this behavior through a plugin or simply use it as is.(I think there is setting to not check for unsaved stuff )

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment(i.e Bump!) or this will be closed in 14 days.

[migo557]

Close it

On Sun, Jun 1, 2025, 6:19 AM github-actions[bot] @.***> wrote:

github-actions[bot] left a comment (Acode-Foundation/Acode#1173) https://github.com/Acode-Foundation/Acode/issues/1173#issuecomment-2926370256

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment(i.e Bump!) or this will be closed in 14 days.

— Reply to this email directly, view it on GitHub https://github.com/Acode-Foundation/Acode/issues/1173#issuecomment-2926370256, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGYNRJXQG6BYC5VPYVLCFZD3BJWN7AVCNFSM6AAAAABWM46QLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRWGM3TAMRVGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.