From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ahyatt@gmail.com, 1092@debbugs.gnu.org
Subject: bug#1092: compilation-goto-error goes to wrong location when buffer has hidden regions
Date: Sun, 03 Jan 2016 14:39:44 -0500 [thread overview]
Message-ID: <jwvr3hyxxky.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8360zaa9l2.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Jan 2016 18:53:13 +0200")
>> It's not a problem in itself, no. But it means that if you want to
>> obsolete only one of the two uses, you can't just mark the variable
>> as obsolete.
> We cannot declare it obsolete without replacement features in place to
> which we can point.
For the selective-display=t case, we have had replacement features in
place and in wide use for what, twenty years?
We can very definitely declare this use case obsolete and stop trying to
fix problems we bump into when it's used.
Stefan
next prev parent reply other threads:[~2016-01-03 19:39 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr3hyxxky.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1092@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.