That all works in screen, at least to some extent. Years ago I discovered I
could write a script and connect its stdin to the stdout of whatever was in
the screen, and vice versa. I think what led me to the discovery was
someone's description of how to do zmodem over SSH to a network switch (it
When you need CTRL-\, you *really* need it...
On Sun, May 19, 2019, 04:35 Rob Landley Would anyone aware of freebsd's CTRL-T want to weigh in on this thread?
>
> https://twitter.com/freebsdfrau/status/1128017757734297600
>
> I can remap ctrl-\ to ctrl-t and have SIGQUIT produce statistics,
For what it's worth,
http://www.gnu.org/software/mailman/mailman-admin/node25.html
It's been several years since I had to deal with this kind of thing,
but the behavior we're seeing is similar to a case I had to
troubleshoot in the past where the bounce-processing was configured to
be too
I've seen that when javascript is blocked, or partially blocked. I
think I've seen it once when I was behind a non-transparent
non-CONNECT proxy, but that was a while ago and I can't verify.
It's not new behavior. I've been seeing this for at least two years,
unless I allow *all* javascript on
It's nice where the "what do I put here?" and the "that particular
argument isn't supported in this version" logic cases can be folded
together. Just list valid choices for that argument, then terminates
unsuccessfully (non-zero error code, but without the normal "I didn't
understand you" error
I've seen a fair number of scripts that use printf's ability to
interpret hex and octal arguments. This is often combined with
printf's ability to format outputs into decimal, octal, or hex, to
make a convenient base-shifter. For this discussion, it's the argument
conversion, not the formatting
;r...@landley.net> wrote:
> On 02/05/2018 04:01 PM, Robert Thompson wrote:
>> It seems that the single-equals is POSIX, while the double-equals is a
>> bash extension that at one point bash preferred and extended the match
>> behavior of.
>>
>> But,
It seems that the single-equals is POSIX, while the double-equals is a
bash extension that at one point bash preferred and extended the match
behavior of.
But, the bash manpage now documents double-equals (when in the
context of the builtin test or its '[' alias) as equivalent to
single-equals.
, Rob Landley <r...@landley.net> wrote:
> On 09/04/2017 08:22 PM, Robert Thompson wrote:
> > From the toybox point of view, wouldn't this introduce direct link
> > dependency on ssl/tls libraries?
>
> There's already an optional dependency to accelerate hash calculations
>From the toybox point of view, wouldn't this introduce direct link
dependency on ssl/tls libraries?
If that's acceptable, the ktls stuff looks like a simple addition (on top
of base in-toybox tls) with potential performance improvements, once the
code settles down.
On Sun, Sep 3, 2017 at 11:12
It's pretty heavily used in combination with noerror. I can personally
attest to its usefulness when working with both damaged optical media and
spinning rust (with the correct blocksize in each case).
Each block read either contains blocksize data bytes or blocksize null
bytes, so that the
Not sure this is relevant, but I just noticed that on my Debian system my
output is a little different from the mentioned outputs. Mainly, it's not
quoting or escaping anything, except for the tag_ENC values in -o udev
...
Could be a bug, could be version-skewed behavior, but it's a real world
Once upon a time, the serial issue would have kept me using screen. But,
these days I use picoterm as the minimal pty--serial connector, and that
works as well with tmux as screen's own serial handling worked with screen.
It also works well without any multiplexer, just letting your (virtual)
.
On Dec 24, 2014 9:47 PM, Rob Landley r...@landley.net wrote:
On 12/12/14 17:19, Robert Thompson wrote:
I ran across a variance between toybox factor and coreutils factor.
Coreutils factor will accept numbers on stdin separated by any whitespace
(including newlines and tabs) between
...@google.com wrote:
On Wed, Dec 24, 2014 at 7:47 PM, Rob Landley r...@landley.net wrote:
On 12/12/14 17:19, Robert Thompson wrote:
I ran across a variance between toybox factor and coreutils factor.
Coreutils factor will accept numbers on stdin separated by any
whitespace
(including
I ran across a variance between toybox factor and coreutils factor.
Coreutils factor will accept numbers on stdin separated by any whitespace
(including newlines and tabs) between integers, but toybox factor was only
accepting one integer per line.
I added a test for this, and hacked factor to
The most common issue that would impact UTF-8 is programs that use strchr()
and pointer math on strings that originated in the passwd file.
There are also issues about various services that have to implement
different rules than the usual unix world about safe/valid characters. Many
of these tend
I'm having to fight gmail-web's reformatting more than normal today...
On Sat, Apr 12, 2014 at 9:00 PM, Rob Landley r...@landley.net wrote:
On 04/08/14 23:46, Robert Thompson wrote:
In the context of terminal control, 8-bit encoding is a bit
misleading, especially if you're googling
I personally would also find a pure simple single-purpose unfold useful.
If you feel like going just a touch beyond a simple unfold, you might
want to look at the fmt utility. I've seen several scripts in the wild that
used fold and/or fmt. A couple of them used fold to do the folding and fmt
Not that it's really relevant to most linux environments, but the OSX
version (with a BSD manpage) appears to not execute any commandline that
would have no added arguments. A quick test suggests this is true for both
normal and null-separated modes.
Specifically, echo | xargs echo foo; echo
20 matches
Mail list logo
