summaryrefslogblamecommitdiffstats
path: root/2023/talks/emacsen.md
blob: d1b7cc7e37194e5767c432cb785ad54a2de8e158 (plain) (tree)
1
2
3
4
5
6
7
8
9
10
11
12
13











                                                                                                    





                                                                                                                                                                                                                           





                                                                      


                                                                   
 










                                                                         
                                                                     






                                                                      
                                                                   












                                                                         



                                                               
[[!meta title="The Emacsen family, the design of an Emacs and the importance of Lisp"]]
[[!meta copyright="Copyright © 2023 Fermin"]]
[[!inline pages="internal(2023/info/emacsen-nav)" raw="yes"]]

<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
<!-- You can manually edit this file to update the abstract, add links, etc. --->


# The Emacsen family, the design of an Emacs and the importance of Lisp
Fermin (he/him) - <https://codeberg.org/sasanidas>

[[!inline pages="internal(2023/info/emacsen-before)" raw="yes"]]

[[!template id="help"
volunteer=""
summary="Q&A could be indexed with chapter markers"
tags="help_with_chapter_markers"
message="""The Q&A session for this talk does not have chapter markers yet.
Would you like to help? See [[help_with_chapter_markers]] for more details. You can use the vidid="emacsen-qanda" if adding the markers to this wiki page, or e-mail your chapter notes to <emacsconf-submit@gnu.org>."""]]

This talk is about the design of an Emacs the Emacsen editors, GNU
Emacs, Emacs Lisp and the extensibility of GNU Emacs (and Lem as an
example of Common Lisp). I want to focus the talk about the understand
of the concept of Emacs but with concrete examples (GNU Emacs and
Lem), also highlight some historical Emacsen and how the family of
editors is doing today.

About the speaker:

I'm Fermin MF, I'm a Software Engineer from Spain with interest in 
Emacsy editors.

# Discussion

## Questions and answers

-   Q: How large is the LEM community? How big is the chance of it
    surviving long term?
    -   A:
-   Q:Are there any Lisp machine capabilities you are trying to revive
    that GNU Emacs lacks?  The typed objects capability in the editor as
    an example.
    -   A:
-   Q: What about using Lem for things other than coding common lisp,
    dired magit "notes org mode dentoe org roam" emms pdf tools shell
    mode?
    -   A:
-   Q:What about using this in conjunction with Nyxt the common lisp;
    web browser
    -   A:
-   Q: What is the license of LEM?
    -   A:
-   Q: Big question, I realize, but: How far is LEM from being able to
    run Elisp libraries, e.g. imagine if Magit could "just work" in
    LEM?
    -   A:
-   Q: How are LEM buffers designed? Similar to Emacs? TextGrid with
    Properties? Or something other? I just tried again to give Emacs
    more interactivity & am thinking if there is a possible display
    future for the Emacsen.
-   Q: What are the things or experances that lem gives you that are
    nicer than Emacs? or make you happy using both?
    -   A:
-   Q: (Forgive me if you answered this already.)  Do you think Lem will
    continue to have a lot of Japanese documentation, or is there a
    chance it will move entirely to English?  (IMHO having much of the
    docs in Japanese will hold back the project.)
    -   A: 

[[!inline pages="internal(2023/info/emacsen-after)" raw="yes"]]

[[!inline pages="internal(2023/info/emacsen-nav)" raw="yes"]]