summaryrefslogblamecommitdiffstats
path: root/2020/subtitles/emacsconf-2020--30-a-tour-of-vterm--questions--gabriele-bozzola-sbozzolo-autogen.sbv
blob: 8378a57778d85116bd989be71f92c1673efc1e97 (plain) (tree)































































































































































































































































































































































































                                        
0:00:01.520,0:00:05.279
okay i mean can you hear me yep i can

0:00:03.360,0:00:07.200
hear you can you hear me

0:00:05.279,0:00:08.480
yes perfect so gabrielle uh if you want

0:00:07.200,0:00:09.280
to start answering questions and by the

0:00:08.480,0:00:10.880
way people for the

0:00:09.280,0:00:12.400
for the stream i'm actually on a phone

0:00:10.880,0:00:13.360
call right now so the quality might be a

0:00:12.400,0:00:17.199
little bad

0:00:13.360,0:00:20.480
but we're trying our best

0:00:17.199,0:00:22.800
hello uh thanks for attending my talk

0:00:20.480,0:00:24.000
i see four questions on the user product

0:00:22.800,0:00:27.039
i'm going to answer

0:00:24.000,0:00:29.039
them okay so the first one is

0:00:27.039,0:00:31.119
can you put your test space from up

0:00:29.039,0:00:31.840
somewhere uh yes they're very simple

0:00:31.119,0:00:33.680
skips

0:00:31.840,0:00:35.520
uh i'll find a way to distribute them

0:00:33.680,0:00:37.600
somehow

0:00:35.520,0:00:38.800
that's so that's an easy one the second

0:00:37.600,0:00:40.559
one is more difficult it's more

0:00:38.800,0:00:44.320
difficult it's the differences between

0:00:40.559,0:00:47.360
e shell and v term so i did very basic

0:00:44.320,0:00:50.399
level the main difference is that v

0:00:47.360,0:00:52.800
term is implemented with

0:00:50.399,0:00:53.840
as a bridge between emacs and an

0:00:52.800,0:00:56.079
external library

0:00:53.840,0:00:57.039
which means that most of the code base

0:00:56.079,0:01:00.320
is actually c

0:00:57.039,0:01:01.280
it's not easy uh this is is a critical

0:01:00.320,0:01:03.760
difference

0:01:01.280,0:01:04.320
uh in terms of performance in terms of

0:01:03.760,0:01:06.960
speed

0:01:04.320,0:01:07.360
and all the other uh features that we

0:01:06.960,0:01:10.400
can

0:01:07.360,0:01:13.119
inherit from this library so vterm

0:01:10.400,0:01:13.600
is similar to a real terminal it's not

0:01:13.119,0:01:15.840
as

0:01:13.600,0:01:17.040
uh it's not like a shell it's a real

0:01:15.840,0:01:19.600
terminal emulator

0:01:17.040,0:01:20.479
that can actually uh display but

0:01:19.600,0:01:22.960
manipulate the

0:01:20.479,0:01:23.520
terminal in pretty much any way whereas

0:01:22.960,0:01:25.759
isha

0:01:23.520,0:01:26.640
is simply a way to interact with your

0:01:25.759,0:01:29.680
system

0:01:26.640,0:01:31.840
in the data page we have a more

0:01:29.680,0:01:33.520
complete discussion about this topic and

0:01:31.840,0:01:34.799
where we compare v-terms with e-shell

0:01:33.520,0:01:38.720
with shell with nc

0:01:34.799,0:01:40.640
term as well i think so

0:01:38.720,0:01:42.000
i think just to conclude this i think

0:01:40.640,0:01:44.079
eshell and v term

0:01:42.000,0:01:45.280
are somehow orthogonal in the sense that

0:01:44.079,0:01:46.880
v3 is before a

0:01:45.280,0:01:49.439
full complete terminal experience

0:01:46.880,0:01:50.240
whereas isil is more for specific tasks

0:01:49.439,0:01:53.280
of this

0:01:50.240,0:01:55.759
uh which are not like terminal uh

0:01:53.280,0:01:56.799
interfaces you know like page stock this

0:01:55.759,0:01:59.759
kind of stuff

0:01:56.799,0:02:01.200
uh the next question is uh is there a

