From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: John Wiegley <jwiegley@gmail.com>
Cc: 1092@debbugs.gnu.org, ahyatt@gmail.com
Subject: bug#1092: compilation-goto-error goes to wrong location when buffer has hidden regions
Date: Wed, 06 Jan 2016 23:17:09 -0500 [thread overview]
Message-ID: <jwvd1te81pf.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <m2si2bkd8o.fsf@newartisans.com> (John Wiegley's message of "Tue, 05 Jan 2016 12:00:55 -0800")
> I have to say I'm in complete agreement with Eli on this point. If it's code
> that we'll ship, it deserves to be fixed like any other functionality we
> deliver. If it's no longer to be fixed or maintained, it should be removed.
> Delivering buggy code is not a sound deprecation strategy.
We're talking a bout bugs we've shipped long before they were
reported. And where removing the feature would piss off many
more people.
Anyway, it's not really my problem any more, luckily,
Stefan
prev parent reply other threads:[~2016-01-07 4:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 18:38 bug#1092: compilation-goto-error goes to wrong location when buffer has hidden regions Peter Sanford
2008-10-07 1:50 ` Stefan Monnier
2011-07-09 18:00 ` Glenn Morris
2016-01-02 21:43 ` Andrew Hyatt
2016-01-03 3:35 ` Eli Zaretskii
2016-01-03 4:06 ` Glenn Morris
2016-01-03 15:25 ` Eli Zaretskii
2016-01-03 21:13 ` John Wiegley
2016-01-03 6:22 ` Stefan Monnier
2016-01-03 15:31 ` Eli Zaretskii
2016-01-03 16:06 ` Stefan Monnier
2016-01-03 16:53 ` Eli Zaretskii
2016-01-03 19:39 ` Stefan Monnier
2016-01-03 19:49 ` Eli Zaretskii
2016-01-04 0:42 ` Stefan Monnier
2016-01-04 15:41 ` Eli Zaretskii
2016-01-05 4:12 ` Stefan Monnier
2016-01-05 4:28 ` Andrew Hyatt
2016-01-05 16:54 ` Eli Zaretskii
2016-01-05 16:52 ` Eli Zaretskii
2016-01-05 17:12 ` Stefan Monnier
2016-01-05 17:27 ` Eli Zaretskii
2016-01-05 20:00 ` John Wiegley
2016-01-07 4:17 ` Stefan Monnier [this message]
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=jwvd1te81pf.fsf-monnier+Inbox@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1092@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=jwiegley@gmail.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.
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).