WEBVTT

00:00:00.240 --> 00:00:01.520
I mean we are ahead of the schedule a

00:00:01.520 --> 00:00:03.679
little bit but I mean we also was a

00:00:03.679 --> 00:00:05.680
little bit earlier in the day

00:00:05.680 --> 00:00:09.040
so yeah yeah I'd say that's fine go for

00:00:09.040 --> 00:00:10.800
it take it away

00:00:10.800 --> 00:00:14.240
sure thank you so am I live already

00:00:14.240 --> 00:00:16.640
you are now unmuted um yep your life

00:00:16.640 --> 00:00:17.359
hello

00:00:17.359 --> 00:00:18.880
spell it so I'll just start the timer to

00:00:18.880 --> 00:00:20.720
make sure that I don't go overboard

00:00:20.720 --> 00:00:22.720
all right so you are now muted okay good

00:00:22.720 --> 00:00:24.160
to go now so

00:00:24.160 --> 00:00:26.960
hello again everyone so I hope you had

00:00:26.960 --> 00:00:28.240
well quite a lot of talks

00:00:28.240 --> 00:00:30.880
ever since the last one I did and all

00:00:30.880 --> 00:00:32.000
more interesting

00:00:32.000 --> 00:00:35.040
uh one after the other so um

00:00:35.040 --> 00:00:36.559
you know I'm a bit in a bit of a weird

00:00:36.559 --> 00:00:38.239
spot right now because I'm supposed to

00:00:38.239 --> 00:00:39.760
be presenting to you as you can see on

00:00:39.760 --> 00:00:40.239
my screen

00:00:40.239 --> 00:00:42.879
one big-ass awk file multiple tiny ones

00:00:42.879 --> 00:00:44.960
finally the end of the debate

00:00:44.960 --> 00:00:48.160
and it sounds about as clickbaity

00:00:48.160 --> 00:00:49.760
as you can possibly get with those

00:00:49.760 --> 00:00:51.280
topics and by the way

00:00:51.280 --> 00:00:54.000
uh credit where credit is due the title

00:00:54.000 --> 00:00:55.760
is not mine it's actually from bastian

00:00:55.760 --> 00:00:57.039
gary the current old

00:00:57.039 --> 00:01:00.719
maintainer and yeah I wanted to

00:01:00.719 --> 00:01:03.199
talk to you a little bit today about

00:01:03.199 --> 00:01:04.879
this question because

00:01:04.879 --> 00:01:07.600
if you are used to going on our slash

00:01:07.600 --> 00:01:09.040
emacs you know the subreddit that we

00:01:09.040 --> 00:01:09.600
have

00:01:09.600 --> 00:01:11.840
if you go on I can use often you know

00:01:11.840 --> 00:01:13.200
it's a question that

00:01:13.200 --> 00:01:16.000
you see pop-up every once in a while

00:01:16.000 --> 00:01:17.520
should I be using

00:01:17.520 --> 00:01:20.640
one big file or should I be using

00:01:20.640 --> 00:01:24.159
a lot of tiny files and I believe you

00:01:24.159 --> 00:01:24.799
know

00:01:24.799 --> 00:01:27.600
we've got defenders on both sides if I

00:01:27.600 --> 00:01:29.520
just show you one examples

00:01:29.520 --> 00:01:32.479
so we have carl voigt okay so he's one

00:01:32.479 --> 00:01:35.280
of the organizers for the conference

00:01:35.280 --> 00:01:37.920
he hears the guy who probably has the

00:01:37.920 --> 00:01:40.000
biggest augment files

00:01:40.000 --> 00:01:42.000
right now in all the people I know and

00:01:42.000 --> 00:01:43.759
god knows I know plenty of people use

00:01:43.759 --> 00:01:44.479
old mode

00:01:44.479 --> 00:01:46.880
but if you just look at this line I hope

00:01:46.880 --> 00:01:48.320
it's not too small you just

00:01:48.320 --> 00:01:51.360
make it a little larger but

00:01:51.360 --> 00:01:56.719
carl basically has a file with 126

00:01:56.719 --> 00:02:01.759
000 lines and I'm just going to pause

00:02:01.759 --> 00:02:04.560
and try to have you imagine how large a

00:02:04.560 --> 00:02:06.399
file it actually is

00:02:06.399 --> 00:02:08.399
just think about all of these lines

