search

pccasto / rubyripper

Automatically exported from code.google.com/p/rubyripper
0 stars 0 forks source link

ripping don't start with " / " in interpret #253

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. start rubyripper (gtk)
2. checkout a music cd
3. enter a "/" in the name for interpret in cd info (e.g. Unk/nown)
4. start ripping

What is the expected output? What do you see instead?
It shoud start ripping, but nothing happens after you see "STATUS" in the log.

1) What version of rubyripper are you using? On what operating system?
0.5.3 (from svn), gentoo

2) Are you using the gtk2 or the commandline interface?
gtk2

3) Is the problem gone with the default settings? If so, please attach your
settings file ($HOME/.rubyripper/settings).
no

Please provide any additional information below.
Don't know if this happens too if I enter a "/" in the other cd info fields.

Original issue reported on code.google.com by jbuec...@gmail.com on 25 Oct 2008 at 12:13

GoogleCodeExporter commented 8 years ago 
sorry, this is not enhancment, this is a defect!!!

Original comment by jbuec...@gmail.com on 25 Oct 2008 at 12:14

GoogleCodeExporter commented 8 years ago 
You didn't exactly specify what the expected output is. According to your 
answer,
stripping the '/' character should be enough. At least, it ensures ripping 
starts.

Using '/' in filenames is kinda impossible. Perhaps it's possible to include it 
in
the tags though. But you didn't request so.

Original comment by rubyripp...@gmail.com on 26 Oct 2008 at 9:19

GoogleCodeExporter commented 8 years ago 
> You didn't exactly specify what the expected output is.

Sorry: Because the rip does not start and the log tells me it will start but 
nothing
happens, 
I thougt there has to be an error message if a "/" is used 
This time rubyripper hangs only.

Original comment by jbuec...@gmail.com on 26 Oct 2008 at 9:57

GoogleCodeExporter commented 8 years ago 
I can't reproduce this bug in current git version. I guess it's solved then. 
See also
the screenshot I made.

Original comment by rubyripp...@gmail.com on 17 Jan 2009 at 6:13

Attachments: