unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: ahyatt@gmail.com, 1092@debbugs.gnu.org
Subject: bug#1092: compilation-goto-error goes to wrong location when buffer has hidden regions
Date: Tue, 05 Jan 2016 18:52:26 +0200	[thread overview]
Message-ID: <8337uc55px.fsf@gnu.org> (raw)
In-Reply-To: <jwvio38el55.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 04 Jan 2016 23:12:29 -0500)

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: ahyatt@gmail.com, 1092@debbugs.gnu.org
> Date: Mon, 04 Jan 2016 23:12:29 -0500
> 
> Declaring a feature obsolete doesn't resolve any problem.
> It just expresses our intent not to resolve those problems.

I think it expresses our intent to remove the feature at some point.
It doesn't necessarily follow that we will let it bitrot until then.

> My only intention in this discussion is to try and saves us from someone
> else ever trying to "fix" such bugs like you did.  Instead we should
> always reply with something like "if it hurts when you use
> selective-display=t, then don't use it".  Same applies for any other
> obsoleted feature.

I understand your intention very well, but I don't agree with such a
policy.  I think as long as the feature is not deleted, we ought to
fix bugs in it, unless the fix is very complex or could adversely
affect other packages, or could cause some other complication.  Bugs
are not a vehicle for telling users not to use an obsolete feature.
If we really want to remove a feature, we should just do that, after
making sure there's a usable replacement.





  parent reply	other threads:[~2016-01-05 16:52 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 [this message]
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

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=8337uc55px.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=1092@debbugs.gnu.org \
    --cc=ahyatt@gmail.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).