Summary: | "Start in same directory as current tab" has no effect | ||
---|---|---|---|
Product: | [Applications] yakuake | Reporter: | Christian Muehlhaeuser <muesli> |
Component: | general | Assignee: | Eike Hein <hein> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugseforuns, chhajedchinmay, frederick888, kde, linken.dinh, nate, yngve |
Priority: | NOR | ||
Version: | 3.0.5 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://cgit.kde.org/yakuake.git/commit/?id=aa5306c478bf93182a96f68a7034d3849120cae4 | Version Fixed In: | 20.04.0 |
Description
Christian Muehlhaeuser
2018-07-13 12:33:36 UTC
I can confirm this too. Same profile in Konsole and the checkbox setting is followed but inside Yakuake new tabs/splits always start in my home folder. Setting an initial folder doesn't make a difference either. I've spent a bit of time getting things set up so I could compile Yakuake and going back to v3.0 and the setting didn't work then either. Looking at the git blame it looks like the line of code for opening the terminal at the path hasn't really changed in 11 years so I'm really not sure what to do now [0] is where the new terminal sessions are opening (or at least, if I change that to `rootPath()` all new terminals open `/`). Checking the previous version it used `KUser` to get the home path but still basically did the same thing. Before that the last change was 11 years ago :-/ I've tried to have a look through the Konsole source to see how that does it but I'm not finding anything that looks useful (I don't know any KDE code really so I'm just trying to search for something similar). 0: https://github.com/KDE/yakuake/blame/master/app/terminal.cpp#L89 There is a link to a github commit which seemed to have fixed it in the past: https://mail.kde.org/pipermail/konsole-devel/2013-June/021269.html https://github.com/panzi/Yakuake/commit/e5668b2ce4d142070631374306667f3e3a3d8369 *** Bug 412392 has been marked as a duplicate of this bug. *** *** Bug 307441 has been marked as a duplicate of this bug. *** |