08-07-2001
Yes I set the AUDIO and SPEAKER vars in .vueprofile and exported them both but I still get the same errors.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I play audio through the web browser and it plays ok on windows. When i try the same thing on unix i get the error message "sh: /usr/local/bin/sox: not found. I've tried 'locate sox' and can't seem to find it. Is there some way I can change the browser settings so they play the audio... (3 Replies)
Discussion started by: molli_81
3 Replies
2. Programming
Hi All,
Looking for an assistance on how to access the speakers of my machine and play audio files using C.
Any tutorials will be of great help.
Regards,
Sayantan. (1 Reply)
Discussion started by: Sayantan
1 Replies
3. UNIX for Advanced & Expert Users
Hello all,
Could anyone help to me :as to how can i record an audio file in unix and convert it into a text . Or anything with audio recording to get started would help .
thanks, (3 Replies)
Discussion started by: phantom308
3 Replies
4. Solaris
I am wondering if there is a way to get opensolaris to accept my realteck hd audio chip set.
dmesg
Thu Oct 23 22:47:38 EDT 2008
Oct 23 22:34:49 opensolaris Use is subject to license terms.
Oct 23 22:34:49 opensolaris unix: features:... (1 Reply)
Discussion started by: FloridaBSD
1 Replies
5. Ubuntu
I want to save a song which is being played from internet.
I cant find where it gets cached. Im also not sure if the whole sing will remain in the cache while the song finishes.
There must be a way using /dev/audio or something. Im not able to figure out. (4 Replies)
Discussion started by: bbala
4 Replies
6. UNIX for Dummies Questions & Answers
Hi, my friend refer me here he was saying that they have the best solution and really good wisdom of the UNIX system , i am learning and trying to install the audio software in my pc , but it 's not working may be i am forgetting something. (2 Replies)
Discussion started by: maggilane
2 Replies
7. UNIX for Dummies Questions & Answers
Hi I recently installed BT 5 Gnome on my Asus laptop running on Intel HD graphics.
I've been having problems with audio, at first I experienced the basic problem that was solved by adding pulse audio to the starting programs. This allowed me to open Sound preferences but I still have no sound.... (0 Replies)
Discussion started by: edreeso
0 Replies
8. UNIX Desktop Questions & Answers
Hello,
i have Debian 6.x and Gnome desktop.
Looking for some lightweight app to trim and crop mp3, wma or similar files. I already have ffmpeg installed.
I tried to load 29Mb file to Audacitty and it was frozing whole day untill i turned off PC.
Some simple tool, even command line,... (1 Reply)
Discussion started by: postcd
1 Replies
9. Slackware
I'm trying to record audio using Audacity 2.0.5 installed from SlackBuilds. My system is 64-bit Slackware 14.1 and a sound card is Intel HD Audio. I didn't change my sound system to OSS. (Default sound system in Slackware 14.1 is ALSA, isn't it?) First, I set Internal Microphone slider in KMix... (2 Replies)
Discussion started by: qzxcvbnm
2 Replies
LEARN ABOUT CENTOS
perl::critic::policy::variables::prohibitpackagevars
Perl::Critic::Policy::Variables::ProhibitPackageVars(3) User Contributed Perl DocumentationPerl::Critic::Policy::Variables::ProhibitPackageVars(3)
NAME
Perl::Critic::Policy::Variables::ProhibitPackageVars - Eliminate globals declared with "our" or "use vars".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Conway suggests avoiding package variables completely, because they expose your internals to other packages. Never use a package variable
when a lexical variable will suffice. If your package needs to keep some dynamic state, consider using an object or closures to keep the
state private.
This policy assumes that you're using "strict vars" so that naked variable declarations are not package variables by default. Thus, it
complains you declare a variable with "our" or "use vars", or if you make reference to variable with a fully-qualified package name.
$Some::Package::foo = 1; # not ok
our $foo = 1; # not ok
use vars '$foo'; # not ok
$foo = 1; # not allowed by 'strict'
local $foo = 1; # bad taste, but technically ok.
use vars '$FOO'; # ok, because it's ALL CAPS
my $foo = 1; # ok
In practice though, its not really practical to prohibit all package variables. Common variables like $VERSION and @EXPORT need to be
global, as do any variables that you want to Export. To work around this, the Policy overlooks any variables that are in ALL_CAPS. This
forces you to put all your exported variables in ALL_CAPS too, which seems to be the usual practice anyway.
CONFIGURATION
There is room for exceptions. Some modules, like the core File::Find module, use package variables as their only interface, and others
like Data::Dumper use package variables as their most common interface. These module can be specified from your .perlcriticrc file, and
the policy will ignore them.
[Variables::ProhibitPackageVars]
packages = Data::Dumper File::Find FindBin Log::Log4perl
This is the default setting. Using "packages =" will override these defaults.
You can also add packages to the defaults like so:
[Variables::ProhibitPackageVars]
add_packages = My::Package
You can add package "main" to the list of packages, but that will only OK variables explicitly in the "main" package.
SEE ALSO
Perl::Critic::Policy::Variables::ProhibitPunctuationVars
Perl::Critic::Policy::Variables::ProhibitLocalVars
AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>
COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.3 2014-06-09 Perl::Critic::Policy::Variables::ProhibitPackageVars(3)