Just two patches I once made on a trip, being annoyed by rttlua not
working as documented or as I expected.
I would seriously recommend to merge the completion+readline code into
ocl such that history is kept automatically and completion works out
of the box. It's just a pain without -- OR -- create an irttlua in ocl
and stuff that with 'i'nteractive features.
Peter
| Attachment | Size |
|---|---|
| 0001-doc-fixup-omissions-from-readme-file.patch | 1.73 KB |
| 0002-complete-slightly-more-intelligent.patch | 1.53 KB |
Patches for rttlua-completion
2012/11/9 Peter Soetens <peter [..] ...>
> Just two patches I once made on a trip, being annoyed by rttlua not
> working as documented or as I expected.
>
> I would seriously recommend to merge the completion+readline code into
> ocl such that history is kept automatically and completion works out
> of the box. It's just a pain without
I'm personnaly using the classical ocl deployer with lua bindings to
prevent this pain. But if I had had completion, I think I would have kept
the lua part.
Patches for rttlua-completion
On Fri, Nov 09, 2012 at 11:28:21PM +0100, Peter Soetens wrote:
> Just two patches I once made on a trip, being annoyed by rttlua not
> working as documented or as I expected.
Nice, thanks! Please apply directly.
> I would seriously recommend to merge the completion+readline code into
> ocl such that history is kept automatically and completion works out
> of the box. It's just a pain without -- OR -- create an irttlua in ocl
> and stuff that with 'i'nteractive features.
Putting it into OCL is fine with me. The only reason I didn't do that
initially was not to fuel the claims that "Lua" was bloating
everything...
Markus