Skip to content

Conversation

@m-j-w
Copy link
Contributor

@m-j-w m-j-w commented Apr 21, 2017

This continues the original PR #20162 of @kbdave134.
See the commit message for the changes made.


The absolute path of the directory containing the Julia executable, which sets
the global variable [`Base.JULIA_HOME`](@ref). If `$JULIA_HOME` is not set, then
`Base.JULIA_HOME` defaults to its compile-time value.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this is still incorrect

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In what sense?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the value of Base.JULIA_HOME is determined at run time, not compile time

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(and sorry for not taking your comments into account, they didn't show up on the last version...)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

github can be weird about when it does or does not show old review comments, no problem


### `JULIA_PKGDIR`

The path of the parent directory `Dir._pkgroot()` for the version-specific Julia
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pkg.Dir._pkgroot(), since Dir isn't re-exported from Pkg

$HOME/.julia
```

Then the repository location [`Base.Pkg.dir`](@ref) for a given Julia version is
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pkg is exported from Base, so we could leave off Base. here

paths

```
$JULIA_HOME/../local/share/julia/site/v$(Base.VERSION.major).$(Base.VERSION.minor)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could leave off Base. from VERSION and LOAD_PATH since those are exported from Base

### `JULIA_GC_WAIT_FOR_DEBUGGER`

If set to anything besides `0`, then the Julia garbage collector will wait for
the debugger to attach instead of aborting whenever there's a critical error.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"a debugger" ? #20162 (comment)

!!! note

This environment variable has an effect only if Julia was compiled with
`JL_DEBUG_BUILD` set—in particular, the `julia-debug` executable is always
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"set - in particular" #20162 (comment)

@tkelman
Copy link
Contributor

tkelman commented Apr 21, 2017

The previous commit here failed the doc build. Does this build for you locally? Shouldn't do [ci skip] here.

@tkelman
Copy link
Contributor

tkelman commented Apr 21, 2017

Probably also want to squash together any commits by the same author that failed the whitespace check (or doc build). If you'd prefer, I could do that as long as you enabled "allow edits by maintainers."

@m-j-w m-j-w force-pushed the doc-environment-variables-continued branch from d6d5381 to f56ff83 Compare April 21, 2017 22:43
@m-j-w
Copy link
Contributor Author

m-j-w commented Apr 21, 2017

Okay, I squashed my commits and made the documentation building work again (removed a faulty reference at the top introduced by myself)

Rebase didn't work due to conflicts. If possible, I'd prefer if you'd make that squash and take a look at the conflict (it was in io.jl). Not sure which one to pick.

"Allow edits from maintainers" is enabled.

@tkelman tkelman force-pushed the doc-environment-variables-continued branch from f56ff83 to 1c63f27 Compare April 21, 2017 23:08
@tkelman
Copy link
Contributor

tkelman commented Apr 21, 2017

I didn't see a conflict. Rebased though, squashed the original PR content into 4 commits, each of which passes make check-whitespace docs locally, plus your additional commit, and removed [ci skip] and the @ signs from the commit message (that would send these users a notification every time anyone rebases the commit, so is best to avoid)

@m-j-w
Copy link
Contributor Author

m-j-w commented Apr 21, 2017

Great, thanks. And good to know with the @ signs.

The environment variables that Julia uses generally start with `JULIA`. If
[`Base.versioninfo`](@ref) is called with `verbose` equal to `true`, then the
output will list all environment variables for which `JULIA` appears in the
name.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change to: "output will list all defined environmental variables"

/home/alice/.julia
```

and the package repository for version 0.5 of Julia would be
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems wordy. Maybe change to "for Julia 0.5 would be"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disagree. It highlights the version being the point why being mentioned as an example, rather than being a specific behaviour of version 0.5

## REPL formatting

Environment variables that determine how REPL output should be formatted at the
terminal. Generally, these variables should be set to [ANSI terminal escape
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change to one space after period.

small typo

forgot about make.jl

Line width to 80 characters; strip trailing spaces; line breaks after h3

added threading/debugging entries and cross-references.

Increase text width to 92 columns, cull spurious line breaks, switch to admonition syntax, simplify cross-references, fix title.

Trailing whitespace

Admonition line breaks; editor envvar heading.

clarify integer types, remove outdated notes, whitespace change

whitespace

No windows shell, English fixes, delete reference to base, clarify 'r', julia-debug.
@m-j-w m-j-w force-pushed the doc-environment-variables-continued branch 2 times, most recently from a789161 to cded04d Compare April 22, 2017 07:07
Please take into account that this file was originally authored by kbdave314.

- Explain how to set environment variables (fredrikekre)
- Corrected `Base.REPL.find_history_file()` (GregPlowman)
- Mentioned editor is a command with vim as example (yuyichao)

Also made it stick to 80 character text width.

Implemented review comments of tkelman
- JULIA_HOME determined at run-time.
- added `Pkg` to `Dir...`
- removed `Base` from `Base.Pkg....`, `Base.VERSION....` and `Base.LOAD_PATH`.
- "a debugger"
- whitespace " - "

Made 'make docs' work again...by removing the faulty reference to JULIA_HOME
introduced by myself.

- clarified output of environment variables.
- removed a blank

Bumped mentioned versions to 0.6 - its a 0.6 documentation after all.

Squashed commits to one for each author.
@m-j-w m-j-w force-pushed the doc-environment-variables-continued branch from cded04d to a8de1ac Compare April 22, 2017 10:59
@tkelman tkelman merged commit e2a4c32 into JuliaLang:master Apr 23, 2017
@KristofferC
Copy link
Member

Really nice to have this merged. Thanks @kbdave314 and @m-j-w

@m-j-w
Copy link
Contributor Author

m-j-w commented Apr 23, 2017

Indeed, thanks @kbdave314 for the effort. Now I don't have to search the source a little less frequently!

@fredrikekre
Copy link
Member

Should close #5432, #19988 as noted in the original PR #20162

@m-j-w m-j-w deleted the doc-environment-variables-continued branch April 23, 2017 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants