This commit does the following:
* Canonicalize the style:
* Use two-space indentations.
* Un-Autotools-ify option names.
* Don’t align arguments, simply increase indentation.
* Don’t add a space before opening parenthesis in calls.
* Remove unused variables.
* Remove unused dependencies.
* Remove config.h.meson.
* Optimize dependencies.
* Use disabler functionality for libselinux dependency, to save lines.
Currently, the process for getting the common prefix of a list of file
names is a tad too greedy:
1. Find the common prefix of all the strings.
2. Strip the extension from the prefix.
3. Strip trailing punctuation.
Step 2 may strip dots if there’s trailing whitespace and step 3 may
strip useful punctuation (e.g. parentheses). This commit reworks the
process as such:
1. Strip the extension from all the file names.
2. Find the common prefix of all the strings.
3. Trim trailing whitespace.
Fixes#174.
Drag and dropping on a search or starred location tab gives an error dialog
that says "Error while copying to /".
In order to be able to drop the selection on a target it is also necessary
to check whether it is editable, property which is set False for the Star
and Search directories.
https://gitlab.gnome.org/GNOME/nautilus/issues/168
As the eel_gtk_message_dialog_set_details_label function is only used once,
we can safely remove it and do everything inside of nautilus-file-operations.c.
Thus, we deleted the eel function and we do everything inside the
do_run_simple_dialog function and remove the function header from the header
file. We add the label straight into the content_area of the dialog box.
https://bugzilla.gnome.org/show_bug.cgi?id=598671
Creating directories within read-only ones is not allowed and appropriate
error messages pop up.
Trying to create a directory within a read-only directory opens a window
showing the error. Within the window, an expander shows the error details.
Whenever the expander is clicked, the window moves unexpectedly.
We need to fix this as the behaviour is not normal and doesn't look good.
In order to fix the issue, we removed the expander and included the error
details as a label inside the dialog box itself.
https://bugzilla.gnome.org/show_bug.cgi?id=786212
We already included gdk/gdkkeysyms.h, which is generated from
X11/XF86keysym.h
Doing this, we can drop the ifdefs. Also, revert the build
configuration introduced in 2c5882aaff.
Currently, when checking if the user pressed ctrl-z, an equality check
is used on the state to determine whether the ctrl key is pressed. That
does not work, however, as there may be other modifier masks applied, be
it internal GDK values or mapping of num lock to mod2.
That is fixed by using binary AND on the state with the relevant mask.
Closes#149.