completely 0.7.1.pre.rc1 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +15 -0
  3. data/lib/completely/version.rb +1 -1
  4. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 26eb35aee6ffcd3a79abf3959fd766ddda7ea9a40023fb0a55fe6d9cbfde31f1
4
- data.tar.gz: 2bff8085afe95bb8d6e989932c2a68a24af91067d93e3e325370afacf65ebc08
3
+ metadata.gz: 8afc0f96ec2612d016fd4a9914b7257f18c2b9e8302b7579129dab4fcaa2ebf1
4
+ data.tar.gz: f94b94f03d432c374f11c006f089f31e78b24aab124f3abf996e4a13f96fdcf5
5
5
  SHA512:
6
- metadata.gz: b353204d2c671744376afa41e21781b544d69b3d556ace709508804cab83b02761ae3ee9d76c4100b5dec05af538c10bbb8e088371155e77c9397545fadc8455
7
- data.tar.gz: 121232ecd8b89208923307a663dea3156c0c16910b8cfbf71c9a9ab0251cdf6229057b188fb4d1d6df83c31f7cc499a54633434c308fc497217f09eaba0fc739
6
+ metadata.gz: 88f5725ccbd2532d6270e8de9cba476ca14a37917bc87b0dd284928cf27a7c08ca6fcdca54c5fa49d7fb63c74197617f81c641ded2f91fa74d5c6c1ec9bf33bc
7
+ data.tar.gz: 78ee662b15cc64f7172410c6f28aa2ed55f1224aaa0e66700c51380cc36e6ad6fbc4740d11cf4387e58c683d0050122d47d88b4f93a9031a6065c1e359a36b8d
data/README.md CHANGED
@@ -40,6 +40,7 @@ or with Docker:
40
40
  $ alias completely='docker run --rm -it --user $(id -u):$(id -g) --volume "$PWD:/app" dannyben/completely'
41
41
  ```
42
42
 
43
+
43
44
  ## Configuration syntax
44
45
 
45
46
  Completely works with a simple YAML configuration file as input, and generates
@@ -246,6 +247,7 @@ The rules here are as follows:
246
247
  hash key (e.g., `+--branch` or `"*--branch"`). Note that when using a `*`,
247
248
  the hash key must be quoted since asterisks have special meaning in YAML.
248
249
 
250
+
249
251
  ## Using the generated completion scripts
250
252
 
251
253
  In order to enable the completions, simply source the generated script:
@@ -268,6 +270,7 @@ Alternatively, you can copy the script manually to one of these directories
268
270
  - `/usr/local/etc/bash_completion.d`
269
271
  - `~/.local/share/bash-completion/completions`
270
272
 
273
+
271
274
  ## Testing and debugging completion scripts
272
275
 
273
276
  You can use the built in completions script tester by running `completely test`.
@@ -305,6 +308,7 @@ puts completions.wrapper_function "custom_function_name"
305
308
  p completions.tester.test "mygit status "
306
309
  ```
307
310
 
311
+
308
312
  ## Completions in ZSH
309
313
 
310
314
  If you are using Oh-My-Zsh, bash completions should already be enabled,
@@ -317,6 +321,17 @@ autoload -Uz +X compinit && compinit
317
321
  autoload -Uz +X bashcompinit && bashcompinit
318
322
  ```
319
323
 
324
+ ## Customizing the `complete` command
325
+
326
+ In case you wish to customize the `complete` command call in the generated
327
+ script, you can do so by adding any additional flags to the `completely.yaml`
328
+ configuration file using the special `completely_options` key. For example:
329
+
330
+ ```yaml
331
+ completely_options:
332
+ complete_options: -o nosort
333
+ ```
334
+
320
335
  ## Contributing / Support
321
336
 
322
337
  If you experience any issue, have a question or a suggestion, or if you wish
@@ -1,3 +1,3 @@
1
1
  module Completely
2
- VERSION = '0.7.1-rc1'
2
+ VERSION = '0.7.1'
3
3
  end
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: completely
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.7.1.pre.rc1
4
+ version: 0.7.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Danny Ben Shitrit
8
8
  bindir: bin
9
9
  cert_chain: []
10
- date: 2025-03-25 00:00:00.000000000 Z
10
+ date: 2025-04-04 00:00:00.000000000 Z
11
11
  dependencies:
12
12
  - !ruby/object:Gem::Dependency
13
13
  name: colsole