report-bug is also broken in emacs

report-bug is also broken in emacs

[Jude DaShiell]

It allows at most one line of text if that for describing how to reproduce 
a bug.  What I found with saveplace would need more than one line to 
explain but not much more than one line.  So all of this is unreportable.



--

Re: report-bug is also broken in emacs

[Dmitry Gutov]

What's report-bug? M-x report-emacs-bug?

On 07/05/2015 08:07 PM, Jude DaShiell wrote:
> It allows at most one line of text if that for describing how to
> reproduce a bug.

Why do you think so?

What actions have you tried, and what have you seen as a result?

Re: report-bug is also broken in emacs

[Óscar Fuentes]

Jude DaShiell <jdashiel@panix.com> writes:

> It allows at most one line of text if that for describing how to
> reproduce a bug.  What I found with saveplace would need more than one
> line to explain but not much more than one line.  So all of this is
> unreportable.

Just after M-x report-emacs-bug (not report-bug) the user is prompted
for a one-line short description which acts as a summary. Then a buffer
is shown prefiled with relevant info about your configuration. There,
you can write all the details about your report, with no length limit.

Are you saying that you don't see the buffer mentioned above?

Re: report-bug is also broken in emacs

[Jude DaShiell]

m-x report-emacs-bug just returns no match in emacs 24.51 over here.
On 
Sun, 5 Jul 2015, Dmitry Gutov wrote:

> Date: Sun, 5 Jul 2015 13:20:56
> From: Dmitry Gutov <dgutov@yandex.ru>
> To: Jude DaShiell <jdashiel@panix.com>, help-gnu-emacs@gnu.org
> Subject: Re: report-bug is also broken in emacs
> 
> What's report-bug? M-x report-emacs-bug?
>
> On 07/05/2015 08:07 PM, Jude DaShiell wrote:
>> It allows at most one line of text if that for describing how to
>> reproduce a bug.
>
> Why do you think so?
>
> What actions have you tried, and what have you seen as a result?
>

-- 

Re: report-bug is also broken in emacs

[Óscar Fuentes]

Jude DaShiell <jdashiel@panix.com> writes:

> m-x report-emacs-bug just returns no match in emacs 24.51 over here.

In the Help menu do you see "Send Bug Report..." ?

What's the output of

M-x version

?

Re: report-bug is also broken in emacs

[Jude DaShiell]

This gets even more interesting.
First time I run m-x report-emacs-bug I get a no match error so hit c-g.
Then I run m-x report-bug and get into a form and fill it as best I can.
next when I run m-x report-emacs-bug this time m-x report-emacs-bug 
works.
Only thing I can figure is the m-x report-bug triggered something that 
made m-x report-emacs-bug work that third time around.

On Sun, 5 Jul 2015, ?scar Fuentes wrote:

> Date: Sun, 5 Jul 2015 13:25:16
> From: ?scar Fuentes <ofv@wanadoo.es>
> To: help-gnu-emacs@gnu.org
> Subject: Re: report-bug is also broken in emacs
> 
> Jude DaShiell <jdashiel@panix.com> writes:
>
>> It allows at most one line of text if that for describing how to
>> reproduce a bug.  What I found with saveplace would need more than one
>> line to explain but not much more than one line.  So all of this is
>> unreportable.
>
> Just after M-x report-emacs-bug (not report-bug) the user is prompted
> for a one-line short description which acts as a summary. Then a buffer
> is shown prefiled with relevant info about your configuration. There,
> you can write all the details about your report, with no length limit.
>
> Are you saying that you don't see the buffer mentioned above?
>
>
>

-- 

Re: report-bug is also broken in emacs

[Dmitry Gutov]

On 07/05/2015 09:59 PM, Jude DaShiell wrote:
> This gets even more interesting.
> First time I run m-x report-emacs-bug I get a no match error so hit c-g.
> Then I run m-x report-bug and get into a form and fill it as best I can.
> next when I run m-x report-emacs-bug this time m-x report-emacs-bug works.
> Only thing I can figure is the m-x report-bug triggered something that
> made m-x report-emacs-bug work that third time around.

You seem to have a broken Emacs setup (or installation).

Have you tried starting with 'emacs -Q'?

Re: report-bug is also broken in emacs

[Jude DaShiell]

I think I can probably reproduce both the saveplace bug and what happens 
with emacs-report-bug using script and saving a typescript file and then 
I could put those typescript files up in web space for anyone interested 
to download.

On Sun, 5 Jul 2015, Dmitry Gutov wrote:

> Date: Sun, 5 Jul 2015 15:06:09
> From: Dmitry Gutov <dgutov@yandex.ru>
> To: Jude DaShiell <jdashiel@panix.com>, ?scar Fuentes <ofv@wanadoo.es>,
>     help-gnu-emacs@gnu.org
> Subject: Re: report-bug is also broken in emacs
> 
> On 07/05/2015 09:59 PM, Jude DaShiell wrote:
>> This gets even more interesting.
>> First time I run m-x report-emacs-bug I get a no match error so hit c-g.
>> Then I run m-x report-bug and get into a form and fill it as best I can.
>> next when I run m-x report-emacs-bug this time m-x report-emacs-bug works.
>> Only thing I can figure is the m-x report-bug triggered something that
>> made m-x report-emacs-bug work that third time around.
>
> You seem to have a broken Emacs setup (or installation).
>
> Have you tried starting with 'emacs -Q'?
>

