On Monday, June 16, 2008 3:14 am Colin Guthrie wrote:
> AAW wrote:
> > Thanks for responding. The two directories aren't triggered by kde3
> > apps. I made sure of that much.
>
> I wasn't suggesting that both directories were triggered by kde3, but
> that .kde4 is triggered by kde4 and, during it's startup some kde3 apps
> were launched (e.g. basket or similar), which triggered .kde3...
>
> > It took me forever to discover how to move the konsole Tab
> > Bar from bottom to top. <grumble>And I still don't understand why the
> > hell they replaced a simple right-click>Tab Bar with
> > MenuBar>Settings>Edit Profile>Tabs.</grumble>
>
> Ahhh, that's how you do it.... :)
>
> My current gripe is that the View Menu Bar (How often do you need a menu
> in a terminal?) option is not sticky... it only works for the current
> terminal. Gah! (yes I should report and/or fix this!)
>

I did understand what you meant, just expressed it very poorly. The .kde
directory is created even when (according to ksysguard) no kde3 apps are
running on the box. It appears to be almost a skeleton directory. All the
config files I've checked are empty except for [$Version] sections with
update-info entries.

Like tab position, display of the menu bar is controlled by the profile. Edit
Profile>General, "Show menu bar in new windows". The changes don't show up
until konsole is closed and restarted. From my limited experiments, the
setting is sticky, even from login to login.

That gave me the idea of creating a second terminal profile (NewLocation) set
to open at a different location than the default one. It works and the
profile is now remembered from login to login. Unfortunately, when I save a
KDE session with two tabs (Shell and NewLocation), only a single tab (Shell)
is opened at login.

Appeal to any KDE4 gurus out there:
If this is the best KDE4 is capable of right now, would someone PLEASE tell
me. I've wasted far too much time on this. If I'm just missing something, a
hint or two would be greatly appreciated.

Thanks,
Arn