From: Anand Buddhdev <arhbkb@gmail.com>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: bash completion error with 0.17
Date: Sun, 2 Feb 2014 11:46:30 +0100 [thread overview]
Message-ID: <CANbPJF=FHTp3YXE-LPtk1ijBg8OxU8uY83PXBW+RxMSK1mzeUA@mail.gmail.com> (raw)
In-Reply-To: <87a9e9yeta.fsf@nikula.org>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
Hi Jani,
I already have bash-completion installed, although it's version 1.3.
On 2 February 2014 11:44, Jani Nikula <jani@nikula.org> wrote:
> On Sun, 02 Feb 2014, Anand Buddhdev <arhbkb@gmail.com> wrote:
> > Hi people,
> >
> > I've just discovered notmuch. I've installed version 0.17 on my Mac using
> > Homebrew. I've also built a forked mutt with notmuch support, and I'm
> > exploring setting up virtual folders, and keeping all mail in a single
> "All
> > Mail" Maildir, with everything just tagged, a la Gmail :) I love it.
> >
> > I have one issue to report: when I type "notmuch" at the command-line and
> > press tab, bash completion gives me the following error:
> >
> > $ notmuch -bash: _init_completion: command not found
> >
> > Looks like something is missing in the bash completion script. I'd
> > appreciate if someone could make a patch.
>
> You'll need the bash-completion package [1] too. I'm not sure about
> versions, but likely reasonably recent.
>
> The trivial "fix" patch would likely just check for the existence of
> _init_completion, and refuse to complete without it. For anything
> fancier, patches welcome...
>
>
> BR,
> Jani.
>
>
> [1] http://bash-completion.alioth.debian.org/
>
[-- Attachment #2: Type: text/html, Size: 1895 bytes --]
next prev parent reply other threads:[~2014-02-02 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 10:35 bash completion error with 0.17 Anand Buddhdev
2014-02-02 10:44 ` Jani Nikula
2014-02-02 10:46 ` Anand Buddhdev [this message]
2014-02-02 11:52 ` Jani Nikula
2014-02-02 12:54 ` Jani Nikula
2014-02-02 14:33 ` Anand Buddhdev
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANbPJF=FHTp3YXE-LPtk1ijBg8OxU8uY83PXBW+RxMSK1mzeUA@mail.gmail.com' \
--to=arhbkb@gmail.com \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).