9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "James A. Robinson" <jim.robinson@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] question re acme and plumber
Date: Thu, 25 Jul 2019 13:54:29 -0700	[thread overview]
Message-ID: <CAPd04b4UPOvKPx=PzBdeBHAs4iso9vLaZT+tNMhtd75tAjoJ3Q@mail.gmail.com> (raw)
In-Reply-To: <CAHqDL_-0XBNSfhreoM+VT_XtPXv3M6EHP4OQs9JewgyFUJNCxg@mail.gmail.com>

Thanks, I stopped digging after that and just added a shell script
wrapper to reformat the lines in question ¯\_(ツ)_/¯

$ 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
<ole.hjalmar.kristensen@gmail.com> wrote:
>
> I think the text that is selected and sent by button 3 is hard-coded in acme, 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 <jim.robinson@gmail.com>:
>>
>> Well, I can see this is getting called:
>>
>> look.c:187: if(m->ndata<messagesize-1024 &&
>> plumbsendtofid(plumbsendfid, m) >= 0){
>>
>> and the m->data is the full line, including the trailing
>> ".java:[<lineno>,<colno>]" 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
>>



      reply	other threads:[~2019-07-25 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 18:44 James A. Robinson
2019-07-11  6:25 ` Martin Kühl
2019-07-11 19:57   ` James A. Robinson
2019-07-11 21:28     ` James A. Robinson
2019-07-24 21:18       ` Ole-Hjalmar Kristensen
2019-07-25 20:54         ` James A. Robinson [this message]

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='CAPd04b4UPOvKPx=PzBdeBHAs4iso9vLaZT+tNMhtd75tAjoJ3Q@mail.gmail.com' \
    --to=jim.robinson@gmail.com \
    --cc=9fans@9fans.net \
    /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).