bug reporting

bug reporting

[Benjamin Dreux]

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

Hi i'm a emacs22 user. I really appreciate it.
Like i say in the titile i found a bug in the parentheses matching. I'm
coding into c++ and i worte that:
bool flotte::continuer()
{
  return nbBateau[5]>nbBateau[6];
}

If you try it you will see that the > thake the place of the }.

In the hope that could help you.
Thanks a lot for the fsf work.
Benjamin DREUX

[-- Attachment #2: Type: text/html, Size: 419 bytes --]

Re: bug reporting

[Chong Yidong]

"Benjamin Dreux" <benjiiiiii@gmail.com> writes:

> Like i say in the titile i found a bug in the parentheses
> matching. I'm coding into c++ and i worte that:
>
> bool flotte::continuer()
> {
>   return nbBateau[5]>nbBateau[6];
> }
>
> If you try it you will see that the > thake the place of the }.

I can't reproduce this.  Could you give a more precise recipe?

Re: bug reporting

[martin rudalics]

> bool flotte::continuer()
> {
>   return nbBateau[5]>nbBateau[6];
> }

Could you please move the cursor immediately before the > type

M-x: describe-char RET

and post here what Emacs tells you.

[lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]

[Richard Stallman]

[I sent this message twice but did not get a response.]

Would someone please DTRT and ack?

------- Start of forwarded message -------
Date: Sat, 16 Dec 2006 14:02:48 +0100
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
MIME-Version: 1.0
To: Emacs Devel <emacs-devel@gnu.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Subject: compilation-previous-error fails if first error is at start of
	buffer
X-Spam-Status: No, score=0.5 required=5.0 tests=FROM_ENDS_IN_NUMS 
	autolearn=no version=3.0.4

If the compilation buffer begins with error lines right at the top:

c:/EmacsW32/etc/EmacsW32Util.html:7:5: Warning: <link> inserting "type" 
attribute
c:/EmacsW32/etc/EmacsW32Util.html:12:19: Warning: <table> lacks 
"summary" attribute
c:/EmacsW32/etc/EmacsW32Util.html:29:5: Warning: <table> lacks "summary" 
attribute

then if point is on second line compilation-previous-error fails.


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
------- End of forwarded message -------

Re: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]

[Jan Djärv]

Richard Stallman skrev:
> [I sent this message twice but did not get a response.]
> 
> Would someone please DTRT and ack?
> 
> ------- Start of forwarded message -------
> Date: Sat, 16 Dec 2006 14:02:48 +0100
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> MIME-Version: 1.0
> To: Emacs Devel <emacs-devel@gnu.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Subject: compilation-previous-error fails if first error is at start of
> 	buffer
> X-Spam-Status: No, score=0.5 required=5.0 tests=FROM_ENDS_IN_NUMS 
> 	autolearn=no version=3.0.4
> 
> If the compilation buffer begins with error lines right at the top:
> 
> c:/EmacsW32/etc/EmacsW32Util.html:7:5: Warning: <link> inserting "type" 
> attribute
> c:/EmacsW32/etc/EmacsW32Util.html:12:19: Warning: <table> lacks 
> "summary" attribute
> c:/EmacsW32/etc/EmacsW32Util.html:29:5: Warning: <table> lacks "summary" 
> attribute
> 
> then if point is on second line compilation-previous-error fails.
> 

What is the error message?

	Jan D.

Re: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]

[Nick Roberts]

 > > If the compilation buffer begins with error lines right at the top:
 > > 
 > > c:/EmacsW32/etc/EmacsW32Util.html:7:5: Warning: <link> inserting "type" 
 > > attribute
 > > c:/EmacsW32/etc/EmacsW32Util.html:12:19: Warning: <table> lacks 
 > > "summary" attribute
 > > c:/EmacsW32/etc/EmacsW32Util.html:29:5: Warning: <table> lacks "summary" 
 > > attribute
 > > 
 > > then if point is on second line compilation-previous-error fails.
 > > 
 > 
 > What is the error message?

