path: root/2024/captions/emacsconf-2024-color--colour-your-emacs-with-ease--ryota--answers.vtt

WEBVTT

00:00:00.000 --> 00:00:06.039
... Org mode and kind of note taking. And that meant that it wasn't

00:00:06.040 --> 00:00:10.679
too difficult to get started with. But when I started more on

00:00:10.680 --> 00:00:14.959
the coding side, because I'm a software engineer, you know,

00:00:14.960 --> 00:00:20.679
on the day job. That kind of got me to think that the colors and

00:00:20.680 --> 00:00:26.479
how themes look, how Emacs looks, was affecting. And that's

00:00:26.480 --> 00:00:30.719
how it kind of came to picture. So I could have kind of gone

00:00:30.720 --> 00:00:34.919
into a little bit more coding side of things, but I didn't

00:00:34.920 --> 00:00:38.319
want to stress too much on the talk. So that's why I kind of

00:00:38.320 --> 00:00:43.439
stuck to a very small bits of Org Mode and Elisp. And yeah, I

00:00:43.440 --> 00:00:48.159
think that's how it came about. Yeah, but that's perfectly

00:00:48.160 --> 00:00:52.119
fine. That's one of the chief reasons why we have two tracks

00:00:52.120 --> 00:00:54.799
for Emacs content. We've had those for the last four years, I

00:00:54.800 --> 00:00:57.279
think. It's because we have a general track, which is more

00:00:57.280 --> 00:00:59.239
geared towards people who want a general... well,

00:00:59.240 --> 00:01:01.799
generally people who are highly interested into org mode

00:01:01.800 --> 00:01:03.999
and not necessarily into coding, but just to whet their

00:01:04.000 --> 00:01:08.399
appetite to what can be done. And on the DevTrack, we have,

00:01:08.400 --> 00:01:11.519
well, this year we have talked about Rust and about other

00:01:11.520 --> 00:01:13.559
fancy things that people can do with Emacs. But, you know,

00:01:13.560 --> 00:01:15.559
I'm also a software engineer, you know, we do this all the

00:01:15.560 --> 00:01:18.079
time. Sometimes it's just fine to just chat about colors and

00:01:18.080 --> 00:01:20.959
just the results of what we develop rather than how the

00:01:20.960 --> 00:01:24.839
sausage is made. So that's completely fine too. I'm not sure

NOTE Why colour?

00:01:24.840 --> 00:01:28.879
if you mentioned it in your presentation, but why color, out

00:01:28.880 --> 00:01:31.479
of all the things you could be ricing on your setup, why were

00:01:31.480 --> 00:01:37.559
you so interested about colors? I think it was just that

00:01:37.560 --> 00:01:40.239
mainly that I had to do a lot of context switch between

00:01:40.240 --> 00:01:44.119
different languages. Elisp is not the one because Elisp is

00:01:44.120 --> 00:01:48.079
something that I would do for Emacs editing. But for day job,

00:01:48.080 --> 00:01:52.999
I had to use mainly Go as I work with Kubernetes quite a bit. So

00:01:53.000 --> 00:01:58.119
Go and also web languages like TypeScript, JavaScript, you

00:01:58.120 --> 00:02:01.519
know, those languages, where I felt that whenever I was

00:02:01.520 --> 00:02:05.359
switching context to a different language, I felt that it's

00:02:05.360 --> 00:02:08.839
kind of annoying to see all the different colors in

00:02:08.840 --> 00:02:11.999
languages like TypeScript, where, you know, VS Code way

00:02:12.000 --> 00:02:15.799
would be very full of colors. which I felt that, okay, like,

00:02:15.800 --> 00:02:18.759
why do I have to have that many different colors on let and

00:02:18.760 --> 00:02:23.759
constant or the keywords where it could be just a white text?

00:02:23.760 --> 00:02:27.679
It didn't have to be that colorful. So that was the bit, the