-- 

Re: report-bug is also broken in emacs

[Dmitry Gutov]

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.

Re: report-bug is also broken in emacs

[Jude DaShiell]

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 <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
> 
> 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.
>
>

-- 

Re: report-bug is also broken in emacs

[Óscar Fuentes]

Jude DaShiell <jdashiel@panix.com> writes:

> This gets even more interesting.

What about the output of M-x version I asked for on my previous message?

[snip]

Re: report-bug is also broken in emacs

[Dmitry Gutov]

On 07/05/2015 10:57 PM, Jude DaShiell wrote:
> 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.

Thanks. Maybe someone else can look at it and tell if something specific 
looks wrong.

In the meantime, I recommend starting with 'emacs -Q'.

RE: report-bug is also broken in emacs

[Drew Adams]

> I think I can probably reproduce both the saveplace bug and what
> happens with emacs-report-bug using script and saving a typescript
> file and then I could put those typescript files up in web space
> for anyone interested to download.

Narrow it down yourself first, please.  Start with `emacs -Q'
(no init file).  Add whatever else you need to do to repro the
problem, noting explicitly each thing that is _necessary_ to
repro it, in an explicit, step-by-step recipe.  Post only that,
instead of a typescript file full of who-knows-what.

If you don't see the problem when you start with just `emacs -Q'
then you can recursively bisect your init file to locate what
is causing the problem.  You can do that by commenting out 1/2,
then 3/4, 7/8,... of the file and restarting Emacs each time.

Doing that, you might well discover for yourself what the
problem is and how to fix it.  More importantly, you will have
located the problem: narrowed it down and given others a way
to repro it instead of having to guess all that you might have
done.

Re: report-bug is also broken in emacs

[Dan Espen]

Jude DaShiell <jdashiel@panix.com> writes:

> 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.

Top posting in the middle of a conversation???

That script file is going to be an unreadable mess, as the man page
for script warns you.

-- 
Dan Espen

Re: report-bug is also broken in emacs

[Jude DaShiell]

Not all of the text remained on the display so I used script to capture 
output:

Script started on Sun 05 Jul 2015 11:26:22 PM EDT
The Moon is Waning Gibbous (79% of Full)
Time: 11:26:22 PM
  Date: Sunday July 5 2015
  Week: 27
  Day Of Year: 186
Astrolog 5.40 chart for Sun Jul  5, 2015 11:26pm (ST -4:00 GMT)  76:02W 38:01N
Body  Locat. Ret. Lati. Rul.      House  Rul. Veloc.    Placidus Houses.

Sun : 13Can47   - 0:00' (-) [ 5th house] [R] +0.953  -  House cusp  1: 12Pis39
Moon:  7Pis49   + 2:16' (-) [12th house] [-] ______  -  House cusp  2: 26Ari44
Merc: 25Gem28   - 1:14' (R) [ 4th house] [-] +1.643  -  House cusp  3: 27Tau00
Venu: 24Leo38   - 0:08' (-) [ 6th house] [d] +0.579  -  House cusp  4: 20Gem13
Mars:  7Can46   + 0:47' (d) [ 4th house] [d] +0.667  -  House cusp  5: 11Can54
Jupi: 22Leo28   + 0:52' (-) [ 6th house] [F] +0.192  -  House cusp  6:  6Leo49
Satu: 28Sco47 R + 2:05' (-) [ 9th house] [-] -0.041  -  House cusp  7: 12Vir39
Uran: 20Ari21   - 0:38' (-) [ 1st house] [-] +0.016  -  House cusp  8: 26Lib44
Nept:  9Pis40 R - 0:48' (R) [12th house] [R] -0.012  -  House cusp  9: 27Sco00
Plut: 14Cap14 R + 1:59' (-) [11th house] [-] -0.025  -  House cusp 10: 20Sag13
Chir: 22Pis06 R + 4:37' (R) [ 1st house] [-] -0.010  -  House cusp 11: 11Cap54
Cere:  7Aqu07 R - 9:36' (-) [12th house] [-] -0.177  -  House cusp 12:  6Aqu49
Pall: 18Sag02 R +47:20' (-) [ 9th house] [-] -0.219
Juno:  3Vir55   - 0:17' (-) [ 6th house] [-] +0.359     Car Fix Mut TOT   +:10
Vest: 13Ari22   - 7:04' (-) [ 1st house] [-] +0.260  Fir  3   2   2   7   -:12
Node:  5Lib05 R + 0:00' (-) [ 7th house] [-] ______  Ear  1   0   2   3   M: 8
S.No:  5Ari05 R + 0:00' (-) [ 1st house] [-] ______  Air  1   1   1   3   N:12
Fort: 18Can36   _______ (-) [ 5th house] [-] ______  Wat  3   1   5   9   A: 9
Vert: 22Vir33   _______ (d) [ 7th house] [R] ______  TOT  8   4  10  22   D:11
East: 18Pis26   _______ (-) [ 1st house] [R] ______                       <:11
[jude@athame1 ~]$ emacs










