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.
Emacs would be a hell of an operating system if someone would just write a decent text editor for it.
You insensitive text mode clods!
Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
Seriously, this is SUCH a niche product. Everyone uses a VI clone because it's guaranteed to be present on *nux systems.
"Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
After the FFMPEG fork is there a Linux distro that still uses FFMPEG & Mplayer? Every disto I see uses avlib and mpv. I have great animosity towards the avlib team, they have caused me much headaches.
This is just weird. Reminds me of Active Desktop in Windows 98.
At least there are no security issues with doing something like that. Right?
Emacs will be a much better web browser.
Clickety Click
I remember when you would say "Eight Meg And Currently Swapping" and that was a funny criticism of how bloated EMACS was.
What's the mem footprint today?
Give me an effing break! This is not even funny anymore.
How about building in a compiler stack into Emacs, some neat or something usefull if there's nothing more to do on Emacs?
How about building a search function with useful defaults for the options tree or improving its integrated documentation?
Integrated GTK toys - WTF?
One of the huge advantages of emacs is that it runs in the CLI. The GTK Version should get CUAS support and a bar with some buttons at the top (collapsible) and that's just about all Emacs needs in terms of grafical GUI integration. AFAICT it had that allready.
As an Emacs User I see no point whatsoever in this. They should focus on other things IMHO.
We suffer more in our imagination than in reality. - Seneca
I don't know, but let me come with an example.
You can either customize Emacs by writing a bit of Lisp and dumping it in your .emacs (or init.el), but you can also use the built-in customize interface that many packages support.
If you've ever used M-x customize, it's like a... a toolkit built with text elements. It's... weird. I actually tried starting it again now, and I think it's less weird than it used to be, but it's still some way from any configuration window you'd ever see in a regular GUI editor.
So presumably some of that gap can now be bridged.
This is great news. I've been wanting to especially combine full fledged web rendering into Emacs. Next up opengl? Full power of lisp, slime/cider, tramp meets graphical support. Good job guys
A very good question. EMACS tries to be all things to all people ... and it is. I've used it since almost the very beginning and can't live without it.
That said, I'm not interested in the GUI stuff because it slows me down, and since EMACS is infinitely customizable I just turn it off. To each his own; some people like menus and so on. I do enable display of in-line graphics but no more than that.
Yes, there is confusion over purpose and direction, but to somewhat justify it, I'll say this. Learning EMACS, which is a big job, is a lot easier with menus and a GUI interface to help get started. Over time you learn the keystrokes and become more efficient until eventually you don't need the GUI (but you can of course still keep it).
EMACS is very much not for everyone, but for those who love it, it's indispensable.
And one more little fact: on my Asus Zenbook, I typically get 5 hours running time with a mixed environment. But if I run EMACS and EMACS alone, in a full screen, I get 10 hours.
How does this compare to ActiveX? Yes, I know tons of people absolutely loath the thing (myself included), but learning how to program back in the days of Visual Basic 3 on Windows 3.1 and being able to embed an Internet Explorer 2 container into my app sure seemed sweet at the time!
But now I mostly us nano for quick edits from the command line and jedit when in xwindows. Jedit while not perfect I like that I can carry my configuration from windows/linux/mac easily. VI is just plain annoying to use the way I think.
You mean it now looks like a 90s Windows 95-era application instead of like Windows 3.1 like it did before?
My first program:
Hell Segmentation fault
One beautiful thing about Emacs is that you can run it without the GUI:
>$ emacs -nw
I tend to use the terminal mode most of the time - especially for everything remote.
...it became a real true operating system.
I'm going to integrate systemd into emacs, any volunteers ?
After the FFMPEG fork is there a Linux distro that still uses FFMPEG & Mplayer?
Firstly: Not all distro switched to avlib.
Some simply decided to stay with ffmpeg (e.g.: opensuse never switched at all)
Some changed their opinion back (e.g.: Debian went back to ffmpeg after a while)
This is mostly to avlib never really being a good an active fork, and didn't manage to attract most developper to it.
(Unlike OpenOffice.org to which most developer migrated after the fork from LibreOffice.org).
Since then the problematic leader of FFMPEG has decided to step down,
avlib has merged back to ffmpeg
and distro are back to- / or are still using- ffmpeg again.
And the guy is now a contributor. He still writes code for ffmpeg, but he's not having a final say on everything and thus fighting with everyone to have his "one true vision(tm)" imposed.
He has fully realized that his character clashes with some in the community, has seen the disastrous result on having avlib forked (the linux ecosystem split across two different forks, none of which becomes a clear leader and each laging behind the other on some important features), and decide therefor to step down for the greater good of the community.
source: Phoronix
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Both should have quit adding shit when they were great at doing what they were supposed to do[1] and were not trying to mop the kitchen floor too.
[1] Perl is a (programmed) text-editor. It should not have become anything more because everything more that has been added since it was an awesome text editor because none of it has to do with editing text.
Will we be seeing a Slashdot story about how emacs now has native support for systemd?
#DeleteChrome
The xwidgets branch however promises even more. The main use case (at least from my point of view) isn't really to put normal widgets such as gtk buttons or sliders or anything like that in an emacs window. From my point of view the most important thing is that you will be able to embed whole applications using the GtkSocket widget. This means that you could, for example:
* Have a good PDF viewer embedded in one buffer while you are editing latex source code in another and be able to easily switch between those buffers using emacs commands.
* You could have inkscape running in one buffer and use normal inkscape editing commands for almost everything, except when you are editing text. In those situations you may want to use emacs commands instead.
* You could have a *good* webbrowser running inside emacs to search for documentation online while coding
Of course, the main xwidgets branch also opens up possibililties when it comes to prettyifying a lot of built in emacs applications. However, I don't find that very necessary in many cases. One of the main advantages with emacs is that (almost) everything is text, which means that you get a synergistic effect the more you do inside emacs.
; Witty end of comment for emacs aficionados:
(animate-string "Congratulations to Joakim Verona for getting this merged" 10 10)
Inner-plattform effect
There seems to be at least an attempt at interfacing with facebook: http://www.emacswiki.org/emacs...
When I was doing Real Work writing software, I developed the classic Emacs 'carpal tunnel' in the left hand from stretching the pinkie too much for moderator keys. A couple other people I know who are dyed-in-the-wool Emacs users have also developed that.
What other software produces its own injury? ;-)
I too have little use for the menus (not to mention the screen wasting toolbar) of emacs. However, I do like the idea of running a webbrowser from within emacs (a webkit based webbrowser widget was actually the only thing that was merged. The full xwidget branch isn't merged yet). I especially hope that this will make it possible to add words from the webbrowser to emacs autocomplete. That would be really convenient in many cases.
Sorry for being troll-ish, but I've had increasing issues with GTK+ over the years and have been broadly relieved that developers seem to be generally switching over to Qt.
I remember sigs. Oh, a simpler time!
I hope with this emacs will catch up to notepad++ roflmao...
Trying to be all things to all people is not a good way to put it. It's like saying that Java tries to be all things to all people because it let's you create many different kinds of programs. But that's the purpose of a programming language in the first place. Or that a web browser tries to be all things to all people, because you can go to Facebook, or GMail, or Wikipedia, or whatever, but the point of the browser is to let you do many many different things. Once you have a programming language in a system then you automatically can do many different things with few constraints.
So Emacs is the same. It is not an editor. It is a system that you can use to do many many different things, and editing files is just one of the things it can do by default.
Back in the VAX/BSD days, one of my co-workers used emacs as his login shell because he could do everything he wanted AND had a history more easily used than csh. I liked it, but bounced between disparate systems too often to mentally switch back and forth.
With graphics, I may need to give it a try on an X screen, since those are rather ubiquitous now.
GTK+ rendering is fucking slow. In GTK2 I used to choose the Mist rendering engine to speed things to usable speed. That's now gone in GTK3 and I don't know what to do.