Audacity fails to parse “~” tilde for user’s home directory in export audio dialog about audacity HOT 4 OPEN

I'm pretty sure ~ is interpreted by the shell, and file IO primitives including system commands like open do not do regular expression matching or convert ~ to $HOME or replace $HOME for that matter. So you could actually name a file "~" or "$HOME" although it's obviously a bad idea.

from audacity.

All GTK+ file pickers/choosers, Qt, KDE, and all popular desktop applications support "~" expansion.

E.g., right click this page in Firefox or Chrome, type ~/somefile.txt and it'll save it in $HOME/somefile.txt.

Shells do also expand ~ but it isn't limited to a shell feature

from audacity.

According to a comment in the forum (https://forum.audacityteam.org/t/bug-audacity-fails-to-parse-tilde-for-users-home-directory-in-export-audio-dialog/106141) this may be a regression after 3.4.2

from audacity.

It's not technically a regression - before 3.4, the export dialog was a customized file picker. Now, the "browse" button in the export dialog opens the native (and unmodified) file picker, while the box inside the export dialog just is a textbox.

A fix for this probably involves validating mFullName in ExportFilePanel.cpp. There already is ExportFilePanel::ValidateAndFixExt() which does the same for invalid characters in the filename.

from audacity.