I have been using the @nowarn macro mentioned here: https://github.com/JuliaLang/julia/pull/14759#issuecomment-194603246
Hopefully there will eventually be a non-hacky way to customize the display of this warning. On Monday, September 5, 2016 at 10:38:30 AM UTC-4, Scott T wrote: > > I've started putting those functions into a temporary module because > replacing the module produces just one short warning. Right after the end > of that module I will put any analysis code that I want to re-run on each > reload, or sometimes I will write a main() function and call that. > Basically as soon as you remove stuff from the global scope it becomes much > easier to work with. If the functions I am writing prove useful enough and > I stop changing them, I'll write a simple package for my own use and put > them in there. > > Juno also seems to have a nice way to make this easier: > https://github.com/JunoLab/atom-julia-client/blob/master/manual/workflow.md > > On Sunday, 4 September 2016 19:58:39 UTC+1, Matthieu wrote: >> >> My usual workflow is to put all the functions in a file, that I call >> using include(""). >> If I modify one or several of these functions, I call include("") again. >> In Julia 0.5, a method redefinition warning is printed for each function >> in the file. This makes the REPL unreadable. >> Is there a way around it? >> Calling workspace() before include() avoids the warning but it reloads >> every package and recompiles every function which is time consuming. >> >
