Nov 13, 2022, 18:46 by johnw@gnu.org: >>>>>> "Edd" == Emacs development discussions <xenodasein---> writes: >>>>>> > > Edd> How integrated is it with custom, package, etc? > > This is exactly the kind of thinking I was hoping for in suggestion the move > to core. Yes, yes and yes! Integration, documentation, the ability for users > to resolve their own issues (for example, making macro expansion easier to do > for use-package), these do need more thought and care. > > -- > John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F > http://newartisans.com> 60E1 46C4 BD1A 7AC1 4BA2 > Using package.el and custom through their interfaces currently provides the Emacs soft-entry into using packages from outside, use-package provides yet another alternative in between them and manually doing everything. My understanding is that most people would actually prefer solving this without tinkering in init.el but they find custom interface inadequate so they go for the next alternative which is use-package. I think we can bridge that gap somehow. OTOH, use-package also works great for people who'd like to set things through code, like how JW uses it in their config on GH; for that way of doing things it is in much better shape IMO, stable if you will. Eli: You said this can be fixed, of course but wouldn't it be much easier to do without fighting backwards compatibility issues of core code?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4