alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu: use g_printerr for errors, instead of g_warning

Browse Source 
With the new logging setup, we need g_printerr
This commit is contained in:
Dirk-Jan C. Binnema
2020-06-11 22:16:36 +03:00
parent 9b2746dce5
commit 68533cee0d
6 changed files with 26 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
mu/mu-cmd.cc
View File

@ -302,13 +302,13 @@ static gboolean
check_file_okay (const char *path, gboolean cmd_add)
{
if (!g_path_is_absolute (path)) {
g_warning ("path is not absolute: %s", path);
g_printerr ("path is not absolute: %s\n", path);
return FALSE;
}
if (cmd_add && access(path, R_OK) != 0) {
g_warning ("path is not readable: %s: %s",
path, strerror (errno));
g_printerr ("path is not readable: %s: %s\n",
path, strerror (errno));
return FALSE;
}
@ -341,14 +341,14 @@ foreach_msg_file (Mu::Store& store, const MuConfig *opts,
if (!check_file_okay (path, TRUE)) {
all_ok = FALSE;
g_warning ("not a valid message file: %s", path);
g_printerr ("not a valid message file: %s\n", path);
continue;
}
if (!foreach_func (store, path, err)) {
all_ok = FALSE;
g_warning ("error with %s: %s", path,
(err&&*err) ? (*err)->message :
g_printerr ("error with %s: %s\n", path,
(err&&*err) ? (*err)->message :
"something went wrong");
g_clear_error (err);
continue;