WEBVTT indexed by sachac
00:00:00.000 --> 00:00:03.667
... mentally over the next couple of days, but I can assure you
00:00:03.668 --> 00:00:06.759
that it will be many organizers in the background also
00:00:06.760 --> 00:00:10.199
working. You'll probably get to see us later on. But for now,
00:00:10.200 --> 00:00:12.775
without further ado, I want to say hi to Vincent.
00:00:12.776 --> 00:00:15.417
Hi, Vincent.
00:00:15.418 --> 00:00:17.458
Hi, thanks for having me.
00:00:17.459 --> 00:00:18.099
Yeah, and thanks for
00:00:18.140 --> 00:00:22.902
coming and thanks for presenting. I mean, you didn't decide
00:00:22.942 --> 00:00:25.704
to go first. It's mostly the time zone for you which decided
00:00:25.724 --> 00:00:28.883
for you because I believe you are in Japan, correctly. Yeah,
00:00:28.920 --> 00:00:33.039
exactly. So I'm living there now and it's very late. It's
00:00:33.040 --> 00:00:37.319
really funny to see everyone saying good morning in the
00:00:37.320 --> 00:00:39.959
chat. It's always the same for me. So personally, I'm in
00:00:39.960 --> 00:00:43.959
France. So for me, it's only 3 p.m. For you, it's probably 9 or
00:00:43.960 --> 00:00:47.959
10 p.m. if I'm correct. Already 11 here, yeah. It's already
00:00:47.960 --> 00:00:51.678
11, so thank you for staying up so late for us.
00:00:51.679 --> 00:00:55.181
And how about we just get started with the questions
00:00:55.182 --> 00:00:56.521
because you've just presented something
00:00:56.522 --> 00:00:59.200
that is very dear to my heart, which is
00:00:59.240 --> 00:01:01.959
writing academic paper with Org Mode, which is, for the
00:01:01.960 --> 00:01:05.279
record, how I got started with Org Roam and stuff like this.
00:01:05.280 --> 00:01:08.799
So, unless you've got anything else to add on top of your
00:01:08.800 --> 00:01:11.839
presentation that wasn't able to fit in, I suggest we just
00:01:11.840 --> 00:01:16.559
start taking questions. All right. So yeah, right now I'm
00:01:16.560 --> 00:01:19.439
reading the question from IRC and also from the pad. So I
00:01:19.440 --> 00:01:23.159
guess I'm gonna take what's already written there.
NOTE Q: I'd be interested how to start this journey of writing academic papers in Org-Roam when not having used Emacs Org-Mode yet? Thanks!
00:01:23.160 --> 00:01:27.359
So the first one is asking, I'd be interested in how to start this
00:01:27.360 --> 00:01:30.239
journey to write academic paper in org-roam when not having
00:01:30.240 --> 00:01:36.639
used Emacs org mode yet. So I saw this one before and I guess it
00:01:36.640 --> 00:01:43.039
would be possible to do that, to use Org documents only
00:01:43.040 --> 00:01:46.759
as the way that you are writing papers. Maybe you can
00:01:46.760 --> 00:01:51.959
just use that as a template that you're going to export.
00:01:51.960 --> 00:01:54.959
If you are familiar with LaTeX, it's going to be more useful,
00:01:54.960 --> 00:01:59.599
and maybe more convenient to work with inside of
00:01:59.600 --> 00:02:04.999
Emacs. But then I'm not 100% sure if that's... How do you say
00:02:05.000 --> 00:02:10.799
that? Maybe, in my opinion, the benefits of using
00:02:10.800 --> 00:02:14.679
org-roam in that setup is that you can link the things. For
00:02:14.680 --> 00:02:18.839
me, I'm using the search function for org-roam to just
00:02:18.840 --> 00:02:21.959
navigate between the files. So that's really some, a good
00:02:21.960 --> 00:02:26.119
advantage, but like, yeah, that could be, like Leo said in
00:02:26.120 --> 00:02:28.039
the presentation, that's some, maybe that's something you
00:02:28.040 --> 00:02:35.839
can start using org-mode with to write papers. So yeah.
NOTE Q: How about connecting Emacs Org-Roam to Zotero? Is that something you have experience with?
00:02:35.840 --> 00:02:38.879
Second question. So how about connecting Emacs or Roam
00:02:38.880 --> 00:02:42.079
to Zotero? Is that something that you have experience with?
00:02:42.080 --> 00:02:47.119
Not at all. Actually, I used briefly Zotero in the past and I
00:02:47.120 --> 00:02:51.439
really didn't like it or didn't really get into that. I don't
00:02:51.440 --> 00:02:55.599
know. But right now,
NOTE Q: Out of curiosity, how do you manage your bibliography? Do you do it from inside Emacs, or using a separate program like Zotero?
00:02:55.600 --> 00:03:00.319
I don't connect that at all. The question after, out of
00:03:00.320 --> 00:03:03.559
curiosity, how do you manage your bibliography? Do you do it
00:03:03.560 --> 00:03:06.519
from inside Emacs or using a separate program, ex: Zotero?
00:03:06.520 --> 00:03:09.119
Because personally, I have struggled to do it from Emacs,
00:03:09.120 --> 00:03:13.879
though I have wanted to for some time. So the way I manage that
00:03:13.880 --> 00:03:20.799
is I just have a couple of .bib files that I edit by hand, where
00:03:20.800 --> 00:03:25.359
I put the reference when I find them.
00:03:25.360 --> 00:03:28.599
And yeah, I just showed very briefly in the presentation,
00:03:28.600 --> 00:03:34.119
but the way.
00:03:34.120 --> 00:03:39.519
One of the great thing with the org reference system is that
00:03:39.520 --> 00:03:43.239
if you have your bibliographic files that are connected to
00:03:43.240 --> 00:03:47.959
that system, you can just like, you can put the link, the
00:03:47.960 --> 00:03:51.879
reference to the paper, like click on it from your org note,
00:03:51.880 --> 00:03:56.479
and then you can open the PDF. You can open the DOI link to open
00:03:56.480 --> 00:04:00.719
the whatever publisher page.
00:04:00.720 --> 00:04:10.159
So no, I don't use Zotero and I just edit bib or bib files by
00:04:10.160 --> 00:04:12.959
hand in Emacs.
00:04:12.960 --> 00:04:16.159
I was just going to add something because you know
00:04:16.160 --> 00:04:19.024
org-roam-bibtex is actually one of the packages that I
00:04:19.025 --> 00:04:25.399
developed and I got it working with Zotero because for me it
00:04:25.400 --> 00:04:28.524
was convenient. I was studying humanities and for me it was
00:04:28.525 --> 00:04:32.599
very easy to connect reference taken in my browser with
00:04:32.600 --> 00:04:36.799
Zotero and just post-processing them a little bit but it is
00:04:36.800 --> 00:04:40.279
possible to make org-roam, org-roam-bibtex and Zotero
00:04:40.280 --> 00:04:44.959
work together. But it's a little bit of an involved process to
00:04:44.960 --> 00:04:49.439
get everything working in Emacs.
00:04:49.440 --> 00:04:54.519
Yeah, for sure. And
00:04:54.520 --> 00:05:01.999
yeah, I guess the way I'm doing it, I understand the appeal
00:05:02.000 --> 00:05:03.839
for having it integrated in the browser. Maybe
00:05:03.840 --> 00:05:06.279
that's something I should look up, actually, because right
00:05:06.280 --> 00:05:09.359
now I just like doing it very much by hand, like going on the
00:05:09.360 --> 00:05:15.199
publisher page and copying the bibtex block and
00:05:15.200 --> 00:05:20.039
just using putting that in my file. Yes, it can be not a very
00:05:20.040 --> 00:05:23.359
efficient workflow on that side. But after that, you're
00:05:23.360 --> 00:05:26.599
having the PDF and having it inside the note.
00:05:26.600 --> 00:05:30.759
Yeah, it's great. Yeah. To some extent, it kind of depends on
00:05:30.760 --> 00:05:33.319
the reference system that is used by the field in which you
00:05:33.320 --> 00:05:36.279
are or the university in which you're publishing. Because
00:05:36.280 --> 00:05:39.519
sometimes, you know, you're going to have some basic BibTeX
00:05:39.520 --> 00:05:41.479
file and sometimes you're going to have better BibTeX
00:05:41.480 --> 00:05:44.959
files. And those are very different metadata that you need
00:05:44.960 --> 00:05:49.119
to reconcile. And depending on which LaTeX compiler you're
00:05:49.120 --> 00:05:52.439
using, be it zLaTeX[??], be it regular LaTeX, lualatex, it's
00:05:52.440 --> 00:05:55.439
going to be all different. So it's a whole can of worms that
00:05:55.440 --> 00:05:57.799
I'm not sure we want to be opening now. But if you are
00:05:57.800 --> 00:06:00.999
interested and if you're not too attached about getting
00:06:01.000 --> 00:06:03.679
everything right, it's really easy to get started with
00:06:03.680 --> 00:06:06.319
stuff like org-roam-bibtex. It's supposed to get you
00:06:06.320 --> 00:06:11.319
most of the way down to a working setup. And if you need to get
00:06:11.320 --> 00:06:14.359
everything working down to the comma based on your
00:06:14.360 --> 00:06:16.479
reference system, that's going to be a little harder. But
00:06:16.480 --> 00:06:19.439
it's possible. I managed to do it and many people actually
00:06:19.440 --> 00:06:22.599
managed to do it. Okay, anyway, so let's move on to the next
NOTE Q: How do you start a new document?
00:06:22.600 --> 00:06:26.679
question. All right, so the next question asking how do you
00:06:26.680 --> 00:06:30.999
start a new document? There are a lot of headers you have to
00:06:31.000 --> 00:06:34.639
set up. Do you use a template? I'm curious if you use your
00:06:34.640 --> 00:06:38.839
snippets to deal with all of these LaTeX org metacommands.
00:06:38.840 --> 00:06:44.759
So I don't use a snippets template of any kind for that.
00:06:44.760 --> 00:06:47.279
Probably I should. That's actually a good idea. I'm
00:06:47.280 --> 00:06:51.279
probably going to look into that. No, the way I do actually is
00:06:51.280 --> 00:06:56.199
I just reuse some previous documents. I copy it, delete all
00:06:56.200 --> 00:07:01.439
the contents and adjust it until it works the way I like.
00:07:01.440 --> 00:07:09.679
The main issue in general after that step is to make it work
00:07:09.680 --> 00:07:13.999
with the template I receive and Let's say if I have some
00:07:14.000 --> 00:07:20.839
template that needs to work with another LaTeX compiler,
00:07:20.840 --> 00:07:26.599
I'm probably going to try to copy an existing file that I have
00:07:26.600 --> 00:07:30.959
that uses the same compiler to save me some work. But yeah,
00:07:30.960 --> 00:07:37.119
no, I don't use any snippet or something. Probably I should,
00:07:37.120 --> 00:07:40.879
but I'm just doing it the quick and dirty way to just copy some
00:07:40.880 --> 00:07:41.719
existing thing.
NOTE Q: What do you think of using citar with org-roam-bibtex?
00:07:41.720 --> 00:07:48.319
Then what do you think of citar with org-roam-bibtex? It seems
00:07:48.320 --> 00:07:55.999
that bibtex completion is tied to org-roam-bibtex. I don't
00:07:56.000 --> 00:08:02.079
know. I never really looked into citar that much. I
00:08:02.080 --> 00:08:06.799
don't know about that. I don't know either, so I'm not going
00:08:06.800 --> 00:08:07.759
to be able to help on this one.
00:08:07.760 --> 00:08:17.119
Because yeah, the bibtex completion is tied to the overall
00:08:17.120 --> 00:08:24.799
bibtex. I guess so. So what I'm interpreting, because I do,
00:08:24.800 --> 00:08:30.039
so BibTeX completion is the single motor that drives helm
00:08:30.040 --> 00:08:32.719
BibTeX and Ivy BibTeX. Perhaps there's another
00:08:32.720 --> 00:08:35.679
alternative now that is using the Vertico stack for
00:08:35.680 --> 00:08:40.399
completion. But org-roam-bibtex was interfacing with BibTeX
00:08:40.400 --> 00:08:46.679
completion to retrieve all the references from a bib file.
00:08:46.680 --> 00:08:50.599
and I assume citar would be something very similar in a way
00:08:50.600 --> 00:08:54.039
that it interfaces with a bib file, but I couldn't tell you
00:08:54.040 --> 00:08:57.439
more. I need to explore a little more and sadly I haven't
00:08:57.440 --> 00:09:00.759
touched any of this stack in like three years, so I'm a little
00:09:00.760 --> 00:09:03.199
out of touch. I guess this is what comes with leaving
00:09:03.200 --> 00:09:07.519
academia to go work as a corporate developer. I'm no longer
00:09:07.520 --> 00:09:10.319
so interested in the publishing process, even though I'm
00:09:10.320 --> 00:09:12.799
obviously very appreciative of people who still do, and
00:09:12.800 --> 00:09:13.679
especially people who use
00:09:13.680 --> 00:09:20.239
Yeah, same here. I definitely going to look into the citar
00:09:20.240 --> 00:09:23.399
package to see what's possible. Maybe can be using in some
00:09:23.400 --> 00:09:26.319
way that is useful for me. Yeah.
NOTE Q: Most academic journals insist that papers are formatted in their own custom LaTeX documentclass. Does org-roam make it easy to do that?
00:09:26.320 --> 00:09:30.919
And if I go to the next question, so most academic journal
00:09:30.920 --> 00:09:33.639
insist that paper are formatted in their own custom LaTeX
00:09:33.640 --> 00:09:38.199
document class. Does org-roam make it easy to do that? The
00:09:38.200 --> 00:09:43.239
answer is no. That's mostly what I was presenting in the
00:09:43.240 --> 00:09:44.279
slide.
00:09:44.280 --> 00:09:48.000
Actually, that's also why I made the presentation, because
00:09:48.001 --> 00:09:51.940
if someone has a solution, I would gladly take it. No, the way
00:09:51.941 --> 00:09:57.500
I do it is that I have to add a... I don't have that on top of my head.
00:09:57.501 --> 00:10:09.582
plus. Yeah, exactly. So I just make a custom org-latex class with the
00:10:09.583 --> 00:10:16.159
name of the latex template. In general, I think people use
00:10:16.160 --> 00:10:19.359
that to redefine like stuff like section and subsection,
00:10:19.360 --> 00:10:24.279
but for me, I just, it shows in the slide where I just map the
00:10:24.280 --> 00:10:27.239
section to the same section. I just changed the name of the
00:10:27.240 --> 00:10:33.719
class. And this way it allows to import the, the CLS and then
00:10:33.720 --> 00:10:39.079
the rest is just like putting the TeX template that is
00:10:39.080 --> 00:10:48.519
provided either in headers, in LaTeX headers at the top or
00:10:48.520 --> 00:10:56.079
Yeah, or just on a LaTeX block in the body of the document if
00:10:56.080 --> 00:11:02.039
that's needed, for example, for the acknowledgement.
00:11:02.040 --> 00:11:05.759
Sometimes they need some different formatting, but no,
00:11:05.760 --> 00:11:09.079
it's not really easy because it needs to modify some
00:11:09.080 --> 00:11:12.359
configuration in Emacs to do that. Then after that, a little
00:11:12.360 --> 00:11:15.719
bit like manually adapt the templates into your org notes.
00:11:15.720 --> 00:11:18.799
So that's a little bit some upfront work to do. But once it's
00:11:18.800 --> 00:11:22.159
done, your notes are going to be exported exactly like the
00:11:22.160 --> 00:11:27.319
template and you don't have to worry about it. Yeah, it's an
00:11:27.320 --> 00:11:32.679
interesting topic because the thing about, on one side, you
00:11:32.680 --> 00:11:36.159
know, you want to have, when you're using LaTeX, it kind of
00:11:36.160 --> 00:11:39.359
translates into you caring a lot about the document that you
00:11:39.360 --> 00:11:42.879
produce. Either you care about how quickly you can turn a
00:11:42.880 --> 00:11:46.719
plain text document into a very nicely formatted PDF at the
00:11:46.720 --> 00:11:52.239
end, or, you know, you just care about the output of your
00:11:52.240 --> 00:11:54.439
documents, making sure that everything is properly
00:11:54.440 --> 00:11:57.039
formatted. We were talking about references just before,
00:11:57.040 --> 00:12:00.239
you know, the formatting rule for references are highly
00:12:00.240 --> 00:12:04.319
dependent upon the manual that you're using and, you know,
00:12:04.320 --> 00:12:07.159
some people really care about this. And what I found in my
00:12:07.160 --> 00:12:09.799
particular experience, my own personal experience
00:12:09.800 --> 00:12:15.199
writing for academia, was that I was more in the latter crowd
00:12:15.200 --> 00:12:17.839
that really cared about the output format and making sure
00:12:17.840 --> 00:12:20.599
everything was correct and it's really a struggle to get
00:12:20.600 --> 00:12:23.519
everything working especially when you're transpiling
00:12:23.520 --> 00:12:27.199
from Org Mode documents straight into LaTeX. You're
00:12:27.200 --> 00:12:30.119
obviously going to be resorting to a number of hacks to get
00:12:30.120 --> 00:12:32.439
everything working like Vincent just mentioned with the
00:12:32.440 --> 00:12:36.519
class or you're going to end up with many imported files just
00:12:36.520 --> 00:12:39.999
to get everything working, but really you're fighting
00:12:40.000 --> 00:12:42.839
against the tide if you want to get something a little
00:12:42.840 --> 00:12:45.759
different from what is shipping with Walmart. Maybe
00:12:45.760 --> 00:12:48.479
everything has gotten better since I was writing my papers,
00:12:48.480 --> 00:12:53.879
but generally... Kindly disagree. Yeah, go on. I kindly
00:12:53.880 --> 00:12:57.159
disagree. I actually, I'm surprised that a lot of template
00:12:57.160 --> 00:13:00.679
is so complex that you don't just change the document class,
00:13:00.680 --> 00:13:03.359
but also need to do something else. I'd say it's rather
00:13:03.360 --> 00:13:05.919
uncommon. I guess it depends on the area of your search.
00:13:05.920 --> 00:13:12.599
Yeah, exactly. I mean, that's it. It just needs CLS and
00:13:12.600 --> 00:13:17.559
that's all. Yeah, but it really depends on, as you said, on
00:13:17.560 --> 00:13:19.639
the field in which you're publishing. Some fields are a
00:13:19.640 --> 00:13:22.599
little more lax with their rules. And just the fact that you
00:13:22.600 --> 00:13:26.479
can introduce mathematic formulas kind of makes LaTeX the
00:13:26.480 --> 00:13:29.919
de facto for publishing math documents. But when you're
00:13:29.920 --> 00:13:33.599
doing humanities, they're more attached to other kinds of
00:13:33.600 --> 00:13:36.879
formatting. So I think things are much better, anyway,
00:13:36.880 --> 00:13:42.919
since I started five years ago. Oh, yeah. I have heard from
00:13:42.920 --> 00:13:46.639
humanities people Microsoft Word. Yes. Sadly, that's the
00:13:46.640 --> 00:13:51.879
format we're fighting against. Yeah. As for document,
00:13:51.880 --> 00:13:57.079
yeah, for LaTeX classes, it is a customization and it is the
00:13:57.080 --> 00:14:00.319
right way to customize this thing, that's all. I'm not sure
00:14:00.320 --> 00:14:03.999
why it's a hack. It's not a hack. It's an actual user
00:14:04.000 --> 00:14:08.959
customization. Right. So, we've got about four more
00:14:08.960 --> 00:14:13.559
minutes of question. Vincent, we've got a couple of Yeah. So
00:14:13.560 --> 00:14:15.319
I've got a little voice talking in my ear telling me that
00:14:15.320 --> 00:14:17.839
exactly the same thing. So we've got about two more
00:14:17.840 --> 00:14:21.159
questions. Vincent, do you want to field them? Sure. So, are
NOTE Q: Are you using zotra or org-ref?
00:14:21.160 --> 00:14:27.799
you using Zotra (sending some link) or org-ref? No, I don't.
00:14:27.800 --> 00:14:31.879
I've never heard of Zotra, actually. Looking that very
00:14:31.880 --> 00:14:34.639
briefly. That's something I'm going to have to look into.
00:14:34.640 --> 00:14:38.519
Apparently, the short for Zotero translator, so that might
00:14:38.520 --> 00:14:41.759
be something useful for me since I'm not using Zotero yet,
00:14:41.760 --> 00:14:45.119
maybe trying to combine. But no, I've never really tried
NOTE Q: How much of this is tied to org-roam specifically?
00:14:45.120 --> 00:14:52.519
these, but I will. Then the last question, how much of this is
00:14:52.520 --> 00:14:59.479
tied to Org-roam specifically? Not a lot. Actually apart
00:14:59.480 --> 00:15:02.959
from the org-roam-bibtex, I think.
00:15:02.960 --> 00:15:11.919
Maybe I'm mixing up stuff there. But no, not a lot actually.
00:15:11.920 --> 00:15:14.999
It's just the fact that I'm using that as a in my org-roam
00:15:15.000 --> 00:15:22.159
system. But apart from that, most of, I mean, actually all of
00:15:22.160 --> 00:15:27.519
the exports can be done from a normal org-note or any other
00:15:27.520 --> 00:15:31.799
knowledge management system that you do with org-notes. So
00:15:31.800 --> 00:15:34.119
no, it's not specifically tied to org-roam, just that
00:15:34.120 --> 00:15:38.399
that's the way I'm using it. And I'm showing it this way, but
00:15:38.400 --> 00:15:41.759
yeah, actually the export process can be, can be done with,
00:15:41.760 --> 00:15:49.839
Yes, specifically tight work room. Yeah, just confirming
00:15:49.840 --> 00:15:54.519
this, the only way Org Roam intervenes into this process is
00:15:54.520 --> 00:15:57.439
just referencing
00:15:57.440 --> 00:16:00.319
bibliography elements. It just kind of intercedes a little
00:16:00.320 --> 00:16:03.319
bit between what Org Roam usually does. But when it comes to
00:16:03.320 --> 00:16:08.759
the exports to LaTeX and PDF eventually, that's completely
00:16:08.760 --> 00:16:13.279
deferring to org exports. So, ox-latex and all of this. So,
00:16:13.280 --> 00:16:16.039
we are not intervening in any way into this transpiling
00:16:16.040 --> 00:16:20.719
format. One comment. Yeah, I don't know if I imagine it is,
00:16:20.720 --> 00:16:25.759
but it looked from the slides that it was our graph was it.
00:16:25.760 --> 00:16:35.439
Sorry, that it was? org-ref, org-ref.
00:16:35.440 --> 00:16:42.719
Yes. Because it is a link system for citations. Built-in
00:16:42.720 --> 00:16:46.359
citations, which is, there is a built-in citation system in
00:16:46.360 --> 00:16:50.639
art mode. It uses, it doesn't use links. It has a special way
00:16:50.640 --> 00:16:57.359
to cite things. Yeah, because I believe, yeah, go on please,
00:16:57.360 --> 00:17:01.519
Vincent. No, I just wanted to say, in that case, I'm using the
00:17:01.520 --> 00:17:10.119
link with the cite command. I'm not using the org-roam link
00:17:10.120 --> 00:17:14.079
for the reference. I didn't really show that very
00:17:14.080 --> 00:17:17.679
carefully. But then, yeah, it's a site element that is
00:17:17.680 --> 00:17:21.639
exported. So the roam part is just like, you can access the
00:17:21.640 --> 00:17:26.519
org notes that you have attached to a reference paper. But
00:17:26.520 --> 00:17:31.879
that's it. Okay, because I was confused by why the
00:17:31.880 --> 00:17:35.919
bibliography is a link, why style is a link, because it is the
00:17:35.920 --> 00:17:37.239
approach org-ref uses.
00:17:37.240 --> 00:17:47.839
Ah, right. Okay, I see. Yeah, the thing is, actually I don't
00:17:47.840 --> 00:17:52.159
know why, but In my experience, using the org-roam,
00:17:52.160 --> 00:17:57.599
org-roam-bibtex links doesn't export or doesn't export
00:17:57.600 --> 00:18:01.999
properly. So like adding them with the org-ref-cite worked
00:18:02.000 --> 00:18:05.359
better. So that's, that's why I'm using these. If I may
00:18:05.360 --> 00:18:07.439
interject. If you're using org-ref-cite, you're using
00:18:07.440 --> 00:18:11.319
org-ref-for-export, which is slightly different. I'm
00:18:11.320 --> 00:18:14.039
going to interject very quickly because sadly we are a
00:18:14.040 --> 00:18:15.919
little pressed for time because we are heading into the next
00:18:15.920 --> 00:18:18.559
discussion. So just very quickly, if you want to continue
00:18:18.560 --> 00:18:21.279
the discussion, the BBB room is available at
00:18:21.280 --> 00:18:24.319
emacsconf-org. You can go to the talk and get the link to join
00:18:24.320 --> 00:18:27.319
the BBB. And the stream will be moving on to the next stream in
00:18:27.320 --> 00:18:30.239
about 5 to 10 seconds. So I'll see you on the other side. And
00:18:30.240 --> 00:18:36.439
thank you, Vincent. Thank you. All right, sorry for cutting
00:18:36.440 --> 00:18:38.839
a little abruptly. It's because we use crontabs to move to
00:18:38.840 --> 00:18:42.519
the next talk. And sadly, I don't have any leeway on this. So
00:18:42.520 --> 00:18:45.279
feel free to continue the discussion. I'll be moving on to
00:18:45.280 --> 00:18:48.639
make sure everything is working. So enjoy the discussion.
00:18:48.640 --> 00:19:00.720
Thank you very much. Bye-bye.
