Thanks, Thomas.
On Fri, Mar 11, 2016 at 6:21 PM, Thomas Holder <
thomas.hol...@schrodinger.com> wrote:
> Hi Spencer,
>
> Yes this is a bug in the feedback stack. As a workaround, you can enable
> "cmd" and "parser" feedback manually before popping:
>
> _ feedback enable, cmd parser, warnings
Hi Spencer,
Yes this is a bug in the feedback stack. As a workaround, you can enable "cmd"
and "parser" feedback manually before popping:
_ feedback enable, cmd parser, warnings errors results
_ feedback pop
Hope that helps.
Cheers,
Thomas
On 11 Mar 2016, at 04:48, Spencer Bliven
Here's a minimal .pymolrc to demonstrate the issue:
#prints response, as expected
get cartoon_power
_ feedback push
_ feedback disable,all,everything
# Nothing prints here, as expected
get cartoon_power_b
_ feedback pop
# Still nothing prints!
get cartoon_use_shader
P.S. The feedback
Since time immemorial my .pymolrc file has been wrapped by the construct
_ feedback push_ feedback disable,all,everything
..._ feedback pop
However, I've noticed that my `get` command doesn't print anything unless I
specifically re-enable all feedback after starting pymol (or use the
unwieldy