Hello Adam,
Adam Porter writes:
> You might consider using the function buffer-local-value instead of the
> macro with-current-buffer. Not that it matters so much here, but
> benchmarking shows that it is much faster when simply accessing the
> buffer-local value of a variable.
Thank you. Such
On 2019-10-16 at 12:38 +02, Nicolas Goaziou wrote...
> Of course, meawhile, do not rely on undefined behaviour :)
Would you accept a documentation patch that defines the current behavior?
Then I get what I want, and it is on future developers to not mess it up :).
-k.
Hello,
Jens Lechtenboerger writes:
> Thanks! A patch is attached.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Ken Mankoff writes:
> Can you provide a more obvious hint? :)
I don't have enough time to help you more on that, sorry. I didn't even
look closely to the issue you're encountering. Hopefully, someone else
on the ML can provide guidance on it.
> I've read the documentation on called-inte
I guess you are having a problem with the version of jupyter, and maybe
jupyter_client. Maybe upgrading thises will fix the ipython problem.
See notes below for python sessions.
Prof. Dr. Johanna May writes:
> Hi everybody,
>
> I am creating lecture notes including some python snippets. Now, in
Hi Nicolas,
On 2019-10-16 at 12:38 +02, Nicolas Goaziou wrote...
> Note that what you want, i.e., to distinguish behaviour depending on
> the location of the call stack is cheesy, at best. Think about macros,
> user-defined functions, etc.
Yes, it felt a bit hackish. But I'm new to this level of
Hi everybody,
I am creating lecture notes including some python snippets. Now, in
order to teach jupyter notebook use I would like to include just the
same code as in a python snippet in an ipython snippet.
However ipython blocks don't work in my set up and I could not figure
out which dependen
Hello,
Ken Mankoff writes:
> Hmm. So it turns out (I think) this patch isn't necessary. The
> behavior I wanted and thought I implemented is actually the default
> behavior! I think the behavior is undefined for :eval not equal to
> "yes", "no", or "query", but the current undefined implementati
Gustav Wikström writes:
> I'd like to take the next step with this patch. I'm hesitant to do it
> without wider support though, since only a few people have commented.
>
> @Marco Wahl; As I understand you've applied the patch and tried it
> out. Have you found any issues yet? What do you think of
