Re: Vip Editor

2017-01-04 Thread Alexander Burger
Hi David,

> > (For some reasons, the default "libncurses.so" is NOT a shared object
> > library
> > which can be called from C programs, but a text file with some kind of
> > pointer
> > or link in it)
> ...
> Wow...it's situations like this that make me feel I'll never understand C.
> Why use an extension of shared object for not a file whose contents are not
> that of a shared object?

Exactly! This is really sick.

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: Vip Editor

2017-01-04 Thread David Bloom
Hi Alex and thanks for the speedy reply.

>
> Yes, this is the common problem. I tried to explain it in the article,
> perhaps
> it got a bit too short:
>
> Oops, I was trying to avoid the common problem.  Not your directions so
much as my misunderstanding of C perhaps, see below.  Following your
directions I backed up the existing libncurses.so and made the 6.0 version
appropriate files installed by pacman and it worked on the first try.
Thank you for the help and for all of the code.


>It seems that other Linux distributions need similar actions. Good luck!
>
> So it is important that you set the symbolic link!
>
> (For some reasons, the default "libncurses.so" is NOT a shared object
> library
> which can be called from C programs, but a text file with some kind of
> pointer
> or link in it)
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Wow...it's situations like this that make me feel I'll never understand C.
Why use an extension of shared object for not a file whose contents are not
that of a shared object?

That's for another day, I've got some new picolisp code to explore and
learn from.  Hopefully I can produce something useful and give back to the
community one day.  Cheers.

-David


Re: Vip Editor

2017-01-04 Thread Robert W. Brown
I've had the same experience on a 64-bit Linux Mint installation.

Bob

On Tue, Jan 3, 2017 at 10:05 PM, David Bloom  wrote:

> Thank you Alex for another exciting utility as well as more example code
> to learn from.  I'm having some difficulty installing vip and I hope
> someone can help me out.  Using a 64-bit Netrunner (based off of Manjaro
> based off Arch) install, a fresh 16-12 picolisp installation, and ncurses
> installed I get:
>
> $ sudo pacman -Ss curses|grep installed
> core/ncurses 6.0+20161203-1 [installed]
> multilib/lib32-ncurses 6.0-2 [installed]
>
> $ vip testo.l
> [/usr/local/bin/vip:10] !? (265391 $10060141011 $10060141013
> $10060141015)
> [DLL] /usr/lib/libncurses.so: file too short
> ? ^
> -> (265391 $10060141011 $10060141013 $10060141015)
> ?
>
> What does it mean that mean the file is too short?  Thanks and happy new
> year!
>
> Kind regards,
> David
>
> On Mon, Jan 2, 2017 at 2:29 AM, Alexander Burger 
> wrote:
>
>> Hi all,
>>
>> here is an article about Vip, the Vi-Style Editor in PicoLisp:
>>
>>http://picolisp.com/wiki/?vip
>>
>> It consists of only 990 lines of code.
>>
>> Not that the world needs yet another editor! But it may serve as a useful
>> collection of PicoLisp coding examples :)
>>
>> - Alex
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>


Re: Vip Editor

2017-01-03 Thread Alexander Burger
Hi David,

> Thank you Alex for another exciting utility as well as more example code to
> learn from.  I'm having some difficulty installing vip and I hope someone
> can help me out.  Using a 64-bit Netrunner (based off of Manjaro based off
> Arch) install, a fresh 16-12 picolisp installation, and ncurses installed I
> get:
> 
> ...
> [/usr/local/bin/vip:10] !? (265391 $10060141011 $10060141013
> $10060141015)
> [DLL] /usr/lib/libncurses.so: file too short

Yes, this is the common problem. I tried to explain it in the article, perhaps
it got a bit too short:

   For Debian, however, I had to install libncurses5, and set a symbolic link
   (for reasons I don't really understand):

  $ sudo apt-get install libncurses5
  $ (cd /lib/x86_64-linux-gnu; sudo ln -s libncursesw.so.5.9 libncurses.so)

   It seems that other Linux distributions need similar actions. Good luck!

So it is important that you set the symbolic link!

(For some reasons, the default "libncurses.so" is NOT a shared object library
which can be called from C programs, but a text file with some kind of pointer
or link in it)

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: Vip Editor

2017-01-03 Thread David Bloom
Thank you Alex for another exciting utility as well as more example code to
learn from.  I'm having some difficulty installing vip and I hope someone
can help me out.  Using a 64-bit Netrunner (based off of Manjaro based off
Arch) install, a fresh 16-12 picolisp installation, and ncurses installed I
get:

$ sudo pacman -Ss curses|grep installed
core/ncurses 6.0+20161203-1 [installed]
multilib/lib32-ncurses 6.0-2 [installed]

$ vip testo.l
[/usr/local/bin/vip:10] !? (265391 $10060141011 $10060141013
$10060141015)
[DLL] /usr/lib/libncurses.so: file too short
? ^
-> (265391 $10060141011 $10060141013 $10060141015)
?

What does it mean that mean the file is too short?  Thanks and happy new
year!

Kind regards,
David

On Mon, Jan 2, 2017 at 2:29 AM, Alexander Burger 
wrote:

> Hi all,
>
> here is an article about Vip, the Vi-Style Editor in PicoLisp:
>
>http://picolisp.com/wiki/?vip
>
> It consists of only 990 lines of code.
>
> Not that the world needs yet another editor! But it may serve as a useful
> collection of PicoLisp coding examples :)
>
> - Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>


Re: Vip Editor

2017-01-02 Thread Bruno Franco
Downloaded and Installed! Thanks Alex!

On Mon, Jan 2, 2017 at 2:29 AM, Alexander Burger 
wrote:

> Hi all,
>
> here is an article about Vip, the Vi-Style Editor in PicoLisp:
>
>http://picolisp.com/wiki/?vip
>
> It consists of only 990 lines of code.
>
> Not that the world needs yet another editor! But it may serve as a useful
> collection of PicoLisp coding examples :)
>
> - Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>