> On Dec 21, 2015, at 4:57 PM, Michael Albinus <[email protected]> wrote: > > Augie Fackler <[email protected]> writes: > > Hi Augie, > >> As of some recent-ish version of emacs the included tramp no longer >> works out of the box with FreeBSD remote hosts, as they don't accept a >> -l flag for >> /bin/sh. I'm sure I can work around this with some configuration knobs >> (which I'll look into shortly), but I didn't see any evidence of a >> report upstream. It looks like the use of the nonstandard flag was >> introduced by tramp git commit 82088de77ddc238b64665a5318ec7a56ac11b7bd, >> although master has now diverged by enough I'm not sure if it's still a >> problem. > > The problem happens when you have added `tramp-own-remote-path' to > `tramp-remote-path'. With commit 707b51675d18daf4435f474e3942814871d31afe > to the Tramp repository, this has been masked not to be a problem > anymore. I won't call it final fix, because `tramp-own-remote-path' is > not active any more in such case.
Is there any knob I can adjust that would let me not pass -l to the sh instance? This particular machine has bash installed, but not all of the ones I talk to do, and not losing tramp-own-remote-path would be nice in those instances. > > You might test Tramp from its repository (or Emacs from the emacs-25 > branch), or wait a little bit: Tramp 2.2.13 is planned for release still > this year. > > Best regards, Michael. Thanks for the quick response! Augie _______________________________________________ Tramp-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/tramp-devel
