zsh-users
 help / color / mirror / code / Atom feed
From: Nick Croft <nicko@acay.com.au>
To: "Matthias B." <msbREMOVE-THIS@winterdrache.de>
Cc: Nick Croft <nicko@acay.com.au>, zsh-users@sunsite.dk
Subject: Re: bindkey -v and alt-. for previous cmd arg
Date: Tue, 9 Nov 2004 22:18:37 +1100	[thread overview]
Message-ID: <20041109111837.GA14226@tandv.ws> (raw)
In-Reply-To: <20041107142914.67d0b94e@buddha.localdomain.de>

* Matthias B. (msbREMOVE-THIS@winterdrache.de) wrote:
> 
> man xterm
> 
> Never file bug reports without having read the manpage. 
> 
Thanks Matthias,

I skimmed through the manpage.

The debian bug reporting system isn't entirely the same as bug reporting
upstream. It refers mostly to the particular way the debian package is
prepared. There are 8 levels of `bug' ranging from critical bugs (which may
relate to the upstream development) through to `wishlist' bugs. 

I filed this one at the appropriate level - that referring to the usability
of the package.

Not everyone wants to be, or has time to be, an X or xterm or zsh developer.
We use these packages gratefully and in good faith. If your work output is
suddenly put in jeopardy and needs 10 - 30 hours research to find a solution
then the same is probably true for many others. The least you can do is file
a report.

The debian bugs can occur in as a result of injudicious selection of options
in the compiling. I don't wish to bring the distribution any negative
publicity by this, but among the 100's of packages being updated daily,
occasionally a severe mistake gets through (probably 0.01% or less of the
time). 

The worst I've seen is the time when an upgrade to postgresql managed to
wipe out the all the databases of anyone who had the misfortune to upgrade.
The bug only lasted a day for two fortunately.

I mention all this in the context of having for some time compiled my own
xterms in the days before utf-8 support was standard for debian. On the
other hand, I use the unstable debian distribution so I have to be prepared
to experience some inconvenience from time to time.

++++++++++++++++

That said, thanks for the pointer to the 8-bit option. I do appreciate your 
input.

Nick Croft


      reply	other threads:[~2004-11-09 11:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 12:48 Nick Croft
2004-11-03 13:53 ` DervishD
2004-11-03 19:44   ` Nick Croft
2004-11-03 19:57     ` DervishD
2004-11-03 20:01       ` DervishD
2004-11-04 11:43         ` Nick Croft
2004-11-04 12:03           ` DervishD
2004-11-04 12:16           ` Peter Stephenson
2004-11-04 14:20           ` Matthias B.
2004-11-04 14:33             ` Chris Johnson
2004-11-04 19:43               ` Nick Croft
2004-11-07 11:53             ` Nick Croft
2004-11-07 13:29               ` Matthias B.
2004-11-09 11:18                 ` Nick Croft [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041109111837.GA14226@tandv.ws \
    --to=nicko@acay.com.au \
    --cc=msbREMOVE-THIS@winterdrache.de \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).