On Mon, Jan 12, 2026 at 07:47:41PM +0100, Arnt Gulbrandsen wrote: > https://gitlab.com/muttmua/mutt/-/issues/459 says: > > "source ./file is resolved to the current working directory.
No it isn't. "." (on POSIX systems, at least) is an automatically- created hard link to the directory in which the "." exists; i.e. it is in fact that same directory, by another name. It is not "resolved" per se, at least not by Mutt. > 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." I completely disagree with this premise. I think to most experienced users, ./file means exactly what it means to the OS; introducing a different meaning is more likely to cause confusion, not less, and probably likely to break existing configurations that depend on the existing behavior. The correct solution is the one you already proposed in the ticket, or just use absolute paths. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