00:02:08.399 --> 00:02:10.000
being tasked in your days

00:02:10.000 --> 00:02:12.080
think about all those lines being about

00:02:12.080 --> 00:02:13.200
little thoughts

00:02:13.200 --> 00:02:14.400
you know that you've had throughout the

00:02:14.400 --> 00:02:17.200
day or project that you were working on

00:02:17.200 --> 00:02:19.680
and it's massive and you know one of the

00:02:19.680 --> 00:02:20.720
problem that

00:02:20.720 --> 00:02:23.920
uh calvoit actually approaches on

00:02:23.920 --> 00:02:27.680
this topic is that it takes him roughly

00:02:27.680 --> 00:02:30.160
20 seconds to get his old agenda going

00:02:30.160 --> 00:02:32.400
which is a massive amount of time

00:02:32.400 --> 00:02:35.680
I mean we have very fast computers now

00:02:35.680 --> 00:02:37.720
you know ever since e-max was created in

00:02:37.720 --> 00:02:39.200
1976

00:02:39.200 --> 00:02:42.319
computers I have no idea how much faster

00:02:42.319 --> 00:02:43.440
they've gotten

00:02:43.440 --> 00:02:47.760
and yet you know for earth 1000 lines

00:02:47.760 --> 00:02:49.599
emac seems to be choking and it's

00:02:49.599 --> 00:02:51.120
certainly not reasonable in a way to

00:02:51.120 --> 00:02:52.720
have to wait 20 seconds

00:02:52.720 --> 00:02:55.360
just for your entire file to be passed

00:02:55.360 --> 00:02:57.040
so basically what I want to do

00:02:57.040 --> 00:02:58.480
and by the way I forgot to do the

00:02:58.480 --> 00:03:00.879
presentation but I'm leova I did this

00:03:00.879 --> 00:03:02.879
before for those who were around

00:03:02.879 --> 00:03:05.519
and I um help maintain a software which

00:03:05.519 --> 00:03:06.640
is called orgrom

00:03:06.640 --> 00:03:08.560
and that's the expertise that I have on

00:03:08.560 --> 00:03:09.840
the topic

00:03:09.840 --> 00:03:11.760
actually if you go online I do have a

00:03:11.760 --> 00:03:13.599
github page I will make sure that you

00:03:13.599 --> 00:03:15.440
have all the links available afterwards

00:03:15.440 --> 00:03:18.640
but I do publish my init files

00:03:18.640 --> 00:03:20.720
and you can see if you scroll at the

00:03:20.720 --> 00:03:22.319
bottom I have a little demonstration

00:03:22.319 --> 00:03:23.200
which shows you

00:03:23.200 --> 00:03:25.519
the fancy things that I can do with my

00:03:25.519 --> 00:03:27.440
old mood setup and that might be even

00:03:27.440 --> 00:03:28.159
interesting

00:03:28.159 --> 00:03:30.720
in lights of the talk you've just had

00:03:30.720 --> 00:03:32.319
about gtd stuff because

00:03:32.319 --> 00:03:34.080
the first one is about how I end all my

00:03:34.080 --> 00:03:36.159
projects the second one is about

00:03:36.159 --> 00:03:39.680
the flow from a task uh as I work on it

00:03:39.680 --> 00:03:40.000
so

00:03:40.000 --> 00:03:41.519
I won't spend too much time on this but

00:03:41.519 --> 00:03:43.120
basically that's my expertise

00:03:43.120 --> 00:03:45.440
I have spent eight years working with

00:03:45.440 --> 00:03:46.959
working with org mode

00:03:46.959 --> 00:03:48.959
three of them actually thinking about

00:03:48.959 --> 00:03:50.720
writing packages

00:03:50.720 --> 00:03:54.080
and the thing is if I go into a little

00:03:54.080 --> 00:03:55.680
bit of details and obviously it's only a

00:03:55.680 --> 00:03:57.760
lighting talk so I won't have time to

00:03:57.760 --> 00:04:00.720
actually go really in depth about it but

00:04:00.720 --> 00:04:01.840
there is something

00:04:01.840 --> 00:04:03.599
in the ultimate libraries which is

00:04:03.599 --> 00:04:05.200
called org elements

00:04:05.200 --> 00:04:07.000
and you have the name right there org

00:04:07.000 --> 00:04:08.319
element.el

