From: "Clément Lassieur" <clement@lassieur.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: https://issues.guix.info
Date: Sun, 02 Sep 2018 23:17:23 +0200 [thread overview]
Message-ID: <87bm9flhuk.fsf@lassieur.org> (raw)
In-Reply-To: <87r2ibzkio.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Amin,
>
>>> The search box accepts issue numbers (for *any* bug on the GNU instance
>>> of Debbugs), but it also supports a few special queries, such as
>>>
>>> is:open / is:pending –> only open issues
>>> is:done / is:closed –> only completed issues
>>> title:foo -> issues containing “foo” in the title
>>> author:rekado –> issues that “rekado” contributed to
>>>
>>> Other supported terms are “severity”, “tag”, and “submitter”, but not
>>> all of them really work as they should, partly because of bugs in mumi,
>>> partly because of limitations in Debbugs.
>>
>> I think It would be neat to present these to the user, right on
>> the website itself.
>
> I agree. I don’t know how to present these things nicely, but I’ll play
> around with this.
>
> BTW: “submitter:who” should also work now. Like “is:…” it’s a rather
> expensive query because the result set from Debbugs has to be filtered
> locally.
Nice :-) Thank you.
>>> - make the search bar look good
>>
>> Adding class="form-control" would be a nice first step. Also,
>> it'd probably be a good idea to wrap the <form> in a div with
>> class="row", and use bootstrap grids to make the search bar and
>> the button smaller (by putting them in a column), and display the
>> above information about the search syntax in another column to
>> the right of the form.
>
> Thanks for the suggestions. I read the bootstrap CSS docs and came up
> with something that I hope is an improvement.
next prev parent reply other threads:[~2018-09-02 21:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 20:26 https://issues.guix.info Ricardo Wurmus
2018-09-01 21:46 ` https://issues.guix.info Amin Bandali
2018-09-02 20:55 ` https://issues.guix.info Ricardo Wurmus
2018-09-02 21:17 ` Clément Lassieur [this message]
2018-09-02 22:08 ` https://issues.guix.info Amin Bandali
2018-09-03 6:30 ` https://issues.guix.info Pierre Neidhardt
2018-09-03 13:01 ` https://issues.guix.info Ricardo Wurmus
2018-09-03 18:51 ` https://issues.guix.info Amin Bandali
2018-09-03 7:59 ` https://issues.guix.info Hartmut Goebel
2018-09-03 21:17 ` https://issues.guix.info Arun Isaac
2018-09-04 0:33 ` https://issues.guix.info Ricardo Wurmus
2018-09-05 6:50 ` https://issues.guix.info Arun Isaac
2018-09-05 7:10 ` https://issues.guix.info Ricardo Wurmus
2018-09-05 7:51 ` https://issues.guix.info Arun Isaac
2018-09-05 8:07 ` https://issues.guix.info Ricardo Wurmus
2018-09-10 20:57 ` https://issues.guix.info Gábor Boskovits
2018-09-13 22:29 ` https://issues.guix.info Pierre Neidhardt
2018-09-04 21:37 ` https://issues.guix.info Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bm9flhuk.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).