nohup feature request / Please fwd to Jim Meyering

2007-06-07 Thread Jack van de Vossenberg
Dear Jim I use nohup (ubuntu linux), and I have a feature request. Often I run more than one program at a time under nohup, and some of these programs run for at least a couple of hours. Every now and then nohup writes the output to nohup.out, which I find very useful. My request is: could

Re: nohup feature request / Please fwd to Jim Meyering

2007-06-07 Thread Andreas Schwab
Jack van de Vossenberg [EMAIL PROTECTED] writes: Dear Jim I use nohup (ubuntu linux), and I have a feature request. Often I run more than one program at a time under nohup, and some of these programs run for at least a couple of hours. Every now and then nohup writes the output to

Simplifying command line parsing with Genparse

2007-06-07 Thread Michael Geng
Hi, would it be an option to use Genparse (http://genparse.sourceforge.net/) for command line parsing in the GNU Coreutils? I'm one of the developers of Genparse and I recently used some of the well known Coreutils as an exercise for testing Genparse (see

Re: Simplifying command line parsing with Genparse

2007-06-07 Thread Jim Meyering
[EMAIL PROTECTED] (Michael Geng) wrote: would it be an option to use Genparse (http://genparse.sourceforge.net/) for command line parsing in the GNU Coreutils? I'm one of the developers of Genparse and I recently used some of the well known Coreutils as an exercise for testing Genparse (see

Re: Simplifying command line parsing with Genparse

2007-06-07 Thread Andreas Schwab
Jim Meyering [EMAIL PROTECTED] writes: Genparse looks promising. I like the examples. But there are almost 100 programs in the coreutils. If genparse can really handle all of those use cases without causing any significant degradation in the tools, then it will be hard to object. There's

Re: Simplifying command line parsing with Genparse

2007-06-07 Thread Jim Meyering
Andreas Schwab [EMAIL PROTECTED] wrote: Jim Meyering [EMAIL PROTECTED] writes: Genparse looks promising. I like the examples. But there are almost 100 programs in the coreutils. If genparse can really handle all of those use cases without causing any significant degradation in the tools,

sort --debug

2007-06-07 Thread Dan Jacobson
Perhaps add a --debug option, so users don't write mail like the below :-) Kindly add an example to the sort info pages of how to sort zip utils xdm x11 cron admin dpkg admin lilo admin menu admin on the second field. No, -k 2,2 2,2b or whatever doesn't work. Better yet, why don't you also add

Re: Simplifying command line parsing with Genparse

2007-06-07 Thread Michael Geng
On Thu, Jun 07, 2007 at 02:44:38PM +0200, Jim Meyering wrote: [EMAIL PROTECTED] (Michael Geng) wrote: would it be an option to use Genparse (http://genparse.sourceforge.net/) for command line parsing in the GNU Coreutils? I'm one of the developers of Genparse and I recently used some of

Re: nohup feature request / Please fwd to Jim Meyering

2007-06-07 Thread Pádraig Brady
Jack van de Vossenberg wrote: Dear Jim I use nohup (ubuntu linux), and I have a feature request. Often I run more than one program at a time under nohup, and some of these programs run for at least a couple of hours. Every now and then nohup writes the output to nohup.out, which I find

Re: nohup feature request / Please fwd to Jim Meyering

2007-06-07 Thread Phillip Susi
Pádraig Brady wrote: My request is: could the output be preceded by 1) the name/PID of the process that produces the output. That's not possible unfortunately, as nohup just sets things up, and replaces itself with the command. It might suffice to have separate files for each command, which

SEQ BUG

2007-06-07 Thread Patrick Amstutz
Hi, I've the following behavior with the seq function on: Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version 4.1.220061115 (prerelease) (SUSE Linux)) #1 $ echo `seq 0.0 0.1 0.8` 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 $ echo `seq 0.0 0.1 0.9` 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 Best

Re: SEQ BUG

2007-06-07 Thread Micah Cowan
Patrick Amstutz wrote: Hi, I've the following behavior with the seq function on: Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version 4.1.220061115 (prerelease) (SUSE Linux)) #1 $ echo `seq 0.0 0.1 0.8` 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 $ echo `seq 0.0 0.1 0.9` 0 0.1

Re: SEQ BUG

2007-06-07 Thread John Cowan
Patrick Amstutz scripsit: $ echo `seq 0.0 0.1 0.8` 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 $ echo `seq 0.0 0.1 0.9` 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 Welcome to floating-point roundoff errors. The decimal constant 0.1 cannot be exactly represented as a floating-point number on modern hardware, so

Re: SEQ BUG

2007-06-07 Thread John Cowan
Micah Cowan scripsit: You need to use something more like: $ echo `seq 0.0 0.1 0.91` 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 Or better yet, use `seq 0 9` and prepend the 0. part yourself. (The Cowan twins strike again!) -- A witness cannot give evidence of his John Cowan age unless

Re: SEQ BUG

2007-06-07 Thread Pádraig Brady
Micah Cowan wrote: Patrick Amstutz wrote: Hi, I've the following behavior with the seq function on: Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version 4.1.220061115 (prerelease) (SUSE Linux)) #1 $ echo `seq 0.0 0.1 0.8` 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 $ echo `seq 0.0

Re: SEQ BUG

2007-06-07 Thread Micah Cowan
Pádraig Brady wrote: Another thing I just noticed. I would expect the precision of all output in the following command to be to 2 decimal places not 1: $ seq 0.00 0.01 0.90 | grep \.[0-9]$ 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 I wouldn't. The documentation is fairly clear that the

Re: nohup feature request / Please fwd to Jim Meyering

2007-06-07 Thread Bob Proulx
Phillip Susi wrote: Pádraig Brady wrote: That's not possible unfortunately, as nohup just sets things up, and replaces itself with the command. Of course it is possible; nohup knows its pid as well as the command it is asked to run. When it opens the output file it just needs to use

Re: SEQ BUG

2007-06-07 Thread Jim Meyering
Pádraig Brady [EMAIL PROTECTED] wrote: ... Another thing I just noticed. I would expect the precision of all output in the following command to be to 2 decimal places not 1: $ seq 0.00 0.01 0.90 | grep \.[0-9]$ 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 Well, at least with the very latest

Re: Simplifying command line parsing with Genparse

2007-06-07 Thread Bob Proulx
Michael Geng wrote: I would expect Genparse to generate faster code than argp because it does part of the work at compile time while argp does everything at run time since it's a library function. Is the performance of parsing program arguments really a concern? I would think that the

Re: SEQ BUG

2007-06-07 Thread John Cowan
Pádraig Brady scripsit: The issue and work around are documented in the info page, but why don't we do the suggestion automatically in code (using the precision that is automatically worked out already)? That implies using either a fixed-point or a decimal-based floating-point package. GNU