Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Rewrite of zsh-newuser-install
- X-seq: zsh-workers 47963
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: dana <dana@xxxxxxx>
- Cc: Marlon Richert <marlon.richert@xxxxxxxxx>, Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: Rewrite of zsh-newuser-install
- Date: Mon, 8 Feb 2021 22:00:33 -0800
- Archived-at: <https://zsh.org/workers/47963>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2021-02/CAH%2Bw%3D7byVopzqOGJoh6FgEB315pSpkxSetG0sQ2Evc-DFb-i0g%40mail.gmail.com>
- In-reply-to: <19996A10-103F-4054-AD57-FCED8E406687@dana.is>
- List-id: <zsh-workers.zsh.org>
- References: <CAHLkEDv8KDW0iy+EtLXRgFOzgF1BbK5rEKjNBO-=NNUeKR9Xwg@mail.gmail.com> <0102017778f35f33-a962e4d3-83e9-4d3b-a0d7-45701bb40b11-000000@eu-west-1.amazonses.com> <CAHLkEDvL8+32tFQ1n6=SsaRMFQB3U2Di=6qpHtNBz8SkwzH7Zg@mail.gmail.com> <D6B297FA-044D-4F4E-8110-D6F4E2058EFE@larryv.me> <CAHLkEDvToxSvZWGMg7MKkFXjjWEefXW8e=gd+0e5RmuBLkVWEw@mail.gmail.com> <CAN=4vMqjYNtm3KSq47kC_2O4k3=hzF7qwN0sK9deCNgc2xK=kg@mail.gmail.com> <CAHLkEDvrcTdW2B3mxFAj8a7Wmfz-0KHGJkvi5hEdcCFSaP64NA@mail.gmail.com> <8BA25288-0FFB-4FF4-9799-541D6A3C52DA@dana.is> <CAHLkEDvWsv=hTHJ+70d1RQM7sH5_w94LYKhgrV2=vNMTchnx8w@mail.gmail.com> <CAHLkEDur33X5s7Ar8n-9zQR0GqoZm3u_8rPRF3P-Jf=v90aLUA@mail.gmail.com> <19996A10-103F-4054-AD57-FCED8E406687@dana.is>
On Mon, Feb 8, 2021 at 8:51 PM dana <dana@xxxxxxx> wrote:
>
> > zstyle ':completion:*' cache-path "${XDG_CACHE_HOME:-$HOME/.cache}/zcompcache"
> > compinit -d ${XDG_CACHE_HOME:-$HOME/.cache}/zcompdump
>
> I actually don't feel strongly about whether we respect XDGBDS or not.
I feel about it a lot like I feel about POSIX compatibility. Read
into that as you will.
> * How should we handle systems that don't normally use XDGBDS? Should we just
> force the issue and use it everywhere? Or should we have platform-specific
> logic to fall back to ${ZDOTDIR:-$HOME}?
I would recommend ${XDG_CACHE_HOME:-${ZDOTDIR:-$HOME/.cache}} or
similar, now that you mention it.
> * I think the spec says applications should create the directories if they
> don't exist, right? So shouldn't we `mkdir -pm 0700` them (or the defaults)
> if necessary?
Thanks for catching that, yes.
> * I like the right-hand prompt and use it myself, but one disadvantage it has
> is that it makes it annoying to copy and paste from your terminal.
I meant to mention
setopt TRANSIENT_RPROMPT
> [...] i foresee a possible future where heaps of novice
> users are including these long irritating strings of white space in their
> support requests.
That's already a problem for some terminal types, especially when
copy-pasting a completion menu or the like.
> * I do like the idea of encoding the return status in the prompt. I don't feel
> strongly about whether it's indicated by a colour, a symbol, and/or a
> number. I'm pretty sure red/green is the most common type of
> colour-blindness, though, so maybe a colour-only approach is not ideal.
I use reverse-video for this.
> * Whatever we pick for our prompt, should we maybe implement it using the
> prompt-theme system?
That would make it less "abandonware" as it was previously accused of
being (tho if Debian uses it, it can't be considered completely
abandoned).
> > zstyle ':completion:*:(functions|parameters|users)' ignored-patterns '[[:punct:]]*[[:alnum:]]*'
>
> Not sure about this.
I was a little puzzled by "user names beginning with punctuation" but
let it go at the time.
> > export -T LS_COLORS ls_colors
> > export -T ZLS_COLORS zls_colors=(
>
> Nit-picking, but using export for this initially confused me. You're not
> exporting them (and don't want to). I think you should just use typeset.
Good catch.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author