From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why is KDE so bad at multiple monitors?
Date: Sun, 3 Mar 2024 17:47:59 -0600 [thread overview]
Message-ID: <ab6734cc-e78a-686f-8d34-0af0f9300ddb@gmail.com> (raw)
In-Reply-To: <18263f5b-e3ce-4b11-b9a0-cb058fcbc337@gmail.com>
Daniel Frey wrote:
> On 3/3/24 13:57, Dale wrote:
>> I think most is in the .config directory now. I have to say tho, I used
>> to zap that thing about once a year, sometimes two, to correct some
>> things that were weird but couldn't fix otherwise. I think the devs try
>> to make things forward compatible but no one is perfect. Sometimes, you
>> just have to start fresh. I do hate resetting everything tho. It takes
>> a while to get everything back to at least close to the old way.
>>
>> Dale
>>
>> :-) :-)
>>
>
> So many programs store config in there now it's hard to just zap it so
> I generally won't try that. It's not just setting up kde again, it's
> dozens of other programs too. :o(
>
> Dan
>
>
True. Inside .config is kdedefaults. That would likely be a good
start. The directories inside there are mostly KDE. Here's my list.
root@fireball / # /bin/ls /home/dale/.config/kdedefaults/
kcminputrc kdeglobals kscreenlockerrc ksplashrc kwinrc package
plasmarc
root@fireball / #
There's also some files in .config that start with a 'k' that may need
to be renamed or deleted if you are brave.
It's not as easy as it used to be tho. I wonder, can the old .kde4
directory be removed now??? I suspect everything is KDE5 now, with KDE6
right around the corner I think.
Dale
:-) :-)
next prev parent reply other threads:[~2024-03-03 23:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 4:53 [gentoo-user] Why is KDE so bad at multiple monitors? Daniel Frey
2024-02-25 5:52 ` Dale
2024-02-25 9:01 ` Michael
2024-02-25 15:08 ` Dale
2024-02-25 17:36 ` Daniel Frey
2024-02-25 18:10 ` Michael
2024-02-25 17:34 ` Daniel Frey
2024-02-25 18:17 ` Mark Knecht
2024-02-27 15:21 ` Daniel Frey
2024-02-25 11:29 ` Paul Colquhoun
2024-02-28 22:13 ` Paul B. Henson
2024-02-28 22:23 ` Dale
2024-02-28 22:43 ` Mark Knecht
2024-02-29 11:27 ` Dale
2024-03-03 18:59 ` Daniel Frey
2024-03-03 19:31 ` Dale
2024-03-03 19:39 ` Daniel Frey
2024-03-03 21:57 ` Dale
2024-03-03 22:39 ` Daniel Frey
2024-03-03 23:47 ` Dale [this message]
2024-03-03 21:20 ` Michael
2024-03-04 2:39 ` Dale
2024-03-14 21:23 ` Mart Raudsepp
2024-03-05 10:56 ` Arsen Arsenović
2024-03-02 5:11 ` Paul B. Henson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab6734cc-e78a-686f-8d34-0af0f9300ddb@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox