In a message dated: Fri, 03 Jan 2003 16:55:11 EST
Travis Roy said:
Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
What's that Key fingerprint, with all the earlier talk about GPG I'm
curious.. It doesn't look like GPG
Why doesn't it look like GPG? What does GPG look
Why doesn't it look like GPG? What does GPG look like?
They more typical GPG/PGP sig looks like this:
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD4DBQA+E2E6/TBScWXa5IgRAuTrAJ97X850CVvq05FSq4Q0OUBsDoZ/vACWJ0jK
Fingerprint != signature
On Mon, 2003-01-06 at 10:03, Travis Roy wrote:
Why doesn't it look like GPG? What does GPG look like?
They more typical GPG/PGP sig looks like this:
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
One approach:
- Create a script named (say) /tmp/renameSpaces
which consists of the single command:
mv $* `echo $* | sed -e 's/ /_/g'`
- Mark that script executable:
chmod a+x /tmp/renameSpaces
- Then say
find yourMP3directory -type f -exec /tmp/renameSpaces {} \;
Hi All,
I have been trying to organize my MP3's, but I ran into a little
trouble. Apparently, one of the rippers that I used wasn't configured
correctly, and evey albumn and song name has spaces. I can go through
and rename each song one at a time, but that will take forever to do.
So, I figured
Michael O'Donnell wrote:
perl -e 'opendir DIR,.;@f = grep { ! /^\./ -f $_ } readdir(DIR);\
map {($n = $_)=~ s/\s+/_/g; rename ($_, $n) } @f;'
Heh. Just for fun I rot13'd that Perl hack and, for my money,
it's just as readable... ;-
LOL
crey -r 'bcraqve
On Mon, Jan 06, 2003 at 11:55:28AM -0500, Erik Price [EMAIL PROTECTED] wrote:
Michael O'Donnell wrote:
perl -e 'opendir DIR,.;@f = grep { ! /^\./ -f $_ }
readdir(DIR);\
map {($n = $_)=~ s/\s+/_/g; rename ($_, $n) } @f;'
codemap {($n = $_)=~ s/\s+/_/g; rename ($_, $n)
[EMAIL PROTECTED] (Michael O'Donnell) writes:
(Same for Kevin's solution, if you please...)
: perl -MFile::Find -e 'find(sub{$old = $_; y/ /_/; rename($old, $_);},
:kens-mp3-dir);'
Mine just uses the standard File::Find module. To find out more about
this, try typing perldoc File::Find on
On Mon, Jan 06, 2003 at 10:22:14AM -0500, Kenneth E. Lussier wrote:
Hi All,
I have been trying to organize my MP3's, but I ran into a little
trouble. Apparently, one of the rippers that I used wasn't configured
correctly, and evey albumn and song name has spaces. I can go through
and rename
Bob Bell wrote:
One nit: the $_ in the anonymous block passed to map does not come
from grep. Rather, it is a reference to each item (in turn) in the
provided list (here, @f).
Upon re-reading my explanation, I came to the same conclusion -- I was
thinking that the script worked the
In a message dated: Mon, 06 Jan 2003 11:32:55 EST
Michael O'Donnell said:
perl -e 'opendir DIR,.;@f = grep { ! /^\./ -f $_ } readdir(DIR);
\
map {($n = $_)=~ s/\s+/_/g; rename ($_, $n) } @f;'
On a more serious note, I (for one) would be grateful for
a blow-by-blow analysis of
In a message dated: Mon, 06 Jan 2003 11:54:50 EST
Derek Martin said:
Mike, I agree with you 100%. But Perl can be more readable than that,
if the author decides to make it so.
I don't think mine was unreadable given it was on the command line.
Add a few new lines in and you have almost exactly
In a message dated: Mon, 06 Jan 2003 12:05:38 EST
Kevin D. Clark said:
(doesn't the y/// thingie remind you of sed and tr?), and then renames
the thing accordingly (without doing any error checking).
Not only that, but perl has a tr/// thingy which is identical to y///
(*why* does perl have 2
On Mon, 6 Jan 2003, at 10:42am, [EMAIL PROTECTED] wrote:
I had the same problem a while ago with my MP3 collection ...
I guess I'm the only guy on the list who *likes* spaces in my music file
names. ;-)
BTW, let me put in a plug for the SLIMP3. This device ROCKS.
Can it play OGG files?
In a message dated: 06 Jan 2003 10:22:14 EST
Kenneth E. Lussier said:
What am I missing?
Perl of course
:)
perl -e 'opendir DIR,.;@f = grep { ! /^\./ -f $_ } readdir(DIR);\
map {($n = $_)=~ s/\s+/_/g; rename ($_, $n) } @f;'
(sorry it took so long for this one, I ran out of
[EMAIL PROTECTED] writes:
In a message dated: Mon, 06 Jan 2003 12:05:38 EST
Kevin D. Clark said:
(doesn't the y/// thingie remind you of sed and tr?), and then renames
the thing accordingly (without doing any error checking).
Not only that, but perl has a tr/// thingy which is identical to
In a message dated: Mon, 06 Jan 2003 12:52:48 EST
Kevin D. Clark said:
Not only that, but perl has a tr/// thingy which is identical to y///
(*why* does perl have 2 identical operators?)
Because both sed and tr offer this functionality (tr is named tr and
sed offers this functionality with
Gentlemen,
Many thanks for all the excellent followup -
in the immortal words of The Bard:
GNHLUG rocks!
BTW - what would Shakespeare be doing if he were alive today?
.
.
.
.
.
.
In a message dated: Mon, 06 Jan 2003 10:51:04 EST
[EMAIL PROTECTED] said:
I guess I'm the only guy on the list who *likes* spaces in my music file names. ;-)
Spaces in file names are EVIL :)
--
Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
On Mon, 6 Jan 2003, at 11:15am, [EMAIL PROTECTED] wrote:
I guess I'm the only guy on the list who *likes* spaces in my music file
names. ;-)
Spaces in file names are EVIL :)
No, shell scripts that don't quote their arguments are evil. ;-)
--
Ben Scott [EMAIL PROTECTED]
| The
So let me get this straight: For people who don't understand Perl,
Perl is hard to understand.
Now, cut that out. Derek's point, of course, is
that some languages are (can be) gobbledegookier than
others and (for some of us, at least) Perl sure does
seem to make you have to gobble WAY more
On Mon, 6 Jan 2003, at 11:33am, [EMAIL PROTECTED] wrote:
I guess I'm the only guy on the list who *likes* spaces in my music
file names. ;-)
Spaces in file names are EVIL :)
No, shell scripts that don't quote their arguments are evil. ;-)
Threads that don't die that should have 3
On Mon, 6 Jan 2003, at 11:33am, [EMAIL PROTECTED] wrote:
I guess I'm the only guy on the list who *likes* spaces in my music
file names. ;-)
Spaces in file names are EVIL :)
No, shell scripts that don't quote their arguments are evil. ;-)
Threads that don't die that should have 3
On Mon, Jan 06, 2003 at 10:51:04AM -0500, [EMAIL PROTECTED] wrote:
On Mon, 6 Jan 2003, at 10:42am, [EMAIL PROTECTED] wrote:
I had the same problem a while ago with my MP3 collection ...
I guess I'm the only guy on the list who *likes* spaces in my music file
names. ;-)
BTW, let me
My boss just asked me to install Frontpage Database Extensions I can't
find anything about it on the linux side of Frontpage.
Frontpage Extensions is already installed on the box, is there anyway I
can use MySQL or something?
Just to see what I'm dealing with:
Me: is this what you're talking
Derek Martin wrote:
This particular one-liner is very readable when properly indented and
code-formatted, making use of few of the esoteric symbols that make
reading Perl scripts hard. I like it quite a bit.
I disagree, in large part, though I've definitely seen worse. I find
the syntax
[EMAIL PROTECTED] writes:
perl -e 'opendir DIR,.;@f = grep { ! /^\./ -f $_ } readdir(DIR);\
map {($n = $_)=~ s/\s+/_/g; rename ($_, $n) } @f;'
Things that come to mind when I see this:
1: this code doesn't recurse.
2: this code skips over files with a name that begins with
In a message dated: Mon, 06 Jan 2003 12:06:23 EST
Derek Martin said:
I disagree, in large part, though I've definitely seen worse. I find
the syntax of the grep and map to be pretty cryptic,
How is it cryptic?
grep BLOCK LIST
Evaluates the BLOCK or EXPR for each element
On Mon, 6 Jan 2003, at 11:16am, [EMAIL PROTECTED] wrote:
perl -MFile::Find -e 'find(sub{$old = $_; y/ /_/; rename($old, $_);},
kens-mp3-dir);'
For those who find the above one-liner somewhat hard to parse, here is a
file version that uses whitespace and comments, avoids the anonymous
Erik Price [EMAIL PROTECTED] writes:
PS: FWIW, Python is a friendlier and IMO superior language for writing
scripts where legibility is important, but you can't write a oneliner
like the OP's Perl script using Python. I think a lot of Perl users
like the way that it is quick to write.
On Mon, 6 Jan 2003, at 12:30pm, [EMAIL PROTECTED] wrote:
This way it's pretty obvious what the individual steps are:
^^^
This must be some meaning of the word obvious of which I was previously
unaware. ;-)
--
Ben Scott [EMAIL PROTECTED]
| The opinions expressed in
In a message dated: Mon, 06 Jan 2003 12:44:07 EST
Kevin D. Clark said:
[EMAIL PROTECTED] writes:
perl -e 'opendir DIR,.;@f = grep { ! /^\./ -f $_ } readdir(DIR);\
map {($n = $_)=~ s/\s+/_/g; rename ($_, $n) } @f;'
Things that come to mind when I see this:
1: this code doesn't
On Mon, 6 Jan 2003, at 12:42pm, [EMAIL PROTECTED] wrote:
Not only that, but perl has a tr/// thingy which is identical to y///
(*why* does perl have 2 identical operators?)
Same reason about half of Perl is the way it is: It just happened that
way. IIRC, the original operator was y///, but
In a message dated: Mon, 06 Jan 2003 12:49:32 EST
Derek Martin said:
Of course it does. But experienced programmers with no knowledge of
Perl are, I suspect, a lot more likely to guess what they do than to
guess what that obscure map bit does.
I don't believe it was obscure at all. In fact,
On Mon, 6 Jan 2003, at 12:44pm, [EMAIL PROTECTED] wrote:
3: this code doesn't rename directory names with spaces ...
That could be considered a feature. Renaming of such directories breaks
your code. Try it. :-)
--
Ben Scott [EMAIL PROTECTED]
| The opinions expressed in this message are
[EMAIL PROTECTED] writes:
In a message dated: Mon, 06 Jan 2003 12:44:07 EST
Kevin D. Clark said:
1: this code doesn't recurse.
It wasn't intended to, it was intended to replace the OPs shell
script which hosed him because of non-quoted, space-riddled, file
names. His shell script
On Mon, 6 Jan 2003, at 12:49pm, [EMAIL PROTECTED] wrote:
In other words, assuming that the reader of the script does know how
to read Perl including the standard-library functions grep and
map, then the script is perfectly readable,
Yes, but for those NOT familiar with Perl syntax ...
On Mon, 6 Jan 2003, at 12:07pm, [EMAIL PROTECTED] wrote:
Boss: he hasn't a clue, but he said he needs tham
He doesn't know what it is, but he knows he needs it?
Okie dokie, that's not asking much. Right after you satisfy that request,
why don't you build a perpetual motion machine, too?
In a message dated: Mon, 06 Jan 2003 13:10:18 EST
[EMAIL PROTECTED] said:
On Mon, 6 Jan 2003, at 12:44pm, [EMAIL PROTECTED] wrote:
3: this code doesn't rename directory names with spaces ...
That could be considered a feature. Renaming of such directories breaks
your code. Try it. :-)
(Pardon the profanity, but this just has to be said...)
On Mon, 6 Jan 2003, at 1:00pm, [EMAIL PROTECTED] wrote:
Well, again, everybody is entitled to their opinions ...
Opinions are like assholes: Everybody has one, and they all stink!
--
Ben Scott [EMAIL PROTECTED]
| The opinions
On Mon, 6 Jan 2003, at 1:13pm, [EMAIL PROTECTED] wrote:
But I'm telling you, for someone who ain't a perl hacker, what you guys
wrote is gobbledygook.
So let me get this straight: For people who don't understand Perl, Perl is
hard to understand.
Deep wisdom, that. :-)
--
Ben Scott
On Mon, 6 Jan 2003, at 12:01pm, [EMAIL PROTECTED] wrote:
No, as there are few (no?) hardware-based OGG players.
I know. :-(
BUT, you can transcode from OGG to MP3 and play that.
Speaking of evil
--
Ben Scott [EMAIL PROTECTED]
| The opinions expressed in this message are those of
On Mon, 6 Jan 2003, at 1:20pm, [EMAIL PROTECTED] wrote:
That could be considered a feature. Renaming of such directories breaks
your code. Try it. :-)
What if you changed the name after you left?
Can you do that with the File::Find::find() ?
--
Ben Scott [EMAIL PROTECTED]
| The
He doesn't know what it is, but he knows he needs it?
Of course! What's even worse is that the programmer doesn't know what it
is either. Probably just using some generic thing that comes with front
page. Guy is probably getting more then me too. I've offered to re-do the
pages with PHP and
On Mon, Jan 06, 2003 at 01:23:41PM -0500, [EMAIL PROTECTED] wrote:
On Mon, 6 Jan 2003, at 12:01pm, [EMAIL PROTECTED] wrote:
No, as there are few (no?) hardware-based OGG players.
I know. :-(
BUT, you can transcode from OGG to MP3 and play that.
Speaking of evil
Bah. If the
Derek Martin [EMAIL PROTECTED] writes:
But I'm telling you, for someone who ain't a perl hacker,
what you guys wrote is gobbledygook.
I think that you (and anybody who shares your position) would do well
to be a little bit more open-minded about learning now programming
language paradigms.
On Mon, 6 Jan 2003, at 1:34pm, [EMAIL PROTECTED] wrote:
Bah. If the OGG is at a higher rate than the MP3 (say 192kbps OGG to
128kb MP3) then you shouldn't notice anything.
I find that audio converted from one lossy format to another sounds like
crap. I am told that is because the lossy
In a message dated: Mon, 06 Jan 2003 13:13:18 EST
Derek Martin said:
How is it cryptic?
In each case, it is the BLOCK which is unintelligible.
[...snip...]
For example, take the grep. It never would have occurred to me to do a
file test as part of the expression...
It's not an expression,
In a message dated: Mon, 06 Jan 2003 13:19:34 EST
[EMAIL PROTECTED] said:
On Mon, 6 Jan 2003, at 12:07pm, [EMAIL PROTECTED] wrote:
Boss: he hasn't a clue, but he said he needs tham
He doesn't know what it is, but he knows he needs it?
Okie dokie, that's not asking much. Right after you
[EMAIL PROTECTED] (Kevin D. Clark) writes:
[EMAIL PROTECTED] writes:
That could be considered a feature. Renaming of such directories breaks
your code. Try it. :-)
Damn. I thought I tested this too.
OK, this solves this particular problem:
perl -MFile::Find -e 'find({ bydepth = 1,
In a message dated: Mon, 06 Jan 2003 13:34:22 EST
Mark Komarinski said:
I'm not *that* anal about my music. I just want to hear it.
MP3s are fine for stuff ripped from CD, but if you've got a
soundboard recording of a live show that's been converted to mp3 from
wav, you've lost a lot data in
In a message dated: Mon, 06 Jan 2003 13:40:33 EST
[EMAIL PROTECTED] said:
On Mon, 6 Jan 2003, at 1:34pm, [EMAIL PROTECTED] wrote:
Bah. If the OGG is at a higher rate than the MP3 (say 192kbps OGG to
128kb MP3) then you shouldn't notice anything.
I find that audio converted from one lossy
On Mon, 6 Jan 2003, at 1:45pm, [EMAIL PROTECTED] wrote:
... some languages are (can be) gobbledegookier than others and (for some
of us, at least) Perl sure does seem to make you have to gobble WAY more
gook than anyone should have to...
People use that argument against C, /bin/sh, Unix,
Kenny or mod, both of whom, if they had cared to I'm
sure, could have figured either one-liner out in as
much time.
You're right, of course - I did. And I hope
nobody took any offense at my request for
explanations. FYI, when I asked for y'all to
explain your one-liners I did it (as much as
On Mon, 6 Jan 2003, at 1:59pm, [EMAIL PROTECTED] wrote:
Huh? If you have a live show that's a .wav file and convert it to MP3 you
lost a lot of data? How is going from a high quality .wav file to mp3 any
different then CDDA to wav ...
CDDA - WAV is lossless.
anything - MP3 is lossy.
I
In a message dated: Mon, 06 Jan 2003 13:59:20 EST
Travis Roy said:
In a message dated: Mon, 06 Jan 2003 13:34:22 EST
Mark Komarinski said:
I'm not *that* anal about my music. I just want to hear it.
but if you've got a
soundboard recording of a live show that's been converted to mp3 from
In a message dated: Mon, 06 Jan 2003 14:02:44 EST
[EMAIL PROTECTED] said:
CDDA - WAV is lossless.
anything - MP3 is lossy.
I think his point was that live records of a noisy concert -- which tend
to be somewhat muddy to begin with -- tend to sound a lot worse when you hit
them with a
I obviously said some stuff wrong.. Let me clear it up.
In a message dated: Mon, 06 Jan 2003 13:59:20 EST
Travis Roy said:
In a message dated: Mon, 06 Jan 2003 13:34:22 EST
Mark Komarinski said:
I'm not *that* anal about my music. I just want to hear it.
but if you've got a
On Mon, Jan 06, 2003 at 12:49:32PM -0500, Derek Martin [EMAIL PROTECTED] wrote:
But experienced programmers with no knowledge of Perl are, I suspect,
a lot more likely to guess what they do than to guess what that
obscure map bit does.
Perhaps. But someone knowledgable about software
On Mon, Jan 06, 2003 at 01:53:10PM -0500, [EMAIL PROTECTED] wrote:
In a message dated: Mon, 06 Jan 2003 13:34:22 EST
Mark Komarinski said:
I'm not *that* anal about my music. I just want to hear it.
MP3s are fine for stuff ripped from CD, but if you've got a
soundboard recording of a
I hope this is my last post in this stupid thread. I initially
responded to this thread just trying to be helpful, and the aftermath
has become painful.
Derek Martin [EMAIL PROTECTED] writes:
Very often Perl hackers (on this list or elsewhere) will spout a Perl
one-liner in response to
On Mon, Jan 06, 2003 at 04:31:57PM -0500, Kevin D. Clark [EMAIL PROTECTED]
wrote:
I have yet to see anybody else post code that implements these features
(recursing + renaming the directories with names containing spaces).
Just because that sounded like a challenge, how about this for
a
Kevin D. Clark wrote:
Erik Price [EMAIL PROTECTED] writes:
PS: FWIW, Python is a friendlier and IMO superior language for writing
scripts where legibility is important, but you can't write a oneliner
like the OP's Perl script using Python. I think a lot of Perl users
like the way that it is
On Mon, Jan 06, 2003 at 04:07:41PM -0500, Mark Komarinski wrote:
Yes, transcoding will lose some of your quality. The question is, how
much are you willing to lose and how much will you notice?
Time to follow up to myself and put my money where my mouth is.
If you go to
64 matches
Mail list logo
