From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C691159CB2 for ; Thu, 14 Apr 2016 18:26:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3F56321C08B; Thu, 14 Apr 2016 18:26:16 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1CE1FE089B for ; Thu, 14 Apr 2016 18:26:14 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aqlxz-0006pG-E3 for gentoo-user@lists.gentoo.org; Thu, 14 Apr 2016 20:26:11 +0200 Received: from ppp118-209-40-116.lns20.mel4.internode.on.net ([118.209.40.116]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Apr 2016 20:26:11 +0200 Received: from kensington by ppp118-209-40-116.lns20.mel4.internode.on.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Apr 2016 20:26:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Michael Palimaka Subject: [gentoo-user] Re: KDE5 & Disabling search and recent documents & thoughts Date: Fri, 15 Apr 2016 04:26:03 +1000 Message-ID: References: <570AE7D9.1@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ppp118-209-40-116.lns20.mel4.internode.on.net X-Enigmail-Draft-Status: N1110 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 In-Reply-To: <570AE7D9.1@gmail.com> X-Archives-Salt: 26502e78-e014-40bc-b527-dd2ef73d7f77 X-Archives-Hash: 16e89f359cc8b01127c858b4cb01f0f9 Hi Dan, On 11/04/16 09:55, Daniel Frey wrote: > OK > > We're in 2016 now. And KDE *still* doesn't make it easy to disable their > damn indexer. I've never wanted to search through my menu, I've never > wanted it to remember every damn file I've opened. It's a personal > preference. > > WHY can't we have a single checkbox to disable all this crap? I found > one and it didn't work (search in system settings.) Then when I was > searching around online I found out it will reenable itself magically > randomly anyway! > > I also tried balooctl and it didn't work either. > > So I got very pissed off at this point and did the following: > > $ chmod 444 ~/.kde4/share/apps/RecentDocuments/ > $ rm /usr/bin/*baloo* > > Rebooted > > $ rm -rf ~/.config/baloo* > $ rm -rf ~/.local/share/baloo > > Rebooted again > > ...and FINALLY it stopped indexing and remembering stuff that I told it > not to. It still remembers the last application used, but I don't really > care about that. I've put those commands in a script in /etc/local.d too. > > Just figured others might want the info. A note, searching for files > through Dolphin can be affected by this. I never do that myself, I > always use a shell (konsole, etc.) > > I've been using and tweaking for a couple hours now and haven't seen any > ill side-effects from my "nuclear" option. In System Settings -> Search there's options to turn off the file indexer as well as all the other search plugins (including recent documents). I've heard that sometimes it can take a little bit for the indexer to stop, but otherwise it seems to work OK fo rme. Duncan has some patches floating around if you want to strip baloo out completely. > One other gripe on KDE5: it's 2016, why can't we use the meta key to pop > up the menu? Really... Not sure the reason why it's not native functionality, but you might try x11-misc/ksuperkey. > Other than that, things are a bit different. I'm not sure I like the > flat look yet. After the upgrade for some reason the K menu was > invisible, but when I set the theme to Oxygen it was visible again? I > thought that was odd, did anyone else experience that? Maybe a botched settings migration? > > Dan > > Kind regards, Michael