From 532bc5cda6dc0f094e9adcfdadfdc7bf435779f0 Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Thu, 2 Dec 2021 00:30:50 -0500 Subject: Add day 1 IRC notes --- 2021/talks/babel.md | 25 +++++++++++++++++++++---- 2021/talks/cs.md | 15 ++++++++++++++- 2021/talks/day1-close.md | 11 +++++++++++ 2021/talks/day2-close.md | 2 -- 2021/talks/design.md | 27 +++++++++++++++++++++++++-- 2021/talks/dev-update.md | 13 +++++++++++++ 2021/talks/erg.md | 3 +++ 2021/talks/exec.md | 13 ++++++++++++- 2021/talks/freedom.md | 18 ++++++++++++++++++ 2021/talks/gregorian.md | 3 +++ 2021/talks/invoice.md | 6 ++++++ 2021/talks/janitor.md | 22 ++++++++++++++++++++++ 2021/talks/molecular.md | 7 +++++++ 2021/talks/montessori.md | 7 +++++-- 2021/talks/nangulator.md | 11 +++++++++++ 2021/talks/nyxt.md | 14 +++++++++++++- 2021/talks/omegat.md | 4 ++++ 2021/talks/org-outside.md | 24 ++++++++++++++++++++++-- 2021/talks/pattern.md | 6 ++++++ 2021/talks/professional.md | 14 ++++++++++++-- 2021/talks/project.md | 13 +++++++++---- 2021/talks/research.md | 6 ++++++ 2021/talks/teach.md | 8 ++++++-- 2021/talks/tech.md | 11 +++++++++-- 2021/talks/telega.md | 4 ++++ 25 files changed, 262 insertions(+), 25 deletions(-) (limited to '2021/talks') diff --git a/2021/talks/babel.md b/2021/talks/babel.md index 7f81b7ad..8a26dd0a 100644 --- a/2021/talks/babel.md +++ b/2021/talks/babel.md @@ -7,8 +7,6 @@ # Babel for academics Asilata Bapat - - [[!inline pages="internal(2021/info/babel-schedule)" raw="yes"]] Plain org-mode is already an extremely powerful and @@ -47,12 +45,31 @@ I will try to showcase features of babel that academics could find helpful, by presenting some ways in which I have tried to use babel. I would also like to be inspired by other people's babel workflows! -## Links +# Links - Course webpage: - Code: - Code (gitlab mirror): -## Speaker information +# Discussion + +IRC nick: asilata + +- the export-setup block is a great use case for orgstrap :) + - asilata: I was just thinking that after the orgstrap presentation :) +- Man I was just wondering how to write LateX in Emacs this is incredible. +- I really liked the resulting LaTeX output file -- looked gorgeous :) +- Yeah seriously. I am pleasantly surprised. I think I'll have to switch over to using Emacs and LateX +- Theme: zenburn +- wait ... does elisp support unicode lambda like racket? + - I mean... you can make it, but not out of the box. + - asilata: I think it's just an org prettification + - prettify-symbols-mode +- do you use latex preview in the org buffer too? + - asilata: no, I usually don't, I find it slows down my system a bit. +- some very nice examples of wicked-cool org stuff there :) +- I also use python to generate latex from babel so that I don't mess things up + +# Speaker information - Name pronunciation: /ˈəsɪʟət̪ɑ ˈbɑpəʈ/ UH-si-luh-tah BAH-putt - Pronouns: she/her - Homepage: diff --git a/2021/talks/cs.md b/2021/talks/cs.md index 31e54b3c..80f77758 100644 --- a/2021/talks/cs.md +++ b/2021/talks/cs.md @@ -20,7 +20,20 @@ MS CS student at Georgia Tech, in the hopes that I can both get feedback on ways to improve the system I use, as well as hopefully inspire others to build workflows that make them more productive. - +# Discussion + +IRC nick: gcoladon + +- gcoladon: Yes it was software called ThoughtManager which ran on my Palm Treo 680 +- a similar workflow for videos using timestamps would be quite interesting +- this is a sweet script, surely it should be possible to write in elisp though... +- i know there exists the anki-editor package that works pretty well + - gcoladon: Yeah I am going to explore anki-editor sometime. It would be much better than my sed script :) +- how to get started? this is a great workflow + - gcoladon: not sure how to help people get started with this workflow, but I am happy to work on such a thing +- This is a workflow I really do like. Well done! +- interesting on the custom id approach, I stick a timestamp on nearly every heading that I create, but I never thought to make it a custom id +- gcoladon: I haven't tried to make my config sharable yet # Outline diff --git a/2021/talks/day1-close.md b/2021/talks/day1-close.md index 8c7293b3..e7a4bb41 100644 --- a/2021/talks/day1-close.md +++ b/2021/talks/day1-close.md @@ -19,6 +19,17 @@ [[!inline pages="internal(2021/info/day1-close-schedule)" raw="yes"]] +# Discussion + +- Is there any documentation anywhere how to give financial support to EmacsConf? + - sachac: That's very thoughtful of you! We cover EmacsConf costs out of pocket. I think the speakers have some support links on their pages. So if you particularly liked a talk, please feel free to e-mail a speaker or see if they have a tip jar! + - sachac: also, if you want to contribute time by volunteering to help with EmacsConf this year or next year, that would be even better =) For example, it was super-helpful to have a couple of volunteers help me caption all the day 1 talks and most of the day 2 talks this year, _and_ they got early access to all the talks and could caption the talks they wanted. We did the captioning using subed.el in Emacs, using the speakers' Org files or autogenerated captions from Youtube as starting points. + - sachac: for example, if some people could help with streaming alternate tracks, we could have longer talks and longer Q&As, because I think we're just going to have more and more awesome Emacs talks, and I think we're reaching the limit of how much we can physically squeeze into two days ;) so our current strategy is lots of short talks/demos, and then people can learn more about the stuff that they find interesting. but it would be so nice to have more deep dives too. + - I think having alternate tracks is a great idea sachac, I think I noticed that speakers were very rushed because time was tight, and it'd be cool to that have that alleviated. And it would likely reduce stress for you guys so that technical issues aren't as dire. + - maybe if we can figure out some topics that would be good to dive deeper into (attendee feedback) that could be looked in to +- maybe each presentation should allocated five or ten minutes for a Q&A session afterwards before the next presentation starts. +- the subtitles are really good! you can tell it was human-written :) even nasty names are right +- Love the citations in subtitles. [[!inline pages="internal(2021/captions/day1-close)" raw="yes"]] diff --git a/2021/talks/day2-close.md b/2021/talks/day2-close.md index 9cd48ef1..f7bf2b84 100644 --- a/2021/talks/day2-close.md +++ b/2021/talks/day2-close.md @@ -51,8 +51,6 @@ # Feedback -- the subtitles are really good! you can tell it was human-written :) even nasty names are right -- Love the citations in subtitles. [[!inline pages="internal(2021/captions/day2-close)" raw="yes"]] diff --git a/2021/talks/design.md b/2021/talks/design.md index 71ba4652..943114b4 100644 --- a/2021/talks/design.md +++ b/2021/talks/design.md @@ -26,7 +26,7 @@ alternatives using GNU Emacs. 1. Review of a "modern" code editor (5mn) 2. Introduction of an alternative using Emacs (5mn) -## Links from the slides: +# Links from the slides: * [Elegant Emacs](https://github.com/rougier/elegant-emacs) (https://github.com/rougier/elegant-emacs) * [On the Design of Text Editors](https://arxiv.org/abs/2008.06030) (https://arxiv.org/abs/2008.06030) @@ -36,7 +36,30 @@ alternatives using GNU Emacs. * [nano-modeline (ELPA)](https://elpa.gnu.org/packages/nano-modeline.html) (https://elpa.gnu.org/packages/nano-modeline.html) * [nano-agenda (ELPA)](https://elpa.gnu.org/packages/nano-agenda.html) (https://elpa.gnu.org/packages/nano-agenda.html) -## Contact information +# Discussion + +- What's this theme? +- i'll be sharing this with my friends that praise on vscode +- Wow, incredible analysis of that editor. +- looks beautiful +- how much of that is just bigger margins and roboto though? +- I love nano Emacs. I use it too +- i wonder if I can steal the splash screen and header line +- I really think that the default emacs theme could use this kind of effort and scrutiny in order to improve it +- A4: good idea, but few people have A4 *screens*... +- holy crap it looks so good +- yet again, though, the contrast is awful! black and white, please, not light grey and not-quite-so-light grey. it's almost unreadable, IMHO +- How hard would it be to integrate nano emacs changes with the default emacs? Like, would there be a lot of pushback? + - of course! there was massive pushbac over using curly quotes, for goodness' sake +- Are you aware of the modus-themes and what are your thoughts after contrast and accessibility? + - yeah, i just love modus themes by Prot because i'm colorblind and the fact that it has a strict contrast ratio is really really helpful, but even on modus themes i have to set success, error and warning to some really strong colors like pure red, green and blue + - I'm *not* colourblind and having high contrast is still good! there's a reason books are black on white, not grey on grey. or at least the background and body-text foreground must be highly distinct + - protesilaos: there are also options for deuteranopia, in case you need them (will need to refactor them for simplicity's sake) +- What Nicolas Rougier does is most welcome. Emacs can benefit a lot from such work. +- hmmm maybe Emacs needs to be able to handle WOFF! sounds like a job for fontconfig, I might look at it some day +- Nano Emacs + modus-themes would be a perfect combination, as it were. + +# Contact information * Contact [nicolas.rougier@inria.fr](mailto:nicolas.rougier@inria.fr) * Follow my work at [github.com/rougier](https://github.com/rougier) * Support my work at [github.com/sponsors/rougier](https://github.com/sponsors/rougier) or [en.liberapay.com/rougier/](https://en.liberapay.com/rougier/) diff --git a/2021/talks/dev-update.md b/2021/talks/dev-update.md index 34c7d3a6..a3467171 100644 --- a/2021/talks/dev-update.md +++ b/2021/talks/dev-update.md @@ -10,6 +10,19 @@ John Wiegley [[!inline pages="internal(2021/info/dev-update-schedule)" raw="yes"]] +# Discussion + +- the real question: do we still have time to get our patches in to the 28 branch ^_^ +- So I assume a lot of distros will make those native-comp related packages some sort of dependency, right? + - the conversations I have seen among the distro maintainers seems to suggest that at least some of them will bundle the .eln files + - What about ELPAs? + - if a distro packages elisp files they would, but for ELPA even the .elc files aren't stored (iirc?), so those would be compiled asynchrously +- That's great so that I'm not using weird commands on incompatible modes +- Yes yes yes, the input mode update sounds incredible. I already hack that in my init.el, but I guess it'll be native. +- thank you so much for the great work on Emacs! +- why would emoji support be important in any way.. for anybody? Especially.. in the larger scheme of things or more important problems? Am i missing something? + - Unicode compatibility's always a good thing +- so you have to have a toolchain present even if you are only using precompiled .eln files [[!inline pages="internal(2021/captions/dev-update)" raw="yes"]] diff --git a/2021/talks/erg.md b/2021/talks/erg.md index 2b2a9004..dae8b210 100644 --- a/2021/talks/erg.md +++ b/2021/talks/erg.md @@ -31,6 +31,9 @@ In our short talk we share information about these methods, making a case for other people getting together and creating their own small research communities similar to ours. +# Discussion + +- So this group really spawned out of last year's conf? You four were just met up and kept in touch? [[!inline pages="internal(2021/captions/erg)" raw="yes"]] diff --git a/2021/talks/exec.md b/2021/talks/exec.md index ee487b54..a69c0dfa 100644 --- a/2021/talks/exec.md +++ b/2021/talks/exec.md @@ -51,7 +51,18 @@ transform Org files from plain text documents with a bit of markup into self describing computational documents, or interactive applications. - +# Discussion + +IRC nick: tgbugs + +- This is supercool !! +- That is absolutely wild +- is the hash not just security theater? + - tgbugs: you need it to enable non-theater workflows + - anyone who could write the org-file could update the hash as well, no? +- I don't understand why he needs to talk about powershell, more than the other shell. :( + - tgbugs: very late response, but the reason I talked about powershell more than the others is because it is the most different and required some explainiation, I also was :/ about that + - that sounds that is a good reason to not include it xD . you can add fish in the talk and it will be bettter. # Outline diff --git a/2021/talks/freedom.md b/2021/talks/freedom.md index 0d8a6391..9328e7ae 100644 --- a/2021/talks/freedom.md +++ b/2021/talks/freedom.md @@ -36,6 +36,24 @@ If, however, this is absolutely required for administrative purposes I shall furnish one regardless with the proviso that I am in no way bound by it and thus reserve the right to modify it ahead of the main event. +# Discussion + +Questions: + +- are "Prometheas" & "Prometheus" both forms acceptable? Is one "truer" than the other? + - protesilaos: Both are correct. The former is modern Greek. + +Feedback: + +- "I'll definitly use this talk to try to convert more colleagues :D (not joking)" +- Wow, you phrased prometheus bit that excellently! +- wow great point on new users being enticed by the "easy productivity" angle +- I want to be productive, so give me this really complicated tool with countless high-level functions so I can get stuff done ASAP. bit of a paradox, really. very well said. +- what a well thought-through and well prepared talk. really appreciating this! +- you can't be an emacs tourist because IT SUCKS YOU IN AND DOESN'T LET GO +- protesilaos is a gift to the community +- i really appreciate prot's point right here: emacs is "free software" in the strongest sense of the word, from a practical point of a view since even if another program is libre, its usually so darn complicated that the freedom to modify the program is pretty useless since i'm not smart enough to do it +- the nuance brought by protesilaos between ellitism and exigence is very good. [[!inline pages="internal(2021/captions/freedom)" raw="yes"]] diff --git a/2021/talks/gregorian.md b/2021/talks/gregorian.md index 1d13e7b6..8c61e394 100644 --- a/2021/talks/gregorian.md +++ b/2021/talks/gregorian.md @@ -21,7 +21,10 @@ Emacs by typesetting a simple score. All code and examples will be made available to help new users get started with typesetting their own scores. +# Discussion +- what are the advantages of this over lilypond? +- do you know if there is something similar for byzantine notation? # Outline diff --git a/2021/talks/invoice.md b/2021/talks/invoice.md index d9deb359..43e8a845 100644 --- a/2021/talks/invoice.md +++ b/2021/talks/invoice.md @@ -44,6 +44,12 @@ We will use the following packages: - python layer (I use spacemacs, so whatever is the equivalent in your config) - Some unnecessary Shakespearean references +# Discussion + +- okay, this is some next level invoicing automation! +- The accounting system transactions are a nice touch +- it's really hard to tell that came from org :) +- European format would be DD.MM.YYYY and not with dashes which can be mixed up with ISO or other formats. in the UK it's often with slashes: DD/MM/YYYY [[!inline pages="internal(2021/captions/invoice)" raw="yes"]] diff --git a/2021/talks/janitor.md b/2021/talks/janitor.md index 68548f61..23420a0e 100644 --- a/2021/talks/janitor.md +++ b/2021/talks/janitor.md @@ -19,6 +19,28 @@ Because of a reckless former Emacs maintainer that shall In this documentary we will follow a famous janitor in his every day job dealing with the aftermath of the cl-lib / lexical-binding party. +# Discussion + +- Question: Is there a place where these conventions and compilers checks are listed? A web page, an info perhaps? +- Wow, I think you are going to have to know a LOT on Emacs development, versions, Elisp details, ... to do that kind of work. + - One very helpful thing anyone can do is just confirm bug reports and add reproduction steps if they are missing. +- The double-dash is a convention for an func intended to be called internally only? + - Yes. `pacakge-foo` is public, `package--foo` is internal. +- mindless tree-wide transforms like this are what coccinelle is for. why are emacs maintainers still doing this by hand? you'd think lisp would be well-suited for expressing semantic patches to lisp... :/ this ceases to seem interesting when you've seen cocci do ten thousand transforms like this across a 500MiB tree in 20s or so + - Does cocci work on elisp? + - no, but the *idea* should work there, and Lisp is so regular in structure that something like coccinelle is the sort of thing lisp boosters say is really easy in lisp. but nooo, none exists that I know of :( (coccinelle itself is written in ocaml :) ) + - https://coccinelle.gitlabpages.inria.fr/website/ +- There's a monstrous heap of regexps that match most reasonable compiler output. I wrapped an ancient MS-DOS compiler for an obsolete language in a script that invokes it inside DOSBox and echos the output‚ and it Just Worked with compilation mode. + - Wow, that's awesome! Yes, lots of the "historic" parts of emacs are amazing. +- if folks are interested in the lexical dynamic transition: https://hopl4.sigplan.org/details/hopl-4-papers/13/Evolution-of-Emacs-Lisp + +Feedback: + +- OK, this blows my mind in a sense that I realize that I really don't have an idea of coding Elisp. +- This talk is great. There should be more like that online, so more people learn to help with "janitorial" work + +# Outline + - ~20 minutes Here really, I'm not sure how much time this will take. I put 20 minutes because I think I might be able to fill that and I think more diff --git a/2021/talks/molecular.md b/2021/talks/molecular.md index 9486789e..b2ebfaa4 100644 --- a/2021/talks/molecular.md +++ b/2021/talks/molecular.md @@ -46,6 +46,13 @@ into a script file, and submit these for non-Emacs users. We describe the content of the library and provide examples of the running PyMOL from Org-mode documents. +# Discussion + +- which is the package name for export org mode to pymol? +- the async header argument can be helpful with the problem of the amount of time for generating the images +- think of this is use case explication for being able to manage and render 3d models in org +- It might be faster to keep sections folded by default +- This is exactly the sort of thing my users love. # Outline diff --git a/2021/talks/montessori.md b/2021/talks/montessori.md index 31127e1a..b10396c8 100644 --- a/2021/talks/montessori.md +++ b/2021/talks/montessori.md @@ -19,12 +19,15 @@ drives present in everybody that allow us to explore and make sense of our world # Discussion -Feedback - - having studied in a school which founded by following Montessori Philosophy, I can relate <3 - Love the emphasis on creativity! - Such a cool talk - Great perspective in that talk. +- the reference to Montessori made me think of Alan Kay's talks about Frenet and Papert. + - i was thinking the exact same thing regarding Alan Kay and his talks about education, and of his philosophies behind Smalltalk (the programming language). + - and Smalltalk as a platform shares a lot with Emacs, both are a world where a user lives and develops + - garjola: yeah...the whole thing about discovery, figuring things out for yourself, having an epiphany. + # Outline diff --git a/2021/talks/nangulator.md b/2021/talks/nangulator.md index 076d4084..9992cbd5 100644 --- a/2021/talks/nangulator.md +++ b/2021/talks/nangulator.md @@ -19,6 +19,17 @@ can effectively leverage the logical tri-angulation (or, more properly N-Angulator is the genesis, to wit, the "Model-T," of such a program. +# Discussion + +IRC nick: N-Angulator + +- N-Angulator: I wrote it 10 years ago and am no porting it to GNU emacs +- is this a graph-as-filesystem +- I'd much rather work with keybindings rather than clicking things. Is there support for that? + - N-Angulator: I think the menu system does automatically assign some unique keys but it's been a long time since I looked at it +- I love these kind of advanced file systems +- This is weirdware in the best sort of way. + # Outline - 5-10 minutes: (brief description/outline) diff --git a/2021/talks/nyxt.md b/2021/talks/nyxt.md index 49c43a91..371f9ea5 100644 --- a/2021/talks/nyxt.md +++ b/2021/talks/nyxt.md @@ -28,7 +28,19 @@ miss this talk! You can learn more about this at: - +# Discussion + +IRC nick: `andrea + +- I thought I read somewhere that this browser was attempting to allow extensions in a similar manner to Chrome/Firefox extensions. It'd be nice to have a central location to grab those, install them etc. +- does nyxt also have an inspector, to edit html and css? + - `andrea: yes, I am just sending my JS to the inspector via Common Lisp +- loving the youtube note taking with the timestamp +- If you've been following Nyxt for a while, one of the core design goals is to push web browsing back towards its original conception of intertwingling readership and authorship. +- you have some amazing elisp skills and ideas +- Back when I was using Nyxt I had it tied to stumpwm and I puppeteered them both from emacs with sly. +- I wonder how hard it would be to integrate or compile JS extension to a form available to Nyxt +- `andrea: I need to ask about LibreJS: they have a discourse https://discourse.atlas.engineer/ # Outline diff --git a/2021/talks/omegat.md b/2021/talks/omegat.md index ed6c9516..33c46ab9 100644 --- a/2021/talks/omegat.md +++ b/2021/talks/omegat.md @@ -27,9 +27,13 @@ The sources are regularly updated with a po4a based shell script. # Discussion +IRC nick: brandelune + - translation is nice but typing anything non latin or cyrillic is hard with keyboard - Try out the Emacs IMF. One of the main reasons I use Emacs. Input Method Framework: https://www.gnu.org/software/emacs/manual/html_node/emacs/Input-Methods.html - Hi, thanks for the talk. I love OmegaT and use it always. But I would have liked to here about the experience of working both with Emacs and OmegaT. Can you tell us something about it? +- brandelune: wondering if anyone is interested in working on translating the emacs manuals to a language different from French. I know there are ongoing attempts in a number of languages (Japanese for one). LibreOffice JA has worked with "machine translation post editing" (MTPE in the "industry") and they seem to have produced good results. + - i'd definitely be interested, tho not sure i'll have the time anytime soon. but if there's a mailing list i'd be interested in subscribing or joining an irc channel. Feedback: diff --git a/2021/talks/org-outside.md b/2021/talks/org-outside.md index 71a6baf9..0df228e3 100644 --- a/2021/talks/org-outside.md +++ b/2021/talks/org-outside.md @@ -8,8 +8,6 @@ # The use of Org mode syntax outside of GNU/Emacs Karl Voit - - [[!inline pages="internal(2021/info/org-outside-schedule)" raw="yes"]] With the rising interest in Org mode, the GNU/Emacs community gained @@ -37,6 +35,28 @@ motivation article [Orgdown - a New Lightweight Markup Standard for Text Documents](https://karl-voit.at/2021/11/27/orgdown/) for further information. +# Discussion + +IRC nick: publicvoit + +- is there a tree-sitter parser for orgdown already? :P +- it seems to me that as org evolves, either orgdown eventually becomes incompatible with org or org is prevented from changing because it would break orgdown. I guess backcompat with existing org documents constrains org-mode this way already, though +- what level would you call github's implementation is? +- i'm not sure if we want a proliferation of org-syntaxes like markdown's +- Disentangling "org" the markup language and "org"/"org-mode" the piece of software that runs inside Emacs is long overdue +- I gotta say, why "Orgdown" and not just "Org"? That way we've got "Org" (the markup syntax) and "Org-Mode", the mode for that. Just delineate the mode from the thing the mode handles. + - there was a move in the opposite direction, using "Org" instead of "Org-mode" for the piece of software that runs inside Emacs, which to me is where the problem arises... +- +1 for "org" aas the format name, and the (already present) derived handling of the format being org-mode! To be clear, +1000000% in favour of this generally. +- Next year. Talk on presenting org as a mime-type. Who? + - it's officially being considered as a 'thing to be done or at least talked about', but I don't have a better status than that. +- I think the org/orgdown split makes sense: orgdown stripped-down org +- Why GitLab? GitLab.com requires reCAPTCHA to sign up, and nonfree cloudflare js to sign in + - publicvoit: I wanted to test an alternative to GitHub which I was using so far. + - I recommend codeberg.org, notabug.org, sr.ht, or savannah.nongnu.org +- already uses the ".org.txt" file extension, so that tools that don't otherwise support the org file type will at the very least read them +- sorry to have missed out on the discussion during your talk, but I'm extremely interested in getting org working outside elisp (re: https://github.com/tgbugs/laundry/tree/next). I started there long ago, at this point the issues that really need standardization is org-babel, but in order to do that we need the syntax settled, which has turned out to be a _lot_ of work +- having orgdown as a way to talk about files that have org syntax seems like it is a critical piece for effective outreach + # Outline - The term Org mode stands for different things diff --git a/2021/talks/pattern.md b/2021/talks/pattern.md index 524345f6..2000c242 100644 --- a/2021/talks/pattern.md +++ b/2021/talks/pattern.md @@ -52,6 +52,10 @@ four years of Learning@Scale and charting the future. L@S 2018, June 26–28, 20 - greta: Thanks for that link! - if I may ask, what's the little toy figure in the background, looks nice :D - A wooden (fake) Transformer :) +- do you think emacs could have implemented with this design pattern, but in another programming language? + +Feedback: + - That's a great point about the sketches, and why Emacs graphical improvements are important. - yes this talk is excellent. i'm very happy to find some of my thoughts echoed here in such a clear and well researched way - this is exactly my experience. using/learning emacs is THE way that i gained the skills, the learning to learn skills i needed to become a professional programmer (which is incidental to the growing up into a hacker :P) @@ -60,6 +64,8 @@ four years of Learning@Scale and charting the future. L@S 2018, June 26–28, 20 - This is saying out loud in concrete language everything I've felt about emacs and the community since e.g. the package system became available and social git forges made it easy to explore others' configs - What a wonderfully diverse set of viewpoints so far. Not just viewpoints but concepts I would never have expected in an ‘Emacs conf’. I'm glad I dropped by. Thank you greta. - This quote of Richard Gabriel rings a bell in the emacs context: "If it is small, it was written by an extraordinary person, someone I would like as a friend; if it is large, it was not designed by one person, but over time in a slow, careful, incremental way" (Gabriel, R. (1996). Patterns of software: tales from the software community. New York: Oxford University Press. (https://dreamsongs.com/Files/PatternsOfSoftware.pdf) +- I just finished listening to Greta Goetz's talk and I love it so much. +- I listened to it after listening to acdw's talk on the frownies mode, a little mode to do something very simple, how he met people, wrote that mode, published it, got feedback. Your talk felt like an excellent background on the experience. The part about helping each other also really resonated with me. I would like to search for how many messages I must have posted to comp.emacs and gnu.emacs.help back in the days. I feel like it must have been about 2000 of them. :) Much of that long before I started writing any code. # Speaker release diff --git a/2021/talks/professional.md b/2021/talks/professional.md index 8781f521..e0233886 100644 --- a/2021/talks/professional.md +++ b/2021/talks/professional.md @@ -8,8 +8,6 @@ # Using Org-Mode For Recording Continuous Professional Development Philip Beadling - - [[!inline pages="internal(2021/info/professional-schedule)" raw="yes"]] I recently had the pleasure of being audited for my CPD record with one @@ -54,7 +52,19 @@ to execute it on opening the Org file. The elisp concerns itself with nice custom org capture functions and a few functions to ensure nice formatting on export, etc. +# Discussion + +IRC nick: pbeadling +- Very impressive use of capturing +- This is madness, and I am a little ashamed of saying that I have wanted to do something similar for personal reasons. I feel it is an overkill I cannot justify to myself + - pbeadling: For me it largely motivated by trying to make the whole task more interesting + - i think of like lots of us falling in lots of rabbit holes, making for quite a cavernous attack surface, when we consider Emacs is including it's various package arcives. +- hmm, hooking is a neat way to check in/ouut +- the workflow looks good but why he isn't integrating this with org agenda ? + - pbeadling: Agree - merging with org-agenda is the next thing I want to do with this + - pbeadling: For the CPD thing the biggest limitation I think is that you have to have the org file in the current buffer to add items - really you want to be able to capture CPD items from anywhere in your workflow - when I get some time I'll update the script to integrate better with capture and agenda like this. +- # Outline diff --git a/2021/talks/project.md b/2021/talks/project.md index 6a405b23..36fabeb2 100644 --- a/2021/talks/project.md +++ b/2021/talks/project.md @@ -17,12 +17,17 @@ We are a small company and we are still tuning and improving the process, but with a bit of Emacs Lisp, the functions Org Mode provides, and reading here and there what other users do, we implemented an effective workflow we have been using for nearly a -year, now, and with which we are very happy. Talk duration: +year, now, and with which we are very happy. -–> 20 minutes seems to be right (15 talk + questions) -–> I can also make in 10 minutes, by focusing the talk on - budgeting (or monitoring) +# Discussion +IRC nick: adolfo + +- Why is Michele working more than Adolfo??? + - adolfo: I can answer that :-) because he is better than I am ;-) +- watching this talk I really want to get the OPENED: cookie added +- what is the difference between hledger and ledger ? + - adolfo: implementation. hledger is in Haskell, ledger written in C++; there are also some differences in the format supported [[!inline pages="internal(2021/captions/project)" raw="yes"]] diff --git a/2021/talks/research.md b/2021/talks/research.md index 0b1f13c6..770e6185 100644 --- a/2021/talks/research.md +++ b/2021/talks/research.md @@ -33,7 +33,13 @@ will share my Doom Emacs configuration for this workflow, but it is not limited to Doom. +# Discussion +- Are there any good packages for emacs/Lisp libraries that are similar to Matplotlib/Pyplot/Numpy? + - use numpy with org-mode and babel + - plotting is a bleak spot in the lisp space, racket has a built in plot library that is probably the best on that front +- are these helper functions public? +- this talk just gave me an idea, I organize repos inside ~/code/{github.com,gitlab.com,gnu.org,etc}/author@repository-name.git - and I can instead use a single directory and use this strategy for projectile-switch-project where author is one column, repository name is another, git remote is another, etc # Outline diff --git a/2021/talks/teach.md b/2021/talks/teach.md index 21d3462b..210735dd 100644 --- a/2021/talks/teach.md +++ b/2021/talks/teach.md @@ -8,8 +8,6 @@ # Using Org-mode to teach programming Daniel German - - [[!inline pages="internal(2021/info/teach-schedule)" raw="yes"]] In this presentation I will explain how to use org-mode effectively to @@ -33,7 +31,13 @@ for an example). Finally, I will discuss some important aspects to consider when using org-mode for this purpose. +# Discussion +- how do you keep the discipline of working on your notes? that's probably my biggest problem +- I like "Try that with PowerPoint!" as a new org-babel slogan +- we just need krita and inkscape modes +- i remember doing similar in Smalltalk using a presentation tool with in it but with a full on graphical display of the Smalltalk environment not just text based. +- I liked the trick with annotating the code in xournal -- what is the elisp glue for that? Do you have a package for that? # Outline diff --git a/2021/talks/tech.md b/2021/talks/tech.md index bdb7f28b..d9a3e8a1 100644 --- a/2021/talks/tech.md +++ b/2021/talks/tech.md @@ -8,8 +8,6 @@ # Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide Jan Ypma - - [[!inline pages="internal(2021/info/tech-schedule)" raw="yes"]] The emacs org-babel package is often mentioned in conjunction with @@ -26,6 +24,15 @@ sure that the documentation and slides are never out of date. The session will show how leverage org-babel, restclient and org-treeslide to write and present technical documentation with style. +# Discussion + +IRC nick: jan-ypma + +- I use restclient everyday, but never thought about using it from code blocks, duh! Very interesting talk! +- This is a good demo, I've found org-babel to be a really amazing glue language for stuff that's sort of annoying to automate otherwise. +- Thanks! :) So the fonts of the current talk are: Fixed pitch (serif): New Heterodox Mono, Variable pitch (serif): ETBembo +- for live coding presentations, demo-it is also pretty cool +- indeed, i have been trying to work out literate devops through org documents. Very cool and useful in specific contexts atleast I guess. like finding the status of a service quickly right within a structured org document. # Outline diff --git a/2021/talks/telega.md b/2021/talks/telega.md index 7bbdd95a..e664bf4e 100644 --- a/2021/talks/telega.md +++ b/2021/talks/telega.md @@ -20,6 +20,10 @@ the vast majority of the features supported by the official clients, while adding several unique ones. In the talk, I will present the package and highlight some of the most important features. +# Discussion + +- Does telega still require company for completion? +- Telegram has become a real (and desired) option to WhatsApp, thanks to telega.el [[!inline pages="internal(2021/captions/telega)" raw="yes"]] -- cgit v1.2.3