On 08/07/2018 09:52 AM, Gene Heskett wrote:
On Tuesday 07 August 2018 01:18:03 David C. Rankin wrote:
On 08/06/2018 01:24 PM, Gene Heskett wrote:
Didn't that use to be kbuildcycoca or similar to restore that stuffs?
kbuildsycoca --noincremental
Then log out/log in. Though I'm not sure how much of the xdg_menu it touches, but it should sort out any kmenuedit issues with locally added entries.
And as usual, oldtimers (I'm 83) at work, I forgot the logout/login part. :( Still haven't done it. My working system starts most as me, a whole bunch of stuff after I login, and it takes me 5+ minutes to get everything restarted. A common shell history is a problem, each terminal _and_ tab should have its own history, but they don't. So I have to search thru the common to all history to find what I was previously running in _this_ workspace and _this_ tab. With a months uptime right now, thats a llllloooooonnngg history file. ;-)
Chuckling...
I have a dcop script that restores my konsole session and restores the connections to the remote hosts when I launch it. I have 5 local tabs open and 5 remote. History file does get quite lengthy, and it has always been frustrating that all local history from the 5 local tabs all ends up one histfile (and then only if you exit gracefully)
Above that, I keep 40K of entries in my histfile config in ~/.bashrc, e.g.
export HISTFILESIZE=40000 export HISTSIZE=40000 export HISTCONTROL=ignoreboth:erasedups export HISTIGNORE=' *:&'
I cheat too, I have a short function aliased to 'hist' in my .bashrc as well,
showhist() { [ -z "$1" ] && { printf "usage: hist <search term>\n"; return 1; } history | grep "$1" return 0 }
That allows a simple 'hist term' at the command line to find what I'm looking for with minimal typing :)
I looked further and kbuildsycoca should sort out the xdg_menu entries, it also has a '--menutest' option as well that preforms the abbreviated check of the menu setup.