Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/919
https://github.com/apache/zeppelin/pull/1218 is better way.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does no
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/919
Thank you for your detailed explanation @Leemoonsoo and I agree with moving
interpreter-setting.json.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/919
Like comment
https://github.com/apache/zeppelin/pull/966#issuecomment-224127925 from
@felixcheung, it'll be great if interpreter-setting.json can configure
code-editor.
For example, ad
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/919
@bzz Thank you for your detail review!
I was worring about changing tab size per interpreter as @Leemoonsoo
suggests is more hard to config than per notebook or per paragraph.
How about i
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/919
To be able to change indention is very reasonable option, esp. as soon as
you start working with Python.
@astroshim It could be hard to implement per-interpreter as @Leemoonsoo
suggests for no
