All talks: https://emacsconf.org/2023/talks/
Speedcubing in Emacs
https://emacsconf.org/2023/talks/cubing - wasamasa - Track: General
Watch/participate: https://emacsconf.org/2023/watch/gen/
Q&A: IRC (https://chat.emacsconf.org/?join=emacsconf)
IRC: Speaker nick: wasamasa - https://chat.emacsconf.org/#/connect?join=emacsconf,emacsconf-gen or #emacsconf-gen on libera.chat network
Guidelines for conduct: https://emacsconf.org/conduct
See end of file for license (CC Attribution-ShareAlike 4.0 + GPLv3 or later)
----------------------------------------------------------------
Notes, discussions, links, feedback:
----------------------------------------------------------------
Questions and answers go here:
- Q: I see that there is a way to document the time it took to complete the puzzle; however, what about other things such as the date and time, and potentially a note on technique or warm up routine etc? It seems like an interface that included these things would also help people who are practicing and trying to improve. It would help answer the question... what kinds of things do I need to do to improve. ;;Thank you for your answer.
- A: Currently, only the timestamp and completion time are recorded for the puzzle/label. However, I've looked at twisty-timer and it does record both the used scramble and a comment field as well, so I plan adding those once the other features work properly. This would allow keeping track of particularly good/bad solves for example.
- Q:
- Q: As a side-note, could you say something about how you use emacs to help with your cybersecurity or CTF actifivities? Are there some recommended packages or do you use all of your own templates and procedures to speed your activity? Maybe just post a link to your homepage or GH repositories.
- A: It's pretty much only Org usage to document my activities in a way that I know what I did 3 weeks ago and can pick up my research from then. I do not use Emacs for source code review specifically (depending on the target environment, there are better suited tools). The thing with the field is that often, one has to resort to work with whatever tools are at hand and to make the most of them, which is kind of at odds with using Emacs first and foremost as an integrated environment for everything. Other than Org, I use it as an editor for pretty much any programming language I encounter.
- Q: What are the biggest challenges to using transient?
- A: The documentation was very high-level compared to what I'm used to, so I had to skim it a lot to find out how to use it for basic tasks. I think it would be useful to have some slightly more hands-on examples for common tasks. One issue I've run into a few times was the code using generic functions, so it was difficult to debug errors (like using a non-interactive lambda form when a command was expected and getting an unhelpful error message).
- Q:
- Q: Very cool project. Alas I'm not a cuber, so my question is merely, what did you learn in the process of making this presentation?
- A: I've never recorded a demo video happening outside of my laptop before, so getting the external recording setup right was... fun. It involved a ladder, several cardboard boxes and my phone. After five attempts (one of which ended up with the cube rolling off the desk loudly), I finally got an okayish recording to use for the presentation.
- Q: Does svg.el support tap events?
- A: svg.el is only responsible for generating valid SVG documents and one can put whichever tags/attributes there they wish. From my understanding, anything interactive usually solved with JS in the browser would need to be rewritten using Emacs Lisp instead. Tap events for example could be solved with the ":map" property put on the image and would work for other image formats than SVG as well.
- Q:
- Q:
- Q:
----------------------------------------------------------------
Next talks:
Questions/comments related to EmacsConf 2023 as a whole? https://pad.emacsconf.org/2023
----------------------------------------------------------------
This pad will be archived at https://emacsconf.org/2023/talks/cubing after the conference.
Except where otherwise noted, the material on the EmacsConf pad are dual-licensed under the terms of the Creative Commons Attribution-ShareAlike 4.0 International Public License; and the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) an later version. Copies of these two licenses are included in the EmacsConf wiki repository, in the COPYING.GPL and COPYING.CC-BY-SA files (https://emacsconf.org/COPYING/)
By contributing to this pad, you agree to make your contributions available under the above licenses. You are also promising that you are the author of your changes, or that you copied them from a work in the public domain or a work released under a free license that is compatible with the above two licenses. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION.