Nautilus, the Gnome file assistant manager, sucks utter donkeyballs. Let us make an unordered list of the ways:

  • If the underlying filesystem changes, say a copy operation, the file manager view does not update without a manual refresh by CTL+R. This leaves the view in a stale state, presenting false file information to the user, who might never know until they do something bad. This is a showstopper bug that’s been hanging around since forever.

  • Batch rename. Good luck trying to rename a series of files ordered sequentially by number, if the number happens to start with any number other than one. A sequence from 2 to x is impossible to batch rename. Because regex in sed never worked either. No, wait. It’s always worked! For like, 50 years.

  • Why, when moving a collection of files or a directory within the same filesystem, does it actually perform a copy and delete operation, taking cpu and time, when the inode location could just be updated like mv does?

  • Thumbnails? Why do they take longer to generate for images and video than than the totality of the existence of the universe?

Nautilus is an unusable mess. If command line file utils were this bad, we’d never be able to reliably store and manipulate files. Who in their right mind actually uses this junk?

  • Skull giver@popplesburger.hilciferous.nl
    link
    fedilink
    arrow-up
    2
    ·
    8 months ago

    I agree that this should be done better. I’m not sure why it’s not implemented, I guess not enough people care about this for a programmer to pick this up. I have to admit I myself am not interested enough to put in the effort to come up with a fix for this.

    In theory it should just be “no write access, attempt opening admin://$PWD and retry drop action”.