0:00:00.240,0:00:03.679
I mean we are ahead of the schedule a

0:00:01.520,0:00:05.680
little bit but I mean we also was a

0:00:03.679,0:00:09.040
little bit earlier in the day

0:00:05.680,0:00:10.800
so yeah yeah I'd say that's fine go for

0:00:09.040,0:00:14.240
it take it away

0:00:10.800,0:00:16.640
sure thank you so am I live already

0:00:14.240,0:00:17.359
you are now unmuted um yep your life

0:00:16.640,0:00:18.880
hello

0:00:17.359,0:00:20.720
spell it so I'll just start the timer to

0:00:18.880,0:00:22.720
make sure that I don't go overboard

0:00:20.720,0:00:24.160
all right so you are now muted okay good

0:00:22.720,0:00:26.960
to go now so

0:00:24.160,0:00:28.240
hello again everyone so I hope you had

0:00:26.960,0:00:30.880
well quite a lot of talks

0:00:28.240,0:00:32.000
ever since the last one I did and all

0:00:30.880,0:00:35.040
more interesting

0:00:32.000,0:00:36.559
uh one after the other so um

0:00:35.040,0:00:38.239
you know I'm a bit in a bit of a weird

0:00:36.559,0:00:39.760
spot right now because I'm supposed to

0:00:38.239,0:00:40.239
be presenting to you as you can see on

0:00:39.760,0:00:42.879
my screen

0:00:40.239,0:00:44.960
one big-ass awk file multiple tiny ones

0:00:42.879,0:00:48.160
finally the end of the debate

0:00:44.960,0:00:49.760
and it sounds about as clickbaity

0:00:48.160,0:00:51.280
as you can possibly get with those

0:00:49.760,0:00:54.000
topics and by the way

0:00:51.280,0:00:55.760
uh credit where credit is due the title

0:00:54.000,0:00:57.039
is not mine it's actually from bastian

0:00:55.760,0:01:00.719
gary the current old

0:00:57.039,0:01:03.199
maintainer and yeah I wanted to

0:01:00.719,0:01:04.879
talk to you a little bit today about

0:01:03.199,0:01:07.600
this question because

0:01:04.879,0:01:09.040
if you are used to going on our slash

0:01:07.600,0:01:09.600
emacs you know the subreddit that we

0:01:09.040,0:01:11.840
have

0:01:09.600,0:01:13.200
if you go on I can use often you know

0:01:11.840,0:01:16.000
it's a question that

0:01:13.200,0:01:17.520
you see pop-up every once in a while

0:01:16.000,0:01:20.640
should I be using

0:01:17.520,0:01:24.159
one big file or should I be using

0:01:20.640,0:01:24.799
a lot of tiny files and I believe you

0:01:24.159,0:01:27.600
know

0:01:24.799,0:01:29.520
we've got defenders on both sides if I

0:01:27.600,0:01:32.479
just show you one examples

0:01:29.520,0:01:35.280
so we have carl voigt okay so he's one

0:01:32.479,0:01:37.920
of the organizers for the conference

0:01:35.280,0:01:40.000
he hears the guy who probably has the

0:01:37.920,0:01:42.000
biggest augment files

0:01:40.000,0:01:43.759
right now in all the people I know and

0:01:42.000,0:01:44.479
god knows I know plenty of people use

0:01:43.759,0:01:46.880
old mode

0:01:44.479,0:01:48.320
but if you just look at this line I hope

0:01:46.880,0:01:51.360
it's not too small you just

0:01:48.320,0:01:56.719
make it a little larger but

0:01:51.360,0:02:01.759
carl basically has a file with 126

0:01:56.719,0:02:04.560
000 lines and I'm just going to pause

0:02:01.759,0:02:06.399
and try to have you imagine how large a

0:02:04.560,0:02:08.399
file it actually is

0:02:06.399,0:02:10.000
just think about all of these lines

