bug-zile
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-zile] Running bleeding-edge github Zile [WAS Re: Problems generatin


From: Gary V. Vaughan
Subject: [Bug-zile] Running bleeding-edge github Zile [WAS Re: Problems generating manpage]
Date: Tue, 29 Jul 2014 13:45:09 +0100

Hi Stefan,

On Jul 29, 2014, at 5:13 AM, Stefan Husmann <address@hidden> wrote:
> I checked out 3.843.gff79b8b from your github repo, but cannot compile. 
> Running zemacs --help
> now gives errors again.
> /usr/bin/lua: ...g/maintained_by_me/zile-git/src/zile/lib/zile/syntax.lua:36: 
> module 'std.array' not found:
>       no field package.preload['std.array']
>       no file 
> '/home/haawda/paketierung/maintained_by_me/zile-git/src/zile/lib/std/array.lua'
>       no file 
> '/home/haawda/paketierung/maintained_by_me/zile-git/src/zile/lib/std/array.lua'
>       no file '/usr/share/lua/5.2/std/array.lua'
>       no file '/usr/share/lua/5.2/std/array/init.lua'
>       no file '/usr/lib/lua/5.2/std/array.lua'
>       no file '/usr/lib/lua/5.2/std/array/init.lua'
>       no file '/usr/lib/lua/5.2/std/array.so'
>       no file '/usr/lib/lua/5.2/loadall.so'
>       no file './std/array.so'        open file 
> '/home/haawda/paketierung/maintained_by_me/zile-git/src/zile/lib/std/array-bundle.lua'
>  failed: 
> /home/haawda/paketierung/maintained_by_me/zile-git/src/zile/lib/std/array-bundle.lua:
>  No such file or directory
>       open file 
> '/home/haawda/paketierung/maintained_by_me/zile-git/src/zile/lib/std/array-bundle.lua'
>  failed: 
> /home/haawda/paketierung/maintained_by_me/zile-git/src/zile/lib/std/array-bundle.lua:
>  No such file or directory
>       open file '/usr/share/lua/5.2/std/array-bundle.lua' failed: 
> /usr/share/lua/5.2/std/array-bundle.lua: No such file or directory
>       open file '/usr/share/lua/5.2/std/array/init-bundle.lua' failed: 
> /usr/share/lua/5.2/std/array/init-bundle.lua: No such file or directory
>       open file '/usr/lib/lua/5.2/std/array-bundle.lua' failed: 
> /usr/lib/lua/5.2/std/array-bundle.lua: No such file or directory
>       open file '/usr/lib/lua/5.2/std/array/init-bundle.lua' failed: 
> /usr/lib/lua/5.2/std/array/init-bundle.lua: No such file or directory
> stack traceback:
>       [C]: in function 'require'
>       ...g/maintained_by_me/zile-git/src/zile/lib/zile/syntax.lua:36: in main 
> chunk
>       [C]: in function 'require'
>       ...ined_by_me/zile-git/src/zile/lib/zile/term_redisplay.lua:21: in main 
> chunk
>       [C]: in function 'require'
>       ...aketierung/maintained_by_me/zile-git/src/zile/bin/zemacs:133: in 
> main chunk
>       [C]: in ?

Yes, the github mirror is sometimes slightly ahead of the official savannah 
repository, and is much more prone to breakage that will force you to do a 
fresh git checkout from time to time if I rewrite history as I fix things 
before pushing to the official savannah repo. In this case you picked up some 
changes I added to test moving the former `zile.Array` into stdlib as 
`std.array` where it can be useful to other projects... although I've since 
renamed that module to `std.vector` in github stdlib.

From here you have a couple of options to get going:

  1. You are very welcome to try bleeding edge zile and report any problems you 
find, which I'll fix as quickly as possible.  Unfortunately you'll need to 
update to the latest git version of stdlib too in this case.  I've just pushed 
another commit to github zile to catch up with the most recent upgrades to 
github stdlib.  I've also tested all of these together this morning, and 
everything appears to be working well here.

  2. If you don't want to fiddle with setting up a separate package.path for 
bleeding edge stdlib, or you're worried about breaking other Lua programs by 
overwriting the stable stdlib in the main package tree, you should use the 
savannah git repo for Zile, which works with stdlib v40.

Apologies for the dust and scaffolding while I'm making the current round of 
improvements to the infrastructure.

If there's anything else I can help with, please feel free to post again to the 
mailing list.

Cheers,
-- 
Gary V. Vaughan (gary AT vaughan DOT pe)

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail


reply via email to

[Prev in Thread] Current Thread [Next in Thread]