4 ms·
I love julia and wouldn't mention this if I hadn't written a big chunk of data-analysis code with it... It's a small gripe, but one thing that really bothers m
by CountSessine 5y ago
I love julia and wouldn't mention this if I hadn't written a big chunk of data-analysis code with it...
It's a small gripe, but one thing that really bothers me is that they gave up on libreadline for the REPL (for what seem like fairly superficial build management issues, looking at the original email threads) in favor of a custom solution, which
* doesn't support vim-like or emacs-like keybindings, and
* won't read my .inputrc file and my customizations
It's just maddening using julia's REPL without this. It's easy to dismiss user complaints like this, but I can go back and forth between bash and into the python REPL and all of my line discipline actually makes sense, but then the julia REPL is broken and clumsy.
Also, pdb.set_trace() is a lot easier and more productive than what Debugging.jl has to offer.
- AlexCoventry 5y agoHave you experimented with something like rlwrap? https://github.com/hanslub42/rlwrap https://github.com/hanslub42/rlwrap
- CountSessine 5y agoIt interferes with the Julia REPL line discipline.
- rrock 5y agoYou might have some sort of dangling config issue somewhere? I use the emacs keybindings in the Julia REPL all the time. They work fine out of the box (at least here).
- CountSessine 5y agoAh good to hear. I wish I could edit my post. But vim bindings are nowhere to be found. The good news I guess is that having a clumsy REPL has really gotten me into vim-slime.
- ChrisFoster 5y agoHave you tried Infiltrator.jl? It's great for breaking out into an interactive REPL from some inner scope, allowing you to examine the local variables and other program state interactively. This covers the part of the functionality of pdb.set_trace() which I care about.