unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>,
	"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 'Chong Yidong' <cyd@stupidchicken.com>,
	'MON KEY' <monkey@sandpframing.com>,
	5122@debbugs.gnu.org
Subject: bug#5122: Mismatched parentheses when dealing with huge buffercontent
Date: Wed, 13 Jul 2011 10:26:08 -0700	[thread overview]
Message-ID: <E7BFC4DE58E549C992CF93CF169427E8@us.oracle.com> (raw)
In-Reply-To: 

> Stefan says what "clearly, the only real answer" is.
> He says that can be tried, and he makes a suggestion how.
> 
> So why, if that is clearly the answer, do you close the bug?
> Makes no sense.  Is the goal just to close bugs or to fix the problem?
> Is someone getting paid by the bug closure or something? ;-)

And why close it as `fixed' if Emacs Dev will not fix it?
The problem reported is still there, AFAIK.  Why not `wontfix'?






  parent reply	other threads:[~2011-07-13 17:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05 20:57 bug#5122: Mismatched parentheses when dealing with huge buffercontent Chong Yidong
2009-12-05 21:42 ` Stefan Monnier
2009-12-05 22:06   ` Chong Yidong
2009-12-05 21:47 ` Eli Zaretskii
2009-12-05 22:11   ` Chong Yidong
2009-12-06  2:08     ` bug#5122: Mismatched parentheses when dealing with hugebuffercontent Drew Adams
2009-12-06 15:15       ` Drew Adams
2009-12-06 19:13       ` Chong Yidong
2009-12-06 20:57         ` Drew Adams
2009-12-06  4:03     ` bug#5122: Mismatched parentheses when dealing with huge buffercontent Eli Zaretskii
2009-12-06 15:30       ` Chong Yidong
2009-12-06 17:05         ` bug#5122: Mismatched parentheses when dealing with hugebuffercontent Drew Adams
2009-12-06 17:52         ` bug#5122: Mismatched parentheses when dealing with huge buffercontent Eli Zaretskii
2009-12-06 18:59           ` Chong Yidong
2009-12-06 19:23             ` bug#5122: Mismatched parentheses when dealing with hugebuffercontent Drew Adams
2009-12-07  2:25   ` bug#5122: Mismatched parentheses when dealing with huge buffercontent Stefan Monnier
2011-07-13 14:59     ` Lars Magne Ingebrigtsen
2011-07-13 16:35       ` Drew Adams
2011-07-13 17:26       ` Drew Adams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-08 21:11 MON KEY
2009-12-04 15:31 bug#5122: Mismatched parentheses when dealing with huge buffer content Deniz Dogan
2009-12-04 22:27 ` bug#5122: Mismatched parentheses when dealing with huge buffercontent Drew Adams
2009-12-05  0:27   ` Deniz Dogan
2009-12-05  0:31     ` Drew Adams
2009-12-05  0:35       ` Deniz Dogan
2009-12-05  9:27       ` Eli Zaretskii
2009-12-05 16:10         ` Drew Adams

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=E7BFC4DE58E549C992CF93CF169427E8@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=5122@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=larsi@gnus.org \
    --cc=monkey@sandpframing.com \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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