Відео

Nice!

Great timing. I literally started searching for Emacs theme creation tutorials today.

Great video

This is awesome!

I would love that org-mode have an "easy" way to create cyclical task for everyday of the week excluding weekends. Something like: <2025-01-02 Tue 18:00-19:00 +1d{1 2 3 4 5}> So in that way I would be able to say that this task is for every day, but only the days 1,2,3,4,5 of the week. I don't know how to create a mode in emacs, neither how to extend an existent one such as org-mode. But Im learning lisp, then I will check some source code to have an idea to make experiments by myself, unfortunately that will take me long. I would love to find a resource to teach you all that step by step.

Audio levels are unbearably low

this is impressive work so fully featured!

Phenomenal.

I would love an guile emacs, except for the support for other languages than lisp to extend emacs, that would be horrible

Why the obsession for re writte all the open source apps with rust?

Wow its really nice that there's already a huge elisp test suite that can be used for a different core interpreter. Ack, I can't believe I've already starred the repo and haven't contributed anything to it. That'll be on my Jan 2025 goals list!

Hey, thanks for this talk I needed it!

Thanks for your work. Have a great day

Huh I have actually been struggling to learn the various ways to use a marked rectangle region. I think transient will be a great way to learn!

Turns out you can't really use at-symbol @ for defining Eshell commands - it gets confused (at least on the latest Emacs). I had to do it this way: (defun eshell/b* (buffer-or-name) "Return specified buffer as a string." (with-current-buffer buffer-or-name (buffer-string))) And then you can do: b* #<buffer *Messages*> | grep "^Warning" > #<buffer All_Warnings> Note how eshell-insert-buffer-name prepends it with #<buffer, unlike in the video, but that's not necessary, it works either way.

Many of Emacs' powerful features and commands are simply overlooked by users, or users are unaware of them altogether. And even the features one has learned but doesn't use daily tend to be forgotten. I completely agree with this. Casual shows users which features they can use and how, making it much easier to explore Emacs and addressing a fundamental problem. An excellent project! Please keep it going!

I think I know the name. Prepare for the big reveal: Schemacs! Maybe SchEmacs or Skemacs for a more obvious pronunciation) :) It looks like a really cool project. Nice work!

I'm so looking forward to this. How cool would it be to work with Guile inside Emacs the way we currently work with Elisp (manipulating a cursor, working with buffers, etc.)

I started trying to apply/use literate programming but I saw this video and I feel like a newborn. Wow! that was awesome 😎

The best reason I've heard explaining why most programmers don't (and won't) use literate programming. It requires them to be literate in *three* languages: the programming language, the markup language, and most challenging of all, English.

Awesome.

Congratulations! I'm super excited for the things to come, especially about mobile apps not being an afterthought anymore. Also looking forward to the transition to transient menus!

Thank you for this. Around 18:20, you say something that sounded like “para structure.” Is that the name for the approach of you’ve shared over the course of this talk?

Really interesting approach. I like the humility in the beginning, the likes of "this is to try new approaches".

Nice, this seems to do basically the same thing as C++ ranges, which I've enjoyed using a lot

Good

Phenomenal thinking. I will be reading the Nature of Polyexistentials

Literate programming is very appealing in theory, but it's difficult with languages like Go where your code is split across multiple files. Any suggestions?

Dude was cooking with this one 🔥🔥🔥🔥

Nice presentation!

Legend

Howard! Your videos have been such an amazing source of information. You voice is engrained in my brains haha

❤

Very impressive, thanks!

1:00 So Knuth invented literate programming in the 19th century? I knew he was old, but not that old!

thats novel and intersting . The ship wrek analogy was perfect too

Finally a perspective on a potential real excel killer.

When I was a student, I would take notes on paper. They would be messy. I would review, re-write, and organize my notes on paper. Then I would type them into the computer so I can print out nicely formatted notes. I did all this on a 16bit Atari ST and it blew my instructors mind in electronics school when I turned in my ring bound, printed notes for grading / review. I had drawn circuits and did all this desktop publishing work on it. It was very new at the time, only Macs, Atari, Commodore were doing this stuff at the time. Really wish I had today's Emacs back then. Even if I could have obtained a copy of Emacs it would have been lacking a GUI and Org-Mode and most of the popular packages. So today, is the best time to pick up Emacs because it is even more useful today than 40 years ago.

Great presentation! I've been using Casual since it arrived and have been very happy with it; it makes working with emacs much easier. I now also create transients for commands I use, neatly grouped in categories. Transients: life saver.

That is interesting, but there is too much emphasis on the little details. The best talk of this type was a five-minute introduction concentrating on the principles and the big picture. Without enough talk about the principles, one may end up trying to follow your method too literally. Because we are unique individuals there is difficulty of finding somebody else's method that will work for you the same as for the original author. Big picture and the principles will help to use yours and others ideas to be more creative and find a method that is a good fit in the current circumstances.

How is the duckdb more coming along?

Cool, great, amazing. Extremely ambitious. A clone like this project might be significant harder than for example Lem, which does not care about backward compatibility with Emacs. A clone also is somewhat harder to create a unique selling point for. Especially if Guile-Emacs is also going to be a thing now. Just my 2 cents up to discussions. Anyway I am excited and will follow it:)

This is great! Emacs's plethora of powerful functionality really needs a better way to surface itself to users and this is a great step in that dirrection. I do have a few thoughts, though: - Is there a convenient way for a user in a transient to get more information about a menu entries? Specifically: the normal keybindings (if available) and command documentation. - It could be useful to gather and display statistics about menu usage. Imagine being able to generate a personalized keybinding cheat sheet with the menu items you use the most!

11:28 This should have been a shell-command instead of an eshell-command.

Wow… thank you

is the voice generated by a software program?

Surprised you didn't mention "vterm" or "multi-vterm" especially if some shell commands have fancy ansi output. I have a question regarding command line argument passing with emacsclient. In my fish.config file create a function called "e' so I can just type e sometext.txt emacsclient -c "$argv[1]" # But I want this actually emacsclient -c -a "" --eval "(set-frame-size (selected-frame) 106 42)" "$argv[1]" so $ e sometext.txt #^That works but below doesn't work and I get an elisp message #If I use that emacsclient with --eval $ e sometext.txt #says "nil"... and I don't get emacsclient to open up with the text file I want. It is very annoying and I guess once you put --eval you can't do argument passing but #goes into an elisp mode I assume.

That was a great talk. Thank you for bringing all that information together and thank you for your work on org-mode. I use it every day and it's good to see it's still in active and constructive development. I particularly like the focus on the standard and parsers to define the format and clean up code bases both in org-mode and beyond.

0:20 I think of Emacs as an OS