No operator defined for property header-args

No operator defined for property header-args

[Kevin Foley]

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

I'm getting the error "No operator defined for property header-args" when
trying to run `org-property-action` on the `header-args` property below:

    * outline header
    :PROPERTIES:
    :header-args:bash:    :tangle yes
    :END:

I'm able to set the same properties using

    #+PROPERTY: header-args:bash :tangle yes

I've tried running `emacs -Q` and get the same error.  I'm using
org-version is 9.0.7

[-- Attachment #2: Type: text/html, Size: 617 bytes --]

Re: No operator defined for property header-args

[Nicolas Goaziou]

Hello,

Kevin Foley <kfoley15@gmail.com> writes:

> I'm getting the error "No operator defined for property header-args" when
> trying to run `org-property-action` on the `header-args` property below:
>
>     * outline header
>     :PROPERTIES:
>     :header-args:bash:    :tangle yes
>     :END:
>
> I'm able to set the same properties using
>
>     #+PROPERTY: header-args:bash :tangle yes
>
> I've tried running `emacs -Q` and get the same error.  I'm using
> org-version is 9.0.7

I'm not able to reproduce it. Could you post an ECM and a backtrace?

Regards,

-- 
Nicolas Goaziou

Re: No operator defined for property header-args

[Kevin Foley]

[-- Attachment #1.1: Type: text/plain, Size: 2042 bytes --]

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)

Thanks,
Kevin Foley

On Mon, Jun 5, 2017 at 5:00 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Kevin Foley <kfoley15@gmail.com> writes:
>
> > I'm getting the error "No operator defined for property header-args" when
> > trying to run `org-property-action` on the `header-args` property below:
> >
> >     * outline header
> >     :PROPERTIES:
> >     :header-args:bash:    :tangle yes
> >     :END:
> >
> > I'm able to set the same properties using
> >
> >     #+PROPERTY: header-args:bash :tangle yes
> >
> > I've tried running `emacs -Q` and get the same error.  I'm using
> > org-version is 9.0.7
>
> I'm not able to reproduce it. Could you post an ECM and a backtrace?
>
> Regards,
>
> --
> Nicolas Goaziou
>

[-- Attachment #1.2: Type: text/html, Size: 3347 bytes --]

[-- Attachment #2: header-args-ecm.org --]
[-- Type: application/octet-stream, Size: 107 bytes --]

* outline header
:PROPERTIES:
:header-args:bash:    :tangle yes
:END:

#+BEGIN_SRC bash
  ls -la
#+END_SRC

Re: No operator defined for property header-args

[Nicolas Goaziou]

Hello,

Kevin Foley <kfoley15@gmail.com> 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

Re: No operator defined for property header-args

[Kevin Foley]

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

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 <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Kevin Foley <kfoley15@gmail.com> 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

[-- Attachment #2: Type: text/html, Size: 2911 bytes --]

Re: No operator defined for property header-args

[Nicolas Goaziou]

Hello,

Kevin Foley <kfoley15@gmail.com> writes:

> 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?

I don't think you need to refresh anything for node properties. I.e.,
the new value will be used during next evaluation.


Regards,

-- 
Nicolas Goaziou

Re: No operator defined for property header-args

[Kevin Foley]

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

You're right, I thought because a refresh was needed for #+PROPERTY: it was
also needed for property blocks.  Thanks for your help.

Thanks,
Kevin Foley

On Wed, Jun 7, 2017 at 12:20 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Kevin Foley <kfoley15@gmail.com> writes:
>
> > 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?
>
> I don't think you need to refresh anything for node properties. I.e.,
> the new value will be used during next evaluation.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

[-- Attachment #2: Type: text/html, Size: 1394 bytes --]