From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Bounties
Date: Thu, 16 Jan 2020 23:03:20 +0000 [thread overview]
Message-ID: <2454b8e7-4d27-4a67-a250-cf6e7dc9e662@www.fastmail.com> (raw)
In-Reply-To: <4d66318f-2d4d-4121-991d-c15383c23f3d@www.fastmail.com>
On Thu, Jan 16, 2020, at 7:35 PM, Calvin Morrison wrote:
>
> A second follow up. I think that ACME as the WM is a very laudable and
> realistic goal. It implements sub windows (but not /dev/draw for each
> window) and handles columns rows, minimization, and you can implement
> programs (like wiki) to work with ACME with some good benefits.
I found Acme's dynamic window placement gets in the way if I'm doing anything other than editing C code. It's not the worst possible issue, but it did get in the way rather a lot when I used Acme to organize my notes and projects like a sort of personal wiki. Increasing the number of columns helps a lot, but 3 columns is the minimum for comfort and my weakening eyesight requires ever-larger fonts, so it's now untenable.
For perspective, I should probably say I also found dwm's dynamic window placement a bit confusing too, but I didn't give it much of a chance.
next prev parent reply other threads:[~2020-01-16 23:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 7:06 Bounties Jens Staal
2020-01-16 18:05 ` [9front] Bounties Ethan Gardener
2020-01-17 0:47 ` sl
2020-01-16 18:51 ` Calvin Morrison
2020-01-16 19:35 ` Calvin Morrison
2020-01-16 23:03 ` Ethan Gardener [this message]
[not found] <FEFDF1EDDEF96554EC8D099B3EFFBCE2@ewsd.inri.net>
2020-01-17 0:57 ` umbraticus
[not found] <134490038A9377D966659F986F257F34@ewsd.inri.net>
2020-01-17 14:43 ` Ethan Gardener
2020-01-17 16:05 ` kvik
2020-01-17 21:55 ` Silas McCroskey
2020-01-21 8:37 ` Ethan Gardener
2020-01-22 17:04 ` Ori Bernstein
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=2454b8e7-4d27-4a67-a250-cf6e7dc9e662@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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 NNTP newsgroup(s).