Thanks a lot for the explanation guys.
Cheers,
Wojtek
śr., 26 cze 2019 o 02:14 Alexander Burger napisał(a):
> Hi Wojtek,
>
> > I'm wondering then... what if someone wanted to use PicoLisp to emit
> > characters somewhere (say, to a listening process) and the case required
> > one to send a
Hi Wojtek,
> I'm wondering then... what if someone wanted to use PicoLisp to emit
> characters somewhere (say, to a listening process) and the case required
> one to send a null byte. Does this limitation extend to all attempts at
> representing the null byte or only in the file context?
As
Hi Wojtek
This limitation only extends to all "text i/o" contexts, you can freely
read (rd with 'cnt argument) and write (wr) NULL with raw binary i/o
functions.
When reading text with (read), (from), (till), (line) and friends, the
data is automatically turned into picolisp symbols (as it is
Hi Alex,
I see. Thanks for the response.
I'm wondering then... what if someone wanted to use PicoLisp to emit
characters somewhere (say, to a listening process) and the case required
one to send a null byte. Does this limitation extend to all attempts at
representing the null byte or only in
Hi Wojtek,
> I've noticed this when messing around with my .emacs file. When you have a
> file with a null character somewhere within a double-quoted string
> (e.g. "\0") and you try to insert it into the current buffer with :r, then
> it breaks Vip
Right, this is a limitation of Vip (and
Hi everyone!
I've noticed this when messing around with my .emacs file. When you have a
file with a null character somewhere within a double-quoted string
(e.g. "\0") and you try to insert it into the current buffer with :r, then
it breaks Vip with the following message:
!? (set C T)
