From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Robert Weiner Newsgroups: gmane.emacs.devel Subject: Re: Development suggestions from an ENSIME developer Date: Fri, 22 Jul 2016 10:28:30 -0400 Message-ID: References: <87wpke3kdj.fsf@russet.org.uk> <83h9biyek4.fsf@gnu.org> <877fce3flr.fsf@russet.org.uk> <83d1m6xint.fsf@gnu.org> <83vazxx0dz.fsf@gnu.org> Reply-To: rswgnu@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c1920465f754405383a4158 X-Trace: ger.gmane.org 1469197760 14592 80.91.229.3 (22 Jul 2016 14:29:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 22 Jul 2016 14:29:20 +0000 (UTC) Cc: Lars Ingebrigtsen , emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 22 16:29:15 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bQbRy-0004nz-Hl for ged-emacs-devel@m.gmane.org; Fri, 22 Jul 2016 16:29:14 +0200 Original-Received: from localhost ([::1]:47484 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQbRx-00059J-UN for ged-emacs-devel@m.gmane.org; Fri, 22 Jul 2016 10:29:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46346) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQbRp-00057o-4m for emacs-devel@gnu.org; Fri, 22 Jul 2016 10:29:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bQbRl-0004QW-MQ for emacs-devel@gnu.org; Fri, 22 Jul 2016 10:29:05 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40259) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQbRl-0004QC-Ih for emacs-devel@gnu.org; Fri, 22 Jul 2016 10:29:01 -0400 Original-Received: from mail-oi0-f49.google.com ([209.85.218.49]:36523) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bQbRk-0005Rr-8T; Fri, 22 Jul 2016 10:29:00 -0400 Original-Received: by mail-oi0-f49.google.com with SMTP id w18so164994423oiw.3; Fri, 22 Jul 2016 07:29:00 -0700 (PDT) X-Gm-Message-State: AEkoouuN5nPk2WuzjTeLY1uLdU6hDeR8w5d3j8Bp5fyq/4wGJmqLM3eOPDtj2hXf5ky+6jYw4q5g3uiEWzyExg== X-Received: by 10.157.21.1 with SMTP id u1mr2120497otf.143.1469197739568; Fri, 22 Jul 2016 07:28:59 -0700 (PDT) Original-Received: by 10.202.199.143 with HTTP; Fri, 22 Jul 2016 07:28:30 -0700 (PDT) In-Reply-To: <83vazxx0dz.fsf@gnu.org> X-Gmail-Original-Message-ID: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:206026 Archived-At: --94eb2c1920465f754405383a4158 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Jul 22, 2016 at 9:34 AM, Eli Zaretskii wrote: > > It should at least have a google-like search field that lets one > > quickly search for bugs based on subject line, bug id or the full text > of discussions, so one does not have to > > master any field-based searching initially. > > That it does have, look near the end of the page. =E2=80=8BGood. The results seem to come back reasonably quickly as well.= =E2=80=8B =E2=80=8BI would suggest the following for the web interface: - the full text search field =E2=80=8Bbe added to the home page and be ne= ar the top so casual users find it right away and everyone can use it quickly with navigating to a separate page - that the status/pending of the issue be displayed (right now only severity is displayed) - that there be an easy way to navigate from a full text search result connected to a specific bug to a place where a new comment can be added or a status can be changed (with the appropriate authority) Bob --94eb2c1920465f754405383a4158 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On F= ri, Jul 22, 2016 at 9:34 AM, Eli Zaretskii <eliz@gnu.org> wrote:<= br>
> It should at least = have a google-like search field that lets one
> quickly search for bugs based on subject line, bug id or the full text= of discussions, so one does not have to
> master any field-based searching initially.

That it does have, look near the end of the page.
=

=E2=80=8BGood.=C2=A0 The results seem to c= ome back reasonably quickly as well.=E2=80=8B

=E2=80=8BI would suggest= the following for the web interface:
=C2=A0 - the full text search field = =E2=80=8Bbe added to the home page and be near the top so casual users find= it right away and everyone can use it quickly with navigating to a separat= e page
=C2=A0 - that the status/pending of the issue be displayed (right n= ow only severity is displayed)
=C2=A0 - that there be an easy way to navig= ate from a full text search result connected to a specific bug
=C2=A0 =C2= =A0 to a place where a new comment can be added or a status can be changed = (with the appropriate authority)

Bob


--94eb2c1920465f754405383a4158--