From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: completion for compilers (cc, gcc...) and -o
Date: Thu, 30 Apr 2020 10:57:06 -0700 [thread overview]
Message-ID: <CAH+w=7Zz4sdtg_GDQnR=X9g7RSzySWJxV-icsW=NXm4ksOksOA@mail.gmail.com> (raw)
In-Reply-To: <20200430085111.GA1649750@zira.vinc17.org>
On Thu, Apr 30, 2020 at 1:52 AM Vincent Lefevre <vincent@vinc17.net> wrote:
>
> The -o option is currently handled by
>
> '-o:output file:_files -g "^*.(c|h|cc|C|cxx)(-.)"'
>
> I wonder whether .i files (preprocessed files, e.g. for bug reports)
> should be excluded too.
>
> Moreover, if I have a C source "myprogram.c", I generally want the
> output file (program name) to be "myprogram", or if I need several
> versions (e.g. because I test several options [...]
>
> cc -o my[TAB]
>
> I'd like the "myprogram" to be taken into account.
That seems pretty simple:
zstyle :completion::complete:gcc:option-o-1: file-patterns \
"^*.(c|h|cc|C|cxx|i)(-.) *.(c|cc|C|cxx)(N\:r)"
Interesting tidbit, you have to backslash the colon there because
_files is parsing this in pattern:tag format, and it's not clever
about parens.
If we think this is useful enough to fold in to the default (pardon
likely line wrapping by gmail):
diff --git a/Completion/Unix/Command/_gcc b/Completion/Unix/Command/_gcc
index 9ec09200e..7437b96c0 100644
--- a/Completion/Unix/Command/_gcc
+++ b/Completion/Unix/Command/_gcc
@@ -390,7 +390,7 @@ languages=(
# generic options (from --help)
args+=(
'-###[print commands to run this compilation]'
- '-o:output file:_files -g "^*.(c|h|cc|C|cxx)(-.)"'
+ '-o:output file:_files -g "^*.(c|h|cc|C|cxx|i)(-.) *.(c|cc|C|cxx)(N\:r)"'
'-x[Specify the language of the following input files]:input file
language:('"$languages"')'
'+e-:virtual function definitions in classes:((0\:only\ interface
1\:generate\ code))'
'-d-:dump:->dump'
next prev parent reply other threads:[~2020-04-30 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 8:51 Vincent Lefevre
2020-04-30 17:57 ` Bart Schaefer [this message]
2020-04-30 18:14 ` Daniel Shahaf
2020-04-30 20:17 ` Vincent Lefevre
2020-04-30 20:32 ` Bart Schaefer
2020-04-30 20:54 ` Vincent Lefevre
2020-04-30 22:34 ` Daniel Shahaf
2020-04-30 22:36 ` Daniel Shahaf
2020-04-30 23:07 ` Bart Schaefer
2020-04-30 22:05 ` Daniel Shahaf
2020-05-01 1:11 ` Vincent Lefevre
2020-05-02 0:43 ` Daniel Shahaf
2020-05-02 1:26 ` Bart Schaefer
2020-05-03 23:17 ` Vincent Lefevre
2020-05-04 23:58 ` Daniel Shahaf
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=7Zz4sdtg_GDQnR=X9g7RSzySWJxV-icsW=NXm4ksOksOA@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).