out of curiosity, do you envision a way to make something based on
gorram net/http Get http://foo.org
"Just Work"? (i.e. it would get you what the user is most likely
interested in: the resp.Body)
I must admit it's the first thing I tried as it would have been a
gorram fun replacement for curl.
Looks shiny!
But is there some sort of cache I have to clear? I've just updated and
rebuilt, and I still get the old behaviour.
On 8 October 2016 at 04:05, Nate Finch wrote:
> ...and now it works like you'd hope :)
>
>
> $ gorram net/http Get https://npf.io/gorram/run
> href="https://npf.io/gor
Hi,
Just a heads up for Acme users since it's not listed on
https://docs.google.com/document/d/1_Y9xCEMj5S-7rv2ooHpZNH15JgRT5iM742gJkw5LtmQ/edit
:
I've modified the tool I'm using for my searches in acme
(https://github.com/mpl/gofinder) so that it now supports Go guru.
hth,
Mathieu
--
You rece
aha! that was it, thanks.
On 11 October 2016 at 18:16, Edward Muller wrote:
> gorram -r <...>
>
> On Mon, Oct 10, 2016 at 3:02 PM Mathieu Lonjaret
> wrote:
>>
>> Looks shiny!
>> But is there some sort of cache I have to clear? I've just updated and
>
As you said, sometimes one is not sure in which X for "go help X" one
might find the information they're looking for. So one can end up
trying several of them before finding the relevant info. I can think
of one way that would alleviate that pain a bit: something like a "go
help all" command that w
> FWIW 'go help all' is essentially 'go doc go'.
>
> On Fri, Oct 21, 2016 at 9:46 AM Mathieu Lonjaret
> wrote:
>>
>> As you said, sometimes one is not sure in which X for "go help X" one
>> might find the information they're looking
Hi,
I've been using the Go fonts (in p9p acme) for a week now, and so far I
kind of like it, so thanks for making it.
Anyway, I've just noticed this error message in the terminal from which I
launched acme, so I assume acme is the one complaining about it, but I
haven't dug any deeper.
"stringwi
gt; a loop or hole in its definition. In particular it's about the textual Plan
> 9 font file, not the subfont images.
>
> But it should be easy to figure out: where does rune U+ map to,
> according to the font? I suspect the answer is "nowhere" and that's wha
Ah thanks, I had forgotten to try reading that one. Here goes:
$ 9p read 'font/Go Mono/11/font'
16 13
0x 0x001f x.bit
0x0020 0x003f x0020.bit
...
On 10 January 2017 at 17:13, andrey mirtchovski
wrote:
> > Sorry, I don't understand what you mean by the textual Plan 9 f
