Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Rewrite of zsh-newuser-install
- X-seq: zsh-workers 47964
- From: dana <dana@xxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Cc: Marlon Richert <marlon.richert@xxxxxxxxx>, Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: Rewrite of zsh-newuser-install
- Date: Tue, 9 Feb 2021 01:30:54 -0600
- Archived-at: <https://zsh.org/workers/47964>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2021-02/CB574EAD-B2C6-4F78-8B67-0DF7D088B963%40dana.is>
- In-reply-to: <CAH+w=7byVopzqOGJoh6FgEB315pSpkxSetG0sQ2Evc-DFb-i0g@mail.gmail.com>
- 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> <CAH+w=7byVopzqOGJoh6FgEB315pSpkxSetG0sQ2Evc-DFb-i0g@mail.gmail.com>
On 9 Feb 2021, at 00:00, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> I feel about it a lot like I feel about POSIX compatibility. Read
> into that as you will.
🤔
On 9 Feb 2021, at 00:00, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>> * 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.
Actually i think the standard is referring to creating application
*sub-directories* under the base ones (e.g., $XDG_CACHE_HOME/zsh). I guess
that's the usual way to do it. But yeah, either way we'd probably need to
handle directory creation if we weren't going to just use ${ZDOTDIR:-$HOME}.
On 9 Feb 2021, at 00:00, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> setopt TRANSIENT_RPROMPT
I wonder if that makes the proposed RPROMPT more or less useful though. The
thinking behind it seemed like you'd have the time there as an historical
record, and if you made it transient you'd only have the time the last command
finished executing / the current prompt appeared. And if you're in screen/tmux
or a graphical terminal, you probably already have a clock, so....
On 9 Feb 2021, at 00:00, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> I was a little puzzled by "user names beginning with punctuation" but
> let it go at the time.
I actually do hide them myself, because macOS has a huge amount of
irrelevant-to-me system users with names like _timed and _hidd. I'm just not
sure if it's a good idea for every user on every platform.
btw: An improvement to the (Z)LS_COLORS stuff would be to source from
dircolors where available. Debian just do `eval "$(dircolors -b)"`, but that
overrides/exports LS_COLORS, and i'm not sure we want to be in the business of
screwing with parameters that don't belong to the shell. (Now that i think of
it, even just doing the LS_COLORS tie command could cause later profile
additions to falsely assume that LS_COLORS was set by the user.) Maybe
something like this (untested):
typeset -T ZLS_COLORS zls_colors=( 'any defaults here' )
if (( $+LS_COLORS )) || (( ! $+commands[dircolors] )); then
typeset -T LS_COLORS ls_colors
zls_colors+=( $ls_colors )
else
zls_colors+=( ${(s<:>):-"$(
eval "$( dircolors -b )"; print -r - $LS_COLORS
)"} )
fi
Not sure if it's worth checking for gdircolors (Homebrew name), but that's a
thought too
dana
Messages sorted by:
Reverse Date,
Date,
Thread,
Author