From: ng0 <ng0@we.make.ritual.n0.is>
To: Hartmut Goebel <h.goebel@goebel-consult.de>, help-guix@gnu.org
Subject: Re: neo tty layout
Date: Mon, 29 Aug 2016 14:13:31 +0000 [thread overview]
Message-ID: <87d1krzmr8.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <57B1A96E.5070309@goebel-consult.de>
Hi,
Hartmut Goebel <h.goebel@goebel-consult.de> writes:
> Am 13.08.2016 um 18:15 schrieb ng0:
>> Would it be okay to replicate this for Guix?
>
> +1 (Currently trying to learn myself neo :-)
If you think you can do it and have the resources to do so, could you
take on this task?
I will probably not come back to this in a considerable long time
because it is low priority to me.
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-08-29 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 16:15 neo tty layout ng0
2016-08-13 23:13 ` Leo Famulari
2016-08-14 9:07 ` ng0
2016-08-14 16:21 ` Alex Kost
2016-08-14 17:36 ` ng0
2016-08-14 13:41 ` Ricardo Wurmus
2016-08-15 11:37 ` Hartmut Goebel
2016-08-29 14:13 ` ng0 [this message]
2016-09-05 13:40 ` Hartmut Goebel
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=87d1krzmr8.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=h.goebel@goebel-consult.de \
--cc=help-guix@gnu.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).