aMule Forum

English => aMule Help => Topic started by: Yionel on January 26, 2010, 09:56:34 PM

Title: Problem with the size of the result of amulecmd command
Post by: Yionel on January 26, 2010, 09:56:34 PM
Hi !

On my 17', if I want

Code: [Select]
aMulecmd$ statistics
the result is larger than my screen, so I can't see the first lines :(, and I can't use shell command like statistics | less or other thing.

Have you got an idea ?

Thanks
Title: Re: Problem with the size of the result of amulecmd command
Post by: wuischke on January 27, 2010, 09:02:47 AM
Hi Yionel,

You could try scrolling with Shift+Page Up/Down to see the beginning of the output.
Title: Re: Problem with the size of the result of amulecmd command
Post by: Yionel on January 27, 2010, 02:18:15 PM
Hi Yionel,

You could try scrolling with Shift+Page Up/Down to see the beginning of the output.
No, it doesn't work  :'(
Title: Re: Problem with the size of the result of amulecmd command
Post by: GonoszTopi on January 27, 2010, 04:08:46 PM
On my 17', if I want

Code: [Select]
aMulecmd$ statistics
the result is larger than my screen, so I can't see the first lines :(, and I can't use shell command like statistics | less or other thing.

Have you got an idea ?
That's currently impossible. For that to work amulecmd should check whether its output goes to a terminal, if yes, check terminal size, etc. -- or allow command output piping to an external program. I don't think either is nearby the top of the TODO list of any developer...

However, you can work it around by capturing the output in the shell. The easiest way is
Code: [Select]
$ amulecmd -c "statistics" | more
or something similar.
Title: Re: Problem with the size of the result of amulecmd command
Post by: Yionel on January 27, 2010, 05:17:07 PM
On my 17', if I want

Code: [Select]
aMulecmd$ statistics
the result is larger than my screen, so I can't see the first lines :(, and I can't use shell command like statistics | less or other thing.

Have you got an idea ?
That's currently impossible. For that to work amulecmd should check whether its output goes to a terminal, if yes, check terminal size, etc. -- or allow command output piping to an external program. I don't think either is nearby the top of the TODO list of any developer...

However, you can work it around by capturing the output in the shell. The easiest way is
Code: [Select]
$ amulecmd -c "statistics" | more
or something similar.

Yes cool it works  \o/

Thanks!