Blame


1 2c31ce4d 2019-10-26 op # acmetag
2 2c31ce4d 2019-10-26 op
3 a2964aa4 2020-06-10 op go get git.omarpolo.com/acmetag
4 2c31ce4d 2019-10-26 op
5 4f7fe71a 2020-08-02 op `acmetag` is a tool to programmatically interact with `acme(1)` tag
6 4f7fe71a 2020-08-02 op bar. It provides two flag:
7 a2964aa4 2020-06-10 op
8 2c31ce4d 2019-10-26 op * `-g` prints the tag content (mnemonic: get)
9 2c31ce4d 2019-10-26 op * `-c` clears the tag content (mnemonic: clear)
10 2c31ce4d 2019-10-26 op
11 4f7fe71a 2020-08-02 op Any other argument (if passed) will be appended to the tag bar.
12 2c31ce4d 2019-10-26 op
13 4f7fe71a 2020-08-02 op Of course, you can combine the flags:
14 2c31ce4d 2019-10-26 op
15 2c31ce4d 2019-10-26 op acmetag -g -c fmt
16 2c31ce4d 2019-10-26 op
17 2c31ce4d 2019-10-26 op will first print the current tag content, than clears it and then append
18 2c31ce4d 2019-10-26 op `fmt`.
19 2c31ce4d 2019-10-26 op
20 a2964aa4 2020-06-10 op
21 a2964aa4 2020-06-10 op ### Limitations
22 a2964aa4 2020-06-10 op
23 a2964aa4 2020-06-10 op * It cannot change the text *before* the `|` character.
24 a2964aa4 2020-06-10 op
25 a2964aa4 2020-06-10 op
26 a2964aa4 2020-06-10 op ### Tips
27 a2964aa4 2020-06-10 op
28 2c31ce4d 2019-10-26 op I'm using `acmetag` with [`autoacme`][autoacme] to automatically set
29 2c31ce4d 2019-10-26 op the tag content based on file type.
30 2c31ce4d 2019-10-26 op
31 2c31ce4d 2019-10-26 op [autoacme]: https://github.com/mkhl/cmd/tree/master/acme/autoacme