From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme: some thoughts about design
Date: Wed, 2 Jun 2004 08:42:10 -0400 [thread overview]
Message-ID: <dffaf0fbae9627e844bc9dcf0f8be7c2@9srv.net> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D2012AD@XMAIL.asuch.cas.cz>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 919 bytes --]
//As I mentioned earlier, wouldn't a frame with [sorted] listing of
//window tags be a cleaner solution for navigation?
i don't think so, no. how would it work? say i have some window
containing this list. how's it sorted? lists are one-dimensional; my
acme window arangement is not. while there's a trivial way to do
the transformation (go down col 1, then col 2...), that becomes
quite awkward, mentally.
but the biggest problem is that i want to look at a window and
know which file i'm editing. i have a lot of acme windows most of
the time, and counting down a list - even given some kind of
markers denoting col boundaries - seems like it would take
forever.
and how would commands work? how do you tell Put which
window to Put if they're all in a list?
actually, this all sounds so bad to me i've concluded i don't
really understand what you're suggesting. ââcare to sort me out?
ï
next prev parent reply other threads:[~2004-06-02 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 11:22 cej
2004-06-02 12:42 ` a [this message]
2004-06-02 12:55 ` a
-- strict thread matches above, loose matches on Subject: below --
2004-06-07 7:18 cej
2004-06-04 12:52 cej
2004-06-04 18:21 ` boyd, rounin
2004-06-03 7:48 cej
2004-06-03 9:10 ` boyd, rounin
2004-06-03 9:51 ` Matthias Teege
2004-06-03 10:14 ` boyd, rounin
2004-06-03 11:22 ` Matthias Teege
2004-06-03 11:34 ` boyd, rounin
2004-05-31 9:19 a
2004-05-31 10:17 ` Bruce Ellis
2004-05-29 16:51 Tiit Lankots
2004-05-29 16:58 ` Tristan Seligmann
2004-05-29 22:48 ` boyd, rounin
2004-05-29 23:56 ` Tristan Seligmann
2004-05-29 23:59 ` boyd, rounin
2004-05-30 18:09 ` Bruce Ellis
2004-05-28 9:01 cej
2004-05-29 9:28 ` Matthias Teege
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=dffaf0fbae9627e844bc9dcf0f8be7c2@9srv.net \
--to=a@9srv.net \
--cc=9fans@cse.psu.edu \
/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).