user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: lei stuff that should be in a lei(1) or lei-overview(7)
Date: Thu, 18 Feb 2021 20:28:18 +0000	[thread overview]
Message-ID: <20210218202818.GA19443@dcvr> (raw)

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...

             reply	other threads:[~2021-02-18 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 20:28 Eric Wong [this message]
2021-02-22  3:42 ` Eric Wong

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210218202818.GA19443@dcvr \ \ \
    --subject='Re: lei stuff that should be in a lei(1) or lei-overview(7)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).