Slashdot Mirror


GNU Emacs Now Has Native Support For GTK Widgets (phoronix.com)

An anonymous reader writes: The GNU Emacs text editor now has merged the X Widgets branch. What this work allows is for embedding GTK+ user interface widgets within Emacs for features like landing MPlayer or a full web browser in Emacs. This allows now for more endless opportunities for the 40 year old GNU text editor. The X/GTK widgets support will come with GNU Emacs 25.1.

2 of 133 comments (clear)

  1. Re:EMACS Memory Footprint? by olau · · Score: 5, Informative

    My Emacs with a ton of buffers opened with a bunch of fancy modes is using 66 MB resident, according to top. It's been open for 6 hours now.

    A fresh instance with no stuff in it (emacs -Q) is 39 MB.

  2. Re:Mplayer??? by buchner.johannes · · Score: 3, Informative

    Gentoo, Debian and Ubuntu had switched to libav by default, then switched back to ffmpeg.

    FFmpeg supporters wanted to keep development velocity in favour of more features, while Libav supporters wanted to improve the state of the code, take the time to design better APIs.[9][10]

    The maintainer of the FFmpeg packages for Debian[11] and Ubuntu,[12] being one of the group of developers who forked FFmpeg, switched the packages to this fork in 2011. Hence, most software on these systems that depended on FFmpeg automatically switched to Libav. In July 8, 2015, Debian announced it would return to FFmpeg[13] for various, technical reasons.[14] Several arguments justified this step. FFmpeg first had a better record of responding to vulnerabilities than libav . Secondly, Mateusz “j00ru” Jurczyk, a security-oriented developer at Google, argued that all issues he found were fixed in a timely manner, and the situation was entirely different with libav still affected by a bunch of bugs. Finally, the feature gap between FFmpeg and libav, with FFmpeg supporting a far wider variety of codecs and containers than libav does.

    Even if it has been expressed several time to merge back the two projects, this has still not happened yet. With Debian and Ubuntu stopping to use that library, the future of libav might be compromised and its development may be not sustainable any more without Debian.[15]

    https://en.wikipedia.org/wiki/...

    --
    NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.