From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: Completion script for the ctags program
Date: Tue, 23 Feb 2021 16:52:51 -0800 [thread overview]
Message-ID: <CAH+w=7bzA0OMhvPDE9_OAW6vBSRMM==T1JV9iP3J4e3gNJnj_w@mail.gmail.com> (raw)
In-Reply-To: <37595-1614124296.776153@uVtr.uPmU.Ik0b>
On Tue, Feb 23, 2021 at 3:52 PM Oliver Kiddle <opk@zsh.org> wrote:
>
> What that patch adds is "Contrib" as a subdirectory of Completion
> with identical make rules as for all the other directories at that
> level (Unix, BSD, AIX, Zsh etc). So it'd need it's own subdirectories
> for Type, Command (and perhaps Utility and Widget). [...]
>
> That approach seemed simplest but that's not to say it has to be
> done that way if you think it'd be better under each of the other
> directories.
No, I think that's fine.
> I probably favour Contrib because I've seen it used
> similarly elsewhere.
>
> Other ideas include 'External', 'Independent', 'Extra', 'Supplemental',
> 'Annex', 'Additional', 'Scrap', 'Dump', 'Diverse', 'Sundry'.
Would "Accessory" imply too much approval?
"Extras" would avoid clashing with any of the existing subdirectories,
for people who have the same flavor of "C/U/C<TAB>" habit as you but
for one of the other operating systems. It also has precedence in
some of the Linux repository names. Similarly "External" that you
already mentioned, or "Extension" or "Extended".
next prev parent reply other threads:[~2021-02-24 0:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 3:11 Jacob Gelbman
2021-02-23 10:11 ` Peter Stephenson
2021-02-23 22:20 ` Oliver Kiddle
2021-02-23 22:45 ` Bart Schaefer
2021-02-23 23:51 ` Oliver Kiddle
2021-02-24 0:52 ` Bart Schaefer [this message]
2021-02-24 13:47 ` Daniel Shahaf
2021-02-23 23:05 ` Mikael Magnusson
2021-02-23 21:39 ` Oliver Kiddle
2021-02-24 4:45 ` Jacob Gelbman
2021-02-24 7:20 ` Jacob Gelbman
2021-02-24 9:26 ` Peter Stephenson
2021-02-24 14:24 ` Daniel Shahaf
2021-02-24 18:58 ` Jacob Gelbman
2021-02-24 19:01 ` Bart Schaefer
2021-03-03 20:02 ` Daniel Shahaf
2021-03-03 20:39 ` Jacob Gelbman
2021-03-03 21:40 ` Peter Stephenson
2021-03-03 22:06 ` Daniel Shahaf
2021-03-03 22:08 ` Jacob Gelbman
2021-03-03 23:28 ` Aaron Schrab
2021-03-03 23:43 ` Daniel Shahaf
2021-03-03 23:35 ` Daniel Shahaf
2021-03-07 19:18 ` Jacob Gelbman
2021-03-07 21:42 ` Daniel Shahaf
2021-03-07 21:57 ` Jacob Gelbman
2021-03-07 22:10 ` Daniel Shahaf
2021-03-11 16:15 ` Daniel Shahaf
2021-03-11 17:08 ` Jacob Gelbman
2021-03-20 1:43 ` Lawrence Velázquez
2021-03-27 16:14 ` Lawrence Velázquez
2021-03-27 20:43 ` Daniel Shahaf
2021-03-28 23:29 ` Oliver Kiddle
2021-03-29 8:54 ` Peter Stephenson
2021-03-29 15:07 ` EOL normalization? (Was: Completion script for the ctags program) Lawrence Velázquez
2021-03-29 15:34 ` Daniel Shahaf
2021-03-29 15:41 ` Lawrence Velázquez
2021-02-24 21:54 ` Completion script for the ctags program dana
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7bzA0OMhvPDE9_OAW6vBSRMM==T1JV9iP3J4e3gNJnj_w@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).