all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: larsi@gnus.org, Emacs developers <emacs-devel@gnu.org>,
	Tino Calancha <tino.calancha@gmail.com>
Subject: Re: debbugs-0.10: two comments
Date: Mon, 12 Sep 2016 16:46:09 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1609121645070.31277@calancha-pc> (raw)
In-Reply-To: <87wpihr2t7.fsf@gmx.de>



On Mon, 12 Sep 2016, Michael Albinus wrote:

> Tino Calancha <tino.calancha@gmail.com> writes:
>
> Hi Tino,
>
>>> I have already plans to extend debbugs-gnu-bugs and debbugs-org-bugs.
>>> Currently, they allow only list of bug numbers, like "100,200,300" etc.
>>> I want to allow also ranges, like "100-200,300-400" and so on. A special
>>> range "-10" could mean then "the last 10 bugs". This shall fit your needs.
>> That sounds great!
>> Maybe worth to provide the command for latest bugs with a nice
>> default. It is handy not having to write in the minibuffer the range
>> for this: just
>> RET to accept the default value is very pleasant.
>
> Good idea. Will use "-10" as default, and will make the default customizable.
Great, i love the idea of having a customizable default: that improve my 
original idea.
Thank you!



  reply	other threads:[~2016-09-12  7:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12  6:08 debbugs-0.10: two comments Tino Calancha
2016-09-12  7:05 ` Michael Albinus
2016-09-12  7:24   ` Tino Calancha
2016-09-12  7:32     ` Michael Albinus
2016-09-12  7:46       ` Tino Calancha [this message]
2016-09-13 12:06   ` Michael Albinus
2016-09-23  7:42     ` debbugs-0.10: doc fixes Tino Calancha
2016-09-23 12:40       ` Michael Albinus
2016-09-23 13:14         ` Tino Calancha

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=alpine.DEB.2.20.1609121645070.31277@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    /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.