9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme design
Date: Thu,  3 Jun 2004 10:59:26 -0400	[thread overview]
Message-ID: <e9175ac43ba8d9b0e1ebba54fedad96b@9srv.net> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D2012B8@XMAIL.asuch.cas.cz>

// the list will always take you to the correct 
// place [current window?], won't it? 

i just don't see how. i mean at a functional level - like, what's the thing
*do*? highlight the file my cursor's over? what's the behavior?

// cursor position | highlighting in "listing/tag window" not sufficient?

nope. i want to know by looking at the window i'm typing in, or as close
to it as possible. not some (mentally) unrelated window in another Col.
it's not so much an issue while i'm typing, but when i'm switching from
one win to another, how do i know where to move my mouse?

// use last "ordinary window" [for execution] ... i think 

i don't think that'll work. if i'm editing a window at the top of a Col and
the "tag" window is at the botom of the Col, or two Cols over, how do i
get to it without mousing over another normal window? or do i have to
make some manual change before i can edit that window?

// isn't a tag "line" a special frame that [currently] behaves 
// differently from "normal" one?? 

yes, which is exactly why i said it was a reasonable thing to question. i'd
be interested in ways to structure things that don't have this modality in
them. but i certainly can't come up with one.

// my "tag frame" i think could behave just normal 

except for auto-highlighting or some other indication method, and
automatically updating itself for the list of open files (hopefully!). and how
would i refer to it? how would i Put it?

// as much as you wish, of course, as normal ones... 

this is space-ineffecient. i'd always be resizing it. the current window
tags are (intentionally or no) optimized for the small data they contain
(perhaps too much, hence the splinter-thread about scrolling).



  reply	other threads:[~2004-06-03 14:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 11:21 cej
2004-06-03 14:59 ` a [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  8:22 cej
2004-06-07 13:43 ` Russ Cox
2004-06-07 13:47 ` boyd, rounin
2004-06-04 11:22 cej
2004-06-04  9:12 cej
2004-06-03  8:37 cej
2004-06-03  8:07 cej
2004-06-03  8:52 ` plan9
2004-06-03 13:53 ` rog
2004-06-03 13:55 ` rog
2004-06-05  6:09   ` YAMANASHI Takeshi
2004-06-05 10:07     ` Charles Forsyth
2004-06-05 13:48       ` YAMANASHI Takeshi
2004-06-05 15:50         ` Rob Pike
2004-06-06  2:23           ` YAMANASHI Takeshi
2004-06-06  3:25             ` Rob Pike
2004-06-06  7:24               ` YAMANASHI Takeshi
2004-06-06  8:54               ` vdharani
2004-06-03  7:58 cej
2004-06-03  8:54 ` Kenji Okamoto
2004-06-02 12:57 cej
2004-06-02 13:20 ` a
2004-06-02 15:18   ` plan9
2004-06-03 13:48   ` rog
2004-06-03 14:17     ` lucio
2004-06-03 14:34       ` rog
2004-06-03 15:38         ` kiwane
2004-06-03 15:45           ` rog
2004-06-04  9:19     ` Bengt Kleberg
2004-06-04 10:29       ` Axel Belinfante
2004-06-03  0:54 ` Kenji Okamoto
2004-06-03  0:56   ` Kenji Okamoto
2004-06-03  8:35 ` WLad
2004-06-03  8:40 ` vdharani

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=e9175ac43ba8d9b0e1ebba54fedad96b@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).