From: bluewind at xinu.at (Florian Pritz)
Subject: RFE: .so filters
Date: Fri, 10 Jan 2014 18:12:25 +0100 [thread overview]
Message-ID: <52D029F9.40805@xinu.at> (raw)
In-Reply-To: <CAHmME9rgvZJ_r6B6dPLx_zC6z05dx_TS4PJi5rwA5NNYtH=1FA@mail.gmail.com>
On 10.01.2014 16:57, Jason A. Donenfeld wrote:
> On Fri, Jan 10, 2014 at 10:06 AM, John Keeping <john at keeping.me.uk> wrote:
>>
>> This seems drastically over complicated.
>
> So here's the situation. There's a lot of "state" that we're taking
> advantage of in using processes that terminate, that needs to be
> replicated:
Isn't this (fast scripting with lots of features) when people normally
start using lua?
Having said that, I haven't used lua yet so don't expect any code from
me, but this example [1] looks rather simple.
[1]: http://lua-users.org/wiki/SimpleLuaApiExample
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140110/3f9c5264/attachment.asc>
next prev parent reply other threads:[~2014-01-10 17:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 21:34 Jason
2014-01-09 22:29 ` mailings
2014-01-09 22:58 ` john
2014-01-10 1:41 ` Jason
2014-01-10 2:11 ` Jason
2014-01-10 4:26 ` Jason
2014-01-10 9:06 ` john
2014-01-10 15:57 ` Jason
2014-01-10 17:12 ` bluewind [this message]
2014-01-10 17:20 ` john
2014-01-10 17:43 ` mricon
2014-01-10 18:00 ` Jason
2014-01-10 18:00 ` Jason
2014-01-10 17:57 ` Jason
2014-01-10 20:03 ` bluewind
2014-01-10 20:11 ` john
2014-01-10 20:25 ` bluewind
2014-01-10 20:36 ` john
2014-01-10 20:56 ` bluewind
2014-01-11 2:37 ` Jason
2014-01-11 2:34 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D029F9.40805@xinu.at \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).