Bug 165408
Summary: | --load-cookies documentation incorrect | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Evan Clarke <evanclarke> |
Component: | wget | Assignee: | Karsten Hopp <karsten> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | moritz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-08 14:50:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Evan Clarke
2005-08-09 01:05:34 UTC
fixed in rawhide I propose to change this bug, or at least its wording. I haven't looked at the fix, but I looked at the bug, though the report does not verbosely say what went wrong. The documentation is basically correct. What wget does not do though is to expand the tilde. (This restriction probably applies to tons of programs and might even be a general usability issue.) I tried wget --load-cookies=~/.mozilla/firefox/blabla.default/cookies.txt vs. wget --load-cookies=$HOME/.mozilla/firefox/blabla.default/cookies.txt and got an error message on the former syntax: Cannot open cookies file `~/.mozilla/firefox/zzhw8guq.default/cookies.txt': No such file or directory as wget does not realize "~" means /home/userid (or whatever), or "~userid" means /home/userid. So I suggest either a) leaving the documentation as is, as it is basically correct or a2) adding a note or b) changing (not "fixing") the documentation as is done in the original resolution of this bug, as it is the alternative syntax which works due to program vs. shell expansion or c) adding support for tilde expansion on any file names given on the command line or in config files (dunno how hard this really is) Actually I just wanted to point out and clarify that the documentation was indeed not "incorrect". |