zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: line continuation with sed
Date: Sat, 15 Oct 2022 09:53:39 -0700	[thread overview]
Message-ID: <4e4d53a2-226e-a0ae-a1f7-87619eaff155@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Yp++F1A4JGtrp5cmXRah2dDgwuit_6aKDSoQTX+phuWA@mail.gmail.com>


On 2022-10-14 22:08, Bart Schaefer wrote:
> We went through this a while ago. A comment can't end with a line
> continuation because then it's not possible to distinguish where the
> comment itself ends (is the following line part of the comment?).  A
> comment can't follow a line continuation for the same reason a space
> can't.

I remember.  But it took a while for the memory to resurface, sorry for 
flogging a dead horse.  (But I do think the horse could be flogged a bit 
more ;-)




  reply	other threads:[~2022-10-15 16:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 18:25 Ray Andrews
2022-10-14  6:35 ` Lawrence Velázquez
2022-10-14 11:20   ` Dominik Vogt
2022-10-14 15:44     ` Ray Andrews
2022-10-14 17:10       ` Dominik Vogt
2022-10-14 20:38       ` Lawrence Velázquez
2022-10-14 22:26         ` Ray Andrews
2022-10-14 10:57 ` Marc Chantreux
2022-10-14 11:19 ` Peter Stephenson
2022-10-14 17:15   ` Dominik Vogt
2022-10-14 22:21     ` Ray Andrews
2022-10-15  2:34 ` Aaron Schrab
2022-10-15  2:57   ` Ray Andrews
2022-10-15  5:08     ` Bart Schaefer
2022-10-15 16:53       ` Ray Andrews [this message]
2022-10-17  1:07         ` Bart Schaefer
2022-10-17  3:40           ` Ray Andrews
2022-10-17  4:20             ` Bart Schaefer
2022-10-17  9:19               ` Pier Paolo Grassi
2022-10-17  9:24                 ` Pier Paolo Grassi
2022-10-17  9:31                   ` Pier Paolo Grassi
2022-10-17 16:11                     ` 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=4e4d53a2-226e-a0ae-a1f7-87619eaff155@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).