Windows Title Bar

2006-04-18 Thread Derek Parnell
I'd like to be able to exactly specify the title that appears on the 
console title bar (Windows environment of course). Current the application 
uses the URL that is being got but I'd like to specify it myself. Is there 
a way to do this now or does this have to be an enhancement?

Something like ...

  wget --title=News Server #1 http://www.etc.com/latest_news.html

So that News Server #1 appears as the console title rather than the URL 
(or its possible redirect).

-- 
Derek
(skype: derek.j.parnell)
Melbourne, Australia
Down with mediocracy!
18/04/2006 4:57:08 PM


Re: Windows Title Bar

2006-04-18 Thread www.mail

Derek Parnell wrote:


I'd like to be able to exactly specify the title that appears on the
console title bar (Windows environment of course). Current the application
uses the URL that is being got but I'd like to specify it myself. Is there
a way to do this now or does this have to be an enhancement?

Something like ...

  wget --title=News Server #1 http://www.etc.com/latest_news.html

So that News Server #1 appears as the console title rather than the URL
(or its possible redirect).


I think the standard Windows console application (cmd.exe) always 
changes its title somehow to reflect which command is currently executing.


An alternative would be to download the free console window 
replacement (called Console) from SourceForge:


http://heanet.dl.sourceforge.net/sourceforge/console/Console2_demo_015.zip

It allows you to have multiple tabs, with a console window in each 
tab, and you can rename each tab in the Edit menu.  So you could have 
inidividual tabs called News Server #1, News Server #2, etc., 
and run the appropriate wget command within each tab.


Or, you could hide the tabs completely (in the View menu) to have 
just a single console window, and set its title permanently to News 
Server #1, by changing the text Debug console to News Server #1 
within the file console.xml.


Hope this helps.

Regards,
Jonny



Re: Windows Title Bar

2006-04-18 Thread Hrvoje Niksic
www.mail [EMAIL PROTECTED] writes:

Something like ...

   wget --title=News Server #1 http://www.etc.com/latest_news.html

So that News Server #1 appears as the console title rather than the URL
(or its possible redirect).

 I think the standard Windows console application (cmd.exe) always
 changes its title somehow to reflect which command is currently
 executing.

Wget has code that changes the console title (ws_changetitle in
mswindows.c), which is what Derek is probably referring to.

Changing console title was IMHO a mistaken feature to implement in the
first place, but the original Windows port had it and, not being a
Windows user myself, I didn't want to remove it later.  If we allowed
such an option, it should probably be named --console-title or even
--windows-console-title rather than the generic --title.  It might
include substitutions like %(url) so that the user could specify
different strings that still contained the current URL.  Anyway,
adding further customizations to an already questionnable feature is
IMHO not a very good idea.


RE: Windows Title Bar

2006-04-18 Thread Tony Lewis
Hrvoje Niksic wrote:

 Anyway, adding further customizations to an already questionnable feature
 is IMHO not a very good idea. 

Perhaps Derek would be happy if there were a way to turn off this
questionable feature.

Tony



Re: wget 1.10.x: New option --random to randomize the dns result

2006-04-18 Thread Hrvoje Niksic
[ Moving the discussion to the Wget mailing list.
  Jerry's patch implements a --random option that shuffles the list
  of addresses returned by getaddrinfo. ]

Jerry Lundström [EMAIL PROTECTED] writes:

 A user scenario could be that wget with ipv6 enabled always picks a
 broken website since RFC 3484 deside that it should sort IPs in the way
 it does.

Not really -- Wget (stably) sorts the address list to prefer IPv4
addresses.  This can be influenced using the --prefer-family option.

Even if that were the case, Wget should be perfectly able to connect
to the next host in the address list, so the error would be non-fatal,
only incurring a small delay.

 It is fatal to automated script to always pick the broken mirror.

It is wrong to fix this by: a) introducing randomness, b) requiring
user intervention (how many users will even be aware of this option?),
and c) *still* allowing the broken mirror to be chosen by the said
randomness if the user is unlucky.

 Also, as mirror manager you might get 1/2 overloaded servers since
 the sort function is the way it is.

I don't think Wget is the most popular user agent around, and even if
it were, the option wouldn't be on by default.  Because of that,
implementing this option would not affect mirror server loads.

 Do you mean that the first address in the list is malfunctioning?
 Shouldn't Wget then fall back to the next one?  If one of the
 addresses is malfunctioning, even with --random you could still get
 that address, right?

 I don't see this behavior at all, if the first address returns
 404/403

I was talking about connection errors, not 404/403.  Why would a
mirror which is in DNS return 40x?  That kind of error should be fixed
on the server side, not by hacking Wget.


Re: Windows Title Bar

2006-04-18 Thread www.mail

Hrvoje Niksic wrote:


www.mail [EMAIL PROTECTED] writes:

Something like ...

   wget --title=News Server #1 http://www.etc.com/latest_news.html

So that News Server #1 appears as the console title rather than the URL
(or its possible redirect).

 I think the standard Windows console application (cmd.exe) always
 changes its title somehow to reflect which command is currently
 executing.

Wget has code that changes the console title (ws_changetitle in
mswindows.c), which is what Derek is probably referring to.

