9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Very old bug in db(1)
Date: Thu, 19 Mar 2015 09:01:23 +0100	[thread overview]
Message-ID: <CAHL7psGVDE6G9S20YPdQ2e_NKdXD7Q=uw8sMrBKVsd5vmxgvVg@mail.gmail.com> (raw)
In-Reply-To: <bcb58c031e274b559062dde6296c5066@shike2.com>

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

I could be wrong, but looks like nobody cares about such small fixes.

A few days ago, I've found some very old small errors (one in the 2c(1) man
page and one in col(1) that affects man pages' visualization in variable
width fonts) but had no feedback.
I guess that the most effective way to cope with such old and small bugs,
is to report them on 9fans (and other related mailing lists), possibly with
a patch.
This way, any other user that hit the bug (and find your email) can apply
the patch and fix them in his $home/bin (or somewhere else) and then bind
-b it to /bin.


Giacomo

2015-03-19 7:41 GMT+01:00 Roberto E. Vargas Caballero <k0ga@shike2.com>:

> I was doing some experiments with db(1), when I tried something like:
>
> main:b *argv/X
>
> and it gave me an error. I debugged it and I found that is a bug in the
> code due to a mix between char* and Rune*. I have created a patch
> in sources with the name unicode-db.
>
> The funny thing is this error must be at least 20 years old,
> because clearly its origin is the unicode translation of old unix tools.
> I have checked  labs, 9front and plan9port and all of them have
> the error (in some moment someone realized about a warning
> of the compiler about different pointer types and simply put a
> cast, that is not present in the code of plan9port).
>
> I send this mail here, first because I think is the error is funy,
> second because is my first patch send to plan9 and I'm not sure about
> the process, and third because it affects to all the versions of plan9
> and I'm not sure if all of them take this bug fixes from sources.
>
> Regards,
>
>
>

[-- Attachment #2: Type: text/html, Size: 2110 bytes --]

  reply	other threads:[~2015-03-19  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  6:41 Roberto E. Vargas Caballero
2015-03-19  8:01 ` Giacomo Tesio [this message]
2015-03-19  8:41   ` lucio
2015-03-19  9:12     ` Giacomo Tesio
2015-03-19 10:12       ` lucio
2015-03-19 10:47   ` cinap_lenrek

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='CAHL7psGVDE6G9S20YPdQ2e_NKdXD7Q=uw8sMrBKVsd5vmxgvVg@mail.gmail.com' \
    --to=giacomo@tesio.it \
    --cc=9fans@9fans.net \
    /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.
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).