| /dports/graphics/R-cran-colorspace/colorspace/R/ |
| H A D | specplot.R | 105 HCL <- coords(HCL)[, c("H", "C", "L")]
106 HCL[which(is.na(HCL), arr.ind = TRUE)] <- 0
109 HCL[x.na, i] <- NA
125 md <- median(HCL[2L:nrow(HCL), "H"] - HCL[1L:(nrow(HCL) - 1L), "H"], na.rm = TRUE)
128 d <- HCL[i, "H"] - HCL[i - 1L, "H"]
130 if (abs(HCL[i, "H"]) > 360) HCL[1L:i, "H"] <- HCL[1L:i, "H"] - sign(HCL[i, "H"]) * 360
136 HCL[, "H"] <- mean(HCL[, "H"], na.rm = TRUE)
139 ix <- split(1:nrow(HCL), HCL[,"L"] < 2 | HCL[,"L"] > 98)
142 HCL[ix["TRUE"][[1L]]] <- sapply(ix["TRUE"][[1L]], fun_fix_H, HCL = HCL, ix = ix)
145 n <- nrow(HCL)
[all …]
|
| H A D | hclplot.R | 100 HCL <- hex2RGB(x) functionVar
102 HCL <- x
105 HCL <- coords(as(HCL, "polarLUV"))[, c("H", "C", "L")]
106 n <- nrow(HCL)
128 d <- HCL[i, "H"] - HCL[i - 1L, "H"]
129 if (abs(d) > 320) HCL[i, "H"] <- HCL[i, "H"] - sign(d) * 360
130 if (abs(HCL[i, "H"]) > 360) HCL[1L:i, "H"] <- HCL[1L:i, "H"] - sign(HCL[i, "H"]) * 360
136 HCL[,"H"] <- mean(HCL[,"H"])
327 points(xpos(HCL[, "H"], HCL[, "C"]), ypos(HCL[, "H"], HCL[, "C"]),
329 points(xpos(HCL[, "H"], HCL[, "C"]), ypos(HCL[, "H"], HCL[, "C"]),
[all …]
|
| /dports/sysutils/terraform-switcher/terraform-switcher-0.13.1201/vendor/github.com/hashicorp/hcl2/ |
| H A D | README.md | 1 # HCL chapter
3 HCL is a toolkit for creating structured configuration languages that are
8 HCL has both a _native syntax_, intended to be pleasant to read and write for
30 back in to [the main HCL repository](https://github.com/hashicorp/hcl).
34 switching to a stable release of HCL 2 as soon as possible. For more
35 information on installing HCL 1 and/or HCL 2, please see
43 Newcomers to HCL often ask: why not JSON, YAML, etc?
54 HCL is intended as a base syntax for configuration formats built
69 HCL is built around two primary concepts: _attributes_ and _blocks_. In
145 * [HCL Native Syntax](hcl/hclsyntax/spec.md)
[all …]
|
| /dports/converters/yj/yj-5.0.0/ |
| H A D | README.md | 6 Convert between YAML, TOML, JSON, and HCL.
14 - HCL: **v1** (github.com/hashicorp/hcl)
20 Convert between YAML, TOML, JSON, and HCL.
27 -yc = YAML to HCL
31 -tc = TOML to HCL
35 -jc = JSON to HCL
36 -cy = HCL to YAML
37 -ct = HCL to TOML
38 -cj, -c = HCL to JSON
39 -cc = HCL to HCL
|
| H A D | main.go | 11 Convert between YAML, TOML, JSON, and HCL.
18 -yc = YAML to HCL
22 -tc = TOML to HCL
26 -jc = JSON to HCL
27 -cy = HCL to YAML
28 -ct = HCL to TOML
29 -cj, -c = HCL to JSON
30 -cc = HCL to HCL
|
| /dports/net/cloudquery/cloudquery-0.16.0/vendor/github.com/hashicorp/hcl/v2/ |
| H A D | README.md | 1 # HCL chapter
3 HCL is a toolkit for creating structured configuration languages that are
8 > **NOTE:** This is major version 2 of HCL, whose Go API is incompatible with
73 Newcomers to HCL often ask: why not JSON, YAML, etc?
84 HCL is intended as a base syntax for configuration formats built
99 HCL is built around two primary concepts: _attributes_ and _blocks_. In
175 * [HCL Native Syntax](hclsyntax/spec.md)
180 Version 2.0 of HCL combines the features of HCL 1.0 with those of the
189 It's possible to import both HCL 1 and HCL 2 into the same program using Go's
208 The original HCL parser was ported to pure Go (from yacc) by
[all …]
|
| /dports/sysutils/nomad/nomad-1.1.0/vendor/github.com/hashicorp/hcl/v2/ |
| H A D | README.md | 1 # HCL chapter
3 HCL is a toolkit for creating structured configuration languages that are
8 > **NOTE:** This is major version 2 of HCL, whose Go API is incompatible with
73 Newcomers to HCL often ask: why not JSON, YAML, etc?
84 HCL is intended as a base syntax for configuration formats built
99 HCL is built around two primary concepts: _attributes_ and _blocks_. In
175 * [HCL Native Syntax](hclsyntax/spec.md)
180 Version 2.0 of HCL combines the features of HCL 1.0 with those of the
189 It's possible to import both HCL 1 and HCL 2 into the same program using Go's
208 The original HCL parser was ported to pure Go (from yacc) by
[all …]
|
| /dports/sysutils/terraform-docs/terraform-docs-0.16.0/vendor/github.com/hashicorp/hcl/v2/ |
| H A D | README.md | 1 # HCL chapter
3 HCL is a toolkit for creating structured configuration languages that are
8 > **NOTE:** This is major version 2 of HCL, whose Go API is incompatible with
73 Newcomers to HCL often ask: why not JSON, YAML, etc?
84 HCL is intended as a base syntax for configuration formats built
99 HCL is built around two primary concepts: _attributes_ and _blocks_. In
175 * [HCL Native Syntax](hclsyntax/spec.md)
180 Version 2.0 of HCL combines the features of HCL 1.0 with those of the
189 It's possible to import both HCL 1 and HCL 2 into the same program using Go's
208 The original HCL parser was ported to pure Go (from yacc) by
[all …]
|
| /dports/sysutils/terraform/terraform-1.0.11/vendor/github.com/hashicorp/hcl/v2/ |
| H A D | README.md | 1 # HCL chapter
3 HCL is a toolkit for creating structured configuration languages that are
8 > **NOTE:** This is major version 2 of HCL, whose Go API is incompatible with
73 Newcomers to HCL often ask: why not JSON, YAML, etc?
84 HCL is intended as a base syntax for configuration formats built
99 HCL is built around two primary concepts: _attributes_ and _blocks_. In
175 * [HCL Native Syntax](hclsyntax/spec.md)
180 Version 2.0 of HCL combines the features of HCL 1.0 with those of the
189 It's possible to import both HCL 1 and HCL 2 into the same program using Go's
208 The original HCL parser was ported to pure Go (from yacc) by
[all …]
|
| /dports/sysutils/terraform/terraform-1.0.11/internal/backend/remote/ |
| H A D | backend_context_test.go | 29 HCL: false,
39 HCL: true,
49 HCL: true,
59 HCL: true,
68 HCL: false,
77 HCL: true,
95 HCL: true,
105 HCL: true,
109 …arked in the remote workspace as being specified in HCL syntax, but the given value is not valid H…
115 HCL: true,
[all …]
|
| /dports/sysutils/nomad/nomad-1.1.0/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
10 …:** This is major version 1 of HCL, which is now in maintenence mode only. We strongly recommend t…
14 valid input to a system expecting HCL. This helps to make systems
17 HCL is heavily inspired by
23 A common question when viewing HCL is to ask the question: why not
44 to be written and modified by humans. The API for HCL allows JSON
46 JSON instead of trying to generate HCL).
48 Our goal with HCL is not to alienate other configuration languages.
125 and syntax that HCL was based off of.
[all …]
|
| /dports/security/vuls/vuls-0.13.7/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/net/gscloud/gscloud-0.11.0/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/net/madonctl/madonctl-8d3e9fa/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/net/go-bapu/carlostrub-bapu-23ca6b019fbc/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/net/evans/evans-0.9.1/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/www/carbonapi/carbonapi-0.14.1/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/databases/pg_tileserv/pg_tileserv-1.0.8/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/deskutils/ultralist/ultralist-1.7.0/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/security/vault/vault-1.8.2/vendor/github.com/joyent/triton-go/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/deskutils/noti/noti-3.5.0/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/deskutils/ultralist/ultralist-1.7.0/vendor/github.com/hashicorp/hcl/hcl-1.0.0/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/net-im/matterbridge/matterbridge-1.22.3/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/security/certmgr/certmgr-3.0.3/vendor/github.com/hashicorp/hcl/hcl-1.0.0/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|
| /dports/www/gitlab-workhorse/gitlab-foss-0a901d60f8ae4a60c04ae82e6e9c3a03e9321417/workhorse/vendor/github.com/golang/gddo/vendor/github.com/hashicorp/hcl/ |
| H A D | README.md | 1 # HCL chapter
5 HCL (HashiCorp Configuration Language) is a configuration language built
11 valid input to a system expecting HCL. This helps makes systems
14 HCL is heavily inspired by
20 A common question when viewing HCL is to ask the question: why not
40 that is JSON-compatible. Our configuration language (HCL) is designed
41 to be written and modified by humans. The API for HCL allows JSON
43 JSON instead of trying to generate HCL).
45 Our goal with HCL is not to alienate other configuration languages.
122 and syntax that HCL was based off of.
[all …]
|