From: Felipe Contreras <felipe.contreras@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Most minimal configuration challenge
Date: Fri, 26 Aug 2022 23:30:23 -0500 [thread overview]
Message-ID: <CAMP44s1d7Pnv5oAk4uwnBXhjYUikWSe8nqVZJuXvP4bEv1cCTA@mail.gmail.com> (raw)
Hi,
Now and again I cleanup my entire configuration for various reasons.
By doing that multiple times I've figured out which options I really
need, which are nice to have, and which I don't want.
Sometimes I wonder if there's anybody who doesn't use some of these.
For example, my guess is 99.99% of all people use compinit.
If I was a newcomer to zsh I would probably need some of these as
well, especially compinit.
Anyway, here is the most minimal configuration I can live with:
fpath=(~/.zsh $fpath)
HISTFILE=~/.history
HISTSIZE=10000
SAVEHIST=50000
autoload -U compinit && compinit
autoload -U promptinit && promptinit
prompt felipec
setopt inc_append_history
bindkey -e
bindkey "\e[H" beginning-of-line
bindkey "\e[F" end-of-line
bindkey "\e[A" history-beginning-search-backward
bindkey "\e[B" history-beginning-search-forward
bindkey "\e[3~" delete-char
I need every single line.
Although I usually use a much bigger configuration, I'm able to live
with this minimal configuration for a while.
Does anybody have a similar list of options they absolutely can't live
without? How long can you live with such a minimal configuration?
Cheers.
--
Felipe Contreras
next reply other threads:[~2022-08-27 4:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 4:30 Felipe Contreras [this message]
2022-08-27 16:10 ` Daniel Shahaf
2022-08-27 19:32 ` Vincent Bernat
2022-08-27 20:04 ` Lawrence Velázquez
2022-08-27 23:53 ` Ray Andrews
2022-08-28 7:53 ` zzapper
2022-08-28 10:30 ` Daniel Shahaf
2022-08-28 13:59 ` Ray Andrews
2022-08-28 18:29 ` Daniel Shahaf
2022-08-31 9:28 ` Vincent Lefevre
2022-08-31 14:17 ` Ray Andrews
2022-09-01 21:52 ` Felipe Contreras
2022-09-02 1:41 ` Lawrence Velázquez
2022-09-02 1:26 ` Lawrence Velázquez
2022-09-02 1:49 ` Felipe Contreras
2022-09-02 5:40 ` Lawrence Velázquez
2022-09-02 7:38 ` Felipe Contreras
2022-09-02 10:36 ` Daniel Shahaf
2022-09-02 14:26 ` Ray Andrews
2022-09-04 7:13 ` Daniel Shahaf
2022-09-04 16:30 ` Ray Andrews
2022-09-02 10:39 ` [PATCH] zstyle: Correct and expand docs (was: Re: Most minimal configuration challenge) Daniel Shahaf
2022-09-02 15:05 ` Bart Schaefer
2022-09-04 6:51 ` Daniel Shahaf
2022-09-02 13:55 ` Most minimal configuration challenge Ray Andrews
2022-09-04 7:21 ` Daniel Shahaf
2022-09-04 16:34 ` Ray Andrews
2022-09-02 13:32 ` Ray Andrews
2022-09-04 7:28 ` Daniel Shahaf
2022-09-02 9:53 ` Daniel Shahaf
2022-09-02 9:26 ` Daniel Shahaf
2022-09-02 14:44 ` Vincent Lefevre
2022-09-04 6:42 ` Daniel Shahaf
2022-09-05 9:47 ` Vincent Lefevre
2022-09-12 8:59 ` Daniel Shahaf
2022-08-28 18:58 ` Bart Schaefer
2022-08-28 19:23 ` Felipe Contreras
2022-08-28 19:35 ` Ray Andrews
2022-08-28 18:57 ` Felipe Contreras
2022-09-02 1:36 ` Vincent Lefevre
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=CAMP44s1d7Pnv5oAk4uwnBXhjYUikWSe8nqVZJuXvP4bEv1cCTA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=zsh-users@zsh.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://git.vuxu.org/mirror/zsh/
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).