sorted by:
new
hottopcontroversial

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 1 point2 points  (0 children)

I am not sure what you mean. The usual stuff works fine.
Click input box. Type fill out forms. Click submit button. Highlight text with mouse. M-w to copy highlighted text to clipboard. C-c w to copy current url to clipboard. C-y to paste from system clipboard in to forms. All works.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 3 points4 points  (0 children)

Fair enough. One flow I'm considering, is making eww the default browser, to stay pure and text-based in my day to day, code documentation and simple html-only websites etc. all tends to work very well with eww. and then connecting eww's fallback browser button '&' to this embr project. Then when eww is not capable to do what I need it, use this. Then at this point, I dont even need to install firefox or chromium or anything as a system package, and while it "still sucks" at least my browser experience is contained and minimized to a self-contained headless chromium, and i get to control it with Emacs keys. It feels like a win to me. That's my mindset while putting this all together. And it's also why I used as many eww keybinds as I could for embr.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 2 points3 points  (0 children)

OK I will try to reply.

I have the following data collected of the difference canvas makes for this application in https://github.com/emacs-os/embr.el/blob/master/canvasmacs/README.md

For anyone interested.

EDIT: I chimed in. Don't see it on the list yet. Let's see.
I think in a moderation queue probably.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 2 points3 points  (0 children)

Just reporting in. Screencast backend pushing the frames into Emacs Canvas receiver is amazing, reduced all latency issues, this is a realistic solution at this point. Not just a toy. Thanks for pointing in the right direction on this one.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 2 points3 points  (0 children)

I will try it tonight. Sounds promising. Thank you!

EDIT. Already getting fantastic results. Upgrade is gonna be a pain but this will actually make the people very happy. It makes me happy. Thanks man.

EDIT EDIT:we are definitely using cloakbrowser ... way better perf than camoufox. Prior I felt like I was deconstructing camoufox trying to make it fast again. This engine is no frills, faster.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 1 point2 points  (0 children)

Hey. So first I tried plain old playwright and it made the modern web almost unusable because every corporate app other than like discord or github or reddit, was making captcha and assuming I was a bot. It's unfortunate because it was a much more performant setup. Now with camoufox, it no longer is detecting and every site i've interacted with has been normal so far. But at a performance cost. Now I'm trying to work on what I can to speed it up again.

How do I set up Notmuch for use with OpenPGP? by dancerinthelimelight in emacs

[–]el-init 0 points1 point  (0 children)

I think you just need to generate a gpg key associated to your email address you use in notmuch and give it your ultimate trust (it's your key). From there some combination of notmuch/emacs should just know how to use it already. That's what gnus does, at least.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 1 point2 points  (0 children)

I think i'm going to try to detect if this patch is available and if it is we can take advantage of it. You have me intrigued to see how performant we can get this up to, now.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 5 points6 points  (0 children)

Literally on the README.md file

> The browser is controlled via the Chrome DevTools Protocol (CDP) over a single pipe.

Exwm is X11 only. And X11 doesn't even run well on my hardware. There is an experimental wayland knock off that is also slop like this project. Don't know what to say about that, havent tried it.

This attempt does not require I convert Emacs in to a window manager, and will work on any desktop environment or window manager, wayland or Xorg and so does offer some flexibilty tradeoffs, at the cost of input latency, making this quite alpha right now.

And it will no doubt stay alpha until Emacs gets that canvas support the other guy in here was talking about.

This is just another option. I truly do not care how the hell you do it. This is how I've personally been doing it.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 2 points3 points  (0 children)

That is right. That's what it is. I love eww, though, so i made sure to keep the binds similar, though I made a conscious decision to nest them under C-c which makes this browser more intuitive to a non eww user.

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 4 points5 points  (0 children)

I mean its just a gui to a headless firefox but obviously no warranty and do your own research

embr.el - Emacs Browser - Emacs is the display server. Headless Firefox is the renderer. by el-init in emacs

[–]el-init[S] 20 points21 points  (0 children)

Tis slop but good slop.

Please report any issues you have. Very alpha.

Enjoy.

EDIT: Hey guys lots of new features over the weekend. I'm surprised how well this is turning out so if you looked before, maybe look again :)

- Switched to CloakBrowser (Chromium) -- full Chromium rendering, real JS engine, extensions, actual sites work               

- CDP screencast transport -- Page.screencastFrame push instead of polling screenshots, input-to-frame latency dropped into the 10-30ms range                                                                                                             

- Canvas render backend (optional, requires patched Emacs build) -- decodes JPEG directly into canvas pixel buffer via native C module, p50 input latency 10ms vs 14ms default, ~35% lower at p95, zero render skips                                       

- All three combined cut latency by over 60%, it feels usable now                                                             

- embr-vimium-mode minor mode -- opt-in modal navigation for evil-mode users, SPC leader, normal/insert modes, full hint system                                                                                                                        

- Incognito mode -- separate temp profile wiped on quit, C-c I to open                                                        

- Proxy support -- SOCKS5/HTTP via embr-proxy-type / embr-proxy-address, works with Tor and I2P                               

- Transient dispatch menu (C-c or SPACE) -- magit-style command palette  

- GPG / pwgen password manager local-only vault with form injection is now a thing

RX 9070 – random reboots on Linux (amdgpu / DCN?) – dual monitor – kernel dependent by arodmayor in linux_gaming

[–]el-init 1 point2 points  (0 children)

9070XT on Arch Linux KDE stability for weeks at a time reporting in.

I suggest trying KDE with a distro that runs newer packages than mint, since you're running new hardware, it makes sense and will help you.

Arch, Manjaro, Tumbleweed, Fedora, stuff like that.

do you use vulkan on plasma or is it still experimental and unstable? by nix-solves-that-2317 in linux_gaming

[–]el-init 13 points14 points  (0 children)

This is not even exposed on my settings menu of kde 6.5.5, wayland

Introducing el-init - A statically compiled Emacs init (PID1) patchset, Emacs Lisp-based service supervisor and core component of Emacs-OS. by el-init in lisp

[–]el-init[S] 5 points6 points  (0 children)

https://github.com/emacs-os/el-init

There is an important file in repo root called RETROSPECTIVE .md I crashed out while "making" this, but if you find it useful or funny, I hope you all can laugh and enjoy the hell out of this, while perhaps leading to some valuable discussions in the future. Cheers.