On Mon, Jan 12, 2026 at 07:52:22PM +0100, Matthias Andree via Mutt-dev wrote:
https://gitlab.com/muttmua/mutt/-/issues/459 says:
"source ./file is resolved to the current working directory. While
that may be consistent in interactive use, it is unexpected/unpractical
in configuration files. If, for the sake of consistency with
interactive use, this can't be changed, perhaps we could get a variable
$cwd which is set within configuration files to their respective path,
which would allow for source $cwd/file."
...
If the intention is "relative to the configuration file's path", maybe
we can add such a feature but with a clearer name?
I agree that it should have a different name, because those are two
different ideas. The current working directory is an attribute of a
process, and it can change during the life of the process. The location
of a configuration file has nothing to do with any process's current
working directory.
$cwd as proposed above would change the meaning of current working
directory. Let's not do that.
Also, the proposed thing looks like a general configuration variable,
settable by the user to modify Mutt's behavior, but it's not that. It's
a read-only piece of information supplied by Mutt. I'd want to think
more about how to represent that -- maybe some special symbol rather
than $<name>. Or are there already other read-only variables like that?
