Renamed files should remain in the same directory
Bug #594736 reported by
Tristan Seligmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Renamer |
Fix Committed
|
High
|
Jonathan Jacobs | ||
Bug Description
Currently renamed files land up in the working directory, regardless of where they were originally located. When --move is being used, this may be reasonable, but otherwise this is undesireable and confusing (and potentially dangerous!).
Related branches
lp://staging/~renamer-developers/renamer/ditch-metalanguage
- Tristan Seligmann: Approve
- Andrew Snowden: Approve
-
Diff: 2443 lines (+714/-1378)22 files modifiedLICENSE (+5/-1)
bin/rn (+1/-1)
renamer/__init__.py (+2/-0)
renamer/application.py (+148/-223)
renamer/env.py (+0/-311)
renamer/errors.py (+3/-8)
renamer/irenamer.py (+28/-3)
renamer/logging.py (+12/-7)
renamer/main.py (+2/-3)
renamer/plugin.py (+57/-82)
renamer/plugins/audio.py (+56/-43)
renamer/plugins/common.py (+0/-307)
renamer/plugins/tv.py (+107/-56)
renamer/test/data/tvrage (+19/-0)
renamer/test/test_env.py (+0/-53)
renamer/test/test_plugin.py (+34/-0)
renamer/test/test_tvrage.py (+93/-16)
renamer/test/test_util.py (+89/-0)
renamer/util.py (+57/-175)
scripts/music.rn (+0/-44)
scripts/tv.rn (+0/-44)
setup.py (+1/-1)
| Changed in renamer: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in renamer: | |
| milestone: | none → 0.1.0 |
| assignee: | nobody → Jonathan Jacobs (jjacobs) |
| Changed in renamer: | |
| status: | Triaged → Fix Released |
| status: | Fix Released → Fix Committed |
To post a comment you must log in.
