Edit with Emacs v1.15 released

After a bit of hiatus there was enough of a flurry of patches to make it worth pushing out a new release. I’m in a little bit of a quandary with what to do with this package now. It’s obviously a useful extension for a good number of people but I notice the slowly growing number of issues which I’m not making much progress on. It’s hard to find time to debug and fix things when it’s main state is Works For Me. There is also competition from the Atomic Chrome extension (and it’s related emacs extension). It’s an excellent package and has the advantage of a Chrome extension that is more actively developed and using a bi-directional web-socket to communicate with the edit server. It’s been a feature I’ve wanted to add to Edit with Emacs for a while but my re-factoring efforts are slowed down by the fact that Javascript is not a language I’m fluent in and finding a long enough period of spare time is hard with a family. I guess this is a roundabout way of saying that realistically this package is in maintenance mode and you shouldn’t expect to see any new development for the time being. I’ll of course try my best to address reproducible bugs and process pull requests in a timely manner. That said please enjoy v1.15:

Extension

* Now builds for Firefox using WebExtension hooks
* Use chrome.notifications instead of webkitNotifications
* Use

with style instead of inline for edit button
* fake “input” event to stop active page components overwriting text area

edit-server.el

* avoid calling make-frame-on-display for TTY setups (#103/#132/#133)
* restore edit-server-default-major-mode if auto-mode lookup fails
* delete window when done editing with no new frame

Get the latest from the Chrome Webstore.

5 Comments

  1. Hi Alex, I meant to ask this question somewhere else, may be under qemu related blog while comment of which is closed. Anyway, I refer the article at
    https://www.linaro.org/blog/running-64bit-android-l-qemu/
    https://github.com/robherring/generic_device/wiki/Running-QEMU-KVM

    for how to run android with 64bit arm qemu. Here is my environment:
    1. host : ubuntu16.04 aarch64 server
    2. qemu-system-aarch64 installed by apt-get version:2.6.1
    3. android version: O
    With s/w rendering, android can boot successfully and can be viewed with spice, but my apk using OpenGLes 2.0 can’t run. While if I choose h/w rendering, output of console keeps printing logs as follows, it seems that android can’t be boot normally, I wonder if OpenGL passthrough is implemented now, if so, how can I get the display with h/w rendering since vnc or spice not supported on h/w rendering.

    [ 9.610021] init: starting service ‘surfaceflinger’…
    [ 9.615573] init: property_set(“ro.boottime.surfaceflinger”, “9568305740”) failed: property already set
    [ 9.622341] init: starting service ‘zygote’…
    [ 9.627305] init: property_set(“ro.boottime.zygote”, “9580076950”) failed: property already set
    [ 14.450101] init: starting service ‘netd’…
    [ 14.455001] init: property_set(“ro.boottime.netd”, “14407743670”) failed: property already set
    [ 14.455498] init: Created socket ‘/dev/socket/netd’, mode 660, user 0, group 1000
    [ 14.455798] init: Created socket ‘/dev/socket/dnsproxyd’, mode 660, user 0, group 3003
    [ 14.456071] init: Created socket ‘/dev/socket/mdns’, mode 660, user 0, group 1000
    [ 14.456346] init: Created socket ‘/dev/socket/fwmarkd’, mode 660, user 0, group 3003
    [ 14.459012] type=1400 audit(1516850240.944:97): avc: granted { getattr } for pid=2160 comm=”iptables” path=”/vendor” dev=”rootfs” ino=2117 scontext=u:r:netd:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file
    [ 14.459021] type=1400 audit(1516850245.864:166): avc: granted { getattr } for pid=2213 comm=”netd” path=”/vendor” dev=”rootfs” ino=2117 scontext=u:r:netd:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file
    [ 14.480145] type=1400 audit(1516850245.864:166): avc: granted { getattr } for pid=2213 comm=”netd” path=”/vendor” dev=”rootfs” ino=2117 scontext=u:r:netd:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file
    [ 14.480151] type=1400 audit(1516850245.884:167): avc: granted { getattr } for pid=2214 comm=”iptables-restor” path=”/vendor” dev=”rootfs” ino=2117 scontext=u:r:netd:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file
    [ 14.485079] type=1400 audit(1516850245.884:167): avc: granted { getattr } for pid=2214 comm=”iptables-restor” path=”/vendor” dev=”rootfs” ino=2117 scontext=u:r:netd:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file
    [ 14.485085] type=1400 audit(1516850245.884:168): avc: granted { lock } for pid=2214 comm=”iptables-restor” path=”/system/etc/xtables.lock” dev=”vda” ino=638 scontext=u:r:netd:s0 tcontext=u:object_r:system_file:s0 tclass=file
    [ 14.488401] type=1400 audit(1516850245.884:168): avc: granted { lock } for pid=2214 comm=”iptables-restor” path=”/system/etc/xtables.lock” dev=”vda” ino=638 scontext=u:r:netd:s0 tcontext=u:object_r:system_file:s0 tclass=file
    [ 14.488406] type=1400 audit(1516850245.892:169): avc: granted { getattr } for pid=2215 comm=”ip6tables-resto” path=”/vendor” dev=”rootfs” ino=2117 scontext=u:r:netd:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file
    [ 14.493475] type=1400 audit(1516850245.892:169): avc: granted { getattr } for pid=2215 comm=”ip6tables-resto” path=”/vendor” dev=”rootfs” ino=2117 scontext=u:r:netd:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file
    [ 14.493480] type=1400 audit(1516850245.896:170): avc: granted { lock } for pid=2215 comm=”ip6tables-resto” path=”/system/etc/xtables.lock” dev=”vda” ino=638 scontext=u:r:netd:s0 tcontext=u:object_r:system_file:s0 tclass=file
    [ 14.553492] audit: audit_lost=99 audit_rate_limit=20 audit_backlog_limit=64
    [ 14.553494] audit: rate limit exceeded

Leave a Reply

Your email address will not be published. Required fields are marked *