-
Notifications
You must be signed in to change notification settings - Fork 62
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
method error on julia nightly #222
Comments
Could you try with #223? |
This is weird, I don't get any errors when loading from REPL, but when I add it to |
This happens to me, too. I can run any code in my import Pkg
if isfile("Project.toml")
Pkg.activate(".")
try
using OhMyREPL
colorscheme!("Base16MaterialDarker")
enable_autocomplete_brackets(false)
catch
Pkg.add("OhMyREPL")
end
end julia> versioninfo()
Julia Version 1.6.0-DEV.1378
Commit 905ebec534 (2020-10-29 20:12 UTC)
Platform Info:
OS: macOS (x86_64-apple-darwin18.7.0)
CPU: Intel(R) Xeon(R) W-2140B CPU @ 3.20GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-11.0.0 (ORCJIT, skylake-avx512) Please fix this! |
Hi, I can see that this issue is closed with reference to #223 but I still have it on OhMyREPL master on Julia 1.6: MethodError: no method matching keymap(::Vector{Dict})
Closest candidates are:
keymap(::Any, ::Union{REPL.LineEdit.HistoryPrompt, REPL.LineEdit.PrefixHistoryPrompt}) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.6/REPL/src/LineEdit.jl:2014
keymap(::Union{Vector{Dict{Any, Any}}, Vector{Dict{Char, Any}}}) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.6/REPL/src/LineEdit.jl:1617
keymap(::REPL.LineEdit.PromptState, ::REPL.LineEdit.Prompt) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.6/REPL/src/LineEdit.jl:2512 The offending lines in startup.jl are: try
using OhMyREPL
colorscheme!("Monokai24bit")
catch err
@warn "Could not load OhMyREPL"
end Could we reopen the issue, or is there a fix on a particular branch? |
@sivapvarma this was just fixed in #232 |
The text was updated successfully, but these errors were encountered: