Examples:
comm -12 file1 file2 Print only lines present in both file1 and file2.
comm -3 file1 file2 Print lines in file1 not in file2, and vice versa.
comm -3 prints lines that are unique to both file1 and file2 in separate
columns.
comm *-23* prints the lines that are in file1 and not in
On 16/02/19 23:28, 積丹尼 Dan Jacobson wrote:
>> "PB" == Pádraig Brady writes:
> PB> Fair point. I'm thinking of this extra qualification:
>
> PB> sort: text ordering performed using ‘en_IE.UTF-8’ sorting rules
> Maybe say 'LC_CTYPE=en_IE.UTF-8'
>
On 15/02/19 07:20, Eric Blake wrote:
> Except that POSIX has the nasty requirement that sh started with an
> inherited ignored SIGPIPE must silently ignore all attempts from within
> the shell to restore SIGPIPE handling to child processes of the shell:
>
> $ (trap '' PIPE; bash -c 'trap - PIPE;
On 15/02/19 14:11, Eric Blake wrote:
> On 2/15/19 3:40 PM, Assaf Gordon wrote:
>> Helo,
>>
>> On 2019-02-15 8:20 a.m., Eric Blake wrote:
>>> On 2/15/19 8:43 AM, 積丹尼 Dan Jacobson wrote:
sort: write failed: 'standard output': Broken pipe
sort: write error
>> [...]
>>> Perhaps coreutils
On 16/02/19 23:24, 積丹尼 Dan Jacobson wrote:
> (I recall I heard about 50 years ago when pipe buffers first came to
> Unix they were supposed to be invisible to the user...)
Right. A lot of folks don't understand/handle them fully though:
https://www.pixelbeat.org/programming/sigpipe_handling.html
On 17/02/19 13:00, Paul Eggert wrote:
> You make good points about nohup. Still, it's too bad that we'd have to add a
> new command for such a trivial thing.
>
> Perhaps it'd be better to overload 'env' instead, as you proposed earlier.
> After
> all, env is already being used for another
On 15/02/19 10:32, Assaf Gordon wrote:
> Hello Eric and all,
>
>
> Thanks for the quick and detailed review.
> I've amended all the issues you mentioned.
>
> On 2019-02-13 8:20 p.m., Eric Blake wrote:
>>> 15 files changed, 46 insertions(+), 141 deletions(-)
>>
>> Nice diffstat.
>
> These are
You make good points about nohup. Still, it's too bad that we'd have to add a
new command for such a trivial thing.
Perhaps it'd be better to overload 'env' instead, as you proposed earlier. After
all, env is already being used for another little environmental thing (namely
changing
Hello,
On 2019-02-17 1:12 p.m., Paul Eggert wrote:
Assaf Gordon wrote:
I don't mind either way (env feature or new program).
This should be a new feature of 'nohup' not 'env', as 'nohup' is already
about signal handling. I don't see a need for a new program.
With 'nohup' I don't think
Assaf Gordon wrote:
I don't mind either way (env feature or new program).
This should be a new feature of 'nohup' not 'env', as 'nohup' is already about
signal handling. I don't see a need for a new program.
On 2019-02-16 4:56 p.m., Bernhard Voelker wrote:
On 2/15/19 10:40 PM, Assaf Gordon wrote:
$ seq | env --default-signal PIPE sort -n | sed 5q | wc -l
src/env.c| 90 +++-
That's quite a lot of new code.
What about a new
11 matches
Mail list logo
