[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-08-10 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2462 @malayhm Merged to master. Thanks for the contribution again! --- 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

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-08-09 Thread malayhm
Github user malayhm commented on the issue: https://github.com/apache/zeppelin/pull/2462 Should we merge this PR? --- 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 not have this feature enabled and

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-08-04 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2462 Great! LGTM, let's merge if no more discussion. --- 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 not

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-08-01 Thread malayhm
Github user malayhm commented on the issue: https://github.com/apache/zeppelin/pull/2462 Screenshot with the latest change: ![cursor-change-pr-after-2px](https://user-images.githubusercontent.com/1881135/28850207-548e2f86-76e9-11e7-9fc9-0498f4b7ac0b.gif) --- If your

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-07-27 Thread malayhm
Github user malayhm commented on the issue: https://github.com/apache/zeppelin/pull/2462 Updated screenshot: ![cursor-change-pr-after](https://user-images.githubusercontent.com/1881135/28693294-cb29f036-72d8-11e7-8029-511301b70209.gif) --- If your project is set up

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-07-27 Thread malayhm
Github user malayhm commented on the issue: https://github.com/apache/zeppelin/pull/2462 @1ambda I have changed the fix and also verified it. It should show the thin cursor with latest changes. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-07-25 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2462 @malayhm cursor is still thick. Should I missing something? or.. --- 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

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-07-24 Thread malayhm
Github user malayhm commented on the issue: https://github.com/apache/zeppelin/pull/2462 All the comments are taken care of, if there are no more comments, could we merge this PR to master? --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-07-16 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2462 Hi, @malayhm Could you take a look the comment I left? Thanks! --- 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

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-07-14 Thread zjffdu
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2462 ping @malayhm --- 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 not have this feature enabled and wishes so, or

[GitHub] zeppelin issue #2462: ZEPPELIN-2527 Changed editor cursor to thin

2017-07-04 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2462 Thanks for the contribution @malayhm. I left a comment. --- 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 not