unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Vegard Vesterheim <vegard.vesterheim@uninett.no>
To: Jude DaShiell <jdashiel@panix.com>
Cc: Tassilo Horn <tsdh@gnu.org>,
	"Jorge P. de Morais Neto" <jorge+list@disroot.org>,
	help-gnu-emacs@gnu.org
Subject: Re: Poll: best hackable window manager or DE for Emacs-loving freedom activists
Date: Fri, 05 Nov 2021 09:33:42 +0100	[thread overview]
Message-ID: <87h7crc87t.fsf@uninett.no> (raw)
In-Reply-To: <alpine.NEB.2.23.451.2111050403320.4376@panix1.panix.com> (Jude DaShiell's message of "Fri, 5 Nov 2021 04:04:59 -0400")

On Fri, 5 Nov 2021 04:04:59 -0400 Jude DaShiell <jdashiel@panix.com> wrote:

> stump-wm since it's written in lisp might be a possibility.

I am using the sawfish window manager:
https://en.wikipedia.org/wiki/Sawfish_(window_manager)

"Sawfish uses a Lisp-like scripting language, rep, for all of its code
and configuration, making it particularly easy to customize, or program
many kinds of behavior, responding to window creation, deletion, or any
other changes. There is a GUI configuration utility for users who do not
wish to edit configuration files directly."

There are also some emacs integrations, controlling sawfish from within
emacs and vice versa.

-- 
Vennlig hilsen/Best regards
Vegard Vesterheim
Senior Software engineer
+47 48 11 98 98
vegard.vesterheim@uninett.no



  reply	other threads:[~2021-11-05  8:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 23:58 Poll: best hackable window manager or DE for Emacs-loving freedom activists Jorge P. de Morais Neto
2021-11-05  0:08 ` Po Lu
2021-11-05  7:42   ` tomas
2021-11-05  8:11     ` Po Lu
2021-11-06  2:04       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-05  8:12     ` Po Lu
2021-11-05  8:18       ` tomas
2021-11-06  2:04         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06  2:13           ` Jude DaShiell
2021-11-06  7:50             ` tomas
2021-11-06 15:31               ` Samuel Banya
2021-11-05 13:48   ` Samuel Banya
2021-11-06  2:00   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06  2:16     ` Po Lu
2021-11-11 11:41   ` Jorge P. de Morais Neto
2021-11-05  7:40 ` tomas
2021-11-06  2:06   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-05  7:55 ` Tassilo Horn
2021-11-05  8:04   ` Jude DaShiell
2021-11-05  8:33     ` Vegard Vesterheim [this message]
2021-11-05 12:51 ` Eric S Fraga
2021-11-06  2:08   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-05 13:45 ` Samuel Banya
2021-11-06  2:09   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-05 13:47 ` Samuel Banya
2021-11-05 13:53 ` Samuel Banya
2021-11-06  2:13   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06  2:34     ` Samuel Banya
2021-11-06  2:52       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06  1:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06  6:27 ` Teemu Likonen
2021-11-06 13:57   ` Jude DaShiell
2021-11-07 19:51 ` Jean Louis
2021-11-07 20:28   ` Emanuel Berg via Users list for the GNU Emacs text editor

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87h7crc87t.fsf@uninett.no \
    --to=vegard.vesterheim@uninett.no \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jdashiel@panix.com \
    --cc=jorge+list@disroot.org \
    --cc=tsdh@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).