00:04:08.319 --> 00:04:11.439
dot el being for e-lisp file and as you

00:04:11.439 --> 00:04:12.319
can see

00:04:12.319 --> 00:04:14.799
the page it's on the work wiki so it's

00:04:14.799 --> 00:04:16.239
accessible by everyone

00:04:16.239 --> 00:04:19.280
but it's basically the api that

00:04:19.280 --> 00:04:23.759
org mode uses to pass all mode files

00:04:23.759 --> 00:04:26.400
so for those who don't know passing

00:04:26.400 --> 00:04:27.199
means basically

00:04:27.199 --> 00:04:29.360
checking a file checking all the content

00:04:29.360 --> 00:04:30.880
of the file and extracting all the

00:04:30.880 --> 00:04:32.880
information that we need from that file

00:04:32.880 --> 00:04:34.960
and as you can imagine you all have

00:04:34.960 --> 00:04:36.560
augmented files in your mind

00:04:36.560 --> 00:04:38.240
well you know they can be fairly complex

00:04:38.240 --> 00:04:39.840
you know you can have properties

00:04:39.840 --> 00:04:41.759
you can have contextual information like

00:04:41.759 --> 00:04:43.040
if you write a line

00:04:43.040 --> 00:04:45.199
which starts at column zero which means

00:04:45.199 --> 00:04:46.560
at the left

00:04:46.560 --> 00:04:48.000
you know it doesn't have the same

00:04:48.000 --> 00:04:49.680
meaning whether or not it is

00:04:49.680 --> 00:04:52.639
before the beginning of a headline or if

00:04:52.639 --> 00:04:54.160
it is after the beginning of a red line

00:04:54.160 --> 00:04:55.199
you know it's going to be

00:04:55.199 --> 00:04:57.759
relatively different hierarchically

00:04:57.759 --> 00:04:58.960
speaking

00:04:58.960 --> 00:05:01.759
and so the problem when it comes to the

00:05:01.759 --> 00:05:02.639
question of

00:05:02.639 --> 00:05:05.759
many files versus one big file or

00:05:05.759 --> 00:05:08.560
few big files is that we always have to

00:05:08.560 --> 00:05:09.600
keep in mind

00:05:09.600 --> 00:05:12.880
what org elements want you to do

00:05:12.880 --> 00:05:15.680
and the thing is there are plenty of

00:05:15.680 --> 00:05:17.440
problems when it comes to passing file

00:05:17.440 --> 00:05:18.400
the first one

00:05:18.400 --> 00:05:21.360
being obviously that emacs is a single

00:05:21.360 --> 00:05:22.160
thread

00:05:22.160 --> 00:05:24.880
process or has some threading

00:05:24.880 --> 00:05:26.400
capabilities we're not going to go into

00:05:26.400 --> 00:05:28.639
the details right now that's not my goal

00:05:28.639 --> 00:05:32.400
but it makes it incredibly hard to

00:05:32.400 --> 00:05:35.919
parallelize uh passing processes as

00:05:35.919 --> 00:05:39.280
we currently with the current technology

00:05:39.280 --> 00:05:42.320
and so you'd have to imagine that if you

00:05:42.320 --> 00:05:44.080
have a very large files if you go back

00:05:44.080 --> 00:05:46.479
to the example of carl voice from before

00:05:46.479 --> 00:05:49.199
100 000 lines that means that you have

00:05:49.199 --> 00:05:50.000
to scan

00:05:50.000 --> 00:05:52.320
through every single line basically

00:05:52.320 --> 00:05:53.759
because sometimes let's just say that

00:05:53.759 --> 00:05:56.080
you have a property drawer for instance

00:05:56.080 --> 00:05:59.440
which tells you oh okay uh this tree

00:05:59.440 --> 00:06:03.520
has the tag foo so the problem is there

00:06:03.520 --> 00:06:05.120
are multiple ways for you

00:06:05.120 --> 00:06:08.720
to define a tag okay so you can use the

00:06:08.720 --> 00:06:11.840
usual way which is about wrapping in

00:06:11.840 --> 00:06:14.000
columns the tag at the end of a heading

00:06:14.000 --> 00:06:16.160
so for instance if I I'm not going to

00:06:16.160 --> 00:06:17.360
switch to emac that's going to waste too

00:06:17.360 --> 00:06:18.240
much time

00:06:18.240 --> 00:06:21.039
but that's one way to say your time but

