I was getting unbound function errors, but now it is at the point where it runs without error, but I am not getting my capture template choice opening in emacsclient.
Anyone able to help?
Thanks.
Glenn
[SOLVED]
I got org-protocol working with my capture templates using the following:
(nyxt/mode/bookmarklets:define-bookmarklet-command-global org-capture
"Org capture templates."
"(function() {
var url = location.href;
var title = document.title;
var body = window.getSelection().toString();
var captureURL = 'org-protocol://capture?' + new URLSearchParams({url: url, title: title, body: body}).toString();
alert(captureURL); // Debugging: Display the capture URL
window.location.href = captureURL;
})()")
It alerts the captureURL to see if the constructed URL is correct. This can help verify if the issue lies in constructing the URL or in opening it with window.location.href.
Italso directly sets window.location.href to the captureURL.
This was the only thing stopping me from using Nyxt full time. Now I have this working, I can ditch FF.
I really like Nyxt myself too, it’s a pretty cool browser! I am still learning the ins-and-outs of it, personally, but I think it makes a great complement to Emacs.
Took a ton of reading and scribbling of other people’s attempts to get this working. I’m still learning myself, and recently started to actually understand what I was reading.
Worth it though. I like it. I have it set to use emacs key bindings so it feels familiar.
Questions: How well does Emacs integrate with Nyxt? And is the scripting language of Nyxt Guile (asking this because I hope so)? In general, how well do Emacs, GuixOS, and Nyxt play along with each other?
I wish that some day, a great merging of these three things would occur, so that the system itself, package management, scripting and text editing, and graphics and browsing, etc. (so, everything) become one.[1]
Personally I have not used Guile or Guix or Nyxt yet, as it takes time to learn them and my current focus is on something else, but still wishing this. And sorry for posting on a thread which is recently not active, just really have the urge to ask and to say this, and to expand on the topic if possible. ↩︎
Nyxt is written in the Common Lisp programming language which offers a great perk: everything in the browser can be customized by the user, even while it’s running!
No merging makes sense to me but proper integration by Guix, RDE or this community sounds like a good plan.
Keep in mind, that I myself am still wresting with Guix and Emacs as I have a literal config and how to integrate this with Guix and or home service is still a mystery to me.
Yes, and to go along with this, I think the integration may, at the minimal level, unify the window management of the ambient desktop environment, that of Emacs, and that of Nyxt as a web browser. Also the scripting language would be one and the same, instead of two or three dialects of, lisp.
By a merging, on the other hand, I am hoping for a unification between the Emacs buffers and the DOM trees, but this may require both the Emacs kernel and the browser engine themselves to undergo significant overhauls. This could be just wishful thinking on my part.
Agreed, it may remain impractical or even impossible for a long time for anyone or any team to ever attempt to achieve this unification. But in principle, at least, I do think this is how it should have been done. Perhaps, before it is attempted in practice, a more formalized theory of editing would be a great support for the unification.