^[[?25h^[[?8c^[[H^[[J^[[25d^[[K^[[?25h^[[?0c^[[39;49m
























^[[?25h^[[?8c^[[H^[[J^[[24d^[[?25l^[[?1c^[[7m-UUU:----F1  ^[[0m^[[39;49m^[[27m^[[7m^[[1m*scratch*   ^[[0m^[[39;49m^[[27m^[[7m   All L1     (Fundamental) ---------------------------^[[0m^[[39;49m^[[27m
^[[A^[[2d^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[?25l^[[?1cLoading /usr/share/emacs/site-lisp/ess/ess-site...^[[K^[[H
^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[?25l^[[?1cad-handle-definition: `ido-completing-read' got redefined^[[H
^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[?25l^[[?1cLoading /usr/share/emacs/site-lisp/ess/ess-site...done^[[K^[[H
^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[?25l^[[?1cFor information about GNU Emacs and the GNU system, type C-h C-a.^[[H
^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[?25l^[[?1cFor information about GNU Emacs and the GNU system, type C-h C-a.^[[K^[[H^[[7mFile Edit Options Buffers Tools Lisp-Interaction Help                           ^[[0m^[[39;49m^[[27m
^[[A
^[[33m;; This buffer is for notes you don't want to save, and for Lisp evaluation.    ^[[39;49m
^[[A
^[[33m;; If you want to create a file, visit that file with C-x C-f,                  ^[[39;49m
^[[A
^[[33m;; then enter the text in that file's own buffer.                               ^[[39;49m
^[[A
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[K
^[[7m-UUU:----F1  ^[[0m^[[39;49m^[[27m^[[7m^[[1m*scratch*   ^[[0m^[[39;49m^[[27m^[[7m   All L5     (Lisp Interaction) ----------------------^[[0m^[[39;49m^[[27m
^[[A^[[6d^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[?25l^[[?1c^[[36mM-x ^[[39;49m^[[K^[[1;33H^[[7mMinibuf Help         ^[[0m^[[39;49m^[[27m^[[25;5H^[[?25h^[[?0c^[[?25h^[[?8c^[[?25l^[[?1cv^[[?25h^[[?0c^[[?25h^[[?8c^[[?25l^[[?1ce^[[?25h^[[?0c^[[?25h^[[?8c^[[?25l^[[?1cr^[[?25h^[[?0c^[[?25h^[[?8c^[[?25l^[[?1cs^[[?25h^[[?0c^[[?25h^[[?8c^[[?25l^[[?1ci^[[?25h^[[?0c^[[?25h^[[?8c^[[?25l^[[?1co^[[?25h^[[?0c^[[?25h^[[?8c^[[?25l^[[?1cn^[[?25h^[[?0c^[[?25h^[[?8c
^[[1;24r^[[23;1H^[[1M^[[1;25r^[[25;1H^[[?25l^[[?1con bitzer.hoetzel.info^[[1;33H^[[7mLisp-Interaction Help^[[0m^[[39;49m^[[27m^[[24;1HGNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2) of 2015-04-20 \
^[[A^[[6d^[[?25h^[[?0c^[[?25h^[[?8c^[[1;24r^[[23;1H^[[1L^[[1;25r^[[25;1H^[[K^[[23d^[[K^[[6d^[[25d^[[?25l^[[?1cC-x^[[6;1H^[[?25h^[[?0c^[[?25h^[[?8c^[[25;4H^[[?25l^[[?1c-^[[6;1H^[[?25h^[[?0c^[[?25h^[[?8c^[[25;4H^[[?25l^[[?1c C-c^[[6;1H^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[K^[[6d^[[25d^[[?25l^[[?1c(No files need saving)^[[6;1H^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[?25l^[[?1cWrote /home/jude/.emacs.d/places^[[6;1H^[[?25h^[[?0c^[[?25h^[[?8c^[[25d^[[K^[[?25h^[[?0c^[[39;49m
[jude@athame1 ~]$ exit
exit

Script done on Sun 05 Jul 2015 11:26:56 PM EDT
On Sun, 5 Jul 2015, ?scar Fuentes wrote:

> Date: Sun, 5 Jul 2015 16:02:06
> From: ?scar Fuentes <ofv@wanadoo.es>
> To: help-gnu-emacs@gnu.org
> Subject: Re: report-bug is also broken in emacs
> 
> Jude DaShiell <jdashiel@panix.com> writes:
>
>> This gets even more interesting.
>
> What about the output of M-x version I asked for on my previous message?
>
> [snip]
>
>
>

--