0:02:08.399,0:02:12.080
being tasked in your days

0:02:10.000,0:02:13.200
think about all those lines being about

0:02:12.080,0:02:14.400
little thoughts

0:02:13.200,0:02:17.200
you know that you've had throughout the

0:02:14.400,0:02:19.680
day or project that you were working on

0:02:17.200,0:02:20.720
and it's massive and you know one of the

0:02:19.680,0:02:23.920
problem that

0:02:20.720,0:02:27.680
uh calvoit actually approaches on

0:02:23.920,0:02:30.160
this topic is that it takes him roughly

0:02:27.680,0:02:32.400
20 seconds to get his old agenda going

0:02:30.160,0:02:35.680
which is a massive amount of time

0:02:32.400,0:02:37.720
I mean we have very fast computers now

0:02:35.680,0:02:39.200
you know ever since e-max was created in

0:02:37.720,0:02:42.319
1976

0:02:39.200,0:02:43.440
computers I have no idea how much faster

0:02:42.319,0:02:47.760
they've gotten

0:02:43.440,0:02:49.599
and yet you know for earth 1000 lines

0:02:47.760,0:02:51.120
emac seems to be choking and it's

0:02:49.599,0:02:52.720
certainly not reasonable in a way to

0:02:51.120,0:02:55.360
have to wait 20 seconds

0:02:52.720,0:02:57.040
just for your entire file to be passed

0:02:55.360,0:02:58.480
so basically what I want to do

0:02:57.040,0:03:00.879
and by the way I forgot to do the

0:02:58.480,0:03:02.879
presentation but I'm leova I did this

0:03:00.879,0:03:05.519
before for those who were around

0:03:02.879,0:03:06.640
and I um help maintain a software which

0:03:05.519,0:03:08.560
is called orgrom

0:03:06.640,0:03:09.840
and that's the expertise that I have on

0:03:08.560,0:03:11.760
the topic

0:03:09.840,0:03:13.599
actually if you go online I do have a

0:03:11.760,0:03:15.440
github page I will make sure that you

0:03:13.599,0:03:18.640
have all the links available afterwards

0:03:15.440,0:03:20.720
but I do publish my init files

0:03:18.640,0:03:22.319
and you can see if you scroll at the

0:03:20.720,0:03:23.200
bottom I have a little demonstration

0:03:22.319,0:03:25.519
which shows you

0:03:23.200,0:03:27.440
the fancy things that I can do with my

0:03:25.519,0:03:28.159
old mood setup and that might be even

0:03:27.440,0:03:30.720
interesting

0:03:28.159,0:03:32.319
in lights of the talk you've just had

0:03:30.720,0:03:34.080
about gtd stuff because

0:03:32.319,0:03:36.159
the first one is about how I end all my

0:03:34.080,0:03:39.680
projects the second one is about

0:03:36.159,0:03:40.000
the flow from a task uh as I work on it

0:03:39.680,0:03:41.519
so

0:03:40.000,0:03:43.120
I won't spend too much time on this but

0:03:41.519,0:03:45.440
basically that's my expertise

0:03:43.120,0:03:46.959
I have spent eight years working with

0:03:45.440,0:03:48.959
working with org mode

0:03:46.959,0:03:50.720
three of them actually thinking about

0:03:48.959,0:03:54.080
writing packages

0:03:50.720,0:03:55.680
and the thing is if I go into a little

0:03:54.080,0:03:57.760
bit of details and obviously it's only a

0:03:55.680,0:04:00.720
lighting talk so I won't have time to

0:03:57.760,0:04:01.840
actually go really in depth about it but

0:04:00.720,0:04:03.599
there is something

0:04:01.840,0:04:05.200
in the ultimate libraries which is

0:04:03.599,0:04:07.000
called org elements

0:04:05.200,0:04:08.319
and you have the name right there org

0:04:07.000,0:04:11.439
element.el

0:04:08.319,0:04:12.319
dot el being for e-lisp file and as you

0:04:11.439,0:04:14.799
can see

0:04:12.319,0:04:16.239
the page it's on the work wiki so it's

0:04:14.799,0:04:19.280
accessible by everyone

0:04:16.239,0:04:23.759
but it's basically the api that

0:04:19.280,0:04:26.400
org mode uses to pass all mode files

0:04:23.759,0:04:27.199
so for those who don't know passing

0:04:26.400,0:04:29.360
means basically

0:04:27.199,0:04:30.880
checking a file checking all the content

0:04:29.360,0:04:32.880
of the file and extracting all the

0:04:30.880,0:04:34.960
information that we need from that file

0:04:32.880,0:04:36.560
and as you can imagine you all have

0:04:34.960,0:04:38.240
augmented files in your mind

0:04:36.560,0:04:39.840
well you know they can be fairly complex

0:04:38.240,0:04:41.759
you know you can have properties

0:04:39.840,0:04:43.040
you can have contextual information like

0:04:41.759,0:04:45.199
if you write a line

0:04:43.040,0:04:46.560
which starts at column zero which means

0:04:45.199,0:04:48.000
at the left

0:04:46.560,0:04:49.680
you know it doesn't have the same

0:04:48.000,0:04:52.639
meaning whether or not it is

0:04:49.680,0:04:54.160
before the beginning of a headline or if

0:04:52.639,0:04:55.199
it is after the beginning of a red line

0:04:54.160,0:04:57.759
you know it's going to be

0:04:55.199,0:04:58.960
relatively different hierarchically

0:04:57.759,0:05:01.759
speaking

0:04:58.960,0:05:02.639
and so the problem when it comes to the

0:05:01.759,0:05:05.759
question of

0:05:02.639,0:05:08.560
many files versus one big file or

0:05:05.759,0:05:09.600
few big files is that we always have to

0:05:08.560,0:05:12.880
keep in mind

0:05:09.600,0:05:15.680
what org elements want you to do

0:05:12.880,0:05:17.440
and the thing is there are plenty of

0:05:15.680,0:05:18.400
problems when it comes to passing file

0:05:17.440,0:05:21.360
the first one

0:05:18.400,0:05:22.160
being obviously that emacs is a single

0:05:21.360,0:05:24.880
thread

0:05:22.160,0:05:26.400
process or has some threading

0:05:24.880,0:05:28.639
capabilities we're not going to go into

0:05:26.400,0:05:32.400
the details right now that's not my goal

0:05:28.639,0:05:35.919
but it makes it incredibly hard to

0:05:32.400,0:05:39.280
parallelize uh passing processes as

0:05:35.919,0:05:42.320
we currently with the current technology

0:05:39.280,0:05:44.080
and so you'd have to imagine that if you

0:05:42.320,0:05:46.479
have a very large files if you go back

0:05:44.080,0:05:49.199
to the example of carl voice from before

0:05:46.479,0:05:50.000
100 000 lines that means that you have

0:05:49.199,0:05:52.320
to scan

0:05:50.000,0:05:53.759
through every single line basically

0:05:52.320,0:05:56.080
because sometimes let's just say that

0:05:53.759,0:05:59.440
you have a property drawer for instance

0:05:56.080,0:06:03.520
which tells you oh okay uh this tree

0:05:59.440,0:06:05.120
has the tag foo so the problem is there

0:06:03.520,0:06:08.720
are multiple ways for you

0:06:05.120,0:06:11.840
to define a tag okay so you can use the

0:06:08.720,0:06:14.000
usual way which is about wrapping in

0:06:11.840,0:06:16.160
columns the tag at the end of a heading

0:06:14.000,0:06:17.360
so for instance if I I'm not going to

0:06:16.160,0:06:18.240
switch to emac that's going to waste too

0:06:17.360,0:06:21.039
much time

0:06:18.240,0:06:21.520
but that's one way to say your time but

0:06:21.039,0:06:23.520
say

0:06:21.520,0:06:25.360
you have tag inheritance which means

0:06:23.520,0:06:28.160
that when you have a parent with a tag

0:06:25.360,0:06:29.520
you also want the child to inherit the

0:06:28.160,0:06:32.400
tag so if you have

0:06:29.520,0:06:33.680
first heading with the typhoo you have

0:06:32.400,0:06:37.520
the first subheading

0:06:33.680,0:06:39.680
and the tag foo is implied now imagine

0:06:37.520,0:06:41.039
having to do that with a file that is

0:06:39.680,0:06:44.160
completely nested

0:06:41.039,0:06:47.280
a file that has maybe 9 10

0:06:44.160,0:06:49.039
11 levels of depth to it

0:06:47.280,0:06:51.039
it's mind-bogglingly complicated for the

0:06:49.039,0:06:52.639
software to do that knowing that I've

0:06:51.039,0:06:55.919
told you about tags

0:06:52.639,0:06:58.639
but any property can be inheritable

0:06:55.919,0:07:00.240
anything like priorities even though why

0:06:58.639,0:07:03.759
would you do this

0:07:00.240,0:07:05.599
you can have groups you can all this and

0:07:03.759,0:07:07.199
as someone who went through the trouble

0:07:05.599,0:07:08.560
of optimizing his old agenda so

0:07:07.199,0:07:11.280
basically if we go back to the

0:07:08.560,0:07:12.160
gifts gifs oh god we've already had this

0:07:11.280,0:07:14.479
discussion

0:07:12.160,0:07:16.400
between the git and magit and now I've

0:07:14.479,0:07:18.080
started jeff and gif and I only have one

0:07:16.400,0:07:19.599
more minute left to do so so let's just

0:07:18.080,0:07:23.599
say I'm going to say gif

0:07:19.599,0:07:26.880
just to spice people so if you go on

0:07:23.599,0:07:29.120
the way I organize my agenda what I did

0:07:26.880,0:07:30.960
in order to keep my agenda build time

0:07:29.120,0:07:33.440
under two seconds

0:07:30.960,0:07:35.520
is that I've rewritten a whole lot of

0:07:33.440,0:07:36.560
codes to be able to pass my organ gender

0:07:35.520,0:07:40.080
files

0:07:36.560,0:07:41.360
so the thing is I'm going to be talking

0:07:40.080,0:07:43.440
more about this later

0:07:41.360,0:07:44.479
I only have let's say one minutes to

0:07:43.440,0:07:47.440
conclude

0:07:44.479,0:07:48.479
so as you've gathered I'm not going to

0:07:47.440,0:07:51.039
be giving you the answer

0:07:48.479,0:07:53.440
right now I'm going to be talking about

0:07:51.039,0:07:55.680
orgrum a little later which is about

0:07:53.440,0:07:57.759
following the principle of having many

0:07:55.680,0:08:01.120
small files

0:07:57.759,0:08:02.960
but as someone who has been using

0:08:01.120,0:08:04.879
one large file to manage my life you

0:08:02.960,0:08:08.319
know I'm sitting on the fence

0:08:04.879,0:08:10.560
I do not know which one is the best

0:08:08.319,0:08:12.240
but I hope that my presentation has

0:08:10.560,0:08:15.199
given you a little id

0:08:12.240,0:08:15.520
of what goes on behind the principles

0:08:15.199,0:08:16.560
and

0:08:15.520,0:08:18.560
you also need to think about the

0:08:16.560,0:08:19.120
philosophy behind the organization of

0:08:18.560,0:08:21.039
your notes

0:08:19.120,0:08:23.280
but I hope to be approaching this topic

0:08:21.039,0:08:25.360
with you in about

0:08:23.280,0:08:27.520
two hours or so maybe one hour actually

0:08:25.360,0:08:28.960
so I'm actually finished I've decided to

