lei stuff that should be in a lei(1) or lei-overview(7)

lei stuff that should be in a lei(1) or lei-overview(7)

[Eric Wong]

More random scattered thoughts

* Note bash completions in contrib/, encourage contributions for
  other shells

* Note UI/UX is a deeply personal choice, lei can't satisfy everyone

* Note Inline::C + "mkdir -p ~/.cache/public-inbox/inline-c"
  significantly improves performance.  Socket::MsgHdr
  (libsocket-msghdr-perl in Debian) further improves startup
  performance (most noticeable for bash completion)

* Don't impose or aggressively promote lei in your projects or
  communities.  That defeats the point of open standards.  Until
  AGPL acceptance grows, it's likely many users can't use lei.

* Primary author is scatter-brained, and getting worse :<

More to come...

Re: lei stuff that should be in a lei(1) or lei-overview(7)

[Eric Wong]

Eric Wong <e@80x24.org> wrote:
> More random scattered thoughts

If "lei" conflicts with an existing script or alias on your
system, consider naming it "lorelei"(*).  Of course, the
shorter name is preferred to save keystrokes.

(*) partly named after a well-known instance of public-inbox