Subject: Re: bug#79322: file name transforms inconsistencies

From: Eli Zaretskii <[email-masked]>
Date: Sat, 30 Aug 2025 21:42:57 +0300

> From: Gabriel do Nascimento Ribeiro <[email-masked]>
> CC: "[email-masked]" <[email-masked]>
> Date: Sat, 30 Aug 2025 18:06:15 +0000
> msip_labels:
> 
> Hi Eli,
> 
> > The reason for the warning was an incorrect :type of the defcustom,
> > which didn't take this option into account; I've now fixed that on the
> > master branch.
> 
> Thank you.
> 
> What about 'backup-directory-alist', does it support secure-hash or would be
> feasible to make it so?

It doesn't support that currently, no.  To make it support something
like that we'd need a new option, since backup-directory-alist only
specifies the directory in which to place backup files, it doesn't
specify the backup file names.

> > You could use
> >
> >   (setopt auto-save-file-name-transforms '((".*"  "~/.auto-saves/" t)))
> >
> > instead, no?  Using UNIQUIFY of nil is not recommended, as the doc
> > string says.
> 
> Yes, I agree that UNIQUIFY nil is not recommended.  My point is regarding users
> setting it to nil (for whatever reason) and not getting a warning.  If this user
> option accepts UNIQUIFY nil, it should not warn.  In this case, my suggestion is
> to fix the defcustom :type.

Since we don't recommend to do that, it seems to be okay not to
support it in the defcustom.  Users who want to do that regardless can
always use setq, or disregard the warning that setopt emits.