Greetings all;
Still on wheezy.
Sometime in the last 3-4 days, maybe not this mornings update, I needed to get some stuff out of my camera today, which I normally do with digicam.
Chaseing the rodent up the menu list popup, I stop at graphics, expecting a lengthy popup. Wait, but nothing.
Didn't that use to be kbuildcycoca or similar to restore that stuffs?
On further poking at this yellowjackets nest with kmenuedit, I find its all there, but buried an extra level deep, and does not show that extra level depth with a line item in the menu itself. Call up the kmenuedit handbook and look up copy/paste intending to move it all back to where it belongs, but theres no reaction to highlighting the extra level and pressing control+c, then moving back and highlighting the top level menu where it belongs and pressing control+V. No user feedback whatsoever.
So I decide to quit that as its obviously broken. BUT! When I quit, it updates everything. So I go back to the graphics line, and voila! Its all back where it belongs.
I remember it used to do that, but while you were adjusting stuff so you could see the results in a few seconds. When did it start waiting until you quit? Bad dog, no biscuit.
You shouldn't have to quit but I have always had to save for it to show the updates.
On Mon, Aug 6, 2018 at 2:24 PM, Gene Heskett gheskett@shentel.net wrote:
Greetings all;
Still on wheezy.
Sometime in the last 3-4 days, maybe not this mornings update, I needed to get some stuff out of my camera today, which I normally do with digicam.
Chaseing the rodent up the menu list popup, I stop at graphics, expecting a lengthy popup. Wait, but nothing.
Didn't that use to be kbuildcycoca or similar to restore that stuffs?
On further poking at this yellowjackets nest with kmenuedit, I find its all there, but buried an extra level deep, and does not show that extra level depth with a line item in the menu itself. Call up the kmenuedit handbook and look up copy/paste intending to move it all back to where it belongs, but theres no reaction to highlighting the extra level and pressing control+c, then moving back and highlighting the top level menu where it belongs and pressing control+V. No user feedback whatsoever.
So I decide to quit that as its obviously broken. BUT! When I quit, it updates everything. So I go back to the graphics line, and voila! Its all back where it belongs.
I remember it used to do that, but while you were adjusting stuff so you could see the results in a few seconds. When did it start waiting until you quit? Bad dog, no biscuit.
-- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene
To unsubscribe, e-mail: trinity-users-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-users. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting
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.
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. ;-)
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.
-
David C. Rankin -
Gene Heskett -
Pisini, John