On Tue, 19 Jun 2007, Marc Lehmann wrote:
> On Tue, Jun 19, 2007 at 01:53:26PM +0200, Dag Wieers <[EMAIL PROTECTED]>
> wrote:
> > > than once before as well), I think I'll patch it out of the Debian
> > > package.
> >
> > I think the reason why on Debian it's not liked is because it behaves
> > differently than Red Hat/CentOS/Fedora in this regard.
>
> While it is possible that it is not liked on debian, the explanation bears no
> logic. bash does not, in this respect, work any differently than on any other
> distro: with a single exception, bash works as on other distros.
>
> The default might be different, who knows, but you are not talking about
> defaults.
How would I know, I don't know what Debian does and I'm less inclined to
find out by the rudeness of your comments.
> > As I said, I'm interested to change it in such a way that it works
> > correctly in both situations.
>
> It doesn't work correctly in any situation. The bug might simply be masked
> by somethign the users prompt or prompt comamnd does, but surely you do
> not believe that bash is the only way to start dstat? (If you are: no, you
> cna start dstat from another program, too, lets call it zsh. You can even
> write your own program to do it).
>
> You have to understand that destroying information never works "correctly"
> unless you restore it. It might be *masked* or might might not be
> *important* information that is destroyed, it is even possible that users
> of diferent distros have distinct different tastes with regards to thei
> destruction: some might care, some might not, but you can't help it:
> information is being destroyed.
>
> So please separate yourself from the idea that you can do it "correctly"
> by relying on something external to fix it up.
Why not ? I get the terminal width and height from something external. I
get the fact if colors are supported from somewhere external. So why
couldn't I try to see whether the terminal title can be used or not. Or
reset it.
I don't see a problem with that, but obviously you like to complain about
it.
> > I added it because it was useful in the same situation where dstat was
> > useful and I see it as an integer part of dstat.
>
> Nobody doubts that it can be useful. I think in most situations it is not
> useful, but even I can imagine that there are uses for that feature. I could
> even imagine that most people find it useful in a majority of situations.
So that's your opinion. I think most people like it. You're the only one
complaining (in a rude way).
> But regardless, it never is always usefull to everybody who finds dstat
> useful, and given that the feature is not at all cleanly implemented or
> graceful, it should be made optional.
I disagree and that's that.
> > (if you interactively monitor 5 to 10 clusters, you need a way to find out
> > which output belongs to what machine and space is scarce)
>
> So use the window title. I do that all the time, I do not need dstat to do
> it, because I can configure it much better on my own.
>
> The problem is that dstat doesn't give a shit to my carefully crafted
> window titles and destroys them with soemthing much less useful to me.
>
> You *have* to understand that something that is useful to you is nto
> automatically useful to others.
I do understand that. You're so full of yourself that you only think of
yourself. I can see that now as well. It's not because something is not
useful to you, it is automatically useless to everyone else.
I do not have to modify the behaviour because of one (abusive) person.
> Which is, in itself, not a problem. It becomes a problem if the
> implementation of the feature is of either low enough quality that it
> doesn't work well (in the case of dstat setting the window title: it is
> not being restored).
It is being restored on Red Hat. Sure, that's not dstat's work but dstat
cannot restore it. Maybe your use of the xterm title should be made
differently so returning to the shell resets it.
There is no unwritten rule that a program running in a terminal cannot set
the xterm title. According to you, nobody else could do anything with the
xterm title because the shell (or the terminal whatever) owns it ??
That's bullshit. Instead of being rude you could have come up with
something better.
> > I have no problem if you patch it out as long as you add an option to
> > enable it when users require it. In fact, if you like I can produce a
> > patch to do this and ship it with dstat ? Is that useful ?
>
> Very.
>
> And it would also be very useful to have some .dstat like file where you
> could put configuration items. I use this function for eternity now:
>
> cmd_ds() {
> exec dstat $(cat ~/.dstat) "$@"
> }
>
> Because my machines differ in configuration and I want to monitor
> different disks on diferent machines. Yes, I know I can change the source,
> but I deem changing the source and programming in python not a useful way
> to configure my apps).
There is no config file right now because dstat needs a rewriten anyway.
Feel free to not reply.
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[all I want is a warm bed and a kind word and unlimited power]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
