On Mon, 11 Jul 2022 at 08:53, H <[email protected]> wrote: > > On 07/05/2022 09:40 PM, H wrote: > > On 07/05/2022 08:47 PM, Lex Trotman wrote: > >>> Thank you. It sounds like an interesting feature that is being added. The > >>> latest release seems to be 1.38 - although 1.36 is the latest available > >>> for CentOS 7/RHEL 7 - so this would be forthcoming in 1.39, or? > >> Saving more often is in 1.38, splitting prefs and session will be in > >> 1.39 (unscheduled). > >> > >>> Apart from this new feature, it would certainly be nice to get an update > >>> of Geany for CentOS/RHEL 7... > >> The Geany project does not make packages, you need to ask the distros. > >> > >>> Reading through your comments, it seems that I should rethink how I > >>> organize "projects". I have different types of projects, some of which > >>> fit nicely into the Geany paradigm where I can create a project and then > >>> add various subdirectories to it. > >>> > >>> Other "projects" of mine consist of different types of files, eg .md, > >>> .doc, .sql, .sh, .R etc., which I have hitherto organized more along the > >>> lines of various types of binaries etc, documentation etc. separated as > >>> to "category" of files. May not be the best method for organizing > >>> though... > >>> > >>> Perhaps I should rethink this and simply create "projects" collecting the > >>> different types of files belonging together in various project > >>> subdirectories, or multiple subdirectories under a project subdirectory. > >> Remember Geany does not dictate this, it can handle files scattered > >> everywhere, but plugins do need to have a more constrained view, and > >> "under one directory" is the paradigm they have chosen (IIUC, I don't > >> use those plugins). > >> > >>> The reason I have used the former organization is that I can then keep > >>> the binaries in ~/home/bin which is in the path. If I were to reorganize, > >>> I would lose that - if I don't add all the new binary directories to the > >>> path... > >> I don't know about your projects, but in conventional build workflows > >> (cmake, meson, autotools) it is the job of the "install" step to put > >> binaries in the path. Install is usually a separate step since if it > >> is installing to system directories it needs to be executed with > >> privileges, although thats not a problem for you installing to ~. > >> > >> Cheers > >> Lex > >> > >>> Thoughts appreciated! > >>> > >>> _______________________________________________ > >>> Users mailing list -- [email protected] > >>> To unsubscribe send an email to [email protected] > >> _______________________________________________ > >> Users mailing list -- [email protected] > >> To unsubscribe send an email to [email protected] > > Yes, I am aware I need to ask the distro to update geany and will do so. > > > > I think I should reorganize my "projects" so that they fit better with the > > Geany plugin paradigm. Should make it easier to add using git versioning as > > well. > > > > Most of my "projects" are not "programming" project but consist of various > > types of files that belong together. The binaries are most often shell > > files and I can certainly copy them to ~/bin as needed to be run from there > > (as I said, I added ~/bin to the path a long time ago.) When not added I > > can open a terminal window in the appropriate project subdirectory and run > > them from there. > > > > Thank you for your guidance. > > > > _______________________________________________ > > Users mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > The maintainer of Geany for EPEL states that 1.38 cannot be compiled for > EPEL7 but has not shared the reason. Version 1.37, however, is now in the > EPEL7-testing repository.
Possibly because 1.38 needs some of C++17 but the default 7 compiler is gcc 4.8 IGUC (if google understands correctly). You could try compiling Geany yourself and see if the compiler has enough C++17 working to do it, it doesn't use much of C++17. Or install an upgraded compiler, IGUC there are newer toolsets available for Centos, then compile Geany. See https://github.com/geany/geany/pull/1690/commits/8c0d06378b75bc367e7110ca5f4b6a946e127eef for simple build options (sadly the whole point of that PR was destroyed by the trolls so it never got merged). Cheers Lex > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected]