Warnings and errors are equivalent in the compilation buffer.  I don't see how
Lennart gets error lines right at the top as I always get the following four
lines:

    -*- mode: compilation; default-directory: "~/" -*-
    Compilation started at Mon Jan  8 21:22:48

    `command used for my compilation'


Perhaps this is for his patched version.  Anyway there's not much point fixing
it when, like the heads of the Lernaean Hydra, two new bugs will take it's
place in FOR-RELEASE.


-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]

[Lennart Borgman (gmail)]

Nick Roberts wrote:
>  > > If the compilation buffer begins with error lines right at the top:
>  > > 
>  > > c:/EmacsW32/etc/EmacsW32Util.html:7:5: Warning: <link> inserting "type" 
>  > > attribute
>  > > c:/EmacsW32/etc/EmacsW32Util.html:12:19: Warning: <table> lacks 
>  > > "summary" attribute
>  > > c:/EmacsW32/etc/EmacsW32Util.html:29:5: Warning: <table> lacks "summary" 
>  > > attribute
>  > > 
>  > > then if point is on second line compilation-previous-error fails.
>  > > 
>  > 
>  > What is the error message?
> 
> Warnings and errors are equivalent in the compilation buffer.  I don't see how
> Lennart gets error lines right at the top as I always get the following four
> lines:
> 
>     -*- mode: compilation; default-directory: "~/" -*-
>     Compilation started at Mon Jan  8 21:22:48
> 
>     `command used for my compilation'


The output is from a library not included in Emacs (actually a version 
of tidy.el). The output does not have the lines above at the beginning. 
It would be rather inconvenient if it had, but maybe those line still 
should be there for some reason?


> 
> Perhaps this is for his patched version.  Anyway there's not much point fixing
> it when, like the heads of the Lernaean Hydra, two new bugs will take it's
> place in FOR-RELEASE.

I do not send bug report for the patched version, of course. (And I have 
tried to make it clear on download page on my site that you should use 
the unpatched version for bug reports.)

Here is a way to reproduce the error (CVS Emacs from 2007-01-03):

     emacs -Q
     M-: (switch-to-buffer "TEST")

Paste these lines (inside the "cut lines") into the buffer:

 >>>>> cut here >>>>>>>
c:/EmacsW32/nxml/nxhtml/doc/temp.htm:9:5: Warning: missing </h1> before 
</h3>
c:/EmacsW32/nxml/nxhtml/doc/temp.htm:10:5: Warning: discarding 
unexpected </h3>
c:/EmacsW32/nxml/nxhtml/doc/temp.htm:9:5: Warning: trimming empty <h1>
Info: Doctype given is "-//W3C//DTD XHTML 1.1//EN"
Info: Document content looks like XHTML 1.1
3 warnings, 0 errors were found!
<<<<<<<< cut here <<<<<<<<<<<<

so that the first error is on the first line of the buffer TEST, the 
second error on the second line and the third error on the third line. 
(You may have to edit this a bit because of line breaks in this mail 
message.) Now do

     M-x compilation-mode

Go to the beginning of the buffer. Press TAB. The point should move to 
the second error line. Press TAB again -> to third line.

Now press S-TAB. Should go to second line. S-TAB again should go to 
first line, but it does not.

Is this enough to reproduce it for you?

Bug reporting (was: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer])

[Stefan Monnier]

> I do not send bug report for the patched version, of course. (And I have
> tried to make it clear on download page on my site that you should use the
> unpatched version for bug reports.)

The recommendation should *always* be to do M-x report-emacs-bug.
And make sure that the patched version changes report-emacs-bug-address and
report-emacs-bug-pretest-address to your own address.


        Stefan

Re: Bug reporting

[Lennart Borgman (gmail)]

Stefan Monnier wrote:
>> I do not send bug report for the patched version, of course. (And I have
>> tried to make it clear on download page on my site that you should use the
>> unpatched version for bug reports.)
> 
> The recommendation should *always* be to do M-x report-emacs-bug.
> And make sure that the patched version changes report-emacs-bug-address and
> report-emacs-bug-pretest-address to your own address.


Yes, that is a good way to do it. Less to remember for the users.

And then perhaps include some text that makes the situation clear. 
Something about "try the unpatched version bla bla ....".


I will change this as soon as I get time.