9front - general discussion about 9front
 help / color / mirror / Atom feed
From: umbraticus@prosimetrum.com
To: 9front@9front.org
Subject: Re: [9front] plumbing with spaces
Date: Wed, 06 Nov 2024 17:57:50 +1300	[thread overview]
Message-ID: <A3223ED45264DADD8B67CCBC77DF815D@prosimetrum.com> (raw)
In-Reply-To: <32ERPD9FSEHN0.2PR9UYWTR5B74@canaglie.net>

It's not really the plumber's fault; rather it's how the
programs at either end cope. I do think it would be
nice if you could select a line in rio by double-clicking
then plumb: sadly the newline messes things up, so
one must resort to surrounding spacey plumb strings
with brackets or braces or quotes or whatever to avoid
precision sweeping. Both sam and ed cope with my
'test file with spaces' per the below rule. I pass no
comment on any other editor.

data matches test.*
arg isfile $data
plumb start window sam ''''$file''''

umbraticus

  reply	other threads:[~2024-11-06  4:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  1:15 népéta mew
2024-11-06  4:57 ` umbraticus [this message]
2024-11-06 12:40   ` hiro
2024-11-07  8:46     ` umbraticus
2024-11-07  8:52       ` umbraticus

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=A3223ED45264DADD8B67CCBC77DF815D@prosimetrum.com \
    --to=umbraticus@prosimetrum.com \
    --cc=9front@9front.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.
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).