1. 29 May, 2017 1 commit
  2. 10 Apr, 2017 3 commits
    • Victor Manuel Jaquez Leal's avatar
      gio-tool: Fix errors format string · 3d7534ea
      Victor Manuel Jaquez Leal authored
      Compiling with clang 3.8.1-18 (debian, x86_64) I ran across this
      gio-tool.c:40:31: error: format string is not a string literal [-Werror,-Wformat-nonliteral]
        message = g_strdup_vprintf (format, args);
      gio-tool.c:55:31: error: format string is not a string literal [-Werror,-Wformat-nonliteral]
        message = g_strdup_vprintf (format, args);
      2 errors generated.
      To fix the first one, related with the function print_error(), this
      patch adds to the function prototype a compiler's attribute.
      For the second one, since the usage of that function is to print
      one string and the format is already provided, the patch simplifies
      the function by no receiving variadic arguments.
    • Ondrej Holy's avatar
      gio-tool: Do not leak GOptionContext · fb7d2184
      Ondrej Holy authored
      GOptionContext is freed only in case of success. Free the context
      also in case of failure.
    • Ondrej Holy's avatar
      gio-tool: Various fixes related to error messages · 0beeeb2e
      Ondrej Holy authored
      This patch contains the following changes:
      - Print all errors with "gio: " prefix
      - Print file uri in error for each tool allowing multiple locations
      - Mark all error messages translatable
      - Do not leak strings used in error messages
      - Always start error messages with capital letter
      - Unify some error messages across various tools
      - Fix addional/missing new line characters
  3. 17 Jul, 2016 1 commit
  4. 11 Jul, 2016 1 commit
  5. 01 Jul, 2016 1 commit
    • Matthias Clasen's avatar
      Add a new gio commandline tool · 9edba4e4
      Matthias Clasen authored
      This command collects the various commandline utilities that
      are currently shipped in gvfs, and unifies them under a single,
      command-style binary.
      The tools just use GIO APIs, so it makes sense for them to live here.