On Wednesday 21 November 2018 at 18:28:31 +0000, Mike Crowe wrote: > On Tuesday 06 November 2018 at 19:06:45 +0000, Mike Crowe wrote: > > On Monday 16 July 2018 at 08:19:11 +0200, Steffen Sledz wrote: > > > On 04.07.2018 13:37, Steffen Sledz wrote: > > > > On 03.07.2018 08:04, Steffen Sledz wrote: > > > >> On 02.07.2018 20:25, Khem Raj wrote: > > > >>> On Sun, Jul 1, 2018 at 11:39 PM Steffen Sledz <[email protected]> > > > >>> wrote: > > > >>>> > > > >>>> After upgrading my build system from openSUSE Leap 42.3 to openSUSE > > > >>>> Leap 15.0 a > > > >>>> > > > >>>> bitbake foo -c devshell > > > >>>> > > > >>>> no longer switches to the related work directory. The devshell is > > > >>>> opened in the original directory without any error or warning > > > >>>> instead. > > > >>>> > > > >>>> Any hints what's wrong here or how I can debug this behaviour? > > > >>>> > > > >>> > > > >>> which terminal are you using, probably some default behavior changes > > > >>> there ? > > > >> > > > >> Main terminal is xterm. No special settings for the devshell terminal, > > > >> so tmux is started like before. > > > > > > > > > > > > After some more tests I can limit the problem to OE_TERMINAL="tmux". > > > > Other terminals like screen or xterm work well. > > > > ... > > > > > > > > > Ping! > > > > The same problem happens with Debian Buster (currently "testing".) I was > > unable to reproduce the problem when running > > > > (cd subdirectory && tmux split-window) > > > > from a shell prompt.
This was deemed a bug by tmux upstream and fixed there: https://github.com/tmux/tmux/issues/1549 I reported the bug to Debian, who applied the fix on top of 2.8: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914816 and the fixed version 2.8-2 has now migrated to Debian Buster: https://tracker.debian.org/news/1009699/tmux-28-2-migrated-to-testing/ It looks like Ubuntu Cosmic 18.10 has tmux 2.7-1, so it wasn't affected. Ubuntu Disco (19.04?) currently has 2.8-2 which contains the fix. It would be possible to work around the tmux 2.8 bug in oe-core by always passing the directory as I did in my patch, but I shall let someone who is affected by it decide whether that's worthwhile. Mike. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
