From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Official plugin manager?
Date: Thu, 2 Jan 2020 13:21:46 +0100 [thread overview]
Message-ID: <CAKc7PVBvfhSr1TH7z6Jf=1pdLcB7pyPeZJJSmqpe0q92wdLu_Q@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMrQ91WWAxyw=3_pk5HHc_vk6Ls_GRmpiB5Xkk4N44gKDw@mail.gmail.com>
On Thu, 2 Jan 2020 at 13:01, Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> On Thu, Jan 2, 2020 at 12:04 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > [...] let's talk about problems
>
> (...)
>
> Prompt was missing the information I was used to (the
> default Bash prompt in Ubuntu shows user@host and the current
> directory in different colors).
I think that the prompt problem would be solved by the p-m. A simple:
"zsh-pm load user/theme" added to the .zshrc would give a theme that's
either decent relatively - i.e.: when compared to the default % prompt
- or absolutely - in case of the user/plugin being a good theme.
> Basic keys such as home, end or delete didn't work.
The point 6.: the new way of packaging scripts, not through autoload
functions but by sourceables - would allow bundling a few reasonable
bindkey setups. I suspect that the unclean impression given by doing
this by the autoloads – given because it doesn't feel right to create
a set of functions with just a set of bindkey calls in them – could be
one of the main reasons of why this isn't currently bundled.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2020-01-02 12:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 3:17 Sebastian Gniazdowski
2020-01-02 4:28 ` Eric Cook
2020-01-02 11:03 ` Daniel Shahaf
2020-01-02 11:37 ` Sebastian Gniazdowski
2020-01-02 11:55 ` Sebastian Gniazdowski
2020-01-02 21:30 ` dana
2020-01-03 0:25 ` Sebastian Gniazdowski
2020-01-03 1:36 ` dana
2020-01-03 2:43 ` Sebastian Gniazdowski
2020-01-03 2:45 ` Bart Schaefer
2020-01-03 3:26 ` dana
2020-01-03 5:13 ` Sebastian Gniazdowski
2020-01-03 15:00 ` Peter Stephenson
2020-01-03 20:48 ` Daniel Shahaf
2020-01-03 21:51 ` Roman Perepelitsa
2020-01-03 22:06 ` Daniel Shahaf
2020-01-03 22:26 ` Bart Schaefer
2020-01-03 22:37 ` Roman Perepelitsa
2020-01-04 0:42 ` dana
2020-01-04 1:06 ` Daniel Shahaf
2020-01-04 15:46 ` Roman Perepelitsa
2020-01-04 16:27 ` Daniel Shahaf
2020-01-04 16:41 ` Roman Perepelitsa
2020-01-04 17:35 ` Daniel Shahaf
2020-01-04 17:42 ` Roman Perepelitsa
2020-01-04 17:11 ` Bart Schaefer
2020-01-05 10:40 ` Oliver Kiddle
2020-01-06 17:47 ` Leah Neukirchen
2020-01-03 11:15 ` Oliver Kiddle
2020-01-04 5:16 ` Sebastian Gniazdowski
2020-01-04 6:00 ` Sebastian Gniazdowski
2020-01-02 12:00 ` Roman Perepelitsa
2020-01-02 12:21 ` Sebastian Gniazdowski [this message]
2020-01-02 12:27 ` Roman Perepelitsa
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='CAKc7PVBvfhSr1TH7z6Jf=1pdLcB7pyPeZJJSmqpe0q92wdLu_Q@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=roman.perepelitsa@gmail.com \
--cc=zsh-workers@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).