From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: setopt interactivecomments
Date: Thu, 17 Apr 2014 20:10:41 -0700 [thread overview]
Message-ID: <535097B1.4040107@eastlink.ca> (raw)
In-Reply-To: <140417154117.ZM22891@torch.brasslantern.com>
On 04/17/2014 03:41 PM, Bart Schaefer wrote:
> In fact more often than not for me backspace works just fine in zsh but
> is messed up in other programs like vim. That's not a shell problem,
> it's a tty-driver problem.
All I can say is that the first time I got Linux working, it didn't work
(mind,g that would have been bash) and I'm almost positive that the
first time I tried zsh it didn't work either. I could be wrong about
the latter of course, and it's just a for-instance anyway. I do know
that when I've been forced to run zsh without any .zshrc, it's pretty
raw. I don't stand on details, just the principle of the thing.
Anyway, since it seems there is some sort of config helper for newbies,
that's good enough for me, I'm just sad I missed it. Dunno, maybe it
could be more visible. I found the nucleus of my current .zshrc on the
web somewhere.
> Not sure where that's coming from either, because basic history motions
> are on by default as well. If you're going to make straw men, at least
> make them vaguely humanoid ...
I still have nightmares about that first experience with the shell, and
what I've said was certainly true back then. Maybe I'm just having
flashbacks. If we're more user friendly out of the box than I'm
remembering, then I withdraw all my comments. All I can say is that, on
principle, good stuff should be 'on' by default, and if tcsh didn't have
it 20 years ago that shouldn't be a big concern IMHO. I certainly don't
mean to be contentious. Perhaps, just to air the laundry, there could
be some sort of poll of the list as to who might like something or other
made a default?
next prev parent reply other threads:[~2014-04-18 3:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 14:35 shawn wilson
2014-04-16 17:27 ` Bart Schaefer
2014-04-16 17:37 ` shawn wilson
2014-04-17 14:37 ` Ray Andrews
2014-04-17 19:37 ` Bart Schaefer
2014-04-17 21:36 ` Ray Andrews
2014-04-17 22:07 ` shawn wilson
2014-04-17 22:48 ` Bart Schaefer
2014-04-17 23:51 ` shawn wilson
2014-04-17 22:41 ` Bart Schaefer
2014-04-18 3:10 ` Ray Andrews [this message]
2014-04-18 11:59 ` Roman Neuhauser
2014-04-23 15:50 ` zsh-newuser-install Peter Stephenson
2014-04-23 20:31 ` zsh-newuser-install Yuri D'Elia
2014-04-23 23:53 ` zsh-newuser-install Mikael Magnusson
2014-04-24 6:23 ` zsh-newuser-install Yuri D'Elia
2014-04-24 14:34 ` zsh-newuser-install Ray Andrews
2014-04-24 16:02 ` zsh-newuser-install Yuri D'Elia
2014-04-25 1:38 ` zsh-newuser-install Ray Andrews
2014-04-24 16:04 ` zsh-newuser-install Axel Beckert
2014-04-25 15:43 ` zsh-newuser-install Martin Vaeth
2014-04-25 16:21 ` zsh-newuser-install Peter Stephenson
2014-04-26 10:07 ` zsh-newuser-install Martin Vaeth
2014-04-26 20:21 ` zsh-newuser-install Peter Stephenson
2014-04-26 20:38 ` zsh-newuser-install Bart Schaefer
2014-04-25 17:03 ` zsh-newuser-install Bart Schaefer
2014-04-26 13:49 ` zsh-newuser-install Yuri D'Elia
2014-04-26 21:10 ` zsh-newuser-install Bart Schaefer
2014-04-28 17:35 ` zsh-newuser-install Bart Schaefer
2014-04-24 1:05 ` zsh-newuser-install Ray Andrews
2014-04-17 19:04 ` setopt interactivecomments Bart Schaefer
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=535097B1.4040107@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).