00:02:27.680 --> 00:02:31.399
most annoying bit when it came to context switching. And I

00:02:31.400 --> 00:02:34.759
felt that that just didn't happen in the Org Mode or writing

00:02:34.760 --> 00:02:40.799
in general. So I had to find a way to make it work, make more

00:02:40.800 --> 00:02:46.199
coding make my coding more kind of friendly to me and that's

00:02:46.200 --> 00:02:50.039
when I thought maybe just the colors are something that's

00:02:50.040 --> 00:02:54.039
bothering me and it actually was the case and that's how I got

00:02:54.040 --> 00:02:59.359
to more into the color kind of journey and got too much into it

00:02:59.360 --> 00:03:04.039
I guess. Right, and was it what eventually motivated you to

NOTE What motivated you to learn Elisp and get into the Emacs core?

00:03:04.040 --> 00:03:06.999
learn Elisp and to get into the Emacs core? Because it's

00:03:07.000 --> 00:03:09.399
funny how you find plenty of people using Emacs in Org Mode

00:03:09.400 --> 00:03:11.399
and then they find something that they take particular

00:03:11.400 --> 00:03:15.039
issue with, for you it's the color, and then they just go all

00:03:15.040 --> 00:03:18.039
in trying to pull the rope as far as they can to try to

00:03:18.040 --> 00:03:21.359
understand as much as possible about what code is managing

00:03:21.360 --> 00:03:23.879
this part of the application. Like for you it was color, for

00:03:23.880 --> 00:03:27.999
me it was the org agenda, I desperately wanted to make Org

00:03:28.000 --> 00:03:32.439
Agenda do something that it wasn't able to do. And five

00:03:32.440 --> 00:03:35.199
years, well, actually, no, 10 years later, I find myself

00:03:35.200 --> 00:03:38.199
hosting Emacs Cons. So, you never know just how far you're

00:03:38.200 --> 00:03:40.399
going to be pulling this rope. So, it's really interesting

00:03:40.400 --> 00:03:44.679
for me that my call was this. But back to the question, is this

00:03:44.680 --> 00:03:47.759
what eventually motivated you to get into Elisp and the core

00:03:47.760 --> 00:03:53.439
of Emacs? I think that the original journey to move to Emacs

00:03:53.440 --> 00:03:56.959
was around keybindings that I got annoyed with with other

00:03:56.960 --> 00:03:59.839
solutions, not just, you know, not speaking of Emacs

00:03:59.840 --> 00:04:02.879
keybinding or anything, like anything in general. The main

00:04:02.880 --> 00:04:07.519
reason was that I used Dovrak keyboard layout, and that

00:04:07.520 --> 00:04:10.799
meant that all the C-c, C-v, C-p, whatever, It just is

00:04:10.800 --> 00:04:13.919
all over the place. So I had to find something that could work

00:04:13.920 --> 00:04:17.039
for me. And Emacs was a solution that allowed me to do

00:04:17.040 --> 00:04:20.479
anything. And that's the kind of the journey that it

00:04:20.480 --> 00:04:24.039
originally started. And from there, started tweaking org

00:04:24.040 --> 00:04:28.439
mode and writing experience to be tuned to my liking. Color

00:04:28.440 --> 00:04:32.559
was another thing that I thought, OK, maybe I could do it

00:04:32.560 --> 00:04:36.239
easily with org mode. And when I started to use more of the

00:04:36.240 --> 00:04:40.799
coding side of things on Emacs, I felt that, okay, that was

00:04:40.800 --> 00:04:45.159
something I needed to solve. So Elisp was always kind of

00:04:45.160 --> 00:04:48.439
just a toolkit that, you know, I knew that it was available. I

00:04:48.440 --> 00:04:52.199
knew that it would be something that I want to be able to use.

00:04:52.200 --> 00:04:57.159
So I think in a way color was a good segue to understand how I

