| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Neto <fernandesn@gnome.org>.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
It will autostart nautilus automatically based on the GSettings key
org.gnome.desktop.background show-desktop-icons.
https://bugzilla.gnome.org/show_bug.cgi?id=647267
|
| |
|
| |
|
|
|
|
|
| |
We now do this generically, so no need to special case it in the
"go up" case.
|
|
|
|
|
|
|
| |
We used to special case this for the up button, but that now
only exists as a keyboard shortcut. This more generic approach
gets the same feature also for pathbar navigation and back/forward
history navigation.
|
|
|
|
|
|
| |
Turns out that we didn't pass the NEW_WINDOW flag in the handler
for the LocationOpenAlternate action. This is used when right-clicking
on the location label or the pathbar.
|
|
|
|
|
|
|
|
|
|
| |
We don't need to resort unless e.g. a file changed or was added.
Additionally, for weird reason this makes the keyboard focus handling
work when deleting a file (file after deleted gets focus). This was
broken due to a relayout happening due to a size_allocate due to
a style set due to a focus change when going to/from the "are you sure"
dialog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Usually the default GtkWindow handler for key-press events processes
them in the following order:
- calls gtk_window_activate_key() to process mnemonics/accelerators for
the toplevel window
- calls gtk_window_propagate_key_event() to propagate the events to the
focus widget
- chains up to parent if both fail
We want gtk_window_propagate_key_event() to be called before
gtk_window_activate_key(), as when we're focusing an editable widget
(e.g. renaming a file), we want all keybindings to apply to that, e.g.
Delete, Ctrl+Delete (or Ctrl+W if we're e.g. using an emacs-mode
GTK+ binding set). This interferes a bit with the type-ahead search
windows that NautilusIconContainer and GtkTreeView pop up; we can
control the former, but not the latter, so we need a bit of a hack in
NautilusListView to prevent the search window to steal the pasted URI,
and still not handle the event.
https://bugzilla.gnome.org/show_bug.cgi?id=314431
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=647737
|
|
|
|
|
|
|
|
| |
If e.g. ftp://ftp.example.com is specified as an address, and the FTP
method is chosen, we should strip "ftp://" automatically from the
address before connecting.
https://bugzilla.gnome.org/show_bug.cgi?id=643608
|
|
|
|
|
|
|
| |
This allows to call `nautilus uri:///path/to/file` from the command line
to open uri:///path/to with file pre-selected.
https://bugzilla.gnome.org/show_bug.cgi?id=632427
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that we don't support being a session component anymore, it doesn't
make sense to special case the session autostart. This also breaks
opening new windows when nautilus is added to ~/.config/autostart, which
is now the supported way of having desktop icons automatically, as we
end up reading the env variable every time when parsing the command line
(as the original process will always have that set) and refuse to show a
window.
https://bugzilla.gnome.org/show_bug.cgi?id=649063
|
| |
|
| |
|
|
|
|
|
| |
This should hopefully fix this crash
https://bugzilla.redhat.com/show_bug.cgi?id=699184
|
|
|
|
|
|
|
| |
This fixes a segfault when clicking on the "Select Application" button
when opening a file with no default applications, like in
https://bugzilla.redhat.com/show_bug.cgi?id=699850
|
|
|
|
|
|
|
| |
We were adding them twice in case there was already one operation
running.
https://bugzilla.gnome.org/show_bug.cgi?id=648857
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=648872
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Don't use get_cursor() to open the current item in the sidebar, and use
the tree selection instead, as we modify the selection manually when
evaluating up/down keypresses.
https://bugzilla.gnome.org/show_bug.cgi?id=648555
|
|
|
|
|
|
|
| |
Chaining up resets the background to the default color, which is not
what we want for the desktop container.
https://bugzilla.gnome.org/show_bug.cgi?id=648137
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=647570
|
|
|
|
|
|
|
| |
Otherwise, a fake drag state will leak into the next motion-notify event
when the menu has been dismissed, causing a segfault.
https://bugzilla.gnome.org/show_bug.cgi?id=550253
|
|
|
|
|
|
|
| |
This fixes artifacts while resizing. A similar patch was committed to
GtkInfoBar in https://bugzilla.gnome.org/show_bug.cgi?id=587716.
https://bugzilla.gnome.org/show_bug.cgi?id=647013
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=647088
|
|
|
|
|
|
|
|
|
|
| |
If we don't do this, we ignore any other double click event that happen
during the next 'gtk-double-click-time' interval after the first double
click.
Thanks to Tanyel A. Nimeu for the initial patch.
https://bugzilla.gnome.org/show_bug.cgi?id=647062
|
|
|
|
|
|
|
| |
This also fixes radiobuttons preferences not being applied when opening
the properties dialog.
https://bugzilla.gnome.org/show_bug.cgi?id=644478
|
| |
|
|
|
|
| |
This is not required anymore in GTK+ 3
|