00:06:21.039 --> 00:06:21.520
say

00:06:21.520 --> 00:06:23.520
you have tag inheritance which means

00:06:23.520 --> 00:06:25.360
that when you have a parent with a tag

00:06:25.360 --> 00:06:28.160
you also want the child to inherit the

00:06:28.160 --> 00:06:29.520
tag so if you have

00:06:29.520 --> 00:06:32.400
first heading with the typhoo you have

00:06:32.400 --> 00:06:33.680
the first subheading

00:06:33.680 --> 00:06:37.520
and the tag foo is implied now imagine

00:06:37.520 --> 00:06:39.680
having to do that with a file that is

00:06:39.680 --> 00:06:41.039
completely nested

00:06:41.039 --> 00:06:44.160
a file that has maybe 9 10

00:06:44.160 --> 00:06:47.280
11 levels of depth to it

00:06:47.280 --> 00:06:49.039
it's mind-bogglingly complicated for the

00:06:49.039 --> 00:06:51.039
software to do that knowing that I've

00:06:51.039 --> 00:06:52.639
told you about tags

00:06:52.639 --> 00:06:55.919
but any property can be inheritable

00:06:55.919 --> 00:06:58.639
anything like priorities even though why

00:06:58.639 --> 00:07:00.240
would you do this

00:07:00.240 --> 00:07:03.759
you can have groups you can all this and

00:07:03.759 --> 00:07:05.599
as someone who went through the trouble

00:07:05.599 --> 00:07:07.199
of optimizing his old agenda so

00:07:07.199 --> 00:07:08.560
basically if we go back to the

00:07:08.560 --> 00:07:11.280
gifts gifs oh god we've already had this

00:07:11.280 --> 00:07:12.160
discussion

00:07:12.160 --> 00:07:14.479
between the git and magit and now I've

00:07:14.479 --> 00:07:16.400
started jeff and gif and I only have one

00:07:16.400 --> 00:07:18.080
more minute left to do so so let's just

00:07:18.080 --> 00:07:19.599
say I'm going to say gif

00:07:19.599 --> 00:07:23.599
just to spice people so if you go on

00:07:23.599 --> 00:07:26.880
the way I organize my agenda what I did

00:07:26.880 --> 00:07:29.120
in order to keep my agenda build time

00:07:29.120 --> 00:07:30.960
under two seconds

00:07:30.960 --> 00:07:33.440
is that I've rewritten a whole lot of

00:07:33.440 --> 00:07:35.520
codes to be able to pass my organ gender

00:07:35.520 --> 00:07:36.560
files

00:07:36.560 --> 00:07:40.080
so the thing is I'm going to be talking

00:07:40.080 --> 00:07:41.360
more about this later

00:07:41.360 --> 00:07:43.440
I only have let's say one minutes to

00:07:43.440 --> 00:07:44.479
conclude

00:07:44.479 --> 00:07:47.440
so as you've gathered I'm not going to

00:07:47.440 --> 00:07:48.479
be giving you the answer

00:07:48.479 --> 00:07:51.039
right now I'm going to be talking about

00:07:51.039 --> 00:07:53.440
orgrum a little later which is about

00:07:53.440 --> 00:07:55.680
following the principle of having many

00:07:55.680 --> 00:07:57.759
small files

00:07:57.759 --> 00:08:01.120
but as someone who has been using

00:08:01.120 --> 00:08:02.960
one large file to manage my life you

00:08:02.960 --> 00:08:04.879
know I'm sitting on the fence

00:08:04.879 --> 00:08:08.319
I do not know which one is the best

00:08:08.319 --> 00:08:10.560
but I hope that my presentation has

00:08:10.560 --> 00:08:12.240
given you a little id

00:08:12.240 --> 00:08:15.199
of what goes on behind the principles

00:08:15.199 --> 00:08:15.520
and

00:08:15.520 --> 00:08:16.560
you also need to think about the

00:08:16.560 --> 00:08:18.560
philosophy behind the organization of

00:08:18.560 --> 00:08:19.120
your notes

00:08:19.120 --> 00:08:21.039
but I hope to be approaching this topic

00:08:21.039 --> 00:08:23.280
with you in about

00:08:23.280 --> 00:08:25.360
two hours or so maybe one hour actually

00:08:25.360 --> 00:08:27.520
so I'm actually finished I've decided to

