-
Notifications
You must be signed in to change notification settings - Fork 9
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
reprex exercise #7
Comments
stop("This R error is weird")
#> Error in eval(expr, envir, enclos): This R error is weird Created on 2024-08-28 with reprex v2.1.1 |
1 similar comment
stop("This R error is weird")
#> Error in eval(expr, envir, enclos): This R error is weird Created on 2024-08-28 with reprex v2.1.1 |
stop("This R error is weird")
#> Error in eval(expr, envir, enclos): This R error is weird Created on 2024-08-29 with reprex v2.1.1 |
devel > stop("This R error is weird")
Error: This R error is weird |
stop("This R error is weird") |
stop("This R error is weird") |
stop("This R error is weird") |
stop("This R error is weird")
#> Error in eval(expr, envir, enclos): This R error is weird Created on 2024-08-29 with reprex v2.1.1 |
stop("This R error is weird") |
stop("This R error is weird") |
Created on 2024-09-01 with reprex v2.1.1 |
stop("This R error is weird") |
Somehow my reprex::reprex() is giving a strange answer rather than the correct one, but after I tried a few times it gives the correct answer (shown below). Does anybody know what had happened? stop("This R error is weird")
#> Error in eval(expr, envir, enclos): This R error is weird Created on 2024-09-05 with reprex v2.1.1 |
reprex::reprex() |
stop("This R error is weird") |
I had this same error the first time I tried the exercise. I realized that the Clipboard was storing reprex::reprex() rather than stop("This R error is weird"). |
stop("This R error is weird") |
Got it! I've tried restarting the R session to make it work. Thanks for your answer! |
reprex::reprex() |
Similar to #2, but for 2024.
-- 0 --
Created on 2024-08-20 with reprex v2.1.1
The text was updated successfully, but these errors were encountered: