From andrew spada to ~sircmpwn/godocs.io
On Fri, Jun 25, 2021 at 10:48 PM Adnan Maolood <me@adnano.co> wrote: > Looks like there was an issue with the documentation not being > displayed, which has just been fixed. Looks like I really jumped to conclusions there. My mistake! >We currently don't link to this from anywhere. Perhaps we should add a >link to the homepage or the footer. That sounds reasonable. It took me a couple tries to realize it was "std". By the way, both golang.org/pkg and pkg.go.dev/std both hide internal packages, to keep the list from getting too cluttered. I think it would be nice if godocs.io did the same.
From andrew spada to ~sircmpwn/godocs.io
Did Go/Google ask you to remove it?
From s-video to ~sircmpwn/email-test-drive
--- s-video | 1 + 1 file changed, 1 insertion(+) create mode 100644 s-video diff --git a/s-video b/s-video new file mode 100644 index 0000000..66cb3d4 --- /dev/null +++ b/s-video @@ -0,0 +1 @@ I have successfully used git send-email! -- 2.20.1 [message trimmed]
From s-video to ~sircmpwn/email-test-drive
--- s-video | 1 + 1 file changed, 1 insertion(+) create mode 100644 s-video diff --git a/s-video b/s-video new file mode 100644 index 0000000..6d0ecfd --- /dev/null +++ b/s-video @@ -0,0 +1 @@ I'm about to try git send-email -- 2.20.1 [message trimmed]
From andrew spada to ~s-video/public-inbox
quick test
From andrew spada to ~s-video/public-inbox
This message was sent from the full screen view of the gmail web interface.
From andrew spada to ~s-video/public-inbox
On Thu, Jun 17, 2021 at 3:25 PM andrew spada <spada.andrew.j@gmail.com> wrote: > (This message will also tell us if gmail trims leading newlines) It does. As I mentioned before, gmail automatically puts the quoted email you're replying to you at the bottom, under an extra newline. When you move your cursor under the block quote, the extra lines are still there, but it looks like gmail trimmed them for me.
From andrew spada to ~s-video/public-inbox
On Thu, Jun 17, 2021 at 3:23 PM andrew spada <spada.andrew.j@gmail.com> wrote: > > Note to self: It appears that the gmail web client does not play well with sourcehut. Contrary to my initial assessment, it appears that the gmail web client plays decently, but not ideally, with sourcehut. (This message will also tell us if gmail trims leading newlines)
From andrew spada to ~s-video/public-inbox
Note to self: It appears that the gmail web client does not play well with sourcehut. I attempted to reply to an thread in the /~sircmpwn/sr.ht-discuss by following the mailto link, which opened the gmail web client. Gmail's web client displayed a full screen "New Message" box, not the typical interface for viewing the inbox or threads. Instead of appearing as a reply in both sourcehut's and gmail's interface, my reply appeared as a new thread. I think that gmail's web client may have stripped the in-reply-to parameter from the mailto link when opening, but I'm not sure. I then sent a reply to the thread again, using mutt, manually filling the address and subject field according to the mailto link. This reply didn't appear in the sourecehut interface or mutt at all, but appeared correctly in gmail as a reply to the thread. I'm not sure why sourcehut didn't display the message.
From andrew spada to ~s-video/public-inbox
On Thu, Jun 17, 2021 at 02:44:26PM -0400, andrew spada wrote: > On Thu, Jun 17, 2021 at 2:31 PM andrew spada <spada.andrew.j@gmail.com> wrote: > > > > This may or may not appear as a reply. This message was sent from > > the Gmail web client. > > This reply should not be bottom quoted. It was also sent from the > Gmail web client. I'm replying to this message from mutt.