00:08:27.520 --> 00:08:28.960
leave you two minutes of questions

00:08:28.960 --> 00:08:31.520
so uh if someone could feed me the

00:08:31.520 --> 00:08:32.880
question that might be best

00:08:32.880 --> 00:08:34.399
because I don't want oh actually I can

00:08:34.399 --> 00:08:36.240
just open the year

00:08:36.240 --> 00:08:39.919
I can just open it give me a second okay

00:08:39.919 --> 00:08:40.800
ah

00:08:40.800 --> 00:08:43.039
just loading up huh I might stop showing

00:08:43.039 --> 00:08:43.839
my screen

00:08:43.839 --> 00:08:46.959
that might make it easier so I mean if

00:08:46.959 --> 00:08:47.519
you can make

00:08:47.519 --> 00:08:49.360
myself big now on the screen that would

00:08:49.360 --> 00:08:52.000
be splendid yeah sure

00:08:52.000 --> 00:08:55.839
thank you so uh where are we

00:08:55.839 --> 00:08:58.720
question 12. okay so what's better one

00:08:58.720 --> 00:09:00.160
big file

00:09:00.160 --> 00:09:02.160
I did is it did a job to tell me that I

00:09:02.160 --> 00:09:03.120
haven't answered the question because

00:09:03.120 --> 00:09:04.240
someone just

00:09:04.240 --> 00:09:06.320
asked me the question well personally if

00:09:06.320 --> 00:09:08.080
I were to give you a quick answer in

00:09:08.080 --> 00:09:08.560
like

00:09:08.560 --> 00:09:11.600
20 seconds personally I think it's a

00:09:11.600 --> 00:09:13.920
question that is contextually based

00:09:13.920 --> 00:09:15.680
do you want something that is efficient

00:09:15.680 --> 00:09:17.839
as far as optimization is concerned

00:09:17.839 --> 00:09:21.200
then you need to think about

00:09:21.200 --> 00:09:23.440
this and personally for all the

00:09:23.440 --> 00:09:24.640
organization that I do

00:09:24.640 --> 00:09:26.640
all this stuff all the to-do's that I

00:09:26.640 --> 00:09:27.760
handle

00:09:27.760 --> 00:09:30.080
I like to do this in one simple big file

00:09:30.080 --> 00:09:31.519
because you benefit from all the

00:09:31.519 --> 00:09:33.760
refiling capabilities of log mode

00:09:33.760 --> 00:09:36.320
so I would do that but for knowledge

00:09:36.320 --> 00:09:37.200
management

00:09:37.200 --> 00:09:40.080
for note-taking and all this well I'd

00:09:40.080 --> 00:09:41.279
much rather follow the

00:09:41.279 --> 00:09:42.959
orgrom way of doing things which is

00:09:42.959 --> 00:09:44.480
about having many

00:09:44.480 --> 00:09:48.240
small files okay I'm not getting any

00:09:48.240 --> 00:09:50.000
more questions I'm not sure if there is

00:09:50.000 --> 00:09:52.080
one on ise that could be fed to me

00:09:52.080 --> 00:09:53.040
otherwise I'm

00:09:53.040 --> 00:09:56.399
happy to to uh pass over to the next uh

00:09:56.399 --> 00:09:57.040
speaker

00:09:57.040 --> 00:09:59.360
and by the way just before I finish your

00:09:59.360 --> 00:10:01.360
world is a lie it's not a three-piece

00:10:01.360 --> 00:10:04.399
suit I'm wearing jeans below so I hope

00:10:04.399 --> 00:10:06.520
that satisfies your curiosity

00:10:06.520 --> 00:10:10.640
[Music]

00:10:10.640 --> 00:10:12.640
okay there's one more question appearing

00:10:12.640 --> 00:10:15.040
but otherwise one big file to have

00:10:15.040 --> 00:10:17.680
everything so I'm putting you on the

00:10:17.680 --> 00:10:19.760
spot I believe it was such a short talk

00:10:19.760 --> 00:10:21.040
you know the problem is

00:10:21.040 --> 00:10:23.600
I just wanted to give you a little

00:10:23.600 --> 00:10:24.720
answer

00:10:24.720 --> 00:10:26.959
a little you know path of thinking on

00:10:26.959 --> 00:10:27.920
this topic

00:10:27.920 --> 00:10:29.839
but obviously it's a topic I could be

