diff options
Diffstat (limited to '2022/talks/devel.md')
| -rw-r--r-- | 2022/talks/devel.md | 73 |
1 files changed, 73 insertions, 0 deletions
diff --git a/2022/talks/devel.md b/2022/talks/devel.md new file mode 100644 index 00000000..6ee016c9 --- /dev/null +++ b/2022/talks/devel.md @@ -0,0 +1,73 @@ +[[!meta title="Emacs development updates"]] +[[!meta copyright="Copyright © 2022 John Wiegley"]] +[[!inline pages="internal(2022/info/devel-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-generate-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Emacs development updates +John Wiegley + +[[!inline pages="internal(2022/info/devel-before)" raw="yes"]] + +What has been happening and what is soon to come in Emacs development + +Bio: John Wiegley is a past maintainer of Emacs and frequent contributor of Emacs Lisp. + +# Discussion + +## Questions and answers + +- Q: Any word on bringing someone like John W. back in in a maintainer + role? I think someone like him is good in that role and miss seeing + his messages as frequently! + - A: I very much appreciate the support! but now is not a good time. I have other + distractions that would detract from my ability to support the community + properly. +- Q: Does the user need to do anything to turn on support for long + lines? + - A: No! Just editing files with long lines should become much faster. + - Side note intersting vidoes about long lines + - <https://www.youtube.com/watch?v=5C3wB3xiMmU> Emacs Long + Lines Fix + - <https://www.youtube.com/watch?v=kflDJ9L4siw> Emacs Long + Lines, This Time With Feeling +- Q: Having emace init comand line option is nice" no more chemacs + for multiple emacs configs" and would make starter packs eaiser to + test, or makeing applications or scripts based off of emacs easier + to do. Is there anything else following this decection? + - A: I don't really follow this question well enough to have an answer! +- Q: The discussion during Howard's Eshell talk indicated demand for + enhancing Eshell and its documentation. For those of us interested + in pursuing that, where should we start? Should we explore moving it + from core into an independent package? + - A: Certainly new development could happen in an independent repository, with + releases delivered back to the Emacs repository. There are other packages that + also do this. +- Q: has any date been set for 29 release? + - someone else: I haven't seen dates on devel. The branch was just cut so I would expect it will be at least a few months. Could be longer as there are so many new features in 29 (tree-sitter, sql-lite, use-package to name a few I'm hyped for) + - someone else: Seems like a good release for dropping legacy and using all the new stuff everybody else is using. wayland, lsp, tree-sitter, better performance on long lines. + - A: I'm not aware of a specific date, but if you follow the emacs-devel list, updates are sometimes posted. +- Is tree-sitter useful if you want to parse all the code in an application or is it more narrow, i.e. just for interactive parsing of changing code? + - A: I imagine it's generally useful for parsing any sort of text that you want to + perform structural analysis on, whether in whole, in part or incrementally. I + recommend checking out the web documentation on the tree-sitter libraries. +Notes and other feedback: + +- XInput 2 support author here. X has historically seen three + input APIs: Core Input, legacy XInput, and XInput 2. Emacs only + ever used the first until Emacs 29, where it jumped straight to + using the last. So it's not quite an ``update'', but rather an + entirely new feature. Thanks for the great talk! + - A: Good to know, thank you for that clarification! + +- Thanks John! Thanks Eli! + +## Notes + +[[!inline pages="internal(2022/info/devel-after)" raw="yes"]] + +[[!inline pages="internal(2022/info/devel-nav)" raw="yes"]] + + |