From: Ingo Krabbe <ikrabbe.ask@gmail.com>
To: <9fans@9fans.net>
Subject: Re: [9fans] sam resizing
Date: Tue, 22 Oct 2013 08:30:03 +0200 [thread overview]
Message-ID: <c53d7912a3c2e7bd1aa1d804510f293d@krabbe.dyndns.org> (raw)
In-Reply-To: <befefe5d1d77650a94d37074e2c8fc6b@brasstown.quanstro.net>
On Tue Oct 22 08:19:47 CES 2013, quanstro@quanstro.net wrote:
> so i'm wondering. acme does a good job of auto layout.
> the thing acme lacks is a edit buffer (~~sam~~). so maybe
> it would be fruitful to add edit buffer(s) to acme?
>
> - erik
I don't think its good to compare acme and sam as the approaches are quite different and both tools are useful.
Actually I use acme sometimes as a file browser or remote command windowBut when I work on source code I don't like, for example, that my mouse cursor in acme needs to float over the window I type in.
cheers,
ingo
next prev parent reply other threads:[~2013-10-22 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 20:18 Mark van Atten
2013-10-22 6:13 ` Ingo Krabbe
2013-10-22 6:19 ` erik quanstrom
2013-10-22 6:30 ` Ingo Krabbe [this message]
2013-10-22 7:13 ` Mark van Atten
2013-10-23 4:00 ` BurnZeZ
2013-10-23 4:10 ` Matthew Veety
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=c53d7912a3c2e7bd1aa1d804510f293d@krabbe.dyndns.org \
--to=ikrabbe.ask@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).