On Sun, Aug 16, 2026 at 06:04:17PM -0500, Ranjan Maitra via Mutt-users wrote:
> > 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.
Another aspect of this kind of problem is X11 vs. Wayland. I don't
know which Fedora 44 uses, but you may want to read this Stack
Exchange thread:
https://superuser.com/questions/1658072/whats-the-wayland-equivalent-of-xsession
and maybe this Gnome discourse thread (warning: hostile territory!)
https://discourse.gnome.org/t/gnome-shell-wayland-run-command-how-can-i-set-or-change-path/36596
--
Ian
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.