Patch v5 (fbed0861) of org-protocol.org <http://org-protocol.org/> rewrite.
> 
> Thank you very much for your careful attention to feedback, Charles! And
> thanks to Max for yesterday's careful review, which covered everything I
> spotted and quite a bit I didn't.
> 
> I think this patch is ready to be applied, and that any further
> refinement can be done against Charles' rewrite as the new baseline.
> I'll merge it tomorrow night if there's no objection or new patch.


A pleasure to finally update this page for the Org community. I look forward to 
seeing this in the wild.

Attached below is a patch which reflects comments from Christian. 

> Like Max, though, I think repeating the template twice feels redundant.
> Perhaps the same pedagogical effect could be achieved by keeping the
> longer example and demarcating the template sexp with a comment line?

Removed the single entry capture template example, added demarcation comments.

> 
> Btw, given that the car of a capture template is supposed to be a one-
> or two-character key for template selection, it's fascinating that the
> string "capture" works as a key for Org protocol capture (but fails to
> be shown in the interactive capture template selection dialog, which is
> convenient in this case).
> 


While I have been using this behavior of long key names to omit Org protocol 
capture templates from capture template selection, I wonder if this intended 
design or an incidental implementation. 


Thanks again to Max and Christian for your feedback.

All my best - 
Charles



Attachment: 0001-org-protocol.org-Rewrite-for-2025.patch
Description: Binary data


—
Charles Y. Choi, Ph.D.
kickingve...@gmail.com

Reply via email to