summaryrefslogtreecommitdiffstats
path: root/2023/talks/cubing.md
diff options
context:
space:
mode:
Diffstat (limited to '2023/talks/cubing.md')
-rw-r--r--2023/talks/cubing.md22
1 files changed, 11 insertions, 11 deletions
diff --git a/2023/talks/cubing.md b/2023/talks/cubing.md
index efb3f47d..b8f11327 100644
--- a/2023/talks/cubing.md
+++ b/2023/talks/cubing.md
@@ -33,10 +33,10 @@ features and challenges that came up during development will be shown.
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
+ 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
+ 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
@@ -46,7 +46,7 @@ features and challenges that came up during development will be shown.
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: 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
@@ -57,25 +57,25 @@ features and challenges that came up during development will be shown.
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
+ - 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
+ 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).
- <https://github.com/positron-solutions/transient-showcase>
might be helpful.
- - Definitely, but as I\'ve remarked in the talk, the
- examples felt very \"generic\". Slightly more realistic
+ - Definitely, but as I've remarked in the talk, the
+ examples felt very "generic". Slightly more realistic
examples would make it even better.
-- Q: Very cool project.  Alas I\'m not a cuber, so my question is
+- 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
+ - 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
+ 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.
@@ -84,7 +84,7 @@ features and challenges that came up during development will be shown.
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\"
+ 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.