00:04:57.160 --> 00:05:03.359
can kind of work out more of a complex logic with the editor

00:05:03.360 --> 00:05:06.359
without having to write JavaScript or things that I don't

00:05:06.360 --> 00:05:09.399
particularly like. So yeah, I think the journey around the

00:05:09.400 --> 00:05:11.879
functional languages, functional kind of programming was

00:05:11.880 --> 00:05:15.439
always something that I was keen about. And yeah, the whole

00:05:15.440 --> 00:05:18.479
journey kind of made sense for me. And then moving on to the

00:05:18.480 --> 00:05:21.999
color was just one way to get more involved in. So I can

00:05:22.000 --> 00:05:26.279
totally see that this journey kind of making to a little bit

00:05:26.280 --> 00:05:30.759
different angle But yeah, we shall see how that really turns

00:05:30.760 --> 00:05:33.799
out. But for now, I think I'm happy with the color setup. Now I

00:05:33.800 --> 00:05:37.599
can really focus on the coding. Well, that's all good. And

00:05:37.600 --> 00:05:40.839
I'm sure plenty of people listening to you now, you know,

00:05:40.840 --> 00:05:43.639
find this relatable, how they eventually got into

00:05:43.640 --> 00:05:46.879
programming. Like for you, you did say that you were a

00:05:46.880 --> 00:05:50.519
software engineer now. But I found plenty of people,

00:05:50.520 --> 00:05:54.679
especially doing workshops, that just started you know,

00:05:54.680 --> 00:05:57.639
their software engineering journey just with Emacs and

00:05:57.640 --> 00:05:59.239
they just realized they were doing something completely

00:05:59.240 --> 00:06:01.999
different, like I was studying humanities. But then you

00:06:02.000 --> 00:06:05.079
touch Emacs and you realize, yeah, this whole programming

00:06:05.080 --> 00:06:06.679
shtick is actually pretty damn cool.

00:06:06.680 --> 00:06:09.079
And then you find yourself again,

00:06:09.080 --> 00:06:10.999
five to 10 years later, becoming a software

00:06:11.000 --> 00:06:12.999
engineer. So yeah, that's all good.

00:06:13.000 --> 00:06:13.919
So we do have a couple of

00:06:13.920 --> 00:06:18.439
questions and I'd like to move into them so that I, I mean,

00:06:18.440 --> 00:06:22.399
people have questions and for me it's okay for me to chat with

00:06:22.400 --> 00:06:25.119
you but obviously it's better if people ask you the question

00:06:25.120 --> 00:06:27.639
themselves. And again, if you want to ask questions to Ryota

00:06:27.640 --> 00:06:31.039
directly, feel free to join us on BBB and whenever we're done

00:06:31.040 --> 00:06:33.519
with the questions on the pad, I'm more than happy

00:06:33.520 --> 00:06:35.319
to let you ask your questions live.

NOTE Q: Is there any intention to create a library for working with more experimental color spaces? Pulling code out of Hasliberg for this purpose, perhaps?

00:06:35.320 --> 00:06:37.799
All right, so starting with the first question,

00:06:37.800 --> 00:06:39.999
is there any intention to create a library

00:06:40.000 --> 00:06:42.559
for working with more experimental color spaces, pulling

00:06:42.560 --> 00:06:45.679
code out of Hasliberg for this purpose, perhaps? Although I

00:06:45.680 --> 00:06:50.479
do not know. Hasliberg, you might? Yeah, Hasliberg. And to

00:06:50.480 --> 00:06:55.119
answer the question, started the journey just for myself

00:06:55.120 --> 00:06:58.479
and I didn't think that it would be actually useful for other

00:06:58.480 --> 00:07:03.319
use cases and this conference talk just came about kind of

00:07:03.320 --> 00:07:08.079
out of sheer luck really. So the idea I think I can definitely

00:07:08.080 --> 00:07:12.199
work it out and I don't think there will be too, the original

