nEXT inside a emacs-buffer?

[cjohansson]

I would love having nEXT inside a emacs-buffer, is it possible? If not, would it be possible in the future?

[jmercouris]

Hi Christian, thank you for your question! Yes, it is technically possible, and only on Linux, using something like the XWidgets (I think that’s what it’s called) support in Emacs. This allows you to have an X Application as a buffer. This is of course not ideal. Instead, if on Linux, I would recommend something like Stump WM. If you are on MacOS, as far as I know this will not be easily possible. Thank you for your interest!

…

-John

On Dec 21, 2017, at 10:46, Christian Johansson ***@***.***> wrote: I would love having nEXT inside a emacs-buffer, is it possible? If not, would it be possible in the future? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#44>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABnQDq0JlBNcO7ntggEY4yU3iBl7GD7hks5tCikPgaJpZM4RJlMG>.

[cjohansson]

Ok thanks will check that out :-)

[seanfarley]

Just a note that there is some experimental work for getting xwidgets (well, webkit) in an emacs buffer in macos: https://github.com/veshboo/emacs

I've also done some work to get that to work in Mituharu's macos port of emacs as well: https://bitbucket.org/mituharu/emacs-mac/pull-requests/1/rfc-add-xwidget-implementation/diff

That being said, I'm not sure the emacs approach is really suitable or even a goal of this project (I'd be interested to hear back on that, though).

[jmercouris]

Hey Sean, that is some amazing stuff! I had no idea that was even remotely possible! The emacs approach is not a goal of this project, though I’m not heavily against it if someone wants to integrate it. I imagine if you have just webkit working, and since there is now an X version/ and a cocoa version of nEXT, it should be possible to also run nEXT within a buffer. That may be confusing to have buffers within buffers though.

What also could be possible if I provide an external API for getting individual views extracted out of nEXT to make it easier to have a “buffer per buffer” with on nEXT instance, so you can still have all of the other functionality I’ve built in like link-hinting etc.

[seanfarley]

Oh, yeah, that sounds promising! Having an external API and/or one-buffer makes a lot of sense. I'll have to check back when I have a bit more time to dig around with all of this.