| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 13/12/13 13:31, Samuli Suominen wrote: |
| 5 |
> orc is dev-lang/orc, with binaries like orc-bugreport |
| 6 |
That's fine. There is no binary, orc. |
| 7 |
|
| 8 |
> as said, with tab completion, orc-* would just get mixed up with |
| 9 |
> binaries from dev-lang/orc |
| 10 |
|
| 11 |
Tab-completing orc- will only have one executable not related to |
| 12 |
openrc. If you tab-complete "open" (which is already longer to type) |
| 13 |
on most systems, you get a lot more. So you'd have to tab-complete |
| 14 |
openrc. That's a lot longer than orc-. |
| 15 |
|
| 16 |
Also, I would just tab-complete orc. orcc is obviously a compiler. |
| 17 |
Most people have rcc (also obviously a compiler) on their system, so |
| 18 |
we have that "issue" now as well. |
| 19 |
|
| 20 |
So to sum up: I still think it's fine to call it orc. But honestly, |
| 21 |
there are no catastrophic candidates. Any further discussion is mostly |
| 22 |
just bikeshedding. Let's just nominate some candidates and vote. :-) |
| 23 |
- -- |
| 24 |
Alexander |
| 25 |
alexander@××××××.net |
| 26 |
http://plaimi.net/~alexander |
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 29 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 30 |
|
| 31 |
iF4EAREIAAYFAlKrDBYACgkQRtClrXBQc7XK1gEArFhx0BE2eELesWVQ1p0KyxKC |
| 32 |
TEkWlaqZZsxhvSTHf5cA/2jlE5QcODLk765pbmppIB/aw32BfVYSNxUHXssY4tsx |
| 33 |
=iAkb |
| 34 |
-----END PGP SIGNATURE----- |
Archives