From: Jonathan Nieder <jrnieder@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "SZEDER Gábor" <szeder@ira.uka.de>,
"Thomas Rast" <trast@student.ethz.ch>
Subject: Re: [PATCH v2] completion: add new git_complete helper
Date: Mon, 16 Apr 2012 18:16:26 -0500 [thread overview]
Message-ID: <20120416231626.GW12613@burratino> (raw)
In-Reply-To: <CAMP44s0cdSaiCoMLk7oTHE4dies5-G0C7-RczK5OFEK=pYUW_A@mail.gmail.com>
Felipe Contreras wrote:
> What makes you think this is public? It's under the section '# helper
> functions', which doesn't seem to be public. Plus, it's repeated in
> rpm, rpmbuild, and rpmbuild-md5.
Ok, you win. I hadn't realized we were having a debate, but now I do,
and you have won.
Can we get back to making the completion script nicer for human
beings that have been using it, please?
The following summary may sound annoyed, because I am. On the other
hand I know you mean well and am grateful for your work.
I have said that the convention for bash completion scripts is to
precede all exposed identifier names with an underscore. You
mentioned some old counterexamples that have been grandfathered in.
You mentioned that you do not trust me. Your bash completion script
gets loaded immediately instead of being lazy-loaded, probably because
it is not in /usr/share/bash-completion/completions/. You claimed
that nobody would _ever_ ask for bash completion support at the end of
their .profile and after their custom functions in .profile that do
something unrelated, though I used to do that for a long time and
Debian's default .bashrc loads /etc/bash_completion at the end, too.
I still maintain that namespaces are useful and we should follow the
conventional ones when they exist. What is the next step?
Jonathan
next prev parent reply other threads:[~2012-04-16 23:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 21:20 [PATCH v2] completion: add new git_complete helper Felipe Contreras
2012-04-15 21:37 ` Jonathan Nieder
2012-04-16 10:49 ` Felipe Contreras
2012-04-16 15:54 ` Junio C Hamano
2012-04-16 16:07 ` Jonathan Nieder
2012-04-16 16:32 ` Junio C Hamano
2012-04-16 20:04 ` Felipe Contreras
2012-04-16 20:09 ` Jonathan Nieder
2012-04-16 20:30 ` Felipe Contreras
2012-04-16 20:33 ` Jonathan Nieder
2012-04-16 20:42 ` Felipe Contreras
2012-04-16 20:46 ` Jonathan Nieder
2012-04-16 20:51 ` Felipe Contreras
2012-04-16 20:59 ` Jonathan Nieder
2012-04-21 7:20 ` Ville Skyttä
2012-04-21 15:41 ` [Bash-completion-devel] " Felipe Contreras
2012-04-21 17:39 ` Ville Skyttä
2012-04-22 12:58 ` Felipe Contreras
2012-04-16 20:51 ` Junio C Hamano
2012-04-16 21:09 ` Felipe Contreras
2012-04-16 22:44 ` Jonathan Nieder
2012-04-16 23:04 ` Felipe Contreras
2012-04-16 23:05 ` Jonathan Nieder
2012-04-16 23:16 ` Jonathan Nieder [this message]
2012-04-17 7:10 ` Felipe Contreras
2012-04-17 7:36 ` Jonathan Nieder
2012-04-17 7:56 ` Felipe Contreras
2012-04-17 8:06 ` Jonathan Nieder
2012-04-17 8:22 ` Jonathan Nieder
2012-04-16 16:00 ` Jonathan Nieder
2012-04-16 22:15 ` SZEDER Gábor
2012-04-16 22:33 ` Felipe Contreras
2012-04-17 15:50 ` Junio C Hamano
2012-04-17 16:13 ` Felipe Contreras
2012-04-17 18:15 ` Junio C Hamano
2012-04-17 20:53 ` Felipe Contreras
2012-04-17 21:08 ` Jonathan Nieder
2012-04-17 22:14 ` SZEDER Gábor
2012-04-17 22:19 ` Felipe Contreras
2012-04-17 17:50 ` SZEDER Gábor
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=20120416231626.GW12613@burratino \
--to=jrnieder@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder@ira.uka.de \
--cc=trast@student.ethz.ch \
/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.
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).