Skip to content

Commit f3f45bf

Browse files
committed
docs: fix a typo
Signed-off-by: John E <jeis4wpi@outlook.com>
1 parent 1766d3f commit f3f45bf

24 files changed

Lines changed: 49 additions & 49 deletions

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ It lets you activate the test environment from a given package.
99

1010
### Why is this useful?
1111

12-
This lets you run code in the test enviroment, interactively; giving you access to all your test-only dependencies.
12+
This lets you run code in the test environment, interactively; giving you access to all your test-only dependencies.
1313
When you run `]test` in the REPL, a new Julia process is started which activates a temporary environment containing the tested package together with all its test-only dependencies.
1414
These can be either defined in the `[extras]` section in the package's `Project.toml` or in a separate `test/Project.toml`.
1515
The special temporary environment is different than the plain package environment (which doesn't contain the extra test dependencies) or the `test/Project.toml` environment (which doesn't contain the package itself, and may not exist).
@@ -19,8 +19,8 @@ Julia does not offer an official mechanism to activate such an environment outsi
1919
That's what `TestEnv.activate()` is for.
2020

2121
## Note on installation:
22-
Like other developer focused tools, TestEnv.jl should not be added as a dependency of the package you are developing, but rather added to your global enviroment, so it is always available.
23-
The easiest way to install it to the global enviroment is to start julia (without passing the `--project` argument), and then run `] add TestEnv`.
22+
Like other developer focused tools, TestEnv.jl should not be added as a dependency of the package you are developing, but rather added to your global environment, so it is always available.
23+
The easiest way to install it to the global environment is to start julia (without passing the `--project` argument), and then run `] add TestEnv`.
2424

2525

2626
## Example
@@ -55,4 +55,4 @@ end
5555
```
5656

5757
### See also:
58-
- [Discourse Release Announcement](https://discourse.julialang.org/t/ann-testenv-jl-activate-your-test-enviroment-so-you-can-use-your-test-dependencies/65739)
58+
- [Discourse Release Announcement](https://discourse.julialang.org/t/ann-testenv-jl-activate-your-test-environment-so-you-can-use-your-test-dependencies/65739)

src/julia-1.0/activate_do.jl

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
"""
22
TestEnv.activate(f, [pkg])
33
4-
Activate the test enviroment of `pkg` (defaults to current enviroment), and run `f()`,
5-
then deactivate the enviroment.
6-
This is not useful for many people: Julia is not really designed to have the enviroment
4+
Activate the test environment of `pkg` (defaults to current environment), and run `f()`,
5+
then deactivate the environment.
6+
This is not useful for many people: Julia is not really designed to have the environment
77
being changed while you are executing code.
88
However, this *is* useful for anyone doing something like making a alternative to
99
`Pkg.test()`.

src/julia-1.0/activate_set.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"""
55
TestEnv.activate([pkg])
66
7-
Activate the test enviroment of `pkg` (defaults to current enviroment).
7+
Activate the test environment of `pkg` (defaults to current environment).
88
"""
99
function activate(pkg::AbstractString=current_pkg_name())
1010
outer_tmp = mktempdir()

src/julia-1.1/activate_do.jl

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
"""
22
TestEnv.activate(f, [pkg])
33
4-
Activate the test enviroment of `pkg` (defaults to current enviroment), and run `f()`,
5-
then deactivate the enviroment.
6-
This is not useful for many people: Julia is not really designed to have the enviroment
4+
Activate the test environment of `pkg` (defaults to current environment), and run `f()`,
5+
then deactivate the environment.
6+
This is not useful for many people: Julia is not really designed to have the environment
77
being changed while you are executing code.
88
However, this *is* useful for anyone doing something like making a alternative to
99
`Pkg.test()`.

src/julia-1.1/activate_set.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"""
55
TestEnv.activate([pkg])
66
7-
Activate the test enviroment of `pkg` (defaults to current enviroment).
7+
Activate the test environment of `pkg` (defaults to current environment).
88
"""
99
function activate(pkg::AbstractString=current_pkg_name())
1010
outer_tmp = mktempdir()

src/julia-1.11/activate_do.jl

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
"""
22
TestEnv.activate(f, [pkg]; allow_reresolve=true)
33
4-
Activate the test enviroment of `pkg` (defaults to current enviroment), and run `f()`,
5-
then deactivate the enviroment.
6-
This is not useful for many people: Julia is not really designed to have the enviroment
4+
Activate the test environment of `pkg` (defaults to current environment), and run `f()`,
5+
then deactivate the environment.
6+
This is not useful for many people: Julia is not really designed to have the environment
77
being changed while you are executing code.
88
However, this *is* useful for anyone doing something like making a alternative to
99
`Pkg.test()`.

src/julia-1.11/activate_set.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"""
55
TestEnv.activate([pkg]; allow_reresolve=true)
66
7-
Activate the test enviroment of `pkg` (defaults to current enviroment).
7+
Activate the test environment of `pkg` (defaults to current environment).
88
"""
99
function activate(pkg::AbstractString=current_pkg_name(); allow_reresolve=true)
1010
ctx, pkgspec = ctx_and_pkgspec(pkg)

src/julia-1.12/activate_do.jl

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
"""
22
TestEnv.activate(f, [pkg]; allow_reresolve=true)
33
4-
Activate the test enviroment of `pkg` (defaults to current enviroment), and run `f()`,
5-
then deactivate the enviroment.
6-
This is not useful for many people: Julia is not really designed to have the enviroment
4+
Activate the test environment of `pkg` (defaults to current environment), and run `f()`,
5+
then deactivate the environment.
6+
This is not useful for many people: Julia is not really designed to have the environment
77
being changed while you are executing code.
88
However, this *is* useful for anyone doing something like making a alternative to
99
`Pkg.test()`.

src/julia-1.12/activate_set.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"""
55
TestEnv.activate([pkg]; allow_reresolve=true)
66
7-
Activate the test enviroment of `pkg` (defaults to current enviroment).
7+
Activate the test environment of `pkg` (defaults to current environment).
88
"""
99
function activate(pkg::AbstractString=current_pkg_name(); allow_reresolve=true)
1010
ctx, pkgspec = ctx_and_pkgspec(pkg)

src/julia-1.13/activate_do.jl

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
"""
22
TestEnv.activate(f, [pkg]; allow_reresolve=true)
33
4-
Activate the test enviroment of `pkg` (defaults to current enviroment), and run `f()`,
5-
then deactivate the enviroment.
6-
This is not useful for many people: Julia is not really designed to have the enviroment
4+
Activate the test environment of `pkg` (defaults to current environment), and run `f()`,
5+
then deactivate the environment.
6+
This is not useful for many people: Julia is not really designed to have the environment
77
being changed while you are executing code.
88
However, this *is* useful for anyone doing something like making a alternative to
99
`Pkg.test()`.

0 commit comments

Comments
 (0)