0:08:27.520,0:08:31.520
leave you two minutes of questions

0:08:28.960,0:08:32.880
so uh if someone could feed me the

0:08:31.520,0:08:34.399
question that might be best

0:08:32.880,0:08:36.240
because I don't want oh actually I can

0:08:34.399,0:08:39.919
just open the year

0:08:36.240,0:08:40.800
I can just open it give me a second okay

0:08:39.919,0:08:43.039
ah

0:08:40.800,0:08:43.839
just loading up huh I might stop showing

0:08:43.039,0:08:46.959
my screen

0:08:43.839,0:08:47.519
that might make it easier so I mean if

0:08:46.959,0:08:49.360
you can make

0:08:47.519,0:08:52.000
myself big now on the screen that would

0:08:49.360,0:08:55.839
be splendid yeah sure

0:08:52.000,0:08:58.720
thank you so uh where are we

0:08:55.839,0:09:00.160
question 12. okay so what's better one

0:08:58.720,0:09:02.160
big file

0:09:00.160,0:09:03.120
I did is it did a job to tell me that I

0:09:02.160,0:09:04.240
haven't answered the question because

0:09:03.120,0:09:06.320
someone just

0:09:04.240,0:09:08.080
asked me the question well personally if

0:09:06.320,0:09:08.560
I were to give you a quick answer in

0:09:08.080,0:09:11.600
like

0:09:08.560,0:09:13.920
20 seconds personally I think it's a

0:09:11.600,0:09:15.680
question that is contextually based

0:09:13.920,0:09:17.839
do you want something that is efficient

0:09:15.680,0:09:21.200
as far as optimization is concerned

0:09:17.839,0:09:23.440
then you need to think about

0:09:21.200,0:09:24.640
this and personally for all the

0:09:23.440,0:09:26.640
organization that I do

0:09:24.640,0:09:27.760
all this stuff all the to-do's that I

0:09:26.640,0:09:30.080
handle

0:09:27.760,0:09:31.519
I like to do this in one simple big file

0:09:30.080,0:09:33.760
because you benefit from all the

0:09:31.519,0:09:36.320
refiling capabilities of log mode

0:09:33.760,0:09:37.200
so I would do that but for knowledge

0:09:36.320,0:09:40.080
management

0:09:37.200,0:09:41.279
for note-taking and all this well I'd

0:09:40.080,0:09:42.959
much rather follow the

0:09:41.279,0:09:44.480
orgrom way of doing things which is

0:09:42.959,0:09:48.240
about having many

0:09:44.480,0:09:50.000
small files okay I'm not getting any

0:09:48.240,0:09:52.080
more questions I'm not sure if there is

0:09:50.000,0:09:53.040
one on ise that could be fed to me

0:09:52.080,0:09:56.399
otherwise I'm

0:09:53.040,0:09:57.040
happy to to uh pass over to the next uh

0:09:56.399,0:09:59.360
speaker

0:09:57.040,0:10:01.360
and by the way just before I finish your

0:09:59.360,0:10:04.399
world is a lie it's not a three-piece

0:10:01.360,0:10:06.520
suit I'm wearing jeans below so I hope

0:10:04.399,0:10:09.610
that satisfies your curiosity

0:10:06.520,0:10:09.610
[Music]

0:10:10.640,0:10:15.040
okay there's one more question appearing

0:10:12.640,0:10:17.680
but otherwise one big file to have

0:10:15.040,0:10:19.760
everything so I'm putting you on the

0:10:17.680,0:10:21.040
spot I believe it was such a short talk

0:10:19.760,0:10:23.600
you know the problem is

0:10:21.040,0:10:24.720
I just wanted to give you a little

0:10:23.600,0:10:26.959
answer

0:10:24.720,0:10:27.920
a little you know path of thinking on

0:10:26.959,0:10:29.839
this topic

0:10:27.920,0:10:31.600
but obviously it's a topic I could be

