Currently, when using a GtkFileChooser in GTK_FILE_CHOOSER_ACTION_SAVE mode in our application, the act of entering in a non-existant file name and choosing to save causes a warning after the pattern:

Gtk-WARNING **: Unable to retrieve the file info for `file:///home/clinton/some.file': Error stating file '/home/clinton/some.file': No such file or directory

It appears that, upon the chooser adding a recently-used filename to the recent manager's list, gtk_recent_manager_add_item_query_info() eventually gets called, causing it to attempt to check the status of a file that doesn't exist yet and generate a warning, since we can only proceed to writing the file after we've gotten the filename from the chooser.

Since, depending on what an application is doing at the time, it may be expected that the named file may not exist yet, would it be possible to add an API to tell gtk_recent_manager_add_item_query_info() to fail quietly?