00:10:29.839 --> 00:10:31.600
spending 40 minutes on but

00:10:31.600 --> 00:10:33.200
I'm going to be drained you're going to

00:10:33.200 --> 00:10:35.120
be drained nobody's going to be happy if

00:10:35.120 --> 00:10:35.680
I do this

00:10:35.680 --> 00:10:39.440
so

00:10:39.440 --> 00:10:41.200
and someone asked me if I switch between

00:10:41.200 --> 00:10:42.880
british and french accents

00:10:42.880 --> 00:10:46.560
so a little a little secret for you um

00:10:46.560 --> 00:10:48.480
when I'm stressed I tend to relate to a

00:10:48.480 --> 00:10:49.760
french accent

00:10:49.760 --> 00:10:53.760
so you can measure the amount of stress

00:10:53.760 --> 00:10:56.160
that I'm feeling during this talk

00:10:56.160 --> 00:10:58.880
with the amount of h's that I drop and

00:10:58.880 --> 00:11:00.560
the amount of uh

00:11:00.560 --> 00:11:02.720
sheer fright that you can see sometimes

00:11:02.720 --> 00:11:04.399
in my eyes when I'm thinking about what

00:11:04.399 --> 00:11:08.240
to say next

00:11:08.240 --> 00:11:10.880
all right sir so I mean do you believe

00:11:10.880 --> 00:11:11.360
we can

00:11:11.360 --> 00:11:14.240
leave it at that and uh I'll be you

00:11:14.240 --> 00:11:15.519
people will see plenty more with me

00:11:15.519 --> 00:11:17.040
later on anyway

00:11:17.040 --> 00:11:20.000
right um so looking at the schedule I

00:11:20.000 --> 00:11:20.640
think

00:11:20.640 --> 00:11:23.920
your talk has until like 202 meaning

00:11:23.920 --> 00:11:27.120
like five or six minutes from now oh

00:11:27.120 --> 00:11:28.000
right

00:11:28.000 --> 00:11:30.000
yeah so if you do like to take like one

00:11:30.000 --> 00:11:31.680
or two questions to add two more

00:11:31.680 --> 00:11:33.920
questions by all means

00:11:33.920 --> 00:11:37.040
okay so uh someone has asked me what is

00:11:37.040 --> 00:11:38.320
the emacs icon

00:11:38.320 --> 00:11:40.640
icon sorry see another french accent

00:11:40.640 --> 00:11:42.880
here uh in my status bar

00:11:42.880 --> 00:11:44.880
uh oh sorry I'm not sharing anymore uh I

00:11:44.880 --> 00:11:46.640
might just share again just so that

00:11:46.640 --> 00:11:49.200
everyone can catch a glimpse of that

00:11:49.200 --> 00:11:53.120
uh there we go allow

00:11:53.120 --> 00:11:54.880
so it should be so if you could make me

00:11:54.880 --> 00:11:56.240
small again I'm in I'm not sure if it's

00:11:56.240 --> 00:11:56.959
going to do it

00:11:56.959 --> 00:12:00.480
by itself but I do have a little icon

00:12:00.480 --> 00:12:01.839
here in my status bar

00:12:01.839 --> 00:12:04.480
which is basically a way to interact

00:12:04.480 --> 00:12:05.760
with all protocol

00:12:05.760 --> 00:12:07.279
uh I'm not going to look for it right

00:12:07.279 --> 00:12:09.120
now but it's uh

00:12:09.120 --> 00:12:10.800
it's a browser extension that is

00:12:10.800 --> 00:12:12.399
developed by one of my friends

00:12:12.399 --> 00:12:15.680
over at ranger whose name is v phone and

00:12:15.680 --> 00:12:16.160
uh

00:12:16.160 --> 00:12:18.240
it's very useful I'm someone who uses a

00:12:18.240 --> 00:12:19.680
lot of uh

00:12:19.680 --> 00:12:22.320
of uh all protocols and by the way I

00:12:22.320 --> 00:12:23.040
used to teach

00:12:23.040 --> 00:12:25.279
english okay to high schoolers and they

00:12:25.279 --> 00:12:27.279
were supremely worried

00:12:27.279 --> 00:12:29.600
when I show them my status line and they

00:12:29.600 --> 00:12:30.800
so kill

00:12:30.800 --> 00:12:34.000
and explore in my status line so as

