Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

common-lisp-jupyter #35

Open
utterances-bot opened this issue Sep 28, 2020 · 2 comments
Open

common-lisp-jupyter #35

utterances-bot opened this issue Sep 28, 2020 · 2 comments

Comments

@utterances-bot
Copy link

common-lisp-jupyter

https://40ants.com/lisp-project-of-the-day/2020/09/0197-common-lisp-jupyter.html

Copy link

Thank you for the review! I'll look into adding a render method.

There are some new features that are not very well documented yet. Widgets are probably at the top of that list, but there are also facilities for code inspection and completion. Code inspection can be done in a popup (Shift-Tab) or in a side pane (Ctrl/Cmd-I) and code completion can be done via Tab. Tabbing on a paren will also auto indent the code in the current cell.

@svetlyak40wt
Copy link
Member

Thank you for the review! I'll look into adding a render method.

render method is already there. But seems the code which calls it, checks the type of the value, returned by the cell.

To make render method be useful without having to inherit objects from the jupyter:result, you need to add another method to this protocol – renderable-p. renderable by default should return nil. If returns t, then jupyter:render` can be called for this result to get its representation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants