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 15:58:19 +0000 Message-ID: References: <87pot2zoy0.fsf@gnus.org> <874macho0m.fsf@mat.ucm.es> <87oa8kzne5.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113ce01ccf006a05321a6925 X-Trace: ger.gmane.org 1462463970 19881 80.91.229.3 (5 May 2016 15:59:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 5 May 2016 15:59:30 +0000 (UTC) Cc: Emacs developers , Yuri Khan To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 05 17:59:27 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 1ayLgU-0005jk-At for ged-emacs-devel@m.gmane.org; Thu, 05 May 2016 17:59:26 +0200 Original-Received: from localhost ([::1]:54212 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayLgN-00031z-Ez for ged-emacs-devel@m.gmane.org; Thu, 05 May 2016 11:59:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40893) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayLg3-0002ok-UI for emacs-devel@gnu.org; Thu, 05 May 2016 11:59:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ayLfs-00034z-D1 for emacs-devel@gnu.org; Thu, 05 May 2016 11:58:54 -0400 Original-Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]:36693) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayLfr-0002xh-5d for emacs-devel@gnu.org; Thu, 05 May 2016 11:58:48 -0400 Original-Received: by mail-oi0-x233.google.com with SMTP id x201so107536031oif.3 for ; Thu, 05 May 2016 08:58:32 -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 :cc; bh=CVxDtR2Q5qzYe/c802cTmWFfx/V8E7+SAhmzZyj1M4w=; b=Y5xWkZXzs4zdSZI+YhldDIwlPclQvt/1wokdmCWZP1AW5ozuih3mHZ39pI8GISv8Bg WUhbacjOXnotMDIQS8w9MFxHEFzlJuNj4k8bBdoe7SUI718rHxFTNC7psryUtLh2kUz5 DIXKbyM7H236NC8Dfsq9e1SVUf2WLmW3adAJju+C2ovDGu1tkWivuQdlJUNqCa97IMNU ++P7tQEcq2mGF0jQUB/A3FdwZv+sfWoTO5+tlmNU84MhN5e7jye6coyQXeEvI3ZdPDxw Mhx4i3/0F7M6213gZqjJTiaw/D1geFdTBIjAHtfxB2fUdAkEezwI5udBKABswvLaaaRV KfUw== 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:cc; bh=CVxDtR2Q5qzYe/c802cTmWFfx/V8E7+SAhmzZyj1M4w=; b=nCU08NxodkJfVZFwlIY1niRTr/uks2Ngj2uh5JpRcZSQz+9WtQy+Iq3awheyCd+MpN KUrxfWTpUhWDF5XSlypHslYkNgfCRzlglzC5otVemXA2JSBKtVjiKIbCu3CMMZC7s6vu uNakzwr/slokqPyWPml1iFZBRN3LU9YahsPmvjNrPGmQ1kumihaW4wgUtacbzmG3qCDM i780DrtZUWX4s34td50l4UfkzusaERLZJKiKJ/2SdVPujrcA94WC17aUAFAz1q+2Tm7P 0P5ZzfzS0Tx4JQhJ0LZft5TB4XJFTikIMppfYwkY6ajf05rupIN7GXAKcTufLvhQak6S /vZw== X-Gm-Message-State: AOPr4FXPvNcmyQRBlC95vc1L6iiRgGnhud1I2WK3UsT01FHGyrHB6gTPhuUD9lFTQoMroj6QYiVN2KxlOpvdsQ== X-Received: by 10.202.60.194 with SMTP id j185mr6512981oia.197.1462463909263; Thu, 05 May 2016 08:58:29 -0700 (PDT) In-Reply-To: <87oa8kzne5.fsf@gnus.org> 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:203605 Archived-At: --001a113ce01ccf006a05321a6925 Content-Type: text/plain; charset=UTF-8 > > > So instead of a new send-emacs-patch function, should we simply make it > an > > alias for report-emacs-bug. > > No, the new function would not snarf the Emacs environment, and it would > have a different text. So it'd be a completely different function. That's what I thought too, and so had also proposed the alternative: > 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. -- -- Kaushal Modi --001a113ce01ccf006a05321a6925 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
= > So instead of a new send-emacs-patch function, should we simply make i= t an
> alias for report-emacs-bug.

No, the new function would not snarf the Emacs environment, and it would have a different text.=C2=A0 So it'd be a completely different function= .

That's what I thought too, and so had= also proposed the alternative:

> Or..

> Instead of a new function, rename r= eport-emacs-bug to non-interactive function report-emacs that accepts argum= ents like 'bug, 'feature or 'patch. Then based on the argument,= we can have different wording in the email body, choose to dump the user&#= 39;s emacs state containing variables, last executed commands, etc.

> Th= en we have wrapper interactive functions like report-emacs-bug, request-ema= cs-feature and send-emacs-patch that calls that same base function with dif= ferent arguments.=C2=A0
--

--
Kaushal Modi

--001a113ce01ccf006a05321a6925--