| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Use an unsigned char to avoid implementation-defined behavior of a right
shift.
Shift by 4 rather than 8 to get the second half of a byte.
https://bugzilla.gnome.org/show_bug.cgi?id=711457
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add a new -u option to gvfs-ls utility which will make it output
properly escaped URIs. These URIs may then be passed to other gvfs-*
tools.
Signed-off-by: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>
https://bugzilla.gnome.org/show_bug.cgi?id=683295
|
| |
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=684328
Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
|
|
|
|
| |
Support gvfs-trash --empty to empty the trash.
|
|
|
|
|
|
| |
See http://git.gnome.org/browse/glib/commit/?id=2002479c02fa6e468fc3f67ddc663657a52ebde8
https://bugzilla.gnome.org/show_bug.cgi?id=687236
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=681458
|
|
|
|
| |
Closes https://bugzilla.gnome.org/show_bug.cgi?id=595087
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=595070
|
|
|
|
|
|
|
| |
Unify the spelling. For the discussion see:
https://bugzilla.gnome.org/show_bug.cgi?id=520902
Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating the address of the FSF.
This has been done by:
while read file; do
sed -i 's:59 Temple Place:51 Franklin Street:' $file
sed -i 's:Suite 330:Fifth Floor:' $file
sed -i 's:02111-1307:02110-1301:' $file
done
https://bugzilla.gnome.org/show_bug.cgi?id=656598
Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
|
|
|
|
|
|
| |
The rule for the returning value and multiple arguments is to
go through all of them and return non-zero exit code when one or more
fails.
|
|
|
|
| |
One can trash directories too, thus use LOCATION instead of FILE.
|
|
|
|
|
| |
Move --detail to the end so it comes after the options that
it affects, in help output.
|
|
|
|
| |
The option --print_etag was misnamed. Now it is --print-etag.
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the --help output more consistent across the utilities.
- Capitalize parameters
- Make summaries full sentences
- Shorten some overlong strings
- Strip . off option descriptions
- Make descriptions of identical options the same
- Improve error handling for option parsing
Also, do proper gettext setup in all utilities.
|
|
|
|
|
|
|
|
| |
Apparently g_app_info_launch_default_for_uri() can't handle invalid
URIs like the plain local path, returning G_IO_ERROR_NOT_SUPPORTED.
Let's go through GFile to get a full URI as a fallback.
https://bugzilla.gnome.org/show_bug.cgi?id=676313
|
|
|
|
|
|
|
| |
bash-completion upstream has changed the preferred location for completion
scripts, let's make it consistent across our stack.
https://bugzilla.gnome.org/show_bug.cgi?id=678537
|
|
|
|
|
|
|
| |
g_app_info_launch_default_for_uri() didn't exist when gvfs-open was
first written, but now that it does, there's no reason not to use it.
https://bugzilla.gnome.org/show_bug.cgi?id=676313
|
|
|
|
|
|
| |
Like the rest of gvfs-mount(1), this is mostly useful for debugging.
Signed-off-by: David Zeuthen <davidz@redhat.com>
|
| |
|
|
|
|
| |
As used by the app chooser button
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is detailed in this bug
https://bugzilla.gnome.org/show_bug.cgi?id=661711
Also extend the private D-Bus protocol used between the client- and
service-side for out-of-process volume monitors. In particular,
introduce a new a{sv} member that we can use in the future to for
expansion without breaking ABI.
Signed-off-by: David Zeuthen <davidz@redhat.com>
|
|
|
|
|
| |
Especially now that deprecations are proper gcc warnings, no need
to hardcode this.
|
|
|
|
|
|
| |
List the apps registered for a particular mime-type, and
set a particular application as the default handler for a
mime-type.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=629116
|
|
|
|
|
|
|
|
|
|
|
| |
Previously gvfs-open exited with success (error code 0) even when open
failed, either because file was not found or there was no default
application registred to open it. Without easy testing for error codes,
it was hard to use it in scripts. Now it exits with code 1 when any of
the given files are either not found or its default application is not
registered.
https://bugzilla.gnome.org/show_bug.cgi?id=655470
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=655474
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=641856
|
|
|
|
| |
The case resolved to the default anyway.
|
|
|
|
|
|
|
| |
argc contains the number of arguments, including the name of the program, so it
is one more than expected.
In addition, value must also be checked, otherwise segfault ensues.
|
|
|
|
|
| |
Commit 68607708bc34cfdc357a823fb6f909d3696fec78 added the unset type but
forgot to add it to the documentation.
|
|
|
|
|
|
|
| |
Most of those programs would return 0 even on error. They
should instead return 1 when an error occurred.
https://bugzilla.gnome.org/show_bug.cgi?id=611891
|
| |
|
|
|
| |
Last part to fix bug #593045
|
|
|
| |
Partly fixes bug #593045
|
|
|
| |
Partly fixes bug #593045
|
|
|
|
|
|
| |
GIO gained has support for file-monitoring "move events" since 2.23.4.
Make use of those in gvfs-monitor-[dir|file] unless new commandline
option "-N" is specified. (Bump glib requirement accordingly).
|
|
|
|
|
|
|
|
|
|
|
| |
The "default location" of the given mount is a path that reflects
the main entry point for the user (e.g. the home directory, or the
root of the volume).
Backends can use g_vfs_backend_set_default_location () to set the
default location (before registering the mount).
https://bugzilla.gnome.org/show_bug.cgi?id=561998
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=593045
|
|
|
|
| |
This memory leak was reported by clang. Bug 594829.
|
|
|
|
| |
Lots of not translated strings, some errors did not go to stderr, etc.
|
|
|
|
| |
Also clean up things a bit, and fix up translations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Port everything to use _with_operation() variants of unmount/eject
methods
- Add support for g_file_poll_mountable()
- new job class: GVfsJobPollMountable
- Pass mount operation for unmount/eject ops on GDaemonFile and
GDaemonMount
- receive in the appropriate GVfsJob classes
- also pass unmount flags where it was missing
- port all backends to use this
- Teach GMountSource and GMountOperationDBus about the new
GMountOperation::show-processes signal
- also provide new API
- g_mount_source_is_dummy() - e.g. when the client didn't
passed NULL for the GMountOperation
- g_mount_source_abort() - to send the ::abort signal to the
client-side GMountOperation
- make the client-side of GMountSource return ::reply with
NOT_HANDLED when we do an abort
- Refactor the mount operation handling in GProxyVolumeMonitor
- Pass mount operation for unmount/ejects in GProxyVolumeMonitor
- Pass the process id of the actual reader/writer in OpenForRead
and OpenForWrite daemon methods
- add some private API for making the FUSE client set the
pid of the POSIX client (otherwise it looks like the FUSE
client is blocking) and pass the right pid.
This is because the FUSE client is basically impersonating the
POSIX processes.
- Make the process id mentioned above available in appropriate
GVfsJob classes
- GVfsJobOpenForRead
- GVfsJobOpenForWrite
- GVfsChannel
- Provide API to get a list of all blocking clients, e.g. an array
of GPid
- g_vfs_daemon_get_blocking_processes()
- Provide convenience API to easily doing the right thing on unmount;
e.g. interact with the user about blocking processes - see the gphoto2
backend for example usage
- g_vfs_backend_has_blocking_processes()
- g_vfs_backend_unmount_with_operation() and
g_vfs_backend_unmount_with_operation_finish()
- Only the gphoto2 backend supports ::show-processes right now. Support
for other backends will be added shortly.
- Implement support for ::show-processes in the GDU volume monitor
- right now we don't support "Unmount Anyway" since it requires
ABI changes in libgdu.so - this will be changed as soon as there's
a new gnome-disk-utility release
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example:
vuntz@lyon ~/>gvfs-info -a standard::content-type ~/blah.txt
type: unknown
size: 0
attributes:
standard::content-type: text/plain
type and size probably shouldn't be displayed if a specific attribute was
requested..
|
| |
|