On Mon, Sep 25, 2017 at 09:03:08PM +0900, Osamu Aoki wrote:
> On Mon, Sep 25, 2017 at 12:37:57AM +0200, Adam Borowski wrote:
> ...
> > Here's a patch that implements "~/.boring-bugs". If such a file exists, all
> > lines starting with a bug number make rc-alert and tools that use it filter
> > out those bugs.
>
> Interesting idea. I thought it needs to update manpage rc-alert.1 too.
> Maybe for clarity, something like the following may be a good idea.
I did not include documentation in the first stab because 1. a RFC patch is
likely to be changed (like, an option to show all bugs anyway, a different
location of the file, etc), and 2. the documentation is quite trivial.
> The valid bug number should be listed by itself or followed by a
> whitespace. All other contents in the "~/.boring-bugs" are treated as
> the comment.
So the full paragraph would be something like:
.----
If the file $HOME/.boring-bugs exists, all bugs listed in it are ignored.
Bugs should be listed as numbers on a line by itself or followed by
whitespace and an optional comment. All other lines are also treated as
comments.
`----
> > + while (<BOR>)
> > + {
> > + next unless /^(\d+)\s/;
> > + $boring{$1} = 1;
> > + }
> > + close BOR;
Meow!
--
⢀⣴⠾⠻⢶⣦⠀ We domesticated dogs 36000 years ago; together we chased
⣾⠁⢰⠒⠀⣿⡁ animals, hung out and licked or scratched our private parts.
⢿⡄⠘⠷⠚⠋⠀ Cats domesticated us 9500 years ago, and immediately we got
⠈⠳⣄⠀⠀⠀⠀ agriculture, towns then cities. -- whitroth on /.