00:07:12.200 --> 00:07:17.639
code that I started with was I had to use some color space and I

00:07:17.640 --> 00:07:22.479
started with sRGB and then went to HSL and then went to LCH. So

00:07:22.480 --> 00:07:25.479
I think there has been quite a bit that I learned from it. At

00:07:25.480 --> 00:07:29.999
the same time, I may be tempted to actually maybe perhaps

00:07:30.000 --> 00:07:34.159
contribute back to ct.el rather than creating my own. I

00:07:34.160 --> 00:07:36.279
think that would make more sense perhaps.

00:07:36.280 --> 00:07:39.479
But for my own kind of taste that I thought

00:07:39.480 --> 00:07:42.839
that it would be something I can work out in my theme,

00:07:42.840 --> 00:07:46.879
but I don't have any I think, you know, making a

00:07:46.880 --> 00:07:49.999
library is definitely something that I can think about, but

00:07:50.000 --> 00:07:53.679
perhaps maybe making it too many packages isn't exactly

00:07:53.680 --> 00:07:57.319
what I want. But for my own use case, I think I just wanted to

00:07:57.320 --> 00:07:59.919
have something that just didn't have any external

00:07:59.920 --> 00:08:04.119
dependency so that I can use the vanilla Emacs with my

00:08:04.120 --> 00:08:09.639
colors. I think that's how it started, but I'm definitely up

00:08:09.640 --> 00:08:13.719
for it if there is interest about it. Yeah, well, thank you

00:08:13.720 --> 00:08:15.279
for this. It's always good to contribute.

00:08:15.280 --> 00:08:16.399
I'm tempted to say

00:08:16.400 --> 00:08:18.279
that's how they get you. You know, you do something really

00:08:18.280 --> 00:08:23.639
cool and you share it with people and they have the, you know,

00:08:23.640 --> 00:08:27.239
they just ask you, oh, do you have your code online? And you

00:08:27.240 --> 00:08:29.399
realize, no, I haven't pushed it. And then they start

00:08:29.400 --> 00:08:32.359
pressing you on. well, you need to do this, this is amazing

00:08:32.360 --> 00:08:35.879
and you need to share it. You know, I had plenty of people ask

00:08:35.880 --> 00:08:40.519
me to share my dot files when I was tackling the org agenda

00:08:40.520 --> 00:08:44.039
issue that I mentioned earlier. And yeah, eventually when

00:08:44.040 --> 00:08:47.479
you get to publishing your stuff, you also feel great

00:08:47.480 --> 00:08:50.279
because you're putting a little bit of your intelligence

00:08:50.280 --> 00:08:53.679
into the world and it can be the start of the journey for

00:08:53.680 --> 00:08:56.239
someone else. You know, maybe someone will find your

00:08:56.240 --> 00:08:58.679
library at some point and realize, yeah, I wanted to do

00:08:58.680 --> 00:09:01.239
something slightly differently. and then they either

00:09:01.240 --> 00:09:04.439
contribute to a library or they make their own but it's a

00:09:04.440 --> 00:09:07.359
complete journey that starts with just people taking the

00:09:07.360 --> 00:09:12.039
time to publish the content of the brain basically. Yeah,

00:09:12.040 --> 00:09:15.519
that's the power of open source now. It's just how we really

00:09:15.520 --> 00:09:19.119
appreciate the open source culture being cultivated

00:09:19.120 --> 00:09:23.159
throughout so many years. And yeah, this is something that

00:09:23.160 --> 00:09:26.999
I'm definitely keen about. So yeah, open for suggestions.

00:09:27.000 --> 00:09:30.079
And exactly, that's how I started with the journey. And

00:09:30.080 --> 00:09:33.519
yeah, while this is very experimental and very personal,

00:09:33.520 --> 00:09:38.199
yeah, I'm not, you know, tied down to one particular way

