Skip to content

Fix: Address issue #3677#3766

Closed
a-j-bauer wants to merge 1 commit intolinuxmint:masterfrom
a-j-bauer:issue-3677
Closed

Fix: Address issue #3677#3766
a-j-bauer wants to merge 1 commit intolinuxmint:masterfrom
a-j-bauer:issue-3677

Conversation

@a-j-bauer
Copy link
Copy Markdown

I added an option under Edit / Preferences / Behavior "Force synchronous file operations".
When activated, nemo uses synchronous (O_SYNC) writing and a buffer size adjustment logic to ensure the progress dialog is shown during a file write operation and that the dialog is updated frequently.

@Jeremy7701
Copy link
Copy Markdown
Contributor

Do you distinguish between a data move between filesystems (which is a copy) and a move within a filesystem (which moves no data)?
Do fast devices get larger buffers than slow devices?
Do you take into account the memory requirements of background non-nemo processes (such as VM's etc)?

@mtwebster
Copy link
Copy Markdown
Member

Bring this up with the glib project maybe. The only issue lies with certain removable device types. Applying this to everything is just wrong.

@mtwebster mtwebster closed this May 3, 2026
@a-j-bauer
Copy link
Copy Markdown
Author

a-j-bauer commented May 3, 2026

@Jeremy7701: yes I did.
@mtwebster: untrue but never mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants