From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: M-x send-emacs-patch Date: Thu, 05 May 2016 11:39:05 +0000 Message-ID: References: <87pot2zoy0.fsf@gnus.org> <874macho0m.fsf@mat.ucm.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1141b0ecaceaf9053216caa3 X-Trace: ger.gmane.org 1462448403 24779 80.91.229.3 (5 May 2016 11:40:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 5 May 2016 11:40:03 +0000 (UTC) To: Yuri Khan , Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 05 13:40:02 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 1ayHdS-0001NC-Fv for ged-emacs-devel@m.gmane.org; Thu, 05 May 2016 13:40:02 +0200 Original-Received: from localhost ([::1]:53226 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayHdO-0003pW-F0 for ged-emacs-devel@m.gmane.org; Thu, 05 May 2016 07:39:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53466) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayHdB-0003Ze-DQ for emacs-devel@gnu.org; Thu, 05 May 2016 07:39:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ayHcz-0000rh-Fn for emacs-devel@gnu.org; Thu, 05 May 2016 07:39:39 -0400 Original-Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]:36357) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayHcy-0000oI-8E for emacs-devel@gnu.org; Thu, 05 May 2016 07:39:33 -0400 Original-Received: by mail-oi0-x233.google.com with SMTP id x201so98962266oif.3 for ; Thu, 05 May 2016 04:39:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=l+RMIYihpMSFqXel0IMDAFdGqDZbFjQzHVWQLiUhyt8=; b=afTbchpd/17oI3Y85d7GorIw8fsqfMM9Nocq9gYOhjwX3Cq6S4/xrpF8qxXndjWyCY JTmhaJLnlp4Jz+DSER9CyfRW4cJljV9n5sQxuAWDlK39q/NnX0fXp81lxr+ESK2Wa2AT n9LVEV16WVrefDpRcBEAVBfoxy7Vwakb4/uD2jahUaEZ24F9EntmIsB/XKiSbQ4KFAeh /s6j8R2IyRyI7LK3z9BGRtQe5KlIfS9Qt3kI/g/Ybxp1/OClw6qjfvFemUqW1WLQYBO5 gQ3M2m2PP3/Ty3aPMEIh5hH5kdoqRuLOcScn92Xr2daa+nBlpXjdrd6DHPIWqDZaBLje vLfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=l+RMIYihpMSFqXel0IMDAFdGqDZbFjQzHVWQLiUhyt8=; b=YPfom0UavpAYoJ7BMKe7c/D2dVoBKiaWo64ujHL4fxaG7bJrreKZZxdRV9uwOeVDtf 9LOcZjemLV3yykfdWOXrMqTnNo+TX9TMizLrCJ2bnkCGHCOCyj2Ll1Uel9ot56aER2JJ ryMfCvxKCrvk1EuBEHU0YyMVIs21giPTjOJkqyq6VKIhDKotBpKm6+N+4TPWLKT2cQsB AWiKAfhHk0XI66W5mljSMzQB+ylyHya7QmnBE1IOZYwLzhA/sZdQqpD5GjBgLMtsjICo gi5sP4wvhpZ95SBVQZIOiPfxsQWdUyvzRPhMHX3PtaP3t+58As+R/TgyBmWXW2TcOQOr F2Wg== X-Gm-Message-State: AOPr4FVyCxQrODViSk9Nc+lpRm05KrCGEANaJq8LhxqZcLc6DHHy9rVmLJtvcJSnBdnC8nTi3SImtLjOsKBdXQ== X-Received: by 10.202.231.11 with SMTP id e11mr5713863oih.159.1462448354550; Thu, 05 May 2016 04:39:14 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c06::233 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:203600 Archived-At: --001a1141b0ecaceaf9053216caa3 Content-Type: text/plain; charset=UTF-8 That's a neat idea. So instead of a new send-emacs-patch function, should we simply make it an alias for report-emacs-bug. Then we need to just add more info in report-emacs-bug docstring and reword the email body to that they would apply to bug reports, feature requests and patch submissions. Or.. Instead of a new function, rename report-emacs-bug to non-interactive function report-emacs that accepts arguments like 'bug, 'feature or 'patch. Then based on the argument, we can have different wording in the email body, choose to dump the user's emacs state containing variables, last executed commands, etc. Then we have wrapper interactive functions like report-emacs-bug, request-emacs-feature and send-emacs-patch that calls that same base function with different arguments. On Thu, May 5, 2016, 6:31 AM Yuri Khan wrote: > On Thu, May 5, 2016 at 3:06 PM, Uwe Brauer wrote: > > > But we are supposed to send features request via report-emacs-bug which > > is also odd. > > (defalias request-emacs-feature report-emacs-bug)? :) > > -- -- Kaushal Modi --001a1141b0ecaceaf9053216caa3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

That's a neat idea.

So instead of a new send-emacs-patch function, should we sim= ply make it an alias for report-emacs-bug.

Then we need to just add more info in report-emacs-bug docst= ring and reword the email body to that they would apply to bug reports, fea= ture requests and patch submissions.

Or..

Instead of a new function, rename report-emacs-bug to non-in= teractive function report-emacs that accepts arguments like 'bug, '= feature or 'patch. Then based on the argument, we can have different wo= rding in the email body, choose to dump the user's emacs state containi= ng variables, last executed commands, etc.

Then we have wrapper interactive functions like report-emacs= -bug, request-emacs-feature and send-emacs-patch that calls that same base = function with different arguments.


On Thu, May 5, 2016, 6:31 A= M Yuri Khan <yuri.v.khan@gmail.= com> wrote:
On Thu, May 5, 2= 016 at 3:06 PM, Uwe Brauer <oub@mat.ucm.es> wrote:

> But we are supposed to send features request via report-emacs-bug whic= h
> is also odd.

(defalias request-emacs-feature report-emacs-bug)? :)

--

--
Kaushal Modi

--001a1141b0ecaceaf9053216caa3--