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 <spencer.bli...@gmail.com> wrote:
> 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 docs don't mention the push/pop commands. I likely got them
> from MacOSX-specific_.pymolrc_file
>
>
> On Fri, Mar 11, 2016 at 10:41 AM, Spencer Bliven <spencer.bli...@gmail.com>
> wrote:
> 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
> `print cmd.get("var")`). Removing the feedback manipulation from my pymolrc
> restores the expected output from get. Is this a bug with the feedback stack?
>
> -Spencer
--
Thomas Holder
PyMOL Principal Developer
Schrödinger, Inc.
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net)
Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users
Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