0:10:29.839,0:10:33.200
spending 40 minutes on but

0:10:31.600,0:10:35.120
I'm going to be drained you're going to

0:10:33.200,0:10:35.680
be drained nobody's going to be happy if

0:10:35.120,0:10:37.920
I do this

0:10:35.680,0:10:37.920
so

0:10:39.440,0:10:42.880
and someone asked me if I switch between

0:10:41.200,0:10:46.560
british and french accents

0:10:42.880,0:10:48.480
so a little a little secret for you um

0:10:46.560,0:10:49.760
when I'm stressed I tend to relate to a

0:10:48.480,0:10:53.760
french accent

0:10:49.760,0:10:56.160
so you can measure the amount of stress

0:10:53.760,0:10:58.880
that I'm feeling during this talk

0:10:56.160,0:11:00.560
with the amount of h's that I drop and

0:10:58.880,0:11:02.720
the amount of uh

0:11:00.560,0:11:04.399
sheer fright that you can see sometimes

0:11:02.720,0:11:07.200
in my eyes when I'm thinking about what

0:11:04.399,0:11:07.200
to say next

0:11:08.240,0:11:11.360
all right sir so I mean do you believe

0:11:10.880,0:11:14.240
we can

0:11:11.360,0:11:15.519
leave it at that and uh I'll be you

0:11:14.240,0:11:17.040
people will see plenty more with me

0:11:15.519,0:11:20.000
later on anyway

0:11:17.040,0:11:20.640
right um so looking at the schedule I

0:11:20.000,0:11:23.920
think

0:11:20.640,0:11:27.120
your talk has until like 202 meaning

0:11:23.920,0:11:28.000
like five or six minutes from now oh

0:11:27.120,0:11:30.000
right

0:11:28.000,0:11:31.680
yeah so if you do like to take like one

0:11:30.000,0:11:33.920
or two questions to add two more

0:11:31.680,0:11:37.040
questions by all means

0:11:33.920,0:11:38.320
okay so uh someone has asked me what is

0:11:37.040,0:11:40.640
the emacs icon

0:11:38.320,0:11:42.880
icon sorry see another french accent

0:11:40.640,0:11:44.880
here uh in my status bar

0:11:42.880,0:11:46.640
uh oh sorry I'm not sharing anymore uh I

0:11:44.880,0:11:49.200
might just share again just so that

0:11:46.640,0:11:53.120
everyone can catch a glimpse of that

0:11:49.200,0:11:54.880
uh there we go allow

0:11:53.120,0:11:56.240
so it should be so if you could make me

0:11:54.880,0:11:56.959
small again I'm in I'm not sure if it's

0:11:56.240,0:12:00.480
going to do it

0:11:56.959,0:12:01.839
by itself but I do have a little icon

0:12:00.480,0:12:04.480
here in my status bar

0:12:01.839,0:12:05.760
which is basically a way to interact

0:12:04.480,0:12:07.279
with all protocol

0:12:05.760,0:12:09.120
uh I'm not going to look for it right

0:12:07.279,0:12:10.800
now but it's uh

0:12:09.120,0:12:12.399
it's a browser extension that is

0:12:10.800,0:12:15.680
developed by one of my friends

0:12:12.399,0:12:16.160
over at ranger whose name is v phone and

0:12:15.680,0:12:18.240
uh

0:12:16.160,0:12:19.680
it's very useful I'm someone who uses a

0:12:18.240,0:12:22.320
lot of uh

0:12:19.680,0:12:23.040
of uh all protocols and by the way I

0:12:22.320,0:12:25.279
used to teach

0:12:23.040,0:12:27.279
english okay to high schoolers and they

0:12:25.279,0:12:29.600
were supremely worried

0:12:27.279,0:12:30.800
when I show them my status line and they

0:12:29.600,0:12:34.000
so kill

0:12:30.800,0:12:36.560
and explore in my status line so as

