From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Ray Andrews <rayandrews@eastlink.ca>, Zsh-Users List <zsh-users@zsh.org>
Subject: Re: here document within a switch fails to parse.
Date: Wed, 13 Jan 2021 22:57:02 +0100 [thread overview]
Message-ID: <CAP+y1xCFS_sg6rpOfTLsxC8LsLnith0NK+FWqLQ=PvsFJ5N3Xg@mail.gmail.com> (raw)
In-Reply-To: <5272a248-c9c6-4f0f-86aa-efea5ae4d3ec@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
> I will, for the third and last time, remind you that your fashion of
> comments _will_ break, in a specific way.
Since Ray doesn't ask, I will: what situation will break those "comments"?
Pier Paolo Grassi
Il giorno mer 13 gen 2021 alle ore 17:18 Daniel Shahaf <
d.s@daniel.shahaf.name> ha scritto:
> Ray Andrews wrote on Tue, 12 Jan 2021 14:45 +00:00:
> > On 2021-01-12 5:28 a.m., Daniel Shahaf wrote:
> > > There's an interesting idea! My editor doesn't but that would be
> quite a
> > >> feature.
> > > Did you actually look?
> > >
> > Yes sir I did. I use a very lightweight but understandable IDE, what it
> > lacks in features it makes up in being easy to use.
>
> (Turns out Ray's IDE does have that feature after all.)
>
> > It's too bad there's no place for a guy like me to learn the ropes, I
> > don't know what I don't know. What I'd like is to be is a fly on the
> > wall, watching you adepts work for a week -- I'd learn more in that
> > week than thrashing around by myself for a year.
>
> You're probably right about that, insofar as discovering features is
> concerned. (To a point, anyway; 80/20 still applies. Still, you can
> look for people who post videos of themselves coding.) However,
> knowing a ton of features shouldn't be your highest priority, IMO.
> It's very much like the difference between memorizing a map and
> learning to navigate.
>
> I will, for the third and last time, remind you that your fashion of
> comments _will_ break, in a specific way.
>
> Daniel
>
>
[-- Attachment #2: Type: text/html, Size: 2238 bytes --]
next prev parent reply other threads:[~2021-01-13 21:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:13 Ray Andrews
2021-01-06 16:20 ` Daniel Shahaf
2021-01-06 17:17 ` Ray Andrews
2021-01-06 17:58 ` Lawrence Velázquez
2021-01-06 19:18 ` Bart Schaefer
2021-01-07 7:55 ` Ray Andrews
2021-01-07 15:32 ` Daniel Shahaf
2021-01-07 20:16 ` Ray Andrews
2021-01-08 15:27 ` Karsten Borgwaldt
2021-01-08 15:53 ` Lawrence Velázquez
2021-01-08 17:13 ` Ray Andrews
2021-01-08 18:06 ` Peter Stephenson
2021-01-08 19:39 ` Ray Andrews
2021-01-08 19:56 ` Bart Schaefer
2021-01-09 0:45 ` Ray Andrews
2021-01-09 17:28 ` Ray Andrews
2021-01-12 13:28 ` Daniel Shahaf
2021-01-12 14:45 ` Ray Andrews
2021-01-13 16:17 ` Daniel Shahaf
2021-01-13 21:57 ` Pier Paolo Grassi [this message]
2021-01-13 23:39 ` Ray Andrews
2021-01-13 23:54 ` Lawrence Velázquez
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='CAP+y1xCFS_sg6rpOfTLsxC8LsLnith0NK+FWqLQ=PvsFJ5N3Xg@mail.gmail.com' \
--to=pierpaolog@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=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).