From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Emacs project mission (was Re: "If you're still seeing problems, please reopen." [ Date: Tue, 26 Nov 2019 16:18:57 +0100 Message-ID: References: <20191117113054.49837.qmail@mail.muc.de> <87pnhq7mxg.fsf@gnus.org> <87bltaz9g4.fsf@telefonica.net> <834kz25qp9.fsf@gnu.org> <87y2wexsv1.fsf@telefonica.net> <20191118175639.08d02820@jabberwock.cb.piermont.com> <874kz0pa9y.fsf@gnus.org> <87sgmjyn60.fsf@gmx.de> <87imnezyt5.fsf@gmx.de> <481a1f16-d661-0f96-2f45-3d5ec9c1132e@yandex.ru> <871ru0t7p8.fsf@gnus.org> <7a7f8955-ec5f-4e1e-b258-19379588516a@default> <86sgmftq1m.fsf@zoho.eu> <87a78k8mka.fsf@osv.gnss.ru> <868so4bdsi.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="7968"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Richard Stallman , Emanuel Berg , Emacs developers To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 26 16:19:22 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iZccc-0001s8-73 for ged-emacs-devel@m.gmane.org; Tue, 26 Nov 2019 16:19:22 +0100 Original-Received: from localhost ([::1]:56256 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZcca-0001bv-Pf for ged-emacs-devel@m.gmane.org; Tue, 26 Nov 2019 10:19:20 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56448) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZccS-0001bp-SN for emacs-devel@gnu.org; Tue, 26 Nov 2019 10:19:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZccR-00089o-Qy for emacs-devel@gnu.org; Tue, 26 Nov 2019 10:19:12 -0500 Original-Received: from mail-pj1-f47.google.com ([209.85.216.47]:43611) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iZccQ-00087A-57; Tue, 26 Nov 2019 10:19:10 -0500 Original-Received: by mail-pj1-f47.google.com with SMTP id a10so8417133pju.10; Tue, 26 Nov 2019 07:19:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RVGmufAgmJztHklTK9OYc19XDillq0c5u2yEaCHyoWE=; b=D6Ft+Omt7URwpnzey0rAIVS+RPWUjoMMbawuOinrhx/Gogxxq7nWKJ5GhbgFDJ1N4k 3W6oXRWX75ZKqgFKeYvglY8w+qt9QQVGi3anFIZJHat1q2pazNMm3alEYw/hftLcw5nx aZAIYK8/6hhCf6DilV5ISYT4J+3kaTMY14x4EBIQAPV1bhBPRM7Nq5YbWMXN7BGx4vH9 1QjtPwbjeyUZEm1siZh2WdWdW23TJRYNQXfCSEWH3wudSfiRDtYDX1S/7AUlNKDZCPft 2iiSdMevyQM+MjXVF7PXg+zdWpt9q/xF/Lp1WGFn+qluwy/hMKwkxYsDrZ7co8+QwCsB D/Ow== X-Gm-Message-State: APjAAAVkJ9LP/39vyj7whf5gsVwc8Uxej56XxvEK6PxI2zsRenfwJrRr qwFQv9z/XVXRzUvU3JsG5/mfrnBohRulOd3f2Y0= X-Google-Smtp-Source: APXvYqyfv3fBHKGPst1SjE54ucAHXcEDzdz0HW1dp5QiXcjsoCgsyQp1/3gVaCra6FTTbHbVvEpwfKfjP0uFOS9SAXw= X-Received: by 2002:a17:90a:c89:: with SMTP id v9mr945601pja.1.1574781549035; Tue, 26 Nov 2019 07:19:09 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.216.47 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:242735 Archived-At: Drew Adams writes: > > I have two ideas for changes: > > * Ask whether to include this part. > > * Inform people that they could delete it if > > they don't want it posted to the bug tracker. > > Or offer the choice - via an option. I don't think this is a good fit for an option, since whether or not to include this data or not will be highly situational. > 2. There are individual commands to insert each of> the various fields, so you can easily include > any that you don't choose to include by default. > Most are bound to keys with prefix `c-o'. > > `ebp-insert-all' > `ebp-insert-features' (`C-o f') > `ebp-insert-load-path-shadows' (`C-o l') > `ebp-insert-major-mode' (`C-o j') > `ebp-insert-minor-modes' (`C-o n') > `ebp-insert-recent-input' (`C-o i') > `ebp-insert-recent-messages' (`C-o m') > `ebp-insert-settings' (`C-o s') > `ebp-insert-version' That seems like more typing (and remembering) than I'd prefer. If we want to do something like this, my ideal would be closer to how magit handles chunks: 'n' to go to next, 'k' to kill it. To elaborate, let's say I move point outside the "body text" part of the bug report, on top of the auto generated data. Here, the current "block" (as detailed above: features, load-path-shadows, major-mode, etc.) gets highlighted, and the keys no longer does self-insert-comand, but instead the commands: 'n' move to next block 'p' move to previous block 'e' edit current block (make "block" into regular text, disabling commands) 'k' kill current block Even better if you see a help text in the minibuffer when point is on these blocks. Just an idea. Not sure if it's worth implementing, but I think it would be useful. Best regards, Stefan Kangas