From: Ricardo Wurmus <rekado@elephly.net>
To: Catonano <catonano@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>, help-guix <help-guix@gnu.org>
Subject: Re: tree doesn't get called
Date: Mon, 08 May 2017 19:58:19 +0200 [thread overview]
Message-ID: <8760hbjkn8.fsf@elephly.net> (raw)
In-Reply-To: <CAJ98PDwb_4fNAO4osXn51FZ22gh1gOh69dEffoOnYy23-GW=Eg@mail.gmail.com>
Catonano <catonano@gmail.com> writes:
> In fact, I'd paste code even on IRC channels, I don't do so because I have
> been requested to abstain from pasting code in chat channels in the past
>
> But I don't understand the reason why that is not desirable, inconvenient
> and frown upon.
IRC is for real-time conversations, and pasting many lines of code there
makes it hard to converse. A channel can be very crowded even without
pasting code snippets, so it’s best to keep excess text to a minimum. I
guess that’s why it’s customary on IRC to paste code elsewhere and just
link to it.
For mails it’s fine (and desirable) to include code snippets inline or
as attachments.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2017-05-08 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 15:50 tree doesn't get called Catonano
2017-05-05 22:24 ` Eric Bavier
2017-05-08 5:02 ` Catonano
2017-05-08 6:08 ` Ricardo Wurmus
2017-05-08 17:14 ` Catonano
2017-05-08 17:45 ` Catonano
2017-05-08 20:19 ` Ricardo Wurmus
2017-05-09 15:41 ` Catonano
2017-05-09 15:43 ` Catonano
2017-05-10 19:51 ` Ricardo Wurmus
2017-05-11 4:20 ` Catonano
2017-05-09 17:20 ` Ricardo Wurmus
2017-05-09 18:12 ` Catonano
2017-05-08 7:34 ` Mark H Weaver
2017-05-08 17:28 ` Catonano
2017-05-08 17:58 ` Ricardo Wurmus [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760hbjkn8.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=catonano@gmail.com \
--cc=help-guix@gnu.org \
--cc=mhw@netris.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 read-only IMAP folder(s) and NNTP newsgroup(s).