[cdesktopenv-devel] What hardcoded paths need to be removed?

2020-10-25 Thread Zeke Williams
I am willing to help out with removing all hardcoded paths in CDE. What is left to be removed? If I could have a full list of all hardcoded paths that need to be removed or changed so this ticket here https://sourceforge.net/p/cdesktopenv/tickets/60/ here is resolved, that would be a huge help for

[cdesktopenv-devel] I want to help with porting to GNU autotools but don't know where to start

2021-03-26 Thread Zeke Williams
How should I start helping with porting to GNU autotools on the autotools branch so imake can be removed and CDE installs in proper directories rather than under /usr/dt. Should I just delete the current imake files and make a fresh autoconf setup by scratch? Or what should I do? __

Re: [cdesktopenv-devel] I want to help with porting to GNU autotools but don't know where to start

2021-03-26 Thread Zeke Williams
make everything fair for everyone. On Fri, Mar 26, 2021 at 1:04 PM Jon Trulson wrote: > On 3/26/21 7:08 AM, Zeke Williams wrote: > > How should I start helping with porting to GNU autotools on the autotools > branch so imake can be removed and CDE installs in proper directories > rathe

[cdesktopenv-devel] Why do we require ksh93 to compile CDE?

2021-03-26 Thread Zeke Williams
I already have ksh installed under /bin in my distro. I had to download from github ksh93 because the sourceforge git didn't come with it and the patch as part of compilation failed to apply to be able to compile it and resulted with an error. Is there anything mandatory that ksh93 does for CDE? Ca

Re: [cdesktopenv-devel] Why do we require ksh93 to compile CDE?

2021-03-26 Thread Zeke Williams
hecked out sources > > We build ksh93 as a part of dtksh... > > And yes, I would love to get rid of the requirement to have ksh installed > in order to build CDE itself, but we will always need to build our own for > dtksh. > > -jon > > > > On 3/26/21 11:58 AM, Zeke

Re: [cdesktopenv-devel] Why do we require ksh93 to compile CDE?

2021-03-26 Thread Zeke Williams
it something else so it can co-exist with the OS version of ksh93. Just a thought I had. On Fri, Mar 26, 2021 at 3:44 PM Marcin Cieslak wrote: > On Fri, 26 Mar 2021, Zeke Williams wrote: > > > Can we remove it and just have the already installed ksh do the work > > instead? &g

Re: [cdesktopenv-devel] Why do we require ksh93 to compile CDE?

2021-03-27 Thread Zeke Williams
What is your opinion, Jon, on the shell and sed scripts Edmond posted hours ago? You think this will help out a lot? On Sat, Mar 27, 2021 at 1:45 PM Jon Trulson wrote: > On 3/27/21 11:31 AM, Jon Trulson wrote: > > On 3/27/21 11:07 AM, Zeke Williams wrote: > > > If someone co

Re: [cdesktopenv-devel] Why do we require ksh93 to compile CDE?

2021-03-27 Thread Zeke Williams
Pandoc can convert to many different formats. Perhaps conversion to html with the scripts and then conversion to a desired format with pandoc could be a possibility. https://pandoc.org/ On Sat, Mar 27, 2021, 9:20 PM Jon Trulson wrote: > On 3/27/21 5:25 PM, Zeke Williams wrote: > > Wha

[cdesktopenv-devel] Is ICCCM and Extended Window Manager Hints compliance going to happen?

2021-03-28 Thread Zeke Williams
One tiny thing that bugs me about CDE is not full ICCCM and EWMH compliance that sometimes makes windows act funky compared to other WM/DEs. I'm still pretty new to the project, but are you guys going to make it fully compliant after the autotools branch gets merged and everything else gets cleaned

[cdesktopenv-devel] What is next on the agenda?

2021-07-28 Thread Zeke Williams
Great to see that there has been a new release recently and the move to autotools is complete. What's next on the agenda for CDE? Fixing those known major exploits that are still lingering? Transferring all the help files to HTML? ___ cdesktopenv-devel ma