0:12:34.000,0:12:37.839
fellow emacs users you know that

0:12:36.560,0:12:40.880
obviously kill

0:12:37.839,0:12:44.320
means to kill a selection of text and

0:12:40.880,0:12:47.279
keep it inside your clipboard

0:12:44.320,0:12:48.320
but for my students who you know they

0:12:47.279,0:12:51.600
were very worried

0:12:48.320,0:12:53.600
about what their professor was up to

0:12:51.600,0:12:55.120
doing his nights

0:12:53.600,0:12:56.560
so let's see if we've got more questions

0:12:55.120,0:12:57.920
so I'm showing you the questions on the

0:12:56.560,0:13:00.560
rainbow so let's see if

0:12:57.920,0:13:01.920
we've got more so people are posting a

0:13:00.560,0:13:03.920
lot of questions now

0:13:01.920,0:13:06.399
so how do you feel about archiving files

0:13:03.920,0:13:09.360
in old mode and how can that work in

0:13:06.399,0:13:10.240
so one of the thing when we think about

0:13:09.360,0:13:13.920
optimization

0:13:10.240,0:13:16.240
is yes archiving done trees

0:13:13.920,0:13:17.920
is a good idea because it means that if

0:13:16.240,0:13:18.720
we go back to the org element the way it

0:13:17.920,0:13:20.399
works

0:13:18.720,0:13:22.079
and we'll get into technical details

0:13:20.399,0:13:24.079
afterwards I'm giving a presentation

0:13:22.079,0:13:26.880
about all grown technical suspect

0:13:24.079,0:13:28.399
aspects sorry so I'll have a chance to

0:13:26.880,0:13:31.360
expand a little more on this

0:13:28.399,0:13:32.160
but basically all elements need to uh

0:13:31.360,0:13:35.279
every time

0:13:32.160,0:13:38.320
it sees a to do it has to consider it

0:13:35.279,0:13:40.000
even though it is a done to do why

0:13:38.320,0:13:41.839
because let's say for instance that in

0:13:40.000,0:13:45.519
your agenda you want to activate

0:13:41.839,0:13:48.959
log mode which is going to show the

0:13:45.519,0:13:49.519
tasks which are done now you could be

0:13:48.959,0:13:51.440
clever

0:13:49.519,0:13:53.360
and say oh okay the old agenda does not

0:13:51.440,0:13:54.880
need to show don items so it's not going

0:13:53.360,0:13:56.959
to look for them

0:13:54.880,0:13:58.720
but the problem is that all elements is

0:13:56.959,0:13:59.519
always called it always needs to pass

0:13:58.720,0:14:01.839
the buffer

0:13:59.519,0:14:03.519
you know uh nicodego as you who is the

0:14:01.839,0:14:05.040
french developer who's worked a whole

0:14:03.519,0:14:07.440
lot on all elements

0:14:05.040,0:14:08.399
has gone through a lot of trouble to

0:14:07.440,0:14:11.600
optimize all

0:14:08.399,0:14:13.279
elements but the problem is

0:14:11.600,0:14:14.720
there's just so much that we can do with

0:14:13.279,0:14:18.560
a concurrent process

0:14:14.720,0:14:21.120
and right now it leaves somewhat

0:14:18.560,0:14:22.079
uh you know things to be desired but

0:14:21.120,0:14:24.800
we're working on it

0:14:22.079,0:14:25.839
and one more time I feel like I spent

0:14:24.800,0:14:28.000
half of this talk

0:14:25.839,0:14:29.360
teasing my next talks but I'll be

0:14:28.000,0:14:31.279
talking more about this

0:14:29.360,0:14:32.639
in my future talks in about one to two

0:14:31.279,0:14:34.959
hours

0:14:32.639,0:14:36.079
so continuing with questions how big are

0:14:34.959,0:14:37.760
my org files

0:14:36.079,0:14:39.839
so in the background I'm just going to

