{"id":4151,"date":"2020-12-02T11:29:32","date_gmt":"2020-12-02T17:29:32","guid":{"rendered":"https:\/\/www.logikalsolutions.com\/wordpress\/?p=4151"},"modified":"2023-11-27T18:23:27","modified_gmt":"2023-11-28T00:23:27","slug":"diamond-editor-pull-request","status":"publish","type":"post","link":"https:\/\/www.logikalsolutions.com\/wordpress\/information-technology\/diamond-editor-pull-request\/","title":{"rendered":"CopperSpice Experiments – Pt. 18 – The Pull Request"},"content":{"rendered":"\n

It has been a very long time coming, life kept getting in the way here, but my Diamond editor changes are ready for pull. For those who don’t give a rat’s behind about the pull request, here are the new packages. These are not official<\/strong>. I have tested these Diamond editor packages in bare installs of said operating systems. For Ubuntu installs you need to use the Software Installer, not dpkg from the command line because dpkg won’t install dependencies.<\/p>\n\n\n\n

Note:<\/strong> I don’t remember if I fixed it or not. If you have an existing diamond config, sometimes the only theme you get is the one you had. Just rename your config file before installing. There aren’t that many settings.<\/p>\n\n\n\n

Packages<\/h3>\n\n\n

Diamond for Ubuntu 18.04 LTS<\/a><\/div><\/div>
604<\/span> Downloads<\/span><\/div><\/p>\n\n\n

Diamond for Ubuntu 20.04 LTS<\/a><\/div><\/div>
578<\/span> Downloads<\/span><\/div><\/p>\n\n\n

Diamond for Fedora 33<\/a><\/div><\/div>
639<\/span> Downloads<\/span><\/div><\/p>\n\n\n\n

Package Creation<\/h3>\n\n\n\n

Yes, we now have both RPM and Debian creation.<\/p>\n\n\n\n

\"shell
Shell scripts<\/figcaption><\/figure>\n\n\n\n

build-diamond-deb.sh checks for a Debian based distro then does everything necessary for a full build of source to create a Debian package. One of the things it does up front is run Artistic Style on the src directory.<\/p>\n\n\n\n

\"artistic
Artistic Style control file<\/figcaption><\/figure>\n\n\n\n

When the shell scripts run they use this configuration file. The same configuration file is run when you choose to execute Astyle from within Diamond if you are editing in the src (or any sub-directory.) The Artistic Style command looks first in your local directory then in the project root and I forget where else. <\/p>\n\n\n\n

If multiple developers will work in a code base a method of enforcing common style so things are readable is needed. Artistic Style works well in most of the shops I’m at.<\/p>\n\n\n\n

The astyle-diamond.sh is really just a helper.<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
#!\/bin\/sh<\/span><\/span>\n#<\/span><\/span>\nastyle<\/span> <\/span>-n<\/span> <\/span>src\/<\/span>*<\/span>.cpp<\/span> <\/span>src\/<\/span>*<\/span>.h<\/span><\/span>\n#<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
build-diamond-rpm.sh does the same thing for RPM creation. It checks for a RedHat based distro and checks to ensure rpmdevtools has been installed.<\/p>\n\n\n\n
Both packaging scripts dump the diamond tree into \/opt\/diamond. The .desktop file is copied to the appropriate location and a symbolic link is created in the appropriate directory so one can type diamond at the command line and have it run no matter what directory the user is in.<\/p>\n\n\n\n
The third digit of a release really should no longer be allowed to be a zero. It has to do with RPM packaging viewing that as the “build number.” Most counting systems don’t start at zero.<\/p>\n\n\n\n
Summary of changes<\/h3>\n\n\n\n
The summary at this post<\/a> is still pretty accurate. Life has just been in the way and I have been focused on getting the packing done. Probably best to install one of the packages to kick the tires.<\/p>\n\n\n\n
For “Why EDT?” Read this post<\/a>.<\/p>\n\n\n\n
For “Why Themes?” Read this post<\/a>. If you don’t want to read the entire post I will include the ending paragraph here.<\/p>\n\n\n\n
\n
Do you know why Betty Crocker cake mix crushed the competition despite there being dozens of other brands on the shelf?<\/p>\n<\/blockquote>\n\n\n\n
\n
This was the days when women actually called themselves a \u201cHouse Wife\u201d and were proud of it. All of those other cake mixes were \u201cinstant.\u201d You just added water and put them in the oven. With Betty Crocker you added an egg. Adding an egg crossed the psychological barrier and the conscientious house wife could honestly say \u201cYes, I baked it myself.\u201d Adding an egg made it not instant and therefore okay. Instant is what the bad wives did and you would never find them featured in Good Housekeeping.<\/p>\n<\/blockquote>\n\n\n\n
\n
Putting in place the groundwork for community themes is the text editor equivalent of \u201cadding an egg.\u201d Allowing users to create plug-ins is the text editor equivalent of allowing too many cooks into the kitchen. That\u2019s a condition Emacs suffers quite badly from now. Most of the plug-ins conflict horribly or cause random oddities in unrelated plug-ins. With every plug-in you install it is like tap dancing in a mine field.<\/p>\n<\/blockquote>\n\n\n\n
Some of the other things off the top of my head:<\/h3>\n\n\n\n