Difference between revisions of "User talk:Neitsab"

From ArchWiki
Jump to: navigation, search
(Created page with "You don't need to add --enable-rpc to uGet for it to work with Aria2, while it does require it to function the plugin settings have it set by default so don't actually have to...")
 
(Reply about aria2)
Line 1: Line 1:
 +
[[Aria2]]
 +
----
 
You don't need to add --enable-rpc to uGet for it to work with Aria2, while it does require it to function the plugin settings have it set by default so don't actually have to change anything except for just enabling the plugin. [[User:MichaelTunnell|MichaelTunnell]] ([[User talk:MichaelTunnell|talk]]) 08:03, 11 January 2014 (UTC)
 
You don't need to add --enable-rpc to uGet for it to work with Aria2, while it does require it to function the plugin settings have it set by default so don't actually have to change anything except for just enabling the plugin. [[User:MichaelTunnell|MichaelTunnell]] ([[User talk:MichaelTunnell|talk]]) 08:03, 11 January 2014 (UTC)
 +
:You're right, and it wasn't my intention to say something different. Re-reading the introductory note of "[[Aria2#Frontends|Frontends]]" section, it appears I misunderstood/misread it. To me it was just laying off a distinction between "frontends that needs --rpc-enable option" (wherever it may be set) and those who don't. And as uGet needs this option set in its preferences...
 +
:I'm considering rewriting this section as follows:
 +
===Frontends===
 +
{warning about configuration, specifying that uGet stores its own parameters for aria2}
 +
==== Web UI ====
 +
{note: these front-ends need aria2 to be started with --enable-rpc option (in terminal or as a daemon)}
 +
...
 +
==== Other frontends ====
 +
These frontends ''don't'' need aria2 to be separately started with --enable-rpc.
 +
 +
...
 +
 +
uGet
 +
 +
..."
 +
 +
:What do you think?
 +
 +
-- [[User:Neitsab|Neitsab]] ([[User talk:Neitsab|talk]]) 13:00, 12 January 2014 (UTC)

Revision as of 13:00, 12 January 2014

Aria2


You don't need to add --enable-rpc to uGet for it to work with Aria2, while it does require it to function the plugin settings have it set by default so don't actually have to change anything except for just enabling the plugin. MichaelTunnell (talk) 08:03, 11 January 2014 (UTC)

You're right, and it wasn't my intention to say something different. Re-reading the introductory note of "Frontends" section, it appears I misunderstood/misread it. To me it was just laying off a distinction between "frontends that needs --rpc-enable option" (wherever it may be set) and those who don't. And as uGet needs this option set in its preferences...
I'm considering rewriting this section as follows:

Frontends

{warning about configuration, specifying that uGet stores its own parameters for aria2}

Web UI

{note: these front-ends need aria2 to be started with --enable-rpc option (in terminal or as a daemon)} ...

Other frontends

These frontends don't need aria2 to be separately started with --enable-rpc.

...

uGet

..."

What do you think?

-- Neitsab (talk) 13:00, 12 January 2014 (UTC)