From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: "James A. Robinson" Date: Thu, 25 Jul 2019 13:54:29 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] question re acme and plumber Topicbox-Message-UUID: 02e6f6a6-eada-11e9-9d60-3106f5b1d025 Thanks, I stopped digging after that and just added a shell script wrapper to reformat the lines in question =C2=AF\_(=E3=83=84)_/=C2=AF $ cat ~/bin/mvn #!/bin/sh /usr/local/bin/mvn "$@" | sed 's!\.java:\[\([0-9]*\),[0-9]*\]!.java:\1!g'; On Wed, Jul 24, 2019 at 2:19 PM Ole-Hjalmar Kristensen wrote: > > I think the text that is selected and sent by button 3 is hard-coded in a= cme, so the square brackets acts as delimiters. If you click on the text to= the left of the brackets, the plumber will not see the brackets or what's = inside them. If you sweep and select yourself, the whole selection goes to = the plumber. > > tor. 11. jul. 2019, 23.30 skrev James A. Robinson : >> >> Well, I can see this is getting called: >> >> look.c:187: if(m->ndata> plumbsendtofid(plumbsendfid, m) >=3D 0){ >> >> and the m->data is the full line, including the trailing >> ".java:[,]" data. >> >> So it's certainly appears to be sending the data to the plumber. >> But I don't get the same behavior from acme as when I send the >> same text I see in m->data to plumb(1) directly on the command >> line. >> >> Jim >>