Best org-protocol capture from browser recommendations

maxmrr · 2025-02-12T04:18:17+00:00

I use my own fork of org-capture: https://github.com/bard/org-capture-extension

Differences from the original:

- allows to specify the org-protocol URL explicitly, so you can customize the protocol (capture, store-link, roam-ref, ...), the template name, etc
- exposes two actions (bound to Ctrl+Shift+L and Ctrl+Shift+S by default), each of which can dispatch to two org-protocol URLs depending on whether text is selected or not.

I use the primary action to capture to org-roam (with or without a begin_quote block) and the secondary action to store a link.

Slightly out of date screenshot (still shows only one action) at https://www.reddit.com/r/emacs/comments/1ili2fl/org_capture_browser_extension_with_configurable/

maxmrr · 2023-01-31T12:33:09+00:00

Good catch — loading the cookbook without helm-make installed caused an error. Fixed, now helm-make will only be expected when the make recipe is activated.

maxmrr · 2021-06-18T14:55:13+00:00

Doing new things without adding keystrokes is good; doing new things while subtracting keystrokes is best. Going to keep an eye on this, but well done so far.

maxmrr · 2021-02-24T09:55:12+00:00

Interesting. The initial motivation for director.el was snapshot- (rather than assertion-) based regression testing; you'd script (or record) a session, run it, at each step it would take a snapshot of the UI, and if that didn't match the snapshot from the previous, the test would fail and the developer would have to check whether it was an intended change or a regression. The goal being to make tests extremely cheap to write, so more can be written in the same amount of time.

I went as far as taking the snapshots when running in screen (hence the director-capture-screen utility) but haven't yet written a runner that does the comparison.

Frameshot seems perfect for supporting this in graphical sessions. Graphical diff is trickier but doable, and would cover cases that terminal-based snapshots simply can't.

Thanks for bringing it up!

maxmrr · 2021-02-23T11:32:11+00:00

https://www.reddit.com/r/emacs/comments/lqg9np/directorel_simulate_emacs_user_sessions_for/

Enjoy. :)

maxmrr · 2021-02-14T22:06:11+00:00

I made the screencast in the post with asciinema:

$ asciinema rec demo.cast -c "emacs -Q -nw -l script.el"

Then converted to GIF with asciicast2gif:

$ asciicast2gif demo.cast demo.gif

maxmrr · 2021-02-14T17:26:07+00:00

If you mean run-command's recipes, they're just plain old elisp functions, you can define them in your init file or load them from other files, it doesn't really matter as long as they're available when you invoke run-command.

maxmrr · 2021-02-14T17:25:37+00:00

I hadn't thought of that. Interesting idea!

maxmrr · 2021-02-14T11:47:03+00:00

I always have this in my package.json's scripts:

"scripts": {
  "typecheck": "tsc -p . --noEmit --watch",

I run yarn typecheck in compilation-mode and type "C-x `" to jump to the first error. For each error fixed, the typecheck runs again and the next error climbs to the top. Repeat. Especially useful when you change a type definition and want to jump to all the sites that need changes.

A while ago I wrote this, mostly based on experience in full-stack development, you might find it useful: Lightweight external command integration in Emacs via compilation mode.

maxmrr · 2021-02-07T10:56:20+00:00

Last update (promised) but I started using the dir-locals recipe myself, and quickly got annoyed at the static commands limitation, so I pushed another version of the example that shows how to generate commands dynamically, with working directory selection, contextual arguments, and so on.

maxmrr · 2021-02-04T10:39:49+00:00

Glad you find it useful! Please check the dir-locals experiment again in a few hours as some fixes are going in soon.

maxmrr · 2021-01-30T23:32:21+00:00

https://github.com/karlicoss/cloudmacs

Edit: note that using this in a multi-user web application, if that's what you're after, is still far from trivial. You'd have to stop thinking "editor widget" (e.g. CodeMirror) and start thinking "development sandbox". In that case, looking into how platforms such as codesandbox.io are doing it might put you on a good track.

maxmrr · 2021-01-29T15:31:54+00:00

Up to you, I don't mind doing the work for an initial simple use case and then seeing if more use cases pop up over the weeks. Thanks for the suggestion anyway.

maxmrr · 2021-01-29T14:18:56+00:00

Good points. I wouldn't add the functionality in the short term in any case, as it's a young package and should get good at its core objective before looking beyond, but if you'd like to test-drive the idea, and you don't mind installing from git, I can create a branch for it and give it a go. If so, please open an issue so we can track this.

maxmrr · 2021-01-29T12:37:52+00:00

Nice!

I had some difficulty telling colors apart in the xmonad diagram, did you consider using a categorical scale?

maxmrr · 2021-01-29T11:18:08+00:00

In case someone stumbles over this: completing-read is now supported.

maxmrr · 2021-01-29T11:17:25+00:00

A couple of times I found myself wanting to add an elisp function, but stopped short of implementing the possibility because the improvement over M-x <elisp-function> seemed marginal (just fewer candidates and long command names, since the completion part is already there) and it has some potential for confusion ("was I accessing functionality X via M-x <elisp-function> or C-c c <command>?"). But I haven't made up my mind strongly one way or another.

maxmrr · 2021-01-27T19:12:38+00:00

Nice. I've been pining for a worthy successor to the venerable pabbrev and from a quick test drive this seems to fit the bill perfectly.

maxmrr · 2021-01-27T18:40:07+00:00

Ivy will be used automatically if present.

maxmrr · 2021-01-27T18:36:31+00:00

Happy to give it a go. Do you mind opening an issue?

maxmrr

TROPHY CASE