Call for good plugins list

Call for good plugins list

[Sebastian Gniazdowski]

Hello,
I once tested 40 plugins, when I was creating Zplugin. There were gems, but several problems were noticable, e.g. low commit count.

I'm creating semi-graphical interface to Zplugin. It is called Crasis, written in pure Zshell. It has list of "gold" plugins built in. The list is shown in video below:

https://asciinema.org/a/140446

I want to extend the list. Can I ask of any proposals? Which plugin do you use for a couple of months without problems and which has nice features?

-- 
Sebastian Gniazdowski
psprint /at/ zdharma.org

Re: Call for good plugins list

[Ray Andrews]

> https://asciinema.org/a/140446

Maybe it's just me, but I find Sebastian's animations go so fast I have 
no idea what's going on.  Bound to be very cool stuff tho.

Re: Call for good plugins list

[Bart Schaefer]

On Oct 1,  9:41am, Ray Andrews wrote:
}
} > https://asciinema.org/a/140446
} 
} Maybe it's just me, but I find Sebastian's animations go so fast I have 
} no idea what's going on.

I think think this is a result of asciinema compressing out any "frames"
where the screen doesn't change.  I thought at one point I'd found a way
to make it slow down, but I can't find that control now.

(Incidentally I'm not going to be answering the original question because
I don't use any plugins .. unless VCS_info counts, but I don't use that in
the recommended way either.)

Re: Call for good plugins list

[Daniel Shahaf]

Bart Schaefer wrote on Sun, 01 Oct 2017 11:54 -0700:
> (Incidentally I'm not going to be answering the original question because
> I don't use any plugins .. unless VCS_info counts, but I don't use that in
> the recommended way either.)

I'm curious as to how you do use vcs_info.

(My use of it is standard, modulo that I use 'print -P' from precmd()
rather than promptsubst, and I have a few hooks, e.g., one that during
an rebase with a conflict, sets a variable to the hash of the commit
being re-applied.)

Cheers,

Daniel

VCS info (Re: Call for good plugins list)

[Bart Schaefer]

On Oct 1,  7:29pm, Daniel Shahaf wrote:
}
} I'm curious as to how you do use vcs_info.

The main thing is that I despise prompt_subst, so:

autoload -Uz add-zsh-hook
autoload -Uz vcs_info

vcs-info-v() { vcs_info; RPS1="$vcs_info_msg_0_" }
add-zsh-hook precmd vcs-info-v

zstyle ':vcs_info:*' actionformats \
   '%F{5}(%f%s%F{5})%F{3}-%F{5}[%F{2}%b%F{3}|%F{1}%a%F{5}]%f '
zstyle ':vcs_info:*' formats \
   '%F{5}(%f%s%F{5})%F{3}-%F{5}[%F{2}%b%F{5}]%f '

This is in combination with transient_rprompt so the VCS stuff vanishes
while a command is running.

I did borrow somebody's (yours?) +vi-git-post-backend-updown hook, but
had to hack it because some of my remote terminals don't do UTF-8.

Re: VCS info (Re: Call for good plugins list)

[Daniel Shahaf]

Bart Schaefer wrote on Sun, 01 Oct 2017 14:50 -0700:
> autoload -Uz add-zsh-hook
> autoload -Uz vcs_info
> 
> vcs-info-v() { vcs_info; RPS1="$vcs_info_msg_0_" }
> add-zsh-hook precmd vcs-info-v

I don't use promptsubst either:

_precmd_vcs_info () {
	vcs_info
	[[ -n ${vcs_info_msg_0_} ]] && {
		print
		print -Plr -- ${vcs_info_msg_0_} ${vcs_info_msg_1_}
	}
}

> I did borrow somebody's (yours?) +vi-git-post-backend-updown hook, but

I posted it once, but it had been added to vcs_info-examples before then.

What's wrong with PROMPT_SUBST? (Was: VCS info (Re: Call for good plugins list))

[Lawrence Velázquez]

Hi,

Sorry for dredging this up, but it caught my eye while I was working on
my mailing list backlog.

> On Oct 1, 2017, at 5:50 PM, Bart Schaefer <schaefer@brasslantern.com>
> wrote:
> 
> The main thing is that I despise prompt_subst

Why is that? I'm curious whether it has some drawbacks that I should be
aware of.

vq

Re: What's wrong with PROMPT_SUBST? (Was: VCS info (Re: Call for good plugins list))

[Bart Schaefer]

On Tue, Feb 11, 2020 at 1:38 AM Lawrence Velázquez <vq@larryv.me> wrote:
>
> > On Oct 1, 2017, at 5:50 PM, Bart Schaefer <schaefer@brasslantern.com>
> > wrote:
> >
> > The main thing is that I despise prompt_subst
>
> Why is that?

Mostly it's a matter of taste.  It introduces yet another set of
tokens that you have to escape to use literally in prompts, and I
don't think the prompt is an appropriate place to be running command
substitutions.  It means even more possible collisions on variable
names with unintended side-effects.   Obviously these are things that
can be avoided; I'd just rather not have to think about them.

Re: What's wrong with PROMPT_SUBST? (Was: VCS info (Re: Call for good plugins list))

[Mikael Magnusson]

On 2/12/20, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Tue, Feb 11, 2020 at 1:38 AM Lawrence Velázquez <vq@larryv.me> wrote:
>>
>> > On Oct 1, 2017, at 5:50 PM, Bart Schaefer <schaefer@brasslantern.com>
>> > wrote:
>> >
>> > The main thing is that I despise prompt_subst
>>
>> Why is that?
>
> Mostly it's a matter of taste.  It introduces yet another set of
> tokens that you have to escape to use literally in prompts, and I
> don't think the prompt is an appropriate place to be running command
> substitutions.  It means even more possible collisions on variable
> names with unintended side-effects.   Obviously these are things that
> can be avoided; I'd just rather not have to think about them.

One particular cargo culted piece of setup is the following combo,

setopt prompt_subst
preexec() {
  print -P "$escape_to_set_terminal_title $1 $end_terminal_title"
}

which will result in the following command having funny results,
echo '$(killall -9 zsh)'

(the above code is wrong even without prompt_subst but the
consequences are quite a bit worse with it). The easy fix with
prompt_subst enabled is to use \$1 instead which should be more or
less fine as long as you haven't literally typed in the
$end_terminal_title code.

-- 
Mikael Magnusson