Bug 532 – Windows: Handling of forward slash in plug-in name in audacity.cfg New Keys

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 532 - Windows: Handling of forward slash in plug-in name in audacity.cfg New Keys


Summary:	Windows: Handling of forward slash in plug-in name in audacity.cfg New Keys

Status:	CLOSED NOT-A-BUG

Product:	Audacity
Classification:	Unclassified
Component:	User Interface
Version:	2.0.1
Hardware:	PC Windows (all)

Importance:	P5 Repeatable
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-06-20 17:47 UTC by Gale Andrews
Modified:	2019-05-27 09:57 UTC (History)
CC List:	3 users (show)

See Also:
Steps To Reproduce:	1 Open the Audacity Plug-ins folder, select a Nyquist plug-in and add a forward slash in the ;name line e.g. change "Low Pass Filter..." to "Low Pass/Filter..." 2 Add a shortcut binding for the plug-in in Keyboard Preferences. 3 The shortcut still works even after restart of Audacity but it looks odd in .cfg: [NewKeys/EffectPlugin\:Low Pass] Filter...=Ctrl+8
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2019-05-27 00:00:00

Flags:	petersampsonaudacity: Test‑OK‑Win+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gale Andrews 2012-06-20 17:47:57 UTC

Only tested on Windows. Could be issues with other characters or platforms.

Comment 1 Peter Sampson 2019-05-26 08:11:43 UTC

My test of this on w10 with audacity-2.3.3-alpha-252-88dc11f525215cea57f7a89b0038fc7d40a50149

fails as I am denied access to changing the .ny file at Step 1 - and I suspect that most "civilian" users would be similarly blocked.


I'm failing to see why this is a bug per se:

The steps say "The shortcut still works ..."   - but then goes on to say "but it looks odd in .cfg: "


It works and just looks odd if users poke around "under-the-hood" - to me this looks like NOTABUG


And, as far as I can recall, no users have complianed about this in the 7 years that this "bug" has been extant.