00:12:34.000 --> 00:12:36.560
fellow emacs users you know that

00:12:36.560 --> 00:12:37.839
obviously kill

00:12:37.839 --> 00:12:40.880
means to kill a selection of text and

00:12:40.880 --> 00:12:44.320
keep it inside your clipboard

00:12:44.320 --> 00:12:47.279
but for my students who you know they

00:12:47.279 --> 00:12:48.320
were very worried

00:12:48.320 --> 00:12:51.600
about what their professor was up to

00:12:51.600 --> 00:12:53.600
doing his nights

00:12:53.600 --> 00:12:55.120
so let's see if we've got more questions

00:12:55.120 --> 00:12:56.560
so I'm showing you the questions on the

00:12:56.560 --> 00:12:57.920
rainbow so let's see if

00:12:57.920 --> 00:13:00.560
we've got more so people are posting a

00:13:00.560 --> 00:13:01.920
lot of questions now

00:13:01.920 --> 00:13:03.920
so how do you feel about archiving files

00:13:03.920 --> 00:13:06.399
in old mode and how can that work in

00:13:06.399 --> 00:13:09.360
so one of the thing when we think about

00:13:09.360 --> 00:13:10.240
optimization

00:13:10.240 --> 00:13:13.920
is yes archiving done trees

00:13:13.920 --> 00:13:16.240
is a good idea because it means that if

00:13:16.240 --> 00:13:17.920
we go back to the org element the way it

00:13:17.920 --> 00:13:18.720
works

00:13:18.720 --> 00:13:20.399
and we'll get into technical details

00:13:20.399 --> 00:13:22.079
afterwards I'm giving a presentation

00:13:22.079 --> 00:13:24.079
about all grown technical suspect

00:13:24.079 --> 00:13:26.880
aspects sorry so I'll have a chance to

00:13:26.880 --> 00:13:28.399
expand a little more on this

00:13:28.399 --> 00:13:31.360
but basically all elements need to uh

00:13:31.360 --> 00:13:32.160
every time

00:13:32.160 --> 00:13:35.279
it sees a to do it has to consider it

00:13:35.279 --> 00:13:38.320
even though it is a done to do why

00:13:38.320 --> 00:13:40.000
because let's say for instance that in

00:13:40.000 --> 00:13:41.839
your agenda you want to activate

00:13:41.839 --> 00:13:45.519
log mode which is going to show the

00:13:45.519 --> 00:13:48.959
tasks which are done now you could be

00:13:48.959 --> 00:13:49.519
clever

00:13:49.519 --> 00:13:51.440
and say oh okay the old agenda does not

00:13:51.440 --> 00:13:53.360
need to show don items so it's not going

00:13:53.360 --> 00:13:54.880
to look for them

00:13:54.880 --> 00:13:56.959
but the problem is that all elements is

00:13:56.959 --> 00:13:58.720
always called it always needs to pass

00:13:58.720 --> 00:13:59.519
the buffer

00:13:59.519 --> 00:14:01.839
you know uh nicodego as you who is the

00:14:01.839 --> 00:14:03.519
french developer who's worked a whole

00:14:03.519 --> 00:14:05.040
lot on all elements

00:14:05.040 --> 00:14:07.440
has gone through a lot of trouble to

00:14:07.440 --> 00:14:08.399
optimize all

00:14:08.399 --> 00:14:11.600
elements but the problem is

00:14:11.600 --> 00:14:13.279
there's just so much that we can do with

00:14:13.279 --> 00:14:14.720
a concurrent process

00:14:14.720 --> 00:14:18.560
and right now it leaves somewhat

00:14:18.560 --> 00:14:21.120
uh you know things to be desired but

00:14:21.120 --> 00:14:22.079
we're working on it

00:14:22.079 --> 00:14:24.800
and one more time I feel like I spent

00:14:24.800 --> 00:14:25.839
half of this talk

00:14:25.839 --> 00:14:28.000
teasing my next talks but I'll be

00:14:28.000 --> 00:14:29.360
talking more about this

00:14:29.360 --> 00:14:31.279
in my future talks in about one to two

00:14:31.279 --> 00:14:32.639
hours

00:14:32.639 --> 00:14:34.959
so continuing with questions how big are

00:14:34.959 --> 00:14:36.079
my org files

00:14:36.079 --> 00:14:37.760
so in the background I'm just going to

