From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme hack
Date: Thu, 14 Mar 2013 15:55:23 +0100 [thread overview]
Message-ID: <2378627.cQ21ZJRjWA@coil> (raw)
In-Reply-To: <CADErNDuo1h+1b-3t-aRLQKAcWc-tN3EiGJHH7UcTx87WzuZvWw@mail.gmail.com>
On Thursday 14 of March 2013 15:38:08 yy wrote:
>
> Not that I have any problem with this but, isn't it easier to just Del the
> window so that a new one is created when you need it?
you are right. i use Edit ,d to preserve general window layout.
i'm not happy with Acme's placement of +Errors window in my default workflow.
in two columns, i keep one directory (project root) window, one +Errors window
beneath it (syntax errors, upload progress †, scratchpad) and some 1...6
source code file windows spread 'round.
btw., the patch may not apply cleanly since my p9p fork has `Look' disabled
via if(0) {...}
--
dexen deVries
[[[↓][→]]]
† i'm a LAMP webdeveloper by day.
next prev parent reply other threads:[~2013-03-14 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 13:44 dexen deVries
2013-03-14 14:38 ` yy
2013-03-14 14:55 ` dexen deVries [this message]
2013-03-21 11:03 ` [9fans] Acme hack - a week later dexen deVries
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=2378627.cQ21ZJRjWA@coil \
--to=dexen.devries@gmail.com \
--cc=9fans@9fans.net \
/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).