keno / terminals.jl Goto Github PK

needs something in REQUIRES...

As described in https://discourse.julialang.org/t/ann-plans-for-removing-packages-that-do-not-yet-support-1-0-from-the-general-registry/ we are planning on removing packages that do not support 1.0 from the General registry. This package has been detected to not support 1.0 and is thus slated to be removed. The removal of packages from the registry will happen approximately a month after this issue is open.

To transition to the new Pkg system using Project.toml, see https://github.com/JuliaRegistries/Registrator.jl#transitioning-from-require-to-projecttoml.
To then tag a new version of the package, see https://github.com/JuliaRegistries/Registrator.jl#via-the-github-app.

If you believe this package has erroneously been detected as not supporting 1.0 or have any other questions, don't hesitate to discuss it here or in the thread linked at the top of this post.

A refresh never actually refreshes the entire screen. This seems to be caused by the size of the stdout buffer for large screen updates. I'm not sure if Linux handles this fine, but OS X definitely has some problems. Probably need to experiment with the buffer settings.

See JuliaLang/METADATA.jl#3769; we're about to make Color uninstallable on julia 0.4.

Transition info is here.

http://status.julialang.org

julia> using Terminals
ERROR: Color not found
 in require at loading.jl:39
 in include at boot.jl:238
at /home/idunning/pkgtest/.julia/v0.2/Terminals/src/Terminals.jl:140

This issue is being filed by a script, but if you reply, I will see it.

PackageEvaluator.jl is a script that runs nightly. It attempts to load all Julia packages and run their test (if available) on both the stable version of Julia (0.2) and the nightly build of the unstable version (0.3).

The results of this script are used to generate a package listing enhanced with testing results.

The status of this package, Terminals, on...

• Julia 0.2 is 'Package doesn't load.'
• Julia 0.3 is 'Package doesn't load.'

'No tests, but package loads.' can be due to their being no tests (you should write some if you can!) but can also be due to PackageEvaluator not being able to find your tests. Consider adding a test/runtests.jl file.

'Package doesn't load.' is the worst-case scenario. Sometimes this arises because your package doesn't have BinDeps support, or needs something that can't be installed with BinDeps. If this is the case for your package, please file an issue and an exception can be made so your package will not be tested.

This automatically filed issue is a one-off message. Starting soon, issues will only be filed when the testing status of your package changes in a negative direction (gets worse). If you'd like to opt-out of these status-change messages, reply to this message.

I get a bunch of warnings of the form

Warning: New definition 
    write(Terminal,Uint8,Any) at /Users/stevenj/.julia/Terminals/src/Terminals.jl:351
is ambiguous with 
    write(IO,Integer,Type{ReverseByteOrder}) at io.jl:46.