00:14:37.760 --> 00:14:39.839
check how many lines I have in my main

00:14:39.839 --> 00:14:40.720
file

00:14:40.720 --> 00:14:42.959
so in my own file so the one I told you

00:14:42.959 --> 00:14:44.079
about where I keep all

00:14:44.079 --> 00:14:47.279
my to do gtd stuff I have

00:14:47.279 --> 00:14:50.720
38 000 lines which is

00:14:50.720 --> 00:14:54.000
you know it's sizable definitely

00:14:54.000 --> 00:14:57.040
but I do archive a lot of stuff

00:14:57.040 --> 00:14:58.480
so that might be a slight difference

00:14:58.480 --> 00:15:00.880
between uh my myself and carl voight

00:15:00.880 --> 00:15:02.079
even though I don't remember if they

00:15:02.079 --> 00:15:04.880
actually archive stuff

00:15:04.880 --> 00:15:06.639
so does it not consume more resources

00:15:06.639 --> 00:15:08.480
and time to load multiple files

00:15:08.480 --> 00:15:10.839
files than a large file or the same

00:15:10.839 --> 00:15:12.560
content now

00:15:12.560 --> 00:15:15.839
theoretically yes having many files

00:15:15.839 --> 00:15:19.279
open concurrently is slightly slower

00:15:19.279 --> 00:15:22.240
than having one main file opened

00:15:22.240 --> 00:15:24.160
now the problem is for those of you who

00:15:24.160 --> 00:15:25.279
have large files

00:15:25.279 --> 00:15:27.199
you may have noticed that when you are

00:15:27.199 --> 00:15:29.360
scrolling in a very large file

00:15:29.360 --> 00:15:32.560
it starts taking quite a bit of time why

00:15:32.560 --> 00:15:34.480
it's because you know in old mode you

00:15:34.480 --> 00:15:35.920
have a lot of content

00:15:35.920 --> 00:15:38.959
that is hidden so when you have

00:15:38.959 --> 00:15:40.959
the view mode which hides as much stuff

00:15:40.959 --> 00:15:43.040
as possible means meaning that you only

00:15:43.040 --> 00:15:43.600
see

00:15:43.600 --> 00:15:45.360
the top heading and I'm checking the

00:15:45.360 --> 00:15:46.880
time I mean don't worry I'm I'm finished

00:15:46.880 --> 00:15:50.240
on this one

00:15:50.240 --> 00:15:52.160
when you're hiding a whole lot of stuff

00:15:52.160 --> 00:15:53.360
you know orgmo

00:15:53.360 --> 00:15:54.720
needs to keep track or I should say

00:15:54.720 --> 00:15:56.959
emacs needs to keep track of which areas

00:15:56.959 --> 00:15:58.160
of text to show

00:15:58.160 --> 00:16:00.560
and which areas of text to hide and the

00:16:00.560 --> 00:16:02.320
problem is that when you're hiding stuff

00:16:02.320 --> 00:16:04.480
let's say you're moving from line the

00:16:04.480 --> 00:16:06.320
first heading to the second heading

00:16:06.320 --> 00:16:08.639
but you've got like 10 000 lines between

00:16:08.639 --> 00:16:09.839
those two headings

00:16:09.839 --> 00:16:11.519
well he max needs to compute the

00:16:11.519 --> 00:16:13.680
difference between the two passages

00:16:13.680 --> 00:16:15.680
and that takes quite a lot of time and

00:16:15.680 --> 00:16:17.040
in that that's my

00:16:17.040 --> 00:16:18.560
why you might realize that it's a little

00:16:18.560 --> 00:16:20.560
choppy when you start scrolling in large

00:16:20.560 --> 00:16:21.199
files

00:16:21.199 --> 00:16:22.560
anyway I could be answering questions

00:16:22.560 --> 00:16:24.480
about org mode for literally two hours

00:16:24.480 --> 00:16:25.120
straight

00:16:25.120 --> 00:16:26.720
so I'm gonna end it over to the next

00:16:26.720 --> 00:16:28.639
speakers and I'll be seeing

00:16:28.639 --> 00:16:31.759
seeing you guys a little later thank you

00:16:31.759 --> 00:16:33.440
very much leo

00:16:33.440 --> 00:16:36.959
oh thank you yes bye

00:16:36.959 --> 00:16:39.839
bye