On Sun Aug16'26 06:47:17PM, Todd Zullinger wrote: > From: Todd Zullinger <[email protected]> > Date: Sun, 16 Aug 2026 18:47:17 -0400 > To: [email protected] > Subject: Re: question on executing executable in mailcap > > Ranjan Maitra via Mutt-users wrote: > > On Sun Aug16'26 07:22:46PM, Michael Kjörling wrote: > >> Then check the environment from within mutt. <shell-escape> something > >> like `env | less` and look closely at $PATH. Does it include ~/bin? > > > > Thanks! I am sorry, but what does this mean? I tried > > hitting ESC but did not get anything that can work. Sorry > > about that.
Todd, Thanks very much! > > By '<shell-escape>' Michael means the mutt function which > runs a shell command. It is bound to the '!' key by > default. I see. > If you type '!' and mutt will prompt with 'Shell command: ' > and then you'd put in 'env | less' (no quotes) or 'printenv > PATH | less' or any number of other ways to inspect the > environment for the PATH variable as mutt sees it. Interesting, it is not in the PATH. > If you start mutt via ssh or as a direct command in some > terminal's profile, this may well differ from what you get > if you directly start a shell. That can easily be the > reason that PATH contains ~/bin in your shell sessions but > not mutt's. Thank you for this. I have now figured this out. mutt was being called by a function called xbuffy and what happened was that my new installation of Fedora 44 does not include this path by default so I had to explicitly include it in my .bashrc. But because xbuffy had been called before I figured this out, there was the problem of the path not being found. Now this is fixed by killing and restarting xbuffy. THnk you for your insight and to everyone else for their helpful suggestions! Best wishes, Ranjan