0:14:37.760,0:14:40.720
check how many lines I have in my main

0:14:39.839,0:14:42.959
file

0:14:40.720,0:14:44.079
so in my own file so the one I told you

0:14:42.959,0:14:47.279
about where I keep all

0:14:44.079,0:14:50.720
my to do gtd stuff I have

0:14:47.279,0:14:54.000
38 000 lines which is

0:14:50.720,0:14:57.040
you know it's sizable definitely

0:14:54.000,0:14:58.480
but I do archive a lot of stuff

0:14:57.040,0:15:00.880
so that might be a slight difference

0:14:58.480,0:15:02.079
between uh my myself and carl voight

0:15:00.880,0:15:04.880
even though I don't remember if they

0:15:02.079,0:15:06.639
actually archive stuff

0:15:04.880,0:15:08.480
so does it not consume more resources

0:15:06.639,0:15:10.839
and time to load multiple files

0:15:08.480,0:15:12.560
files than a large file or the same

0:15:10.839,0:15:15.839
content now

0:15:12.560,0:15:19.279
theoretically yes having many files

0:15:15.839,0:15:22.240
open concurrently is slightly slower

0:15:19.279,0:15:24.160
than having one main file opened

0:15:22.240,0:15:25.279
now the problem is for those of you who

0:15:24.160,0:15:27.199
have large files

0:15:25.279,0:15:29.360
you may have noticed that when you are

0:15:27.199,0:15:32.560
scrolling in a very large file

0:15:29.360,0:15:34.480
it starts taking quite a bit of time why

0:15:32.560,0:15:35.920
it's because you know in old mode you

0:15:34.480,0:15:38.959
have a lot of content

0:15:35.920,0:15:40.959
that is hidden so when you have

0:15:38.959,0:15:43.040
the view mode which hides as much stuff

0:15:40.959,0:15:43.600
as possible means meaning that you only

0:15:43.040,0:15:45.360
see

0:15:43.600,0:15:46.880
the top heading and I'm checking the

0:15:45.360,0:15:49.360
time I mean don't worry I'm I'm finished

0:15:46.880,0:15:49.360
on this one

0:15:50.240,0:15:53.360
when you're hiding a whole lot of stuff

0:15:52.160,0:15:54.720
you know orgmo

0:15:53.360,0:15:56.959
needs to keep track or I should say

0:15:54.720,0:15:58.160
emacs needs to keep track of which areas

0:15:56.959,0:16:00.560
of text to show

0:15:58.160,0:16:02.320
and which areas of text to hide and the

0:16:00.560,0:16:04.480
problem is that when you're hiding stuff

0:16:02.320,0:16:06.320
let's say you're moving from line the

0:16:04.480,0:16:08.639
first heading to the second heading

0:16:06.320,0:16:09.839
but you've got like 10 000 lines between

0:16:08.639,0:16:11.519
those two headings

0:16:09.839,0:16:13.680
well he max needs to compute the

0:16:11.519,0:16:15.680
difference between the two passages

0:16:13.680,0:16:17.040
and that takes quite a lot of time and

0:16:15.680,0:16:18.560
in that that's my

0:16:17.040,0:16:20.560
why you might realize that it's a little

0:16:18.560,0:16:21.199
choppy when you start scrolling in large

0:16:20.560,0:16:22.560
files

0:16:21.199,0:16:24.480
anyway I could be answering questions

0:16:22.560,0:16:25.120
about org mode for literally two hours

0:16:24.480,0:16:26.720
straight

0:16:25.120,0:16:28.639
so I'm gonna end it over to the next

0:16:26.720,0:16:31.759
speakers and I'll be seeing

0:16:28.639,0:16:33.440
seeing you guys a little later thank you

0:16:31.759,0:16:36.959
very much leo

0:16:33.440,0:16:39.839
oh thank you yes bye

0:16:36.959,0:16:39.839
bye