0:01:59.759,0:02:02.560
plan to avoid compilation of the initial

0:02:01.200,0:02:05.759
completion steps

0:02:02.560,0:02:08.000
so since the term is based on again

0:02:05.759,0:02:08.800
on an external module we need to combine

0:02:08.000,0:02:10.800
this module

0:02:08.800,0:02:11.920
and we're using the dynamic module

0:02:10.800,0:02:13.920
system to

0:02:11.920,0:02:16.239
be able to interface with this module

0:02:13.920,0:02:18.879
and this requires

0:02:16.239,0:02:20.160
us to compile the module at least the

0:02:18.879,0:02:23.920
very first time you start

0:02:20.160,0:02:26.720
the i don't think we can do

0:02:23.920,0:02:28.480
without that in the near future we need

0:02:26.720,0:02:31.599
to compile this

0:02:28.480,0:02:33.360
and we must there's no way around

0:02:31.599,0:02:36.720
if we cannot simply distribute the

0:02:33.360,0:02:36.720
module um

0:02:37.440,0:02:40.480
if you want to think very long term

0:02:39.519,0:02:42.959
maybe

0:02:40.480,0:02:43.599
uh but i think there's no current plan

0:02:42.959,0:02:45.760
to

0:02:43.599,0:02:47.280
avoid the compilation as the very first

0:02:45.760,0:02:50.400
step the first time you

0:02:47.280,0:02:50.959
uh run vtor however all the subsequent

0:02:50.400,0:02:54.720
times

0:02:50.959,0:02:57.840
you will not have to compile peter um

0:02:54.720,0:02:58.720
so for question four it's uh i have a

0:02:57.840,0:03:01.920
nice looking problem

0:02:58.720,0:03:04.159
thanks uh and if

0:03:01.920,0:03:05.599
there's a git repo where you can see it

0:03:04.159,0:03:08.560
or something like that

0:03:05.599,0:03:09.760
so if you go to my github repo i have

0:03:08.560,0:03:12.560
adobe files

0:03:09.760,0:03:13.840
repo but look at that it's terrible it's

0:03:12.560,0:03:16.800
super updated

0:03:13.840,0:03:17.519
so i've been meaning to polish it for

0:03:16.800,0:03:20.080
like years

0:03:17.519,0:03:21.760
and i haven't got it so don't look at it

0:03:20.080,0:03:25.200
my font is actually extremely simple

0:03:21.760,0:03:26.640
i think it's the pure prompt from uh zsh

0:03:25.200,0:03:28.799
or fish depending

0:03:26.640,0:03:30.640
uh and i think i didn't do anything but

0:03:28.799,0:03:31.360
like maybe tweaking the colors a little

0:03:30.640,0:03:33.280
bit

0:03:31.360,0:03:35.519
okay gabriel just sorry to interject if

0:03:33.280,0:03:37.120
you could just take one more question

0:03:35.519,0:03:39.440
yes the last question is already the

0:03:37.120,0:03:42.480
answer which is uh will it work with

0:03:39.440,0:03:44.480
e max terminal so minus and w and answer

0:03:42.480,0:03:46.239
yes it works without any problem with

0:03:44.480,0:03:47.760
imax terminal so you can run a terminal

0:03:46.239,0:03:49.680
inside image inside of terminal

0:03:47.760,0:03:51.200
and you can continue paying up as much

0:03:49.680,0:03:53.920
as you want okay

0:03:51.200,0:03:56.239
i think that's it explain the question

0:03:53.920,0:03:59.760
oh sorry thank you

0:03:56.239,0:04:01.519
thanks for attending this talk

0:03:59.760,0:04:03.360
well thank you so much for giving it so

0:04:01.519,0:04:07.280
i'm in back to you

0:04:03.360,0:04:09.519
you are now unmuted thank you very much

0:04:07.280,0:04:11.200
to gabrielle for the awesome talk and

0:04:09.519,0:04:14.319
for taking live questions

0:04:11.200,0:04:15.200
and also many thanks to leo for getting

0:04:14.319,0:04:18.720
through to gabriel

0:04:15.200,0:04:20.720
via phone in the face of gabriel having

0:04:18.720,0:04:24.160
technical difficulties

0:04:20.720,0:04:24.160
with using big blue button