--- Zachary Landau <[EMAIL PROTECTED]> wrote:
> like that, I start
> naming them based on what information is on each of
> them. I then jump
> to them by name.
I guess to put things in some context, I use an editor
which makes opens a separate window for each file
currently open (as opposed to say, emacs, which by
default provides ways for you to switch between
buffers , split "buffers", etc, within one "window
manager level" window). This is mostly what I want,
since apart from anything else it means the same
manipulation commands are used for text windows as any
other window on the system. The only snag is that my
files tend to be named so as to be easy to understand
if I come back to them after a two-months working on
something else, so they've got titles like
logicalMovementModule.cc
logicalMovementModule.hh
logicalRoleModule.cc
logicalRoleModule.hh
probabilisticMovementModule.cc
probabilisticMovementModule.hh
probabilisticRoleModule.cc
probabilisticRoleModule.hh
Obviously when compressed to 3--4 characters in a tab
it's difficult to get anything meaningful, and
likewise putting them in a big menu the shared
structure means things don't "leap out" at you. (This
is a bit extreme example, but even with more diverse
names there's still the .cc, .hh repetition.) I'm
trying to think outside the box to see if there's a
good way to deal with this.
> There is another method that might extend that.
> When I used to use
> sawfish, someone sent me a script where you could
> hit a hotkey and
> then start typing the window title. It would give a
> list of all
> possible titles, and keep narrowing them down the
> more you typed, in
> an incremental search fashion. You could then
> either type the number
> that was next to the window to go to it, or wait
> until the one you
> wanted was highlighted and hit enter.
>
> It might be interesting to do something like this
> with ion. You could
> probably do it with tab completion, that that
> doesn't have the same
> visual feedback and isn't as quick.
This sounds an interesting approach. Before I start
too far down this road, a question for Tuomo: in an
ion text-input the tab-complete can show possibilities
every time the tab-key is used. Is this behaviour
hardwired to respond to the tab key at a level
inaccessible from Lua scripts, or would it be possible
to write a lua command which displays a list of
possibilties, with entries being removed as more
letters are typed and they don't match any more (ie,
without pressing tab to redisplay the current
possibilities, just incrementally typing more of the
string)?
Many thanks for any illumination,
cheers, dave tweed
> --
> Zachary P. Landau <[EMAIL PROTECTED]>
>
___________________________________________________________
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail
http://uk.messenger.yahoo.com