00:09:38.200 --> 00:09:41.399
only. So yeah we'll be open to suggestions like this one

00:09:41.400 --> 00:09:44.719
which I would definitely think about. Yeah that's amazing

00:09:44.720 --> 00:09:46.999
and just to be clear you know this is not a there's no

00:09:47.000 --> 00:09:50.639
incentive one. I'm not pushing you to publish your library.

00:09:50.640 --> 00:09:53.799
You know it was very personal for you and at the end if you

00:09:53.800 --> 00:09:56.199
believe it might be useful for others it's a nice thing to

00:09:56.200 --> 00:09:58.799
eventually think about publishing it. But just the fact

00:09:58.800 --> 00:10:01.439
that you showed up at EmacsConf... Sorry, I'm

00:10:01.440 --> 00:10:02.639
starting to lose my voice on the morning

00:10:02.640 --> 00:10:03.839
of the first day. That's

00:10:03.840 --> 00:10:07.639
not boding well for the two next days. I mean, just one day.

00:10:07.640 --> 00:10:09.159
But just the

00:10:09.160 --> 00:10:13.199
fact that you're showing up at EmacsConf and sharing about

00:10:13.200 --> 00:10:17.039
all of this, the process, how you got to it eventually, it's

00:10:17.040 --> 00:10:19.639
also a part of sharing. And I think it's also amazing in its

00:10:19.640 --> 00:10:26.039
own way. Absolutely. Okay, I'm going to try to read the next

00:10:26.040 --> 00:10:31.639
question and then try to cough a little bit. So can we have...

00:10:31.640 --> 00:10:36.759
Oh, sorry, Bala. Sorry. I was the one who asked the question.

00:10:36.760 --> 00:10:40.279
I thought I could ask it live here rather than... Thank you.

00:10:40.280 --> 00:10:46.039
I'll go cough a little bit. So here I am. Thanks, Ryota, for

00:10:46.040 --> 00:10:50.519
the nice talk. This is great. I loved it. Your attention to

00:10:50.520 --> 00:10:51.519
detail was awesome.

NOTE Q: Can we have a dark as well as light theme variations made from your theme?

00:10:51.520 --> 00:10:54.959
So I was just looking at the code and I was

00:10:54.960 --> 00:10:58.759
wondering, do you have a dark and a light theme variation

00:10:58.760 --> 00:11:02.599
which can be made from your theme? Or do you have to customize

00:11:02.600 --> 00:11:06.199
it every time? That was my question. And thanks for that.

00:11:06.200 --> 00:11:09.679
Thank you very much. I appreciate your feedback and

00:11:09.680 --> 00:11:15.039
questions. So to answer the question, the short answer is

00:11:15.040 --> 00:11:18.439
that I do have both dark and light themes with some sorts of

00:11:18.440 --> 00:11:22.199
standard colors that I personally liked. And there were a

00:11:22.200 --> 00:11:26.679
few things that I showed in the demo. where I showed, I think,

00:11:26.680 --> 00:11:29.999
three different dark theme colors. So light theme is

00:11:30.000 --> 00:11:31.559
definitely something that I can do.

00:11:31.560 --> 00:11:33.759
And the idea around Hasliberg theme

00:11:33.760 --> 00:11:36.279
and just my theming in general was that

00:11:36.280 --> 00:11:39.599
when I feel like I want to work in dark theme and when I want to

00:11:39.600 --> 00:11:42.159
work in the standard way, I would just use the standard color.

00:11:42.160 --> 00:11:44.919
But when I feel like maybe it's just so cold that I want

00:11:44.920 --> 00:11:48.519
to have a bit of a warm colors near me, I would use the orange

00:11:48.520 --> 00:11:52.279
theme, without changing too much of the kind of general

00:11:52.280 --> 00:11:55.639
feeling and experience. So that can be said for the light

00:11:55.640 --> 00:11:58.959
theme as well. So there is something and the kind of

