unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Qiantan Hong <qhong@mit.edu>
To: "rms@gnu.org" <rms@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: About implementing libre.js/el in Emacs
Date: Mon, 31 Aug 2020 04:24:00 +0000	[thread overview]
Message-ID: <A866A9AF-E526-4997-88FE-97004ACD1D62@mit.edu> (raw)
In-Reply-To: <E1kCawY-0005VV-Oy@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]



> On Aug 30, 2020, at 11:57 PM, Richard Stallman <rms@gnu.org> wrote:
> 
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 
>> Both will require adding primitives to Emacs C source to expose
>> urlRequest events, etc.
> 
> Can someone explain how those events work?  What do theese events do?
> What code generates them?
> 
> Why does it function that way, rather than by calling Lisp directly?

They are event (technically GTK signals) coming from WebkitGTK.
WebkitGTK emit those event at some interesting moments, e.g.
before a HTTP request is about to be sent. Librejs use Javascript
handlers to intercept requests, analyze scripts and block the bad
ones. This relies on the browser wrapping those event and expose
the interface to JS.

If we decide to let Librejs run in its JS form then we’ll have to do
what those browsers do.

We can also have Librejs.el. In this case there’s a technique concern
though, since WebkitGTK require the send-request signal
to be blocked *synchronously* when executing the signal callback,
we can’t do it the usual way that push a event into emacs’s
input event queue, we have to evaluate Emacs Lisp during
a GTK signal callback. Is this safe from, e.g., deadlock issues?

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1858 bytes --]

      parent reply	other threads:[~2020-08-31  4:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 19:14 About implementing libre.js/el in Emacs Qiantan Hong
2020-08-29 21:10 ` Paul Eggert
2020-08-30  2:26   ` Tim Cross
2020-08-30  2:45     ` Qiantan Hong
2020-08-30  7:44       ` Tim Cross
2020-08-30 14:13       ` T.V Raman
2020-08-31  3:53         ` Richard Stallman
2020-08-31  4:11           ` Qiantan Hong
2020-08-31  4:15             ` Stefan Monnier
2020-08-31  4:17               ` Qiantan Hong
2020-08-31 13:48           ` T.V Raman
2020-09-01  3:22             ` Richard Stallman
2020-08-31  3:57     ` Richard Stallman
2020-08-31  3:57 ` Richard Stallman
2020-08-31  4:13   ` Qiantan Hong
2020-09-01  3:24     ` Richard Stallman
2020-08-31  4:24   ` Qiantan Hong [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A866A9AF-E526-4997-88FE-97004ACD1D62@mit.edu \
    --to=qhong@mit.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).