Bug 307441

Summary: split window open in same path
Product: [Applications] yakuake Reporter: Yngve Levinsen <yngve>
Component: generalAssignee: Eike Hein <hein>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: blueice, frederick888, kajokeji.2013, muesli, sonusalmotahida
Priority: NOR    
Version: 2.9.8   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Yngve Levinsen 2012-09-26 15:36:59 UTC
I have a wish for Yakuake. Very often when I split window horizontally or vertically, I want to open in the same location. E.g. I often want to open a file or two in vim from the current folder while keeping a terminal open in the same folder. Would it be possible to add an option that when one does split window the new terminal session is opened in the same path instead of home?

I see how this could be problematic for e.g. ssh sessions, but you could probably limit yourself to local paths or something like that?

And finally, thanks a lot for making the best Linux terminal experience I know of! :D

Reproducible: Always

Steps to Reproduce:
1. Open a terminal/tab, cd to a folder path
2. Split window vertically/horizontally

Actual Results:  
New session is opened in $HOME instead of previous location, which would at least for me seem more useful/intuitive.
Comment 1 Sonus Sundar 2016-03-16 04:03:51 UTC
Yeah as a consistent user of Yakuaka now a days , I also like to see this option in the tool. Terminator has this feature and I think you guys should try to implement it in the next version.
Comment 2 Frederick Zhang 2017-11-19 16:05:49 UTC
And I reckon just as many other terminals, e.g. Konsole, Terminal in macOS, preserving current working directory after opening a new session would also be useful. It does not need to be the default behaviour, but at least there should be such an option.
Comment 3 Christian Muehlhaeuser 2020-03-10 15:03:19 UTC
Even though this ticket has been created first, I'm going to group reports for this feature under #396472.

*** This bug has been marked as a duplicate of bug 396472 ***