From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jude DaShiell Newsgroups: gmane.emacs.help Subject: Re: report-bug is also broken in emacs Date: Sun, 5 Jul 2015 15:57:45 -0400 (EDT) Message-ID: References: <87d206pldv.fsf@wanadoo.es> <55998021.2070108@yandex.ru> <55998861.9070507@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: ger.gmane.org 1436126293 13002 80.91.229.3 (5 Jul 2015 19:58:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 5 Jul 2015 19:58:13 +0000 (UTC) Cc: help-gnu-emacs To: Dmitry Gutov Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Jul 05 21:58:02 2015 Return-path: Envelope-to: geh-help-gnu-emacs@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 1ZBq36-0001vM-4w for geh-help-gnu-emacs@m.gmane.org; Sun, 05 Jul 2015 21:58:00 +0200 Original-Received: from localhost ([::1]:47513 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZBq35-0008Gz-Fu for geh-help-gnu-emacs@m.gmane.org; Sun, 05 Jul 2015 15:57:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZBq2u-0008Gr-TX for help-gnu-emacs@gnu.org; Sun, 05 Jul 2015 15:57:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZBq2r-00072x-Me for help-gnu-emacs@gnu.org; Sun, 05 Jul 2015 15:57:48 -0400 Original-Received: from mailbackend.panix.com ([166.84.1.89]:52129) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZBq2r-00072t-Im for help-gnu-emacs@gnu.org; Sun, 05 Jul 2015 15:57:45 -0400 Original-Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mailbackend.panix.com (Postfix) with ESMTP id 4F44316B3A; Sun, 5 Jul 2015 15:57:45 -0400 (EDT) Original-Received: by panix1.panix.com (Postfix, from userid 20712) id 3ABD314B9A; Sun, 5 Jul 2015 15:57:45 -0400 (EDT) Original-Received: from localhost (localhost [127.0.0.1]) by panix1.panix.com (Postfix) with ESMTP id 39E5F14B5C; Sun, 5 Jul 2015 15:57:45 -0400 (EDT) In-Reply-To: <55998861.9070507@yandex.ru> User-Agent: Alpine 2.11 (NEB 23 2013-08-11) X-detected-operating-system: by eggs.gnu.org: GNU/Linux (Android) X-Received-From: 166.84.1.89 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:105468 Archived-At: There is a script command in Linux. When it works, it captures everything that goes to stdin stdout and stderr and saves that in a file usually called typescript. Anything happening on a linux terminal visible to the user and what goes to stdout gets put in the typescript file. The man script command should explain better than I'm doing here for you. On Sun, 5 Jul 2015, Dmitry Gutov wrote: > Date: Sun, 5 Jul 2015 15:41:21 > From: Dmitry Gutov > To: Jude DaShiell > Cc: help-gnu-emacs > Subject: Re: report-bug is also broken in emacs > > Please keep help-gnu-emacs in Cc. > > On 07/05/2015 10:25 PM, Jude DaShiell wrote: >> If you want to see what's going on, >> http://www.panix.com/~jdashiel/typescript >> has that information. > > Sorry, I have no idea what I'm supposed to be looking at. The page contains a > lot of text (some of it looking Emacs-y), as well as lots of unreadable > control characters. > > Again, have you tried reproducing the problem starting with 'emacs -Q'? > > And what typescript are you referring to here? I only know of a programming > language with that name, one that compiles to JavaScript. > >> The last word I keyed in on the description area >> just after subject: was again. If report-emacs-bug did capture it, the >> way the display was showing things it gave me the impression only one >> line had been captured with no lines beyond the first. The subject: >> line was on the last line of my emacs display area too. None of this >> may be a bug, and just appear like a bug due to display placement of >> elements of the report. > > I don't understand this paragraph. > >> I will be interested to find out if that's the >> case and would also like to know what the maximum number of lines is for >> that bug description area too. > > There's no maximum number of lines. After you type in the subject, Emacs > opens a Message buffer, where you can type as long a report as you like. > > --