unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Cech <sleep_walker@gnu.org>
To: ng0 <ng0@libertad.pw>
Cc: guix-devel@gnu.org
Subject: Re: Add a pastebin client to the next guixsd image release
Date: Mon, 05 Dec 2016 15:03:28 +0100	[thread overview]
Message-ID: <87k2be8ocv.wl-sleep_walker@gnu.org> (raw)
In-Reply-To: <87mvgby2yr.fsf@we.make.ritual.n0.is>

On Sun, 04 Dec 2016 19:16:28 +0100,
ng0 wrote:
> 
> I think the next release image for GuixSD should include
> wgetpaste as a tool. This would make it possible for people who
> are stuck in the image and who are doing the installation, to
> paste the config.scm or any other command output.
> 
> Are there any security concerns, or is this something we can do?
> If the majority should be against it, another option I can think
> of is that we add it to the documentation as a general suggestion
> to search for "pastebin" with "guix package -s pastebin" and
> install one of the available pastebin clients (there'll be more
> than one at some point).

Good idea.

I like the http://sprunge.us/ solution. It uses curl and has support
for syntax highlighting.

With shell function like this:
sprunge() {
  curl -F 'sprunge=<-' http://sprunge.us
}

you can do:
$ command | sprunge
$ sprunge < file

So it mimics UNIX filosophy and has tiny dependency.

Best regards,

S_W

  parent reply	other threads:[~2016-12-05 14:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04 18:16 Add a pastebin client to the next guixsd image release ng0
2016-12-05  9:21 ` Alex Kost
2016-12-05 11:03   ` ng0
2016-12-05 21:01   ` Ludovic Courtès
2016-12-06  9:45     ` ng0
2016-12-07 22:07       ` Ludovic Courtès
2016-12-07 23:32         ` ng0
2016-12-08  9:28           ` Ludovic Courtès
2016-12-09  5:53             ` Chris Marusich
2016-12-05 14:03 ` Tomas Cech [this message]
2016-12-05 14:19   ` ng0

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=87k2be8ocv.wl-sleep_walker@gnu.org \
    --to=sleep_walker@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@libertad.pw \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).