avoid FILENAME_MAX for allocating on the stack

* FILENAME_MAX is a standard C macro, but it may be arbitrarily long on some platforms
  (like the popular GNU/Hurd). See:
  https://www.gnu.org/software/libc/manual/html_node/Limits-for-Files.html#index-FILENAME_005fMAX
* This means there is no portable macro for the maximum path length.
  You could perhaps define PATH_MAX to MAX_PATH on Windows.
* Instead, we use g_strdup_printf() to calculate the save point name.
  We avoid another g_build_filename() by prepending the directory in the printf().

0 files changed, 0 insertions, 0 deletions