From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: More rabbit-holes with unset variables
Date: Fri, 27 Nov 2020 17:35:44 -0600 [thread overview]
Message-ID: <CAMP44s1jo7Ly-e_veEFSMeKt58D-Ar1myxDwRdt3=KJtxTnHVQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7aPrcaoGyvm6N+ai4ADmWY02RBGUnWiFuAxRLFUAvbrqA@mail.gmail.com>
On Fri, Nov 27, 2020 at 4:06 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Fri, Nov 27, 2020 at 1:49 PM Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> >
> > There's no rabbit hole here. It's obvious that zsh's behavior is inconsistent.
>
> The rabbit holes are all the possible tangents that may or may not be
> additional inconsistencies, into which we keep plunging, rather than
> focusing on the most reasonable way to address the one we started
> with.
Right. But solving the first one (with setopt KSH_TYPESET or
whatever), solves the second one.
So to me they are not unrelated.
--
Felipe Contreras
next prev parent reply other threads:[~2020-11-27 23:36 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 7:02 Bart Schaefer
2020-11-25 13:19 ` Stephane Chazelas
2020-11-25 22:17 ` Felipe Contreras
2020-11-26 6:10 ` Stephane Chazelas
2020-11-26 7:20 ` Felipe Contreras
2020-11-26 11:21 ` Oliver Kiddle
2020-11-26 11:29 ` Roman Perepelitsa
2020-11-26 19:08 ` Felipe Contreras
2020-11-26 19:29 ` Felipe Contreras
2020-11-26 21:13 ` Bart Schaefer
2020-11-26 21:31 ` Felipe Contreras
2020-11-26 23:29 ` Bart Schaefer
2020-11-26 23:32 ` Bart Schaefer
2020-11-26 23:53 ` Felipe Contreras
2020-11-27 0:23 ` Bart Schaefer
2020-11-27 1:51 ` Felipe Contreras
2020-11-27 20:01 ` Bart Schaefer
2020-11-27 21:49 ` Felipe Contreras
2020-11-27 22:06 ` Bart Schaefer
2020-11-27 23:35 ` Felipe Contreras [this message]
2020-11-26 22:07 ` Bart Schaefer
2020-11-26 20:41 ` Bart Schaefer
2020-11-26 20:49 ` Stephane Chazelas
2020-11-26 21:20 ` Felipe Contreras
2020-11-26 22:41 ` Bart Schaefer
2020-11-26 23:45 ` Felipe Contreras
2020-11-27 0:09 ` Bart Schaefer
2020-11-27 0:30 ` Felipe Contreras
2020-11-27 0:51 ` Bart Schaefer
2020-11-27 1:30 ` Felipe Contreras
2020-11-27 20:54 ` Bart Schaefer
2020-11-27 22:10 ` Felipe Contreras
2020-11-27 22:39 ` Bart Schaefer
2020-11-28 0:00 ` Felipe Contreras
2020-11-28 0:04 ` Bart Schaefer
2020-11-28 10:52 ` Felipe Contreras
2020-11-28 0:36 ` The emulation rabbit-hole RE typeset/unset Bart Schaefer
2020-11-28 11:35 ` Felipe Contreras
2020-11-28 16:56 ` Bart Schaefer
2020-12-01 8:49 ` Felipe Contreras
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='CAMP44s1jo7Ly-e_veEFSMeKt58D-Ar1myxDwRdt3=KJtxTnHVQ@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=schaefer@brasslantern.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).