all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Development suggestions from an ENSIME developer
Date: Fri, 22 Jul 2016 10:28:30 -0400	[thread overview]
Message-ID: <CA+OMD9hDZtx=PNY4edcdu+Lko4hLH9xS=RDMvcX8O-FgSLhkmA@mail.gmail.com> (raw)
In-Reply-To: <83vazxx0dz.fsf@gnu.org>

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

On Fri, Jul 22, 2016 at 9:34 AM, Eli Zaretskii <eliz@gnu.org> 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.


​Good.  The results seem to come back reasonably quickly as well.​

​I would suggest the following for the web interface:
  - the full text search field ​be 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 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

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

  reply	other threads:[~2016-07-22 14:28 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 13:54 Development suggestions from an ENSIME developer Lars Ingebrigtsen
2016-07-20 14:02 ` Clément Pit--Claudel
2016-07-22 22:48   ` Robert Cochran
2016-07-23  7:30     ` Eli Zaretskii
2016-07-23  9:00     ` Lars Ingebrigtsen
2016-07-23 19:52       ` Richard Stallman
2016-07-23 13:50     ` Clément Pit--Claudel
2016-07-23 20:14     ` Phillip Lord
2016-07-25 18:34       ` Robert Cochran
2016-08-03  6:05   ` John Wiegley
2016-08-06 18:42     ` Alex Dunn
2016-07-20 14:03 ` Dmitry Gutov
2016-07-20 14:08   ` Lars Ingebrigtsen
2016-07-20 14:12     ` Dmitry Gutov
2016-07-20 14:23       ` Christian Kruse
2016-07-20 14:41         ` Dmitry Gutov
2016-07-20 14:30 ` Christian Kruse
2016-07-20 14:44   ` Lars Ingebrigtsen
2016-07-20 15:02     ` Clément Pit--Claudel
2016-07-20 15:07       ` Lars Ingebrigtsen
2016-07-20 15:31         ` Clément Pit--Claudel
2016-07-20 17:00 ` Stefan Monnier
2016-07-21 18:40   ` Phillip Lord
2016-07-21 19:30     ` Eli Zaretskii
2016-07-21 20:22       ` Stefan Monnier
2016-07-21 21:26         ` Christian Kruse
2016-07-21 22:04         ` Dmitry Gutov
2016-07-21 20:23       ` Phillip Lord
2016-07-21 20:50         ` joakim
2016-07-22  6:59         ` Eli Zaretskii
2016-07-22 10:46           ` Lars Ingebrigtsen
2016-07-22 11:48             ` Lars Ingebrigtsen
2016-07-22 13:00               ` Robert Weiner
2016-07-22 13:34                 ` Eli Zaretskii
2016-07-22 14:28                   ` Robert Weiner [this message]
2016-07-22 14:45             ` Ted Zlatanov
2016-07-22 13:35           ` Stefan Monnier
2016-07-22 14:38             ` Eli Zaretskii
2016-07-22 14:56               ` Stefan Monnier
2016-07-22 15:58                 ` Phillip Lord
2016-07-22 15:47           ` Phillip Lord

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='CA+OMD9hDZtx=PNY4edcdu+Lko4hLH9xS=RDMvcX8O-FgSLhkmA@mail.gmail.com' \
    --to=rsw@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=rswgnu@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.