Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14868
| Path | csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail |
|---|---|
| From | Tom Ryder <tom@sanctum.geek.nz> |
| Newsgroups | gnu.bash.bug |
| Subject | Re: bash-5.0-beta2 breaks ``complete -D'' |
| Date | Fri, 30 Nov 2018 22:33:17 +1300 |
| Lines | 100 |
| Approved | bug-bash@gnu.org |
| Message-ID | <mailman.4913.1543570413.1284.bug-bash@gnu.org> (permalink) |
| References | <CADv8-oi+7kjJj71xTGo2bVa4CpoWr_SFAqwguhBdaHoKvVPH+g@mail.gmail.com> |
| NNTP-Posting-Host | lists.gnu.org |
| Mime-Version | 1.0 |
| Content-Type | multipart/mixed; boundary="zYM0uCDKw75PZbzx" |
| X-Trace | usenet.stanford.edu 1543570414 12207 208.118.235.17 (30 Nov 2018 09:33:34 GMT) |
| X-Complaints-To | action@cs.stanford.edu |
| Cc | bug-bash@gnu.org |
| To | Clark Wang <dearvoid@gmail.com>, Chet Ramey <chet.ramey@case.edu> |
| Envelope-to | bug-bash@gnu.org |
| DKIM-Signature | v=1; a=rsa-sha256; c=simple/simple; d=sanctum.geek.nz; s=mail20160328; t=1543570398; bh=oMiYagr/ILzA/7B+b609n0+il1K4bynEwoLVumDIEoA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=e5C5L7JLY747EJfPPGxnkIbb1e1+JaoWSxPU15E42n1QX59mSggiVclbonFrKa+kT KBpLIwPQIaLhCMRLNyG+zaEmVs5gZ3AsCtOw7E7LZXPSEvHIhcJmWxCF006nLdfeLQ yoNw0GuGEp8SBkTza/CPSKPrtJxFV0pwDmD0fZTI= |
| Content-Disposition | inline |
| In-Reply-To | <CADv8-oi+7kjJj71xTGo2bVa4CpoWr_SFAqwguhBdaHoKvVPH+g@mail.gmail.com> |
| User-Agent | Mutt/1.11+4 (54103972) (2018-11-27) |
| X-detected-operating-system | by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] |
| X-Received-From | 120.138.30.239 |
| X-BeenThere | bug-bash@gnu.org |
| X-Mailman-Version | 2.1.21 |
| Precedence | list |
| List-Id | Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org> |
| List-Unsubscribe | <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe> |
| List-Archive | <http://lists.gnu.org/archive/html/bug-bash/> |
| List-Post | <mailto:bug-bash@gnu.org> |
| List-Help | <mailto:bug-bash-request@gnu.org?subject=help> |
| List-Subscribe | <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe> |
| Xref | csiph.com gnu.bash.bug:14868 |
Show key headers only | View raw
[Multipart message — attachments visible in raw view] - view raw
On Fri, Nov 30, 2018 at 05:21:32PM +0800, Clark Wang wrote:
>Just tried 5.0-beta2 and it broke my completion rules. It can be
>reproduced with the following steps: ...
Hello Clark; I noticed the same thing; I addressed it in an earlier
message with the attached patch as a suggested fix, modifying a patch
from Luca Boccassi.
<https://lists.gnu.org/archive/html/bug-bash/2018-11/msg00097.html>
----- Forwarded message from Tom Ryder <tom@sanctum.geek.nz> -----
Date: Sun, 25 Nov 2018 23:04:18 +1300
From: Tom Ryder <tom@sanctum.geek.nz>
To: Luca Boccassi <bluca@debian.org>
Cc: bug-bash@gnu.org
Subject: Re: [PATCH] Fix custom program's completions when initial word is set
On Fri, Nov 23, 2018 at 12:48:54PM +0000, Luca Boccassi wrote:
> The fix is to only override foundcs if both iw_compspec is not null
> and we are not in command position.
Thank you for this patch. I first ran into the issue with 5.0-beta2 another
way: I noticed that my default completion spec with -D as suggested by the
Bash manual page was no longer working:
_completion_loader()
{
. "/etc/bash_completion.d/$1.sh" >/dev/null 2>&1 && return 124
}
complete -D -F _completion_loader -o bashdefault -o default
In 5.0-beta2, after running this code, for any command with no completion
specs defined in /etc/bash_completion.d, completing an argument does nothing.
Your second patch does not correct that, but it looks like that's because a
non-zero `foundcs` is coerced to 1 in it, when there are other meaningful
values for the integer as the first parameter for
`pcomp_set_readline_variables(int, int)`.
The attached patch is my own attempt, which seems to correct my issues as well
as the one you raised in this post. Long-time user, first-time poster...
----- End forwarded message -----
--
Tom Ryder <https://sanctum.geek.nz/>
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: bash-5.0-beta2 breaks ``complete -D'' Tom Ryder <tom@sanctum.geek.nz> - 2018-11-30 22:33 +1300
csiph-web