From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Date: Thu, 3 Jun 2004 09:48:28 +0200 Message-ID: From: To: <9fans@cse.psu.edu> Subject: [9fans] acme: some thoughts about design Topicbox-Message-UUID: 9129d486-eacd-11e9-9e20-41e7f4b1d025 Thanks for reaction! Here is some explanations to what i meant... /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. why? the list will always take you to the correct place, won't it? = otherwise, OK, one could have such window for each column separately... > but the biggest problem is that i want to look at a window and > know which file i'm editing.=20 cursor position | highlighting in "listing/tag window" not sufficient? =20 > i have a lot of acme windows most of so do i ;-) > 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? use last "ordinary window" ... i think > 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? best regards, ++pac. =20