This issue addresses a bug where 'output.pdf', created by a different program during the runtime of typst-live, is being deleted unexpectedly, even when the no-compilation flag is active. The expected behavior when the no-compilation flag is set is that typst-live should not interfere with or modify any files, including those named 'output.pdf'. However, it appears that the application might be inadvertently deleting or modifying this file, leading to potential data loss and disruption for users. https://github.com/ItsEthra/typst-live/blob/66ee883481796ba1bab8433cdc79e89d86c61904/src/main.rs#L101
This issue addresses a bug where 'output.pdf', created by a different program during the runtime of typst-live, is being deleted unexpectedly, even when the no-compilation flag is active. The expected behavior when the no-compilation flag is set is that typst-live should not interfere with or modify any files, including those named 'output.pdf'. However, it appears that the application might be inadvertently deleting or modifying this file, leading to potential data loss and disruption for users. https://github.com/ItsEthra/typst-live/blob/66ee883481796ba1bab8433cdc79e89d86c61904/src/main.rs#L101