> Nope, the manpage includes this (and looking at git history, has
> since its inception):
>
> EXAMPLES
> st -e scroll /bin/sh
>
> You must have misread it.
You're right, it does say that. But I didn't so much misread it as read the top
of it, were it has:
SYNOPSIS
scroll [-Mh] [-m
Quoth Lee Phillips:
> > What I did to make it work is to run "./scroll" in an already-existing st
> > window, as you would with GNU screen or tmux.
>
> This works! Thank you very much.
>
> I was following the instructions in the man page, which say to do `scroll st`.
Nope, the manpage includes t
> What I did to make it work is to run "./scroll" in an already-existing st
> window, as you would with GNU screen or tmux.
This works! Thank you very much.
I was following the instructions in the man page, which say to do `scroll st`.
On 1/6/21 1:22 PM, Lee Phillips wrote:
Sorry, I think I already had a scrollback patch applied to st, so I could
already scroll back (and I forgot that that patch was in there). So my message
was misleading. However, it has no effect on what I'm after: restoring the
parts of lines cut off hori
> No effect at all? It is at least supposed to allow you to scroll back. I
> suspect something is wrong with the way you're trying to use scroll.
Sorry, I think I already had a scrollback patch applied to st, so I could
already scroll back (and I forgot that that patch was in there). So my mes
On Wed, Jan 6, 2021, at 10:50, Lee Phillips wrote:
> I compiled the current version of this scroll program and used it with
> both st and xterm. It had no effect.
No effect at all? It is at least supposed to allow you to scroll back. I
suspect something is wrong with the way you're trying to u
On 1/6/21 9:48 AM, Laslo Hunhold wrote:> thanks for your mail and
reaching out! This is a philosophical
question, and I agree with you in fixing this in st, others don't (with
good reasons on both sides). Especially in the context of dwm I'm often
annoyed when the text is cut off. To keep things
I compiled the current version of this scroll program and used it with both st
and xterm. It had no effect. The programs behaved as before, with lines getting
erased after window resizing.
I also prefer to use dwm to manage my terminal windows rather than a
multiplexer, so I am keenly intereste
By the way: some other terminal programs do not have this problem. For example,
xfce4-terminal retains the information in its window under dwm resizing.
However, it uses three times the memory of either st or xterm.
On Wed, Jan 6, 2021, at 09:57, Sergey Matveev wrote:
> > clean)
> > redo-always
>
> No need to add redo-always to the targets that only can be "called" by
> the human/user. User uses "redo" command, that forces specified targets
> to be rebuild. So "redo clean/dst/install/whatever"
*** Greg Reagle [2021-01-06 09:50]:
>I have made one improvement already, adding this to the end of the case
>statement:
> echo "no rule to build '$1'" >&2
By using separate .do files, that won't be needed, because redo itself
will tell you about unknown target. You single .do just
*** Greg Reagle [2021-01-06 08:52]:
>I know that there are advantages to having the .do files separated, so there
>is no need to mention that.
But single .do is huge disadvantage. Can not skip mention of that :-)
Each changing of that single .do will expire all targets. Each different
invocation
On Tue, 05 Jan 2021 20:16:57 +0100
LuxGiammi wrote:
Dear Luxgiammi,
> It's my first message in this mailing list.
> I've been using st for more than one year and I've always had the
> intention to ask this. I know that there must be a way to solve the
> problem (in fact, I started to study X p
On Wed, Jan 6, 2021, at 08:52, Greg Reagle wrote:
> Here is my attempt at a redo file for st, instead of a Makefile. I
I have made one improvement already, adding this to the end of the case
statement:
*)
echo "no rule to build '$1'" >&2
exit 1
Here is my attempt at a redo file for st, instead of a Makefile. I expect it
is a complete replacement. If it interests any of you, please take a look and
give me constructive criticism. Does it have any flaws? Could it be improved?
I know that there are advantages to having the .do files s
15 matches
Mail list logo