-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Recommend a workflow for methodswith in the REPL #46746
Conversation
This seems like a strange place to put basic information on how to store objects to variables or how to index arrays etc. But also see #38791.
|
This This PR is recommending a workflow and yeah it might not be the best place to put it, but sure its a workflow. Where do you think it should be anyways? |
Perhaps this could be a section in doc/src/manual/arrays.md about how to view large arrays in the REPL. I've seen that request come up before. |
Don't know where exactly it should be in |
I would note that for Emacs users (maybe Vim? though I know little about Vim), having the REPL dump all on Note that I am not trying to dismiss this PR outright, but I believe that suggesting a burdensome approach in the manual or docstrings should be avoided. |
There are many good ways to view large vectors (e.g. using a text editor or ide as @andrewjradcliffe mentioned). The recommendations in this PR are workable, but I do not think they are worth recommending for all users of |
I've often seen first timers coming from OOP language and then they complain about having to break their workflows and ask questions or google just to know a simple function to use, where in the classical OOP-style, all they needed was an IDE and a dot syntax to list all available methods.
My point is, anything that can help with stuffs like this should be documented in a simple way. My first time using Julia, I certainly didn't wanted the
methodswith
function, because it broke the whole REPL and won't even show the first 100 functions if the methods is more than 700.Until recently I started using the workflow I recommended in this patch. So it will be nice if something of that nature is done and then point users to it to keep their workflow stable, ALL IN THE REPL.