(I am finally at the bottom of my "NEXT" list, and got to reply to this email)
Moakt Temporary Email <[email protected]> writes: >> > Instead of everyone doing the same tasks again and again, we can all >> > do it once for all (of course with the required maintenance). There >> > is a lot of gain here for everyone. >> >> Maintenance is the main problem. What you propose, IMHO, is not going to >> be easy to maintain. > > It again depends on what you mean by “not easy”. We all already do the more > or less the same maintenance tasks in our individual configurations. So > again, doing so in one place is beneficial for everyone. Other maintenance > tasks are normal part of any similar project. > > > Are you planning to start this project ? Or you are just giving an opinion on > that ? No, I do not plan to start this project. Just an opinion (since you wrote to the list). >> >> Instead, >> >> you may build the overall configuration from pieces contributed by >> >> selected specialized configuration. >> > >> > What do you mean exactly ? >> >> Rather than having a single huge configuration file, construct it from >> multiple contributed per-package/topic configurations. > > Can you be more precise on how do you exactly imagine it ? I was referring to something akin > I already mentioned in my first message that each package should be separated > in its own org file. We can > also imagine that users may choose what packages/files to use if they want to. But not for individual packages, rather for package groups. For example, consider configuration for python development. It will require certain packages (eglot, pyvenv, or similar). But individual package configurations may not be enough - one may need to fine-tune inter-operation of multiple packages. That would require some more general configuration. >> > [ I also wanted to send a proposal to implement the tag filtering in org, >> > but >> > I also don’t have time to do so. Did you get the idea ? Is it something >> > you >> > can consider implementing in org ? ] >> >> What exactly are you proposing? > > Very briefly, I imagine a command that insert an org link (filter) for each > tag, at the top of the file for example. > > Clicking on link1/filter1 will call sparse tree on tag1, and in the same time > hide the other links/filters whose tags belong exclusively to the hidden > headings. Clicking on filter1 again for example, will do the reverse steps. > Clicking on filter1 and filter2, will call sparse tree on tag1 and tag2, etc. > > We can also image adding links/filters for properties too, etc. > > This is a know filtering mechanism. It needs to be adapted to org files. > > If the idea is still not clear, I can explain it in a dedicated message when > I have time. Currently, clicking on a tag does something a bit similar - call agenda view for a set of tags in the corresponding heading. I guess something similar can be done for tags listed in #+TAGS: keyword > This being said, what I am proposing here is something different, and I hope > it can have the good amount of energy to push it forward, because it combines > all the possible advantages of all the customization methods, while > eliminating most controversial problems. (Again it is for current and future > org users, though it requires very little org knowledge if any to use it. > And if we add buttons, it can even almost becomes a UI). > > It should be easy to extend it by adding packages, options, choices, etc once > the very basic foundation is there. > > It can also have a huge impact on new users starting with Emacs, like easily > and quickly customizing Emacs, and also easily and gradually learning Emacs > Lisp, etc. Maybe. But to push it successfully, you need to offer people something usable to try. Not just a toy example, but a working configuration. For example, complete configuration suite for some programming language setup. (That's what newbies and even experienced users are often looking for) -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
