I submitted a patch to bug report 388 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=388). The patch restores the visibility of the kdesu "Keep password" check box. In TDE, the check box is hard-coded invisible rather than being a function of the kdesu -t parameter as in 3.5.10.
The patch (kdebase/kdesu/kdesu/kdesu.cpp):
================================================
// Try to exec the command with kdesud.
bool keep = !args->isSet("n") && have_daemon;
- bool terminal = true;
+ bool terminal = args->isSet("t");
bool new_dcop = args->isSet("newdcop");
bool withIgnoreButton = args->isSet("ignorebutton");
================================================
Although I suspect many will welcome the patch, there likely will be just as many who will fear being eaten in the dark by grues if this check box is visible.
I dislike the idea of those who want this check box visible to have to always patch the TDE sources in their build scripts.
Is there a way to test who wants this check box visible and those who don't so no build-time patching is required and everybody is happy?
I think the 'buntu family of distros don't use kdesu and instead use kdesudo. Perhaps this patch does not affect those distros. If that is the case then the discussion falls on everybody else.
Ideas?
Darrell
I'm in shock folks. Really. Yet I'm smiling from ear to ear and giggling like a little kid.
Last week when I was looking in the old KDE SVN for the original patches to Kate --- to restore the ability to specify the number of files to list in the Most Recently Used (MRU) list, I decided to look for the patches that ripped the Konqueror web link context menu.
Long, long ago, in KDE 3.1.3, the web link context menu contained two options: Open in Background Tab and Open in New Tab. The latter option opened links in Tabs in the foreground. Like this:
Open in Background Tab
Open in New Tab
In 3.1.4 the former menu option was ripped from the context menu, much to the dislike of many people. The same function could be achieved by using the Shift key to toggle the function of the Konqueror setting, but that idea never sat well with me. Or others.
Some time back I filed an enhancement request to restore that feature in bug report 245 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=245).
I use that double option all the time in the Firefox context menu, enabled through the TabMix Plus plugin (other plugins provide that feature too). I can't predict when I want a link to open in the foreground or background. That decision depends upon what I am reading. I was using that type of double menu option in Opera (version 5? 6?) before Firefox was born as Phoenix. Opera still supports both menu options as do other web browsers.
Yeah, I'm quite accustomed to those two menu options. Both make sense to me. Pressing the Shift key does not.
I found the original Konqueror patches that removed those options. That developer steadfastly refused to restore the options despite many complaints. Classic KDE developer egotism. At least that developer did not name the patch "useless crap."
Much like my Kate effort last week, with a little trial and effort I succeeded in restoring the old context menu. And the two options just plain work as intended.
Two for two. Not quite the same as hitting two home runs in a single baseball game, but I'm feeling mighty doggone good right now. :)
Woo-hoo!
Darrell
P.S.
I suspect there might be some people who do not want this patch and prefer the current behavior. I've uploaded the patch in the bug report. I hope an overwhelming number of people rejoice and the patch gets merged into R14. :)
I would be grateful if somebody would share any scripts to convert KDE3 code to TDE. Basically something that quickly adds the tqt layer.
Thanks.
Darrell
Do we have a check list to help developers/packagers watch for QA problems with packages? I have not seen any. How about we start one?
1. Check two apps in each menu category of the T-Menu to verify the Help file handbook is available.
2. Run a system test looking for broken sym links. (I use a short script I can share.)
3. Do all apps in the T-Menu start?
4. Check the xsession logs for unexpected or unusual errors and messages.
5. Do kdesu/kdesudo work as expected for your distro?
This is just for starters. Please add to this list.
Darrell
I am trying to run Trinity's KDevelop with KDE 4's KDevelop. Trying to
install from the Trinity repo's is giving me a file is attempting to
overwrite another file. Anyway I can run both of these on the same
system?
--
Bro. Michael Henry
Associate Pastor
Monticello Christian Church
Be kinder than necessary. Everyone you meet is fighting some kind of battle.
You never know when a moment and a few sincere words can have an
impact on a life for a life
Some of my gmail messages are being archived (removed from my inbox but not being deleted) when Kmail checks my gmail account. This only happens when Kmail does it's check, and none of the emails that are being archived are showing up because they aren't in any of my IMAP folders.
I know the archived messages are still there because I can log into gmail's web interface, go to my "All Mail" list, and see the archived messages. When I move them back to my inbox, they will stay there so long as Kmail isn't checking for email.
There is no setting in gmail's settings (either Kmail or the web interface) to do this, nor do they offer any filters that would do this (or at least, I don't have any such filters active in my gmail).
I have checked my IMAP settings in Kmail and gmail web interface. I cannot find any settings that would exhibit this behavior. I do include my inbox (and all the other IMAP folders) in both my serverside and local subscription.
The last detail I can offer is that I'm using cachedimap instead of regular imap.
Is there anything outside of my gmail/IMAP settings that could be causing this?
--
Kristopher Gamrat
Ark Linux webmaster
http://www.arklinux.org/
In my patched startkde script (bug report 675) I include code to automatically migrate a user's existing KDE3 profile directory.
I'm thinking perhaps I move that code to a separate script, say $PREFIX/bin/migratekde3, and source that script in startkde.
That would allow admins and users to run the script as they please and separate maintenance for us. By moving to a separate script we all can test more easily and improve that script without directly impacting startkde. As a separate script testing could be performed in any desktop environment and not just TDE.
Opinions? Yays? Nays?
Darrell
Le mer. 30 nov. 2011 02:06 HNEC, Dr Tony Young a écrit :
>On Wednesday 30 November 2011 09:37:00 ds ds wrote:
>> Is there a build script for Opensuse somewhere ? Even at a work-in-progress
>> state ?
>
>I am assured that there is. :-) It is definitely in progress and I am looking forward to testing
>it.
>Tony
Ok. Where is the web page ?
Dsant
The little things tend to make a difference in our lives. Long ago in this galaxy, a KDE developer decided that being able to specify the number of files in Kate's Most Recently Used (MRU) file list, and to sort the files in the Documents file pane, was "useless crap."
To me those features never were "useless crap." I have missed those features for a long time.
I found the patches where those features were removed.
I am not a C++ coder, not even close. Yet I was able to reverse the patches and add a little "TQT" love.
By golly, the widgets actually appear in Kate! Once again I can set the size of the MRU list to something greater than 10 and sort the file list.
Current Kate 3.5.13 picture:
http://humanreadable.nfshost.com/images/kate-before.png
Patched Kate picture:
http://humanreadable.nfshost.com/images/kate-after.png
The number widget works great. I think some of you will love that restored feature.
Took me a while to realize the sorting option affects the files in the Documents list pane and not in the MRU list. :)
I uploaded the patch to bug report 244.
Woo-hoo! :)
Darrell
