[Bug-wget] [bug #54825] unexpected wget appends .1 after the file extension

[J]

URL:
<https://savannah.gnu.org/bugs/?54825>

Summary: unexpected wget appends .1 after the file extension
Project: GNU Wget
Submitted by: now3d
Submitted on: Fri 12 Oct 2018 09:54:13 AM UTC
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.19.4
Operating System: GNU/Linux
Reproducibility: None
Fixed Release: None
Planned Release: None
Regression: None
Work Required: None
Patch Included: None

_______________________________________________________

Details:

Hello

Can wget not append the .1 after the file extension? It means manual changes
are needed by the user. If Firefox or Chrome downloads the same file twice, it
does not do this.

GNU Wget 1.19.4 built on linux-gnu.
ubuntu


2018-10-12 10:49:24 (582 KB/s) - ‘e.zip.1’ saved [491905/491905]





_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[Darshit Shah]

Follow-up Comment #1, bug #54825 (project wget):

I kind of agree here. Over time Wget has had the --no-clobber option do many
things and trying to preserve backwards compatibility has only complicated
everything. It would be ideal to have a --force option which causes Wget to
overwrite the file. You can currently do that by explicitly specifying the
filename using -O.


However, all new features are currently being added only to Wget2. Which is
the next version of Wget, with (almost) complete command-line parity. However,
we are indeed making some backwards incompatible modification which allow
making changes as you've proposed a lot easier. Please take a look at the
source available here: https://www.gitlab.com/gnuwget/wget2.git. It is also
available on Savannah and has been packaged for Debian already.

_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[J]

Follow-up Comment #2, bug #54825 (project wget):

Thank you for your reply. Will check out wget2

_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[Darshit Shah]

Update of bug #54825 (project wget):

Status: None => Wont Fix
Open/Closed: Open => Closed

_______________________________________________________

Follow-up Comment #3:

EDIT: Will fix in Wget2.

_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[Tim Ruehsen]

Follow-up Comment #4, bug #54825 (project wget):

Just want to add that Wget2 has --keep-extension (commit
c9796a174d04099d07dd7dc70da47ea92d3ba3a6).

E.g. that generates index_1.html instead of index.html.1.


_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[J]

Follow-up Comment #5, bug #54825 (project wget):

That is good.
As wget2 is new, maybe it can be revolutionary and adopt that as default?

_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[Tim Ruehsen]

Follow-up Comment #6, bug #54825 (project wget):

You can make your own default and put it into ~/.wget2rc or any other file set
by $WGET2RC or by --config.

But the hard-coded default will be kept as to make wget2 as nearly compatible
to wget as possible. So it can be used as drop-in replacement for wget, at
least in most cases.


_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[J]

Follow-up Comment #7, bug #54825 (project wget):

Fair enough.

I would probably use the opportunity for wget2 to be more evolutionary, and
adopt some new defaults. Old users could of course use old behavours.

This is a bit like when G++ changes the default C++ language spec to compile
against. Can't hang on with old things for ever..

_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

[Tim Ruehsen]

Follow-up Comment #8, bug #54825 (project wget):

If you have certain things in mind, issues at
https://gitlab.com/gnuwget/wget2/issues are appreciated.

_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?54825>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/