zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Sebastian Gniazdowski <sgniazdowski@gmail.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Official plugin manager?
Date: Thu, 2 Jan 2020 13:00:50 +0100	[thread overview]
Message-ID: <CAN=4vMrQ91WWAxyw=3_pk5HHc_vk6Ls_GRmpiB5Xkk4N44gKDw@mail.gmail.com> (raw)
In-Reply-To: <63663202-4b1d-428a-b16b-5be1425e84ef@www.fastmail.com>

On Thu, Jan 2, 2020 at 12:04 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> [...] let's talk about problems

I've switched to Zsh in early 2019. I don't claim to be a typical user
but perhaps my recollection of the transition will illuminate some of
the difficulties new users face.

The only shell I'd used prior to switching to Zsh was Bash. My rc
files were based on the stock configs supplied by the distro. Over the
years I'd added a few `export`, `alias` and `bind` statements, but
other than that I hadn't changed anything. When upgrading my distro I
would transfer over my rc changes to the new stock files.

When I decided to try zsh, my distro of choice was Ubuntu. The
installation of zsh was as easy as I could ask for -- just `sudo apt
install zsh`. When I typed `zsh`, I was greeted by the new user
dialog. This was a pleasant surprise turned sour. I tried going
through all options to see the whole configuration space but gave up
after a few minutes as I was unable to understand the implications of
my answers. I quit the dialog without writing ~/.zshrc. My idea was to
see what the experience is like without a custom config. It was
intimidating. 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). Basic keys such as home, end or delete
didn't work. I fired zsh again to try the new user dialog once more
and chose the "recommended" option. This hasn't fixed neither prompt
nor key bindings. I deleted ~/.zshrc and gave the new user dialog one
last try. This time I went through every single option to see if it'll
ask me about prompt and key bindings anywhere. No such luck. At this
point I googled "zsh basic config" or something like that. All top
results said to install Oh My Zsh, so I did. This gave me prompt
closer to what I wanted and my keys worked.

I should note that Bash without user rc files is also underwhelming.
While the basic keys still work, prompt is `bash-4.4$`. What makes the
out-of-the-box Bash experience decent on Ubuntu is /etc/skel/.bashrc,
which becomes ~/.bashrc for new users.

Roman.

  parent reply	other threads:[~2020-01-02 12:01 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 [this message]
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='CAN=4vMrQ91WWAxyw=3_pk5HHc_vk6Ls_GRmpiB5Xkk4N44gKDw@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=sgniazdowski@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).