From: Felipe Contreras <felipe.contreras@gmail.com>
To: Marc Khouzam <marc.khouzam@gmail.com>
Cc: szeder@ira.uka.de, git@vger.kernel.org
Subject: Re: [PATCH] tcsh-completion re-using git-completion.bash
Date: Fri, 16 Nov 2012 21:04:06 +0100 [thread overview]
Message-ID: <CAMP44s3S4c7ciJNurxGdS2o_TDJJDkGK73dtCGji+C1NoV+Jvw@mail.gmail.com> (raw)
In-Reply-To: <CAFj1UpHMc-bHJgSZKY13YH_69TXkz-50g5xpLA6C+Eh0aqcN9A@mail.gmail.com>
On Fri, Nov 16, 2012 at 7:20 PM, Marc Khouzam <marc.khouzam@gmail.com> wrote:
> On Fri, Nov 16, 2012 at 12:18 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> On Fri, Nov 16, 2012 at 4:48 PM, Marc Khouzam <marc.khouzam@gmail.com> wrote:
>>> On Fri, Nov 16, 2012 at 10:33 AM, Felipe Contreras
>>> <felipe.contreras@gmail.com> wrote:
>>
>>>> Is it possible to just check if this is a login shell?
>>>
>>> I think it would be nice to allow the user to manually
>>> source git-completion.tcsh, in case they want to make
>>> manual modifications to it.
>>
>> Yeah, they could still do that... because they would be running in a
>> login shell.
>>
>> What I meant is that if the user does: tcsh
>> my_script_that_has_nothing_to_do_with_completion.sh, they would not be
>> executing this whole script.
>
> Oh, I see now.
>
> I can put a check in the script for the existence of the $prompt variable.
> This will indicate if it is a login shell or not.
> However, a good .cshrc file should already have such a check to avoid
> sourcing a bunch of useless things. So, I personally think that we
> should not add it to the git-completion.tcsh script but let the tcsh
> user decide to do it herself. But I don't mind being overruled :)
Sounds sensible to me.
>>> I think the most user-friendly option is to actually re-generate the
>>> script each time. It feels wrong, but it works well :)
>>
>> I'm not too strongly opposed to add that function to the bash
>> completion, but to do it only for tcsh doesn't sound right, specially
>> when there are other alternatives.
>
> I agree, and this is why I made the proposed
> __git_complete_with_output () generic. That way it could be
> used by other shells or programs. But at this time, only tcsh
> would make use of it.
>
> If you think having __git_complete_with_output () could
> be useful for others, I think we should go with solution (A).
> If you don't think so, or if it is better to wait until a need
> arises first, then solution (C) will work fine.
I don't see how it could be useful to others, and if we find out that
it could, we can always move the code.
>> Correct me if I'm wrong, but very few people use tcsh.
>
> Less than I originally thought, when I started working
> on this patch :-\ But I'm still hoping that the those people
> will be a little happier with their git completion.
I think they would :) But we don't need to modify bash's script for
that (for now).
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2012-11-16 20:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFj1UpE6OtJEojaED1_DZJD0kU=nVsFE_w8xa0oJE-6auCU2rw@mail.gmail.com>
2012-11-12 20:07 ` Fwd: [PATCH] Add tcsh-completion support to contrib by using git-completion.bash Marc Khouzam
2012-11-13 11:14 ` SZEDER Gábor
2012-11-13 20:12 ` Marc Khouzam
2012-11-13 23:46 ` SZEDER Gábor
2012-11-14 0:49 ` [PATCH] completion: remove 'help' duplicate from porcelain commands SZEDER Gábor
2012-11-14 4:26 ` Fwd: [PATCH] Add tcsh-completion support to contrib by using git-completion.bash Marc Khouzam
2012-11-15 11:51 ` [PATCH] tcsh-completion re-using git-completion.bash Marc Khouzam
2012-11-16 1:41 ` Felipe Contreras
2012-11-16 14:39 ` Marc Khouzam
2012-11-16 15:33 ` Felipe Contreras
2012-11-16 15:48 ` Marc Khouzam
2012-11-16 16:12 ` [PATCH v3] " Marc Khouzam
2012-11-16 17:21 ` Felipe Contreras
2012-11-16 18:43 ` [PATCH v4] " Marc Khouzam
2012-11-16 19:59 ` Junio C Hamano
2012-11-16 20:01 ` Felipe Contreras
2012-11-16 17:18 ` [PATCH] " Felipe Contreras
2012-11-16 18:20 ` Marc Khouzam
2012-11-16 20:04 ` Felipe Contreras [this message]
2012-11-16 20:40 ` SZEDER Gábor
2012-11-16 21:03 ` Felipe Contreras
2012-11-16 21:22 ` SZEDER Gábor
2012-11-16 21:46 ` Felipe Contreras
2012-11-17 10:56 ` SZEDER Gábor
2012-11-17 11:46 ` Felipe Contreras
2012-11-17 14:17 ` SZEDER Gábor
2012-11-16 21:20 ` Junio C Hamano
2012-11-16 21:56 ` Felipe Contreras
2012-11-17 17:15 ` Marc Khouzam
2012-11-17 18:01 ` Felipe Contreras
2012-11-20 14:58 ` Marc Khouzam
2012-11-20 15:15 ` Felipe Contreras
2012-11-20 18:20 ` Marc Khouzam
2012-11-20 21:07 ` Junio C Hamano
2012-11-13 18:31 ` [PATCH] Add tcsh-completion support to contrib by using git-completion.bash Felipe Contreras
2012-11-14 0:11 ` SZEDER Gábor
2012-11-15 2:40 ` Felipe Contreras
2012-11-14 3:36 ` Marc Khouzam
2012-11-14 0:09 ` Fwd: " 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s3S4c7ciJNurxGdS2o_TDJJDkGK73dtCGji+C1NoV+Jvw@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=marc.khouzam@gmail.com \
--cc=szeder@ira.uka.de \
/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://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).