| From Leland <leland@...>
| Mon, 07 Oct 2013 01:26:33 -0500
| Subject: [Audacity-nyquist] Fwd: [Audacity-devel] Fw: Audacity_Bug_Report
> Doesn't look like this ever got applied...shall I do it now?
I think you must have an old menus.cpp there.
The removal was committed here:
and it's still removed in Menus.cpp in HEAD.
> -------- Original Message -------- Subject: [Audacity-devel] Fw: Audacity_Bug_Report
> Date: Thu, 29 Aug 2013 21:55:28 +0100
> From: Richard Ash <mailto:richard@...>
> Reply-To: audacity-devel@...
> Organization: Audacity Development Team
> To: audacity-devel@...
> I think the bug reported below is caused by some prehistoric #ifdefisms
> which almost certainly ought to come out. I don't want to break things
> this close to a release, but can we log this as a bug so it gets looked
> at after the release (I think we can loose a few lines altogether
> from Menus.cpp as attached (untested)).
> Begin forwarded message:
> Date: Sun, 25 Aug 2013 21:32:34 +0000
> From: "Duarte, Rob" <mailto:rduarte@...>
> To: <mailto:feedback@..." <mailto:feedback@...>
> Subject: Audacity_Bug_Report
> I'm running Audacity 2.0.2 on MacOS 10.8.4
> If I add a Label Track, add some labels and extract those Labels to a
> text file, the resulting file has "classic" MacOS line endings (i.e.:
> MacOS 9 and below - just a CR)
> MacOS 9 is over 10 years old, and I can't remember the last time I used
> Mac software that still writes a CR instead of a unix-style LF. I can't
> see any reason why Audacity shouldn't use LF as the line ending. My
> particular problem is that I'm using those exported label text files as
> input to scripts and command-line programs on the Mac.. all of which
> are expecting a LF line ending.
> Thanks - let me know if you need any more info from me