help / color / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: A bug tracker (was: Re: [Bug] Unexpected process suspension)
Date: Thu, 21 May 2020 15:39:17 +0200
Message-ID: <58530-1590068357.770519@OqB0.VdVl.aCLr> (raw)
In-Reply-To: <20200521033301.35393ae9@tarpaulin.shahaf.local2>

Daniel Shahaf wrote:
> Finally, I have been using Etc/BUGS in git to track bugs.  If someone'd
> like to add an entry there for this set of related bugs, please do.

As I've just been catching up on the list having had little time
recently, here's a collection of some of the outstanding bugs:

44133 debian #924736 (partial patch in 44134) three setopts following `    #`
44850 terminal issues with continuation markers
45422 _arguments !-x !+x: this is on my TODO list
45482 print -v with multibyte characters
45568 repeat-count "illegal character"
  this can't be too hard given it is the meta range of characters
  Incidentally, I don't like the use of "illegal" in error messages.
  Perhaps this is a UK/US difference but to me "illegal" implies
  actually against the law.
45656 -o nobanghist -o emacs segfaults
users/24765 -direct terminals. Not a bug as such but we may need to do
  something if -direct values in TERM are ever common
45830 _gpg, I can't reproduce either.

There are also some outstanding patches:

45393/45396 avoid lseek(2) calls. Doesn't this just need a quick verification?
  I've had some dealings with the patch author in relation to i3 and would
  trust him even without looking at the patch details.
45768 This looks distinctly similar to the above.
45837 Stephane's patch for 45828
45007 has_colors in configure.ac. This didn't reproduce on any of my systems
  but I've just noticed that the originator has a gentoo.org address which might
  provide some extra clues.

There was a recent (45778) reminder about 44525 which is by Roman.

I don't care enough about different bug tracking methods to get much
involved in that discussion. The mailing list perhaps intimidates
potential newcomers nowadays which is not ideal. But it has advantages
like the single archive that can be offline. Integration with a list is
fine if you don't get spammed. All too often every little status change
generates a mail.


  parent reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  7:02 [Bug] Unexpected process suspension Rudi C
2020-05-12 11:48 ` Daniel Shahaf
2020-05-12 11:53   ` Roman Perepelitsa
2020-05-12 11:57     ` Daniel Shahaf
2020-05-12 12:05       ` Roman Perepelitsa
2020-05-12 13:31     ` Stephane Chazelas
2020-05-12 17:38 ` Bart Schaefer
2020-05-13  6:29   ` Stephane Chazelas
2020-05-20 22:32     ` Rudi C
2020-05-21  3:33       ` A bug tracker (was: Re: [Bug] Unexpected process suspension) Daniel Shahaf
2020-05-21  4:44         ` Bart Schaefer
2020-05-21 13:39         ` Oliver Kiddle [this message]
2020-05-21 16:46           ` Daniel Shahaf

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:

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

  git send-email \
    --in-reply-to=58530-1590068357.770519@OqB0.VdVl.aCLr \
    --to=okiddle@yahoo.co.uk \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link


Archives are clonable: git clone --mirror http://inbox.vuxu.org/zsh-workers

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git