From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Wed, 30 Oct 2013 12:15:27 +0300 Message-ID: Subject: a restriction of events in Acme From: Alexander Sychev To: plan9port-dev Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b6dc22420cd9304e9f1c613 Topicbox-Message-UUID: 88b5d6e6-ead8-11e9-9d60-3106f5b1d025 --047d7b6dc22420cd9304e9f1c613 Content-Type: text/plain; charset=ISO-8859-1 Hi, I would like to make a patch of Acme to restrict of sending of events. In a 'ctl' file of a window will be send string 'events xxx', where xxx - a list of events Acme can send. For example, 'events LXx' allows Acme to send events about looking in a body and executing in a tag and in the body of the window The restriction is needed to avoid of loading of CPU and to reduce a latency in events handling. When amail prints status of mailboxes and messages, there is a lot of text inserting events I don't need, but I have to handle them. Actually, the patch is already done. But I would like your opinion for a next case: should I restrict event origins too? For event types I have the use case, but for event origins do not have. -- Best regards, santucco -- --- You received this message because you are subscribed to the Google Groups "plan9port-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to plan9port-dev+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. --047d7b6dc22420cd9304e9f1c613 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I would like to make a patch of Acm= e to restrict of sending of events.
In a 'ctl' file of a = window will be send string 'events xxx', where xxx - a list of even= ts Acme can send.=A0
For example, 'events LXx' allows Acme to send events about loo= king in a body and executing in a tag and in the body of the window

The restriction is needed to avoid of loading of CPU= and to reduce a latency in events handling. When amail prints status of ma= ilboxes and messages, there is a lot of text inserting events =A0I don'= t need, but I have to handle them.

Actually, the patch is already done. But I would like y= our opinion for a next case: should I restrict event origins too? For event= types I have the use case, but for event origins do not have.


--
Best regards,
=A0 santucco

--
 
---
You received this message because you are subscribed to the Google Groups &= quot;plan9port-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to plan9port-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--047d7b6dc22420cd9304e9f1c613--