00:11:58.960 --> 00:12:04.839
customization isn't that difficult to extend. So I do have

00:12:04.840 --> 00:12:09.359
both dark and light, but primarily I'm just looking at the

00:12:09.360 --> 00:12:12.839
dark theme as my main driver. But yeah, they are both

00:12:12.840 --> 00:12:18.239
available. Great. Thank you so much. I will definitely try

00:12:18.240 --> 00:12:21.719
your theme out. I'm definitely on the lookout for a nice,

00:12:21.720 --> 00:12:26.119
friendly theme. Thank you very much. As I said, this is a

00:12:26.120 --> 00:12:31.279
personal theme. I'm not sure if it really fits everyone's

00:12:31.280 --> 00:12:37.159
need, but it is one inspiration that I hope that can lead to

00:12:37.160 --> 00:12:40.639
another nice theming that could work for someone

00:12:40.640 --> 00:12:44.199
specifically for some use cases. I don't have to solve

00:12:44.200 --> 00:12:48.719
everyone's problem. Yeah, and I mean, it was sufficient to

00:12:48.720 --> 00:12:50.719
be inspirational to people. I mean, just Bala just

00:12:50.720 --> 00:12:53.759
mentioned it right now, but I'm sure plenty of people who

00:12:53.760 --> 00:12:55.999
watched live, but also people will be watching in the

00:12:56.000 --> 00:12:58.599
future, will have the interest to speak by what you've done.

00:12:58.600 --> 00:13:05.079
So thank you again so much for this. Yep. All right, well, I

00:13:05.080 --> 00:13:09.719
don't see any further questions. So I suggest we move

00:13:09.720 --> 00:13:14.279
towards closure. Ryota, do you have any last words? No, I

00:13:14.280 --> 00:13:17.079
don't. So yeah, thank you very much for attending. And it was

00:13:17.080 --> 00:13:20.519
great fun putting this together. And I really didn't think

00:13:20.520 --> 00:13:24.759
that I would be talking about my personal colors and

00:13:24.760 --> 00:13:27.759
personal favorites, like orange being my favorite color.

00:13:27.760 --> 00:13:30.119
This wouldn't be something that I would say out in any

00:13:30.120 --> 00:13:34.159
conference, to be honest. But it just came out to be. And

00:13:34.160 --> 00:13:37.479
happy that I had a chance. So thank you very much for giving me

00:13:37.480 --> 00:13:41.439
the opportunity to talk. in this amazing conference and

00:13:41.440 --> 00:13:44.319
yeah I can't just wait to check out other talks which you know

00:13:44.320 --> 00:13:46.919
I know that there isn't you know other talks that are

00:13:46.920 --> 00:13:50.199
happening right now I was actually wanted to to join them and

00:13:50.200 --> 00:13:52.759
check check that out so I will probably do that right now.

00:13:52.760 --> 00:13:56.839
Well, sure. Well, I won't hold you any longer then. Thank

00:13:56.840 --> 00:13:59.759
you. For me, it was just amazing to, you know, generally when

00:13:59.760 --> 00:14:01.639
you ask someone what their favorite color, you know, they

00:14:01.640 --> 00:14:04.399
just tell you orange or blue or whatever. They don't go then

00:14:04.400 --> 00:14:07.039
to chat about 20 minutes about their favorite color and how

00:14:07.040 --> 00:14:10.079
they tuned their entire editor to work exactly around their

00:14:10.080 --> 00:14:14.759
favorite colors. So it was inspiring. And I also want to try

00:14:14.760 --> 00:14:17.999
it out, frankly, because my theme has been utterly bad for

00:14:18.000 --> 00:14:20.639
the last five years and I need some change into my life. All

00:14:20.640 --> 00:14:24.319
right. Thank you so much for your time. Thank you very much,

00:14:24.320 --> 00:14:30.640
everyone. Cheers. Bye-bye.