blob: c9477c2d3fd5b29385ccc622598d9e6d4cc35d49 (
plain) (
tree)
|
|
WEBVTT
00:00:01.520 --> 00:00:03.360
okay I mean can you hear me yep I can
00:00:03.360 --> 00:00:05.279
hear you can you hear me
00:00:05.279 --> 00:00:07.200
yes perfect so gabrielle uh if you want
00:00:07.200 --> 00:00:08.480
to start answering questions and by the
00:00:08.480 --> 00:00:09.280
way people for the
00:00:09.280 --> 00:00:10.880
for the stream I'm actually on a phone
00:00:10.880 --> 00:00:12.400
call right now so the quality might be a
00:00:12.400 --> 00:00:13.360
little bad
00:00:13.360 --> 00:00:17.199
but we're trying our best
00:00:17.199 --> 00:00:20.480
hello uh thanks for attending my talk
00:00:20.480 --> 00:00:22.800
I see four questions on the user product
00:00:22.800 --> 00:00:24.000
I'm going to answer
00:00:24.000 --> 00:00:27.039
them okay so the first one is
00:00:27.039 --> 00:00:29.039
can you put your test space from up
00:00:29.039 --> 00:00:31.119
somewhere uh yes they're very simple
00:00:31.119 --> 00:00:31.840
skips
00:00:31.840 --> 00:00:33.680
uh I'll find a way to distribute them
00:00:33.680 --> 00:00:35.520
somehow
00:00:35.520 --> 00:00:37.600
that's so that's an easy one the second
00:00:37.600 --> 00:00:38.800
one is more difficult it's more
00:00:38.800 --> 00:00:40.559
difficult it's the differences between
00:00:40.559 --> 00:00:44.320
e shell and v term so I did very basic
00:00:44.320 --> 00:00:47.360
level the main difference is that v
00:00:47.360 --> 00:00:50.399
term is implemented with
00:00:50.399 --> 00:00:52.800
as a bridge between Emacs and an
00:00:52.800 --> 00:00:53.840
external library
00:00:53.840 --> 00:00:56.079
which means that most of the code base
00:00:56.079 --> 00:00:57.039
is actually c
00:00:57.039 --> 00:01:00.320
it's not easy uh this is is a critical
00:01:00.320 --> 00:01:01.280
difference
00:01:01.280 --> 00:01:03.760
uh in terms of performance in terms of
00:01:03.760 --> 00:01:04.320
speed
00:01:04.320 --> 00:01:06.960
and all the other uh features that we
00:01:06.960 --> 00:01:07.360
can
00:01:07.360 --> 00:01:10.400
inherit from this library so vterm
00:01:10.400 --> 00:01:13.119
is similar to a real terminal it's not
00:01:13.119 --> 00:01:13.600
as
00:01:13.600 --> 00:01:15.840
uh it's not like a shell it's a real
00:01:15.840 --> 00:01:17.040
terminal emulator
00:01:17.040 --> 00:01:19.600
that can actually uh display but
00:01:19.600 --> 00:01:20.479
manipulate the
00:01:20.479 --> 00:01:22.960
terminal in pretty much any way whereas
00:01:22.960 --> 00:01:23.520
isha
00:01:23.520 --> 00:01:25.759
is simply a way to interact with your
00:01:25.759 --> 00:01:26.640
system
00:01:26.640 --> 00:01:29.680
in the data page we have a more
00:01:29.680 --> 00:01:31.840
complete discussion about this topic and
00:01:31.840 --> 00:01:33.520
where we compare v-terms with e-shell
00:01:33.520 --> 00:01:34.799
with shell with nc
00:01:34.799 --> 00:01:38.720
term as well I think so
00:01:38.720 --> 00:01:40.640
I think just to conclude this I think
00:01:40.640 --> 00:01:42.000
eshell and v term
00:01:42.000 --> 00:01:44.079
are somehow orthogonal in the sense that
00:01:44.079 --> 00:01:45.280
v3 is before a
00:01:45.280 --> 00:01:46.880
full complete terminal experience
00:01:46.880 --> 00:01:49.439
whereas isil is more for specific tasks
00:01:49.439 --> 00:01:50.240
of this
00:01:50.240 --> 00:01:53.280
uh which are not like terminal uh
00:01:53.280 --> 00:01:55.759
interfaces you know like page stock this
00:01:55.759 --> 00:01:56.799
kind of stuff
00:01:56.799 --> 00:01:59.759
uh the next question is uh is there a
00:01:59.759 --> 00:02:01.200
plan to avoid compilation of the initial
00:02:01.200 --> 00:02:02.560
completion steps
00:02:02.560 --> 00:02:05.759
so since the term is based on again
00:02:05.759 --> 00:02:08.000
on an external module we need to combine
00:02:08.000 --> 00:02:08.800
this module
00:02:08.800 --> 00:02:10.800
and we're using the dynamic module
00:02:10.800 --> 00:02:11.920
system to
00:02:11.920 --> 00:02:13.920
be able to interface with this module
00:02:13.920 --> 00:02:16.239
and this requires
00:02:16.239 --> 00:02:18.879
us to compile the module at least the
00:02:18.879 --> 00:02:20.160
very first time you start
00:02:20.160 --> 00:02:23.920
the I don't think we can do
00:02:23.920 --> 00:02:26.720
without that in the near future we need
00:02:26.720 --> 00:02:28.480
to compile this
00:02:28.480 --> 00:02:31.599
and we must there's no way around
00:02:31.599 --> 00:02:33.360
if we cannot simply distribute the
00:02:33.360 --> 00:02:37.440
module um
00:02:37.440 --> 00:02:39.519
if you want to think very long term
00:02:39.519 --> 00:02:40.480
maybe
00:02:40.480 --> 00:02:42.959
uh but I think there's no current plan
00:02:42.959 --> 00:02:43.599
to
00:02:43.599 --> 00:02:45.760
avoid the compilation as the very first
00:02:45.760 --> 00:02:47.280
step the first time you
00:02:47.280 --> 00:02:50.400
uh run vtor however all the subsequent
00:02:50.400 --> 00:02:50.959
times
00:02:50.959 --> 00:02:54.720
you will not have to compile peter um
00:02:54.720 --> 00:02:57.840
so for question four it's uh I have a
00:02:57.840 --> 00:02:58.720
nice looking problem
00:02:58.720 --> 00:03:01.920
thanks uh and if
00:03:01.920 --> 00:03:04.159
there's a git repo where you can see it
00:03:04.159 --> 00:03:05.599
or something like that
00:03:05.599 --> 00:03:08.560
so if you go to my github repo I have
00:03:08.560 --> 00:03:09.760
adobe files
00:03:09.760 --> 00:03:12.560
repo but look at that it's terrible it's
00:03:12.560 --> 00:03:13.840
super updated
00:03:13.840 --> 00:03:16.800
so I've been meaning to polish it for
00:03:16.800 --> 00:03:17.519
like years
00:03:17.519 --> 00:03:20.080
and I haven't got it so don't look at it
00:03:20.080 --> 00:03:21.760
my font is actually extremely simple
00:03:21.760 --> 00:03:25.200
I think it's the pure prompt from uh zsh
00:03:25.200 --> 00:03:26.640
or fish depending
00:03:26.640 --> 00:03:28.799
uh and I think I didn't do anything but
00:03:28.799 --> 00:03:30.640
like maybe tweaking the colors a little
00:03:30.640 --> 00:03:31.360
bit
00:03:31.360 --> 00:03:33.280
okay gabriel just sorry to interject if
00:03:33.280 --> 00:03:35.519
you could just take one more question
00:03:35.519 --> 00:03:37.120
yes the last question is already the
00:03:37.120 --> 00:03:39.440
answer which is uh will it work with
00:03:39.440 --> 00:03:42.480
e max terminal so minus and w and answer
00:03:42.480 --> 00:03:44.480
yes it works without any problem with
00:03:44.480 --> 00:03:46.239
imax terminal so you can run a terminal
00:03:46.239 --> 00:03:47.760
inside image inside of terminal
00:03:47.760 --> 00:03:49.680
and you can continue paying up as much
00:03:49.680 --> 00:03:51.200
as you want okay
00:03:51.200 --> 00:03:53.920
I think that's it explain the question
00:03:53.920 --> 00:03:56.239
oh sorry thank you
00:03:56.239 --> 00:03:59.760
thanks for attending this talk
00:03:59.760 --> 00:04:01.519
well thank you so much for giving it so
00:04:01.519 --> 00:04:03.360
I'm in back to you
00:04:03.360 --> 00:04:07.280
you are now unmuted thank you very much
00:04:07.280 --> 00:04:09.519
to gabrielle for the awesome talk and
00:04:09.519 --> 00:04:11.200
for taking live questions
00:04:11.200 --> 00:04:14.319
and also many thanks to leo for getting
00:04:14.319 --> 00:04:15.200
through to gabriel
00:04:15.200 --> 00:04:18.720
via phone in the face of gabriel having
00:04:18.720 --> 00:04:20.720
technical difficulties
00:04:20.720 --> 00:04:24.160
with using big blue button
|
