From: Kyle Meyer <kyle@kyleam.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org
Subject: Re: lore+lei: getting started
Date: Mon, 10 Jan 2022 20:52:03 -0500 [thread overview]
Message-ID: <874k6bghto.fsf@kyleam.com> (raw)
In-Reply-To: <20220110194037.GA66290@bhelgaas>
Bjorn Helgaas writes:
>> To edit your saved search, just run `lei edit-search`. This will bring up your
>> $EDITOR with the configuration file lei uses internally:
>
> This isn't working for me. With current public-inbox (07cd8973baf8
> ("Makefile.PL: fix useless use of push")), I get:
>
> $ lei edit-search
> usage: lei edit-search OUTPUT
> E: OUTPUT not supplied
> $ lei edit-search out
> --no-save was used with out cwd=/home/bjorn
>
> Maybe I'm doing something wrong?
Specifying an output (a destination previously given to lei-q's
-o/--output/-mfolder) is required. You can see which ones are available
with
$ lei ls-search
> "lei help" and "lei --help" are not very useful because I can't figure
> out how to even get a list of the commands:
>
> $ lei help | cat
> usage: lei help [SUBCOMMAND]
> show help
>
> $ lei --help | cat
> usage: lei COMMAND ...
> ...
>
> lib/PublicInbox/LEI.pm *looks* like it has good help text in it, so
> maybe I'm doing something wrong.
`man lei` provides a pretty complete list of commands.
next prev parent reply other threads:[~2022-01-11 1:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 17:07 lore+lei: getting started Konstantin Ryabitsev
2021-11-08 2:17 ` Randy Dunlap
2021-11-08 19:49 ` Rob Herring
[not found] ` <20211108202204.q5zg6bachnvbjlnx@meerkat.local>
2021-11-08 20:49 ` lei: incorrect quoting on saved searches (was Re: lore+lei: getting started) Eric Wong
2021-11-08 21:36 ` Konstantin Ryabitsev
2021-11-08 21:48 ` Eric Wong
2021-11-08 22:36 ` Konstantin Ryabitsev
2021-11-08 22:57 ` Eric Wong
2022-01-10 19:40 ` lore+lei: getting started Bjorn Helgaas
2022-01-11 1:52 ` Kyle Meyer [this message]
2022-03-07 16:48 ` Rob Herring
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=874k6bghto.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=helgaas@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=workflows@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.