Ah okay it's my misunderstanding then. I'm trying to refresh the local setup to apply a different set of header args to that tree. After some research it looks like I should just be calling org-mode-restart. Does that seem correct? Thanks, Kevin On Tue, Jun 6, 2017 at 8:13 AM Nicolas Goaziou wrote: > Hello, > > Kevin Foley writes: > > > I've attached an ECM and below is my attempt at the backtrace. Let me > know > > if I missed something. > > > > * org-at-property-p() > > * #[0 "\301 \204 \302\303!\210\304\305!\306 \210\307\310 \311#8\204 > > \302\312 \"\210\313 !\207" [org-columns-current-fmt-compiled > > org-at-property-p user-error "Not at a property" > match-string-no-properties > > 2 org-columns-get-format-and-top-level 3 assoc-string t "No operator > > defined for property %s" org-columns-compute] 6 > > ("/home/kevin/.emacs.d/lib/org/lisp/org.elc" > > . 550375) nil]() > > * apply(#[0 "\301 \204 \302\303!\210\304\305!\306 \210\307\310 \311#8\204 > > \302\312 \"\210\313 !\207" [org-columns-current-fmt-compiled > > org-at-property-p user-error "Not at a property" > match-string-no-properties > > 2 org-columns-get-format-and-top-level 3 assoc-string t "No operator > > defined for property %s" org-columns-compute] 6 > > ("/home/kevin/.emacs.d/lib/org/lisp/org.elc" > > . 550375) nil] nil) > > * org-compute-property-at-point() > > funcall-interactively(org-compute-property-at-point) > > call-interactively(org-compute-property-at-point) > > org-property-action() > > funcall-interactively(org-property-action) > > call-interactively(org-property-action) > > org-ctrl-c-ctrl-c(nil) > > funcall-interactively(org-ctrl-c-ctrl-c nil) > > call-interactively(org-ctrl-c-ctrl-c nil nil) > > command-execute(org-ctrl-c-ctrl-c) > > AFAIU, when you are offered the `org-property-action' menu, you press > "c", for `org-compute-property-at-point'. > > As a consequence, the error is expected since there is nothing to > compute here. What did you expect instead? > > Regards, > > -- > Nicolas Goaziou > -- Thanks, Kevin Foley