screen-devel
[Top][All Lists]
Advanced

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

Re: [screen-devel] need help with resize -p and -l


From: Chris Jones
Subject: Re: [screen-devel] need help with resize -p and -l
Date: Sun, 13 Dec 2009 23:51:44 -0500
User-agent: Mutt/1.5.18 (2008-05-17)

On Sun, Dec 13, 2009 at 02:43:33AM EST, Sadrul Habib Chowdhury wrote:
> * Chris Jones had this to say on [12 Dec 2009, 19:22:51 -0500]:
> [snip]
> > 
> > There seem to be other 'hidden' resize options:
> > 
> > ^A resize +
> 
> What does it do?
> 
> > ^A resize _
> 
> This '_' is shorthand for 'max'. There's also '0' for 'min'.
> 
> > And how about:
> > 
> > ^A resize \
> 
> I don't think there's any special meaning for this. Any unrecognized
> parameter is parsed as a number (0), and the selected region gets resized
> to 0 (which actually needs to be fixed).

I suggest you try the following scenario:

^A |
^A S
^A l
^A S
^A resize \
^A j
^A resize \

The right half or the screen now has 2 two-line high regions, and below
that a large open area that does not belong to any region. You cannot
access it via a '^A <Tab>' or ^A j' for instance.

> > I haven't tried other possibilities but I was wondering is a way to
> > make two vertical regions equal, i.e. the converse of:

> > ^A resize =
> 
> 'resize =' should (and does) resize vertical splits to equal widths for
> me. Does it not work for you?

OK. The syntax/semantics are:

^A resize -h =
^A resize -v =

As to:

^A resize 

it is short for, equivalent to:

^A resize -v =

> > As an aside, it would be nice if the delimiter between two vertical
> > regions was the same width as the the one between two horizontal
> > regions.
> > 
> > Instead, I have a rather wide band that is almost one character cell
> > wide as compared with the couple of pixels used to delimit two
> > horizontal regions.
> 
> The separator of two regions is always one character, so for vertical
> splits, it's a single-cell character wide, and for horizontal splits,
> it's one character high (which is really unlikely to be only a couple of
> pixels on any system). 

Sorry, I should have written 'character' instead of 'character cell'.

The cell may be eight pixels wide and twelve pixels high, but the
character displayed within could be just one or two pixels wide or high.
The dash '-', for instance, or the bar, '|' appear to be just one pixel
wide/high with the font I'm using.

> I am not really sure why you should see it any
> different.

I see now that I have this in my .screenrc:

| caption always "%{+d wk} "

Now I remember that I did that at one point because I found those ultra
wide horizontal bands distracting.

So what I see is something like:

|   ┌────────▄────────┐
|   │        █        │
|   │        █        │
|   │        █        │
|   │        █        │
|   ├────────█────────┤
|   │        █        │
|   │        █        │
|   │        █        │
|   │        █        │
|   └────────▀────────┘ 

instead of the standard:

|   ┌────────▄────────┐
|   │        █        │
|   │        █        │
|   │        █        │
|   │        █        │
|   ▐█████████████████▌
|   │        █        │
|   │        █        │
|   │        █        │
|   │        █        │
|   ▐█████████████████▌ 


What I would like to see is:

|   ┌────────┬────────┐
|   │        │        │
|   │        │        │
|   │        │        │
|   │        │        │
|   ├────────┼────────┤
|   │        │        │
|   │        │        │
|   │        │        │
|   │        │        │
|   └────────┴────────┘ 

Both dvtm and tmux provide region delimiters that are one or two pixels
high/wide, so I would imagine screen could do it as well.

Not only are those wide bands pretty ugly, but since the cells in
terminals are usually higher than they are wide, the 'width' of the
horizontal band is different from the 'width' of the vertical band,
which to me at least doesn't right.

Anyway, if you feel this is not worth your attention, could you direct
me to the source file that handles this so I can customize it to my own
liking in the event I am unable to find a workaround?

Thank you for your comments,

CJ





reply via email to

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