From: timsofteng <timsofteng@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rbw shell completion doesn't work
Date: Wed, 25 Jan 2023 15:49:18 +0100 [thread overview]
Message-ID: <20230125144918.IYs3QVjNruw9bBuftJf8n1h6H3h4IVWFF41DT9r__QU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41861@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
New comment by timsofteng on void-packages repository
https://github.com/void-linux/void-packages/issues/41861#issuecomment-1403737882
Comment:
Sorry, my bad. Looks like it was some of shell caching issue. Regular completion after rtw works now fine for me.
Do you know is it possible to get completion for passwords items after `rbw get <press tab>`? If rbw doesn't provide it then issue is totally solved.
next prev parent reply other threads:[~2023-01-25 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 9:31 [ISSUE] " timsofteng
2023-01-25 12:54 ` tranzystorek-io
2023-01-25 13:33 ` paper42
2023-01-25 14:49 ` timsofteng [this message]
2023-01-25 14:55 ` timsofteng
2023-01-25 14:58 ` tranzystorek-io
2023-01-25 15:21 ` [ISSUE] [CLOSED] " classabbyamp
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=20230125144918.IYs3QVjNruw9bBuftJf8n1h6H3h4IVWFF41DT9r__QU@z \
--to=timsofteng@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).