-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 16.04.2011 09:42, schrieb Andreas Röhler: > Am 16.04.2011 13:01, schrieb Georg Brandl: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Am 15.04.2011 23:41, schrieb Andreas Röhler: >>> Am 15.04.2011 22:24, schrieb Barry Warsaw: >>>> On Apr 15, 2011, at 10:28 PM, Andreas Röhler wrote: >>>> >>>>> Am 15.04.2011 22:09, schrieb Barry Warsaw: >>>>>> On Apr 15, 2011, at 10:01 PM, Andreas Röhler wrote: >>>>>> >>>>>>> checked in the fix meanwhile. Behavior of trunk now default again. >>>>>> >>>>>> I just grabbed the update and it looks good. Thanks, I'll use this >>>>>> version >>>>>> over the weekend. >>>>>> >>>>>>> As for the new variable, would prefer a pure boolean for simplicity. >>>>>>> Maybe `py-indent-honor-listing' docstring already tells what's in >>>>>>> question? >>>>>> >>>>>> So would t or nil give the default behavior? >>>>> >>>>> Nil - it's negligent now, doesn't care for listing... >>>> >>>> How about then, calling it py-indent-honor-open-paren? >>> >>> Also good. >>> >>> But let's reflect maybe a little further: >>> point for me is not just the open paren, but the multiline-form it >>> introduces. Open paren followed by a closing same line are not of >>> interest here. >>> >>> Therefore the `listing', which doesn't express that sufficiently either. >> >> FWIW, I would have no idea at all what "py-indent-honor-listing" does if I >> just saw the name. >> >> Georg > > what about `py-indent-honor-multiline-listing' ?
I think the "listing" is the strange word here. For me, a listing is a snippet of code printed in a book. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk2poQYACgkQN9GcIYhpnLDchACfQ/UvFKHyR87MVovONm3n/e3d V6AAnR+h4X8iYYp6e7ATWNt7Tmg7JoQ0 =n/q/ -----END PGP SIGNATURE----- _______________________________________________ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
