From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#22705: audacity help doesn't work Date: Mon, 04 Feb 2019 00:45:34 +0100 Message-ID: <87imy0wi5d.fsf@elephly.net> References: <20160216202052.26df5a85@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:57683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gqTAy-0008Rb-MU for bug-guix@gnu.org; Sun, 03 Feb 2019 20:35:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gqT8A-0002KM-Q2 for bug-guix@gnu.org; Sun, 03 Feb 2019 20:33:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:58651) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gqT8A-0002K9-CH for bug-guix@gnu.org; Sun, 03 Feb 2019 20:33:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gqT8A-0006uv-6J for bug-guix@gnu.org; Sun, 03 Feb 2019 20:33:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20160216202052.26df5a85@scratchpost.org> (Danny Milosavljevic's message of "Tue, 16 Feb 2016 20:20:52 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Danny Milosavljevic Cc: 22705@debbugs.gnu.org Danny Milosavljevic writes: > Running audacity and then opening Help -> Manual doesn't work since, among other things, it defaults to using the local help (non-internet) and can't find it. > > I'd suggest one of > (1) automatically install the local manual as well, or > (2) default HelpMode to internet help (see audacity-minsrc-2.1.2/src/widgets/HelpSystem.cpp HelpSystem::ShowHelpDialog) Audacity does not include the sources for he local manual. It comes with a script that downloads the project wiki (by jumping from link to link) and then converts it. In the build environment we cannot download the wiki like that, so we would have to run the script at packaging time and provide the wiki pages as inputs. This sounds tedious and maintenance-intensive. I prefer option 2.