all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: ng0@n0.is
Cc: 30344@debbugs.gnu.org
Subject: [bug#30344] cwm
Date: Mon, 5 Feb 2018 17:48:26 -0500	[thread overview]
Message-ID: <20180205224826.GB20907@jasmine.lan> (raw)
In-Reply-To: <87d11l6ldy.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

On Sun, Feb 04, 2018 at 11:32:09AM +0000, ng0@n0.is wrote:
> On Sun, 04 Feb 2018, ng0@n0.is wrote:
> > Trying to reduce the amount of software I keep in my domain.
> > Here's cwm, the OpenBSD window manager.
> >
> > From 6c3d991fd5b99dded91e00b6f98d79c041e4be7d Mon Sep 17 00:00:00 2001
> > From: ng0 <ng0@n0.is>
> > Date: Sun, 4 Feb 2018 11:15:19 +0000
> > Subject: [PATCH] gnu: Add cwm.
> >
> > * gnu/packages/wm.scm (cwm): New variable.

> > +    (synopsis "OpenBSD fork of calmwm")
>                            ^- about this...
> 
> > +    (description
> > +     "Cwm is a OpenBSD fork of the clean and lightweight window manager
>                           ^- ... and this I am not so sure, as
>                           the man pages state there has been a
>                           rewrite since then, so maybe just
>                           "inspired by"? It could be the same as
>                           with neomutt.

You could say that it's "derived from" calmwn.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-05 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 11:19 [bug#30344] cwm ng0
2018-02-04 11:32 ` ng0
2018-02-05 22:48   ` Leo Famulari [this message]
2018-02-12 23:45     ` ng0
2018-02-22 18:40       ` ng0
2018-02-22 19:24         ` bug#30344: cwm Leo Famulari
2018-02-22 21:11           ` [bug#30344] cwm 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180205224826.GB20907@jasmine.lan \
    --to=leo@famulari.name \
    --cc=30344@debbugs.gnu.org \
    --cc=ng0@n0.is \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.