Changing console title was IMHO a mistaken feature to implement in the
first place


I agree.

In the case of Windows, I believe that no console application should 
alter the window title, as such applications will overwrite the title 
which was specified at the start of a command script.  Having said 
that, even if wget did not alter the window title, the Windows 
console (cmd.exe) would automatically append the wget command line to 
its window title, if wget was executed directly from the command 
line.  If wget was executed from within a script, then the script 
name would be appended to the console window title.


This is the (annoying, IMHO) behaviour of the Windows console, which 
is why I gave Derek the option of trying a different console 
completely - one where he had more control over the window title.



but the original Windows port had it and, not being a
Windows user myself, I didn't want to remove it later.  If we allowed
such an option, it should probably be named --console-title or even
--windows-console-title rather than the generic --title.  It might
include substitutions like %(url) so that the user could specify
different strings that still contained the current URL.  Anyway,
adding further customizations to an already questionnable feature is
IMHO not a very good idea.


Agreed also.  If the user wants to change the window title in 
Windows, then they should write a command script such as (referring 
to Derek's original example):


@echo off
title News Server #1
echo Downloading latest news...
echo.
wget http://www.etc.com/latest_news.html

Regards,
Jonny



Re: Windows Title Bar

2006-04-18 Thread Hrvoje Niksic
www.mail [EMAIL PROTECTED] writes:

Changing console title was IMHO a mistaken feature to implement in the
first place

 I agree.

 In the case of Windows, I believe that no console application should
 alter the window title, as such applications will overwrite the title
 which was specified at the start of a command script.  Having said
 that, even if wget did not alter the window title, the Windows console
 (cmd.exe) would automatically append the wget command line to its
 window title, if wget was executed directly from the command line.

The idea behind the feature is that you can see which URL is
*currently* being downloaded (you can specify several).  That's
somewhat different than just seeing the command line.  I still
consider it a mistake, though.


Re: Windows Title Bar

2006-04-18 Thread Tobias Tiederle

Hi,

I'm using start [1]. That way I can specify the title, have it running 
in the background and adjust priority and stuff. If you want to use it 
in a batch file you can specify /wait.

[Derek already got this, forgot to cc the list]

TT

[1] builtin command. Useable from cmd.exe or batch files.
START [title] [/Dpath] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED] [/LOW 
| /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL] [/WAIT] 
[/B] [command/program] [parameters]


Derek Parnell wrote:
I'd like to be able to exactly specify the title that appears on the 
console title bar (Windows environment of course). Current the application 
uses the URL that is being got but I'd like to specify it myself. Is there 
a way to do this now or does this have to be an enhancement?


Something like ...

  wget --title=News Server #1 http://www.etc.com/latest_news.html

So that News Server #1 appears as the console title rather than the URL 
(or its possible redirect).


RE: Windows Title Bar

2006-04-18 Thread Herold Heiko
 From: Hrvoje Niksic [mailto:[EMAIL PROTECTED]

 The idea behind the feature is that you can see which URL is
 *currently* being downloaded (you can specify several).  That's
 somewhat different than just seeing the command line.  I still
 consider it a mistake, though.

I like it, for long/slow downloads the tooltip (float your mouse over closed
window) beats opening the window (if logging to stdout) or reloading the log
file (if used).
I understand why you don't like it, but personally I don't think it should
be removed, even if only to default=off, as at least two different
windows-code contributors did in the past (if I remember correctly).
I suppose a question of personal taste, as many other (stupid) religious
wars... anybody remembers the weeks of hate-posts in comp.unix about
display-or-not-display current working directory in the xterm title bar
somewhere around the mid-nineties ? I seldom laughed as much, it was WAY
better than vi vs. emacs :-)

Heiko

-- 
-- PREVINET S.p.A. www.previnet.it
-- Heiko Herold [EMAIL PROTECTED] [EMAIL PROTECTED]
-- +39-041-5907073 / +39-041-5917073 ph
-- +39-041-5907472 / +39-041-5917472 fax


Re: Windows Title Bar

2006-04-18 Thread Hrvoje Niksic
Herold Heiko [EMAIL PROTECTED] writes:

 From: Hrvoje Niksic [mailto:[EMAIL PROTECTED]

 The idea behind the feature is that you can see which URL is
 *currently* being downloaded (you can specify several).  That's
 somewhat different than just seeing the command line.  I still
 consider it a mistake, though.

 I like it, for long/slow downloads the tooltip (float your mouse
 over closed window) beats opening the window (if logging to stdout)
 or reloading the log file (if used).
 I understand why you don't like it, but personally I don't think it
 should be removed,

I suspected that some users have grown to like it.  Plus, no one has
ever complained, at least until now.

 even if only to default=off, as at least two different windows-code
 contributors did in the past (if I remember correctly).  I suppose a
 question of personal taste, as many other (stupid) religious
 wars... anybody remembers the weeks of hate-posts in comp.unix about
 display-or-not-display current working directory in the xterm title
 bar somewhere around the mid-nineties ? I seldom laughed as much, it
 was WAY better than vi vs. emacs :-)

I don't think I ever read comp.unix.  Now I see I've been missing
out.  :-)