balupton
commented
7 months ago From a quick look, I don't see any reason why they should be incompatible. They have quite different approaches which means they shouldn't interfere with each other. Dorothy's install process only makes a single line modification to the appropriate zsh/bash rc files; it's only symlink modification is ensuring its own XDG setup is done correctly. If you do you use both, you would have to decide if you want to place your commands inside Dorothy's user configuration or inside Dotly's. To be honest, I'm not sure what the advantage would be of Dotly over Dorothy, besides more github stars.
b9Joker108
Dear Benjamin and to whomsoever else it may concern
This issue is further to this closed issue:
https://github.com/bevry/dorothy/issues/214
and regarding another dotfile framework and ecosystem, Dotly:
https://github.com/CodelyTV/dotly
I just came across Dorothy again, researching dotfiles management solutions. I had also previously starred Dorothy in GitHub, but haven't recently reviewed my starred projects, which I do periodically. As I had issues with my prior attempt at installing Dorothy in Termux (as per Issue 214), I kind of lost my momentum with it and failed in sticking to it, to realise a solution. In essence, I got distracted doing and progressing other things. It seems like, in my Termux and my various shells, on my tablet, that I am always reactive and putting out spotfires. I feel a dotfiles management solution, will go some way to mitigate this.
I actually, missed your detailed response to my prior issue (214), now closed, and only just now read it. I noted that you had gone to some pains to iterate Dorothy, in response. I thank you so much for your endeavour and for your code. I also note, that you just had surgery and are convalescing. I wish you the best with that, in order to heal. I truly hope you aren't in pain and haven't been significantly or severely debilitated, as a result. Life, I have found, is a matter of constantly 'rolling with the punches', as they say.
Very recently, I installed the Dotly dotfiles framework and ecosystem on my Termux, and the process was initially, profoundly traumatic:
https://github.com/CodelyTV/dotly/discussions/268
But, I am retrofitting my pre-Termux environment and Zsh shell (and .zshrc), which is my principal daily driver, in my host Termux environment, with the new Dotly framework and ecosystem. The process of integrating Dotly, and adapting to it and getting it to adapt to me, has just begun, and I have much yet to successfully implement and realise, in order to get it to work as designed.
That said, I still wish to utilise the Dorothy dotfiles framework and ecosystem as well, and in addition to Dotly dotfiles framework and ecosystem, to get the best of both worlds, and adapt both Dorothy and Dotly, to my own particular workflow and usecase. I call upon your wisdom to assist me to progress the synthesis, and push-the-envelope, with their extensibility, from the Dorothy end.
I am documenting all my Termux and shell learnings and troubleshooting experiences, and my impetus and rationale, in a book I am writing, that I mentioned to you previously, to inform others, in acquiring shell scripting and to become adept at Termux, and unlock the power of Android-*NIX granularity and extensibility. That work may potentially yield a significant uptake of Dorothy and extend the community. You have had significant recent difficulties and challenges, and no doubt, many other projects and occupations, since my initial issue and correspondence to your GitHub Dorothy project repository, that you most probably, do not remember, about my shell scripting project, and have had other things on your mind, due to your health.
When you have time, I would really appreciate your wisdom and input, if Dorothy could be effectively integrated with my Dotly installation in Termux. Not just for me personally, but also for the audience of my book and its project auspice. I appreciate in so doing, that the Dorothy/Dotly hybridisation, is something new, and potentially 'its own beast', and an impossibility for you to most probably visualise and pre-empt all the possible moving parts and complexities that may result. But, I would still really appreciate your wisdom and input, and to ascertain whether such an integration and hybridisation is possible or feasible, or even desirable or valuable.
I anticipate a significant part of this hybridisation is whether symlinks can be symlinked. Which, I do not know. As both Dorothy and Dotly, use symlinks to significant effect, to realise their dotfiles management system, framework and ecosystem. I am sure, too, there are many other factors and contingencies, that I am not aware of.
I really value the Dorothy project, because it is NIX shell agnostic, and natively supports a significant number of shells, out-of-the-box; whereas Dotly, initially, only supports two, Bash and Zsh, though Dotly is of course customisable and extensible. My written work, is initially only focusing on POSIX shell compliance, and the Bash and Zsh shell dialects, extensions and their extensibilities, and all of their shell scripting protocols and best-practices. But, anticipate extending the work to extensively cover as many NIX shells as possible that are installable natively in Termux, or in the PRoot-distro alias guest installations of GNU/Linux distributions, in Termux on Android: I currently regularly drive Debian, Arch, Ubuntu, Parrot and Kali Nethunter Rootless, each with a number of different users, all with a number of different shells. The complexity is profound. In future, I am working towards automatic synchronisation of the dotfiles ecosystems on all these different user accounts and their different shells. I don't even know if this is possible, but I feel it exciting to try. This setup and automation would be invaluable, for a number of reasons and use-cases.
In due course, I patiently anticipate your due consideration, and considered response. There is no rush.
Thanking you in anticipation Beauford
P. S. Have you considered enabling the 'Discussions' (and 'Wiki') functionality in the Dorothy GitHub repository? I feel they would offer significant value and enrichment, for the Dorothy community, and may allow you to focus on other things.