blob: 250a8a95a0fdb55d6ba3320afb22c953f132fbb9 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
[[!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:
- Q: Does the user need to do anything to turn on support for long
lines?
- A:
- 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:
- 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:
- Q: Thanks John! Thanks Eli!
- A:
- Q: 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:
## Notes
[[!inline pages="internal(2022/info/devel-after)" raw="yes"]]
[[!inline pages="internal(2022/info/devel-nav)" raw="yes"]]
|
