/ Sidnei da Silva <sidnei@xxxxxxxxx> was heard to say:
| attribute name. I would prefer to have a variable to control this
| setting, say, 'nxml-indent-attribute-value', which when set to
| non-nil, would generate the following indentation:
|
| <div tal:define="tabindex tabindex/next;
| error_workflow_action errors/workflow_action|nothing;
| objs request/ids|nothing;
| review_state_label string:No change;
| target python:test(objs, objs, here);"
| tal:attributes="class
| python:test(error_workflow_action, 'field error', 'field')"
| tal:condition="not:anonymous">
|
| Does that sound reasonable, or should I just get used to it?
Hmm, I've noticed the same thing, although I'd actually prefer:
<div tal:define="tabindex tabindex/next;
error_workflow_action errors/workflow_action|nothing;
objs request/ids|nothing;
review_state_label string:No change;
target python:test(objs, objs, here);"
tal:attributes="class
python:test(error_workflow_action, 'field error',
'field')"
tal:condition="not:anonymous">
What I have noticed, as a workaround, is that if you ident the second line
of the attribute value by hand, nxml-mode indents all the rest of the lines
"correctly".
Be seeing you,
norm
--
Norman Walsh <normyahoo@xxxxxxxxxx> | Simplicity is always a
http://nwalsh.com/ | virtue.--Edward Abbey
pgpD7aWaPgEBZ.pgp
Description: PGP signature
|
