tde-devels

devels@trinitydesktop.org

1 participants
3754 discussions

Re: [trinity-devel] Kate/Kwrite will not allow any editing of a file deemed to be a binary file

by Darrell Anderson

>When that happens to me I click on "tools" and click on "read only >mode" to remove the check mark. I can edit fine after that. Ah! Thank you. Always something new to learn! :-) Darrell

11 years, 9 months

Kate/Kwrite will not allow any editing of a file deemed to be a binary file

by Darrell Anderson

Hopefully there is a configuration cure to avoid a bug report. Any file that is opened in kate or kwrite resulting in the infamous warning dialog that the file is binary and editing will result in a corrupt file, renders both text editors into a non-editing mode. For example, create a diff file using "diff -urNa" where there are file additions or removals in the target directory. Open the diff file in kate or kwrite. The infamous warning dialog appears and editing thereafter is impossible. Also disabled is searching and seatch-and-replace. Bug or configuration problem? Darrell

11 years, 9 months

Best GIT way to remove multiple files and directories

by Darrell Anderson

I want to close bug report 1344. I need to remove duplicate files and directories. I know which files and directories to delete, but I'm uncertain about the best GIT way to do this. (Doing this outside of GIT is easy. :-) ) Fortunately there are only 9 modules affected, but the number of files and directories to delete varies in each module. Thanks! :-) Darrell

11 years, 9 months

Interesting TED video

by Darrell Anderson

I found the following TED video interesting with respect to software project management: http://www.linux.com/news/featured-blogs/185-jennifer-cloer/715856- jim-zemlin-at-tedx-what-weve-learned-from-linus-torvalds The video is only 18 minutes. Darrell

11 years, 9 months

Re: [trinity-devel] OnlyShowIn vs. NotShowIn

by Darrell Anderson

>Who upstream is making this problematic? Is this a Debian-only >issue? Is this only a packaging issue? Please explain more. What >exactly is needed to provide remedy? > >Trinity is recognized as an XDG desktop. Upstream, whoever they >might be, need to get on board. I doubt "upstream" has failed to >support other XDG recognized desktops. TDE != KDE. :) > >I created a tdelibs patch and am rebuilding now. I'll start >testing thereafter. I updated the patch by adding a -DWITH_OLD_XDG_STD configure option works great. No KDE4 apps autostart, no problems with desktop files in ~/.local/share/applications or $TDEDIRS. Should upstream problems continue then this patch seems like a fair compromise until those problems disappear. I have not tested by building tdelibs with -DWITH_OLD_XDG_STD, which retains the current dual behavior. Darrell

11 years, 9 months

Re: [trinity-devel] OnlyShowIn vs. NotShowIn

by Darrell Anderson

>We would need upstream acceptance of TDE in affected projects for >this to be viable. If this is not done, then users will notice a degraded >experience when basic programs such as Synaptic cease to function >properly. These users would then note that such applications work >properly under KDE, and logically conclude that TDE is broken. > >I think this is a lesser of two evils problem, and would like to >keep the dual test in at this point. > >Thoughts from others knowledgeable in this area? This should not be about lesser evils. Ugly approach! :) Who upstream is making this problematic? Is this a Debian-only issue? Is this only a packaging issue? Please explain more. What exactly is needed to provide remedy? Trinity is recognized as an XDG desktop. Upstream, whoever they might be, need to get on board. I doubt "upstream" has failed to support other XDG recognized desktops. TDE != KDE. :) I created a tdelibs patch and am rebuilding now. I'll start testing thereafter. Darrell

11 years, 9 months

Re: [trinity-devel] OnlyShowIn vs. NotShowIn

by Darrell Anderson

>This was on purpose to allow improperly coded KDE applications to >show up, for instance synaptic will not work otherwise as it uses >OnlyShowIn=KDE. The problem is identified in bug report 1364. I understand how this dual test was added after 3.5.10, when TDE was still considered KDE. Now that TDE is a recognized standalone XDG desktop, the dual testing for both TDE and KDE should be removed in R14.0.0. I don't know that the change should be backported to 3.5.13.x, but the change is needed in R14.0.0. Darrell

11 years, 9 months

OnlyShowIn vs. NotShowIn

by Darrell Anderson

Along with Trinity I have KDE4 installed, mostly for testing and comparisons. When I use OnlyShowIn=KDE; in a desktop file, the item still appears in the Trinity launcher menu. When I use NotShowIn=TDE; the item disappears. The former option should work just as well as the latter. Can anybody else confirm this bahavior? Second, is this a bug with Trinity? Thanks. Darrell

11 years, 9 months

Nightly builds update

by Timothy Pearson

All, Please be advised that the nightly builds repository will be in an inconsistent state for the next few days as the entire archive is rebuilt following recent changes to the common build system files. As a result, the nightly builds may crash or fail to operate properly until the rebuild is complete. Therefore, users of the nightly builds are encouraged to hold off on applying updates for the next few days. Thanks! Tim

11 years, 9 months

Testing apps for R14.0.0 release

by Darrell Anderson

Hi folks, A request to everybody involved to start spot-testing apps. Not the apps you use everyday but the less-used apps. Make sure they open without errors --- starting from konsole is good for that. Spot test that nothing unusual happens with configuration dialogs, etc. We are starting to look pretty good as we move toward an R14.0.0 release. Spot testing apps will help avoid embarassments. :) Thanks! :) Darrell

11 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels