You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<ahref="https://twitter.com/progriumHQ"title="@progriumHQ on Twitter"><imgsrc="https://img.shields.io/badge/[email protected]"alt="@progriumHQ on Twitter"></a>
First, [download Go](https://golang.org/dl/) or `brew install go`. If you have Go installed, make sure it is
21
+
First, [download Go 1.16+](https://golang.org/dl/) or `brew install go`. If already installed, make sure it is
22
22
version 1.16 or greater:
23
23
24
24
```
25
25
$ go version
26
26
go version go1.16.2 darwin/amd64
27
27
```
28
28
29
-
Then use `go get` to download, build, and install the topframe binary into a `PATH` directory:
29
+
Then use `go get` to download, build, and install the topframe binary into a directory in your `PATH`
30
+
by setting `GOBIN`:
30
31
31
32
```
32
33
$ GOBIN=/usr/local/bin go get github.com/progrium/topframe
33
34
```
34
35
35
36
Currently, this is the preferred way to install as anything else requires a much more elaborate
36
37
release process with Apple code signing, etc. Specifying `GOBIN` is optional, but lets you specify
37
-
where to install the binary, ensuring it is put in a directory in your `PATH`.
38
-
39
-
Running `topframe` will create a `~/.topframe` directory with a default `index.html` used for the
40
-
overlay. If you have an `EDITOR` specified, you can run with `-edit` to open this in your preferred editor
41
-
so you can start making changes to your topframe overlay immediately:
38
+
where to install the binary, ensuring it is put in your `PATH`.
The generated plist will use the current binary location, so make sure it's
59
-
in the right place before generating, or modify the plist file.
66
+
It's a good idea to view the output before writing to the file, just to make sure
67
+
paths are correct. If you don't know what is correct, it's probably fine!
60
68
61
69
62
70
## Documentation
63
71
64
-
There is not a whole lot to topframe! I recommend [reading the source](https://github.com/progrium/topframe/blob/main/topframe.go) as its only a few hundred lines,
72
+
There is not a whole lot to Topframe! I recommend [reading the source](https://github.com/progrium/topframe/blob/main/topframe.go) as its only a few hundred lines,
65
73
but otherwise there is a [wiki](https://github.com/progrium/topframe/wiki) ready to document anything else.
66
74
67
75
## Getting Help
@@ -71,7 +79,7 @@ a question into the [discussion forum](https://github.com/progrium/topframe/disc
71
79
72
80
## Contributing
73
81
74
-
Ideally, topframe will be kept small. Bug fixes and other small PRs are welcome and should be merged quickly.
82
+
Ideally, Topframe is kept small. Bug fixes and other small PRs are welcome and should be merged quickly.
75
83
If you happen to have a large PR that we haven't discussed, you should talk about it in the forum first. In order
76
84
to keep the project small, some features suggestions may be held back in favor of determining a good extension point to expose instead.
0 commit comments