zsh-workers
 help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
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: Fri, 3 Jan 2020 18:42:59 -0600	[thread overview]
Message-ID: <DA9882E9-D7B0-444B-82AE-EA1FE6F1294C@dana.is> (raw)
In-Reply-To: <CAN=4vMqxOAVOY_9k9rPO3=BtTEjvBebxGCkpm2ZmP-CuySrrEQ@mail.gmail.com>

On 3 Jan 2020, at 16:37, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
> - Move keybindings (everything, really) from the global zshrc to the
> user and remove fancy indirection from there as well

Actually, if key bindings don't always work well out of the box, and
especially if we can fix that by simply checking terminfo, shouldn't we do
that with the default bindings in the shell itself?

In either case, *not* using terminfo seems like it will limit what we can
actually do, since we risk breaking some terminals otherwise. That's
presumably why the Debian configuration uses it in the first place.

On 3 Jan 2020, at 16:37, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
> - Maybe fewer completion styles. Seems like too much but maybe they
> are really important, I don't know.

Obviously we shouldn't go crazy with it, but i don't see any reason to
specifically limit the use of styles. The style system is an important aspect
of configuring zsh. There are very useful settings that can only be changed
that way, and it's important for users to know about it if they want to make
their own changes.

I agree that everything should be thoroughly commented, and designed to impart
as much general/transferable knowledge as possible to the user. They won't
learn from it easily if the file contains too much magic.

dana


  reply	other threads:[~2020-01-04  0:41 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 [this message]
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
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=DA9882E9-D7B0-444B-82AE-EA1FE6F1294C@dana.is \
    --to=dana@dana.is \
    --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).