unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Jude DaShiell <jdashiel@panix.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: report-bug is also broken in emacs
Date: Sun, 5 Jul 2015 22:41:21 +0300	[thread overview]
Message-ID: <55998861.9070507@yandex.ru> (raw)
In-Reply-To: <alpine.NEB.2.11.1507051519230.12588@panix2.panix.com>

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.



  parent reply	other threads:[~2015-07-05 19:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05 17:07 report-bug is also broken in emacs Jude DaShiell
2015-07-05 17:20 ` Dmitry Gutov
2015-07-05 17:30   ` Jude DaShiell
2015-07-05 17:37     ` Óscar Fuentes
2015-07-05 17:25 ` Óscar Fuentes
2015-07-05 18:59   ` Jude DaShiell
2015-07-05 19:06     ` Dmitry Gutov
2015-07-05 19:09       ` Jude DaShiell
2015-07-05 21:41         ` Drew Adams
     [not found]       ` <alpine.NEB.2.11.1507051519230.12588@panix2.panix.com>
2015-07-05 19:41         ` Dmitry Gutov [this message]
2015-07-05 19:57           ` Jude DaShiell
2015-07-05 20:05             ` Dmitry Gutov
     [not found]           ` <mailman.6396.1436126271.904.help-gnu-emacs@gnu.org>
2015-07-06  1:39             ` Dan Espen
2015-07-05 20:02     ` Óscar Fuentes
2015-07-06  3:31       ` Jude DaShiell

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55998861.9070507@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jdashiel@panix.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).