c7c16d5ac2
Move conflict resolution to nautilus-file. Use the following rough algorithm to resolve conflicts: 1- If file is the start of a chain, start processing it until the end of the chain. If it's not the start of a chain jump to step 3. The file is the begining of a chain if the targeted new name doesn't conflict with another file to be renamed, but may conflict with a name that is designated as stub. 2- Try to rename the file at the start of the chain, if can't be renamed (due to a conflict or depending on a stub), mark it as a stub. Remove the file from the chain and go to step 1 with the next file in the chain. 3- Follow the chain until: you find the beginning on the of the chain, or you reach the same file you started with. If you reached the file you started with, then it's cycle. break the cycle with a temporary name, then go to step 1 with the file at the start of the chain. Fixes https://gitlab.gnome.org/GNOME/nautilus/-/issues/1443 |
||
---|---|---|
.gitlab | ||
build-aux/flatpak | ||
data | ||
docs | ||
eel | ||
extensions | ||
icons | ||
libnautilus-extension | ||
po | ||
src | ||
test | ||
.editorconfig | ||
.git-blame-ignore-revs | ||
.gitattributes | ||
.gitignore | ||
.gitlab-ci.yml | ||
LICENSE | ||
meson_options.txt | ||
meson.build | ||
nautilus.doap | ||
NEWS | ||
README.md |
nautilus
This is the project of the Files app, a file browser for
GNOME, internally known by its historical name nautilus
.
Supported version
Only latest version of Files as provided upstream is supported. Try out the Flatpak nightly installation before filling issues to ensure the installation is reproducible and doesn't have downstream changes on it. In case you cannot reproduce in the nightly installation, don't hesitate to file an issue in your distribution. This is to ensure the issue is well triaged and reaches the proper people.
Hacking on nautilus
To build the development version of the Files app and hack on the code see the general guide for building GNOME apps with Flatpak and GNOME Builder.
Commit messages should follow the expected format detailed here.
Update default branch
The default development branch of nautilus has been renamed to main
. To
update your local checkout, use:
git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main
Runtime dependencies
- Bubblewrap installed. Used for security reasons.
- Tracker (including tracker-miners) properly set up and with all features enabled. Used for fast search and metadata extraction, starred files and batch renaming.
Discourse
For more informal discussion we use GNOME Discourse in the Applications category with the nautilus
tag. Feel free to open a topic there.
Extensions
Documentation for the libnautilus-extension API is available here. Also, if you are interested in developing a Nautilus extension in Python you should refer to the nautilus-python documentation.
How to report issues
Report issues to the GNOME issue tracking system.