[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [screen-devel] new ideas for screen

From: Edward Peschko
Subject: Re: [screen-devel] new ideas for screen
Date: Mon, 27 Oct 2008 14:36:01 -0700

well, a couple of points:

   - no, I'm looking for pattern matching, not tab completion. I don't
want to have to remember my screen name being:

         vim /path/to/very/long/file

         where I could have several of these in different screens.

- the usage (of both pattern matching and multi-buffer search) goes up
dramatically the more windows you have open. If you have 1 or 2
windows, then yes, no big deal. But - if you are managing 30 or 40,
then *yes* it is incredibly helpful because you don't have to remember
which screen you are working on all the time. You can just type in a
contextual string that represents the screen you are working on and
bam - you are there.

Say for example, you have connections to 40 different boxes open. You
don't want to have to do <C-A>" and wade through the menu - you want
to type <C-A> ?<boxname> and go directly there. Likewise, say you were
working on some code, have again 20 windows open, some of which are
tailing logs, one or more of which you know will give a certain error.

Again, you don't want to need to search through all 20 of these
buffers for an error - you want to make screen do the work for you.

All in all, IMO these features would make screen much more scalable
than it is currently, in the number of usable, concurrent sessions it
can support.


On Mon, Oct 27, 2008 at 10:32 AM, Micah Cowan <address@hidden> wrote:
> Hash: SHA1
> Edward Peschko wrote:
>> ok -
>> so with select, you can switch to buffers matching a given pattern? Is
>> that correct? I only see window name or number, not pattern..
> Yes, there's currently not support for pattern (I suppose you're really
> asking for tab-completion? Sadrul recently added tab-completion for
> commands; but we're a ways away from being able to do it for arguments
> at this point).
> I'd consider this desirable (but far from crucial) feature, but really
> the whole way that command arguments are processed needs some close
> attention/rewriting. That would be the time when something like this
> should be thought about (it would obviously require a way to keep track
> of argument "types" in order to be more general than just the select
> command).
>> If it can use a pattern, the only thing missing (that I was asking for
>> - would be to be able to search across multiple buffers with a single
>> search.
> As I previously mentioned, I don't see this as being useful enough to be
> a priority. However, I'd probably accept a well-written patch for this.
>> Is this on the requested feature list? Is there a requested feature list?
> We use the bug-tracker on Savannah (which is less than stellar, but
> works for our needs). You can submit a feature request at
> - --
> Hope that helps,
> Micah J. Cowan
> Programmer, musician, typesetting enthusiast, gamer.
> GNU Maintainer: wget, screen, teseq
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -
> iD8DBQFJBfsb7M8hyUobTrERAnAjAJ4nP9zT1QyqgqgP2ocvHRF+8+VXQQCfR7h+
> tdzGAXmfO7hM+Ye2DOMFs+4=
> =3Gh4

reply via email to

[Prev in Thread] Current Thread [Next in Thread]