unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: 1092@debbugs.gnu.org
Subject: bug#1092: compilation-goto-error goes to wrong location when buffer has hidden regions
Date: Sun, 03 Jan 2016 01:22:31 -0500	[thread overview]
Message-ID: <jwvoad3192k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m2d1tjody3.fsf@gmail.com> (Andrew Hyatt's message of "Sat, 02 Jan 2016 16:43:00 -0500")

> I'd agree that either selective-display should be marked as deprecated,
> or the problem should be fixed. I don't know what the status of
> selective-display is, though - it might be worth bringing this up in
> emacs-devel.

There are several problems with selective-display:
- first and foremost, the variable provides 2 different features:
  - when set to t, it makes CR behave specially (it's a special
    line-separator that makes the next line invisible).
  - when set to a number, it makes all lines indented deeper than this
    number invisible.
- The first use should be declared obsolete because overlays provide
  a much better way to do the same thing.  There might still be a few
  packages out there using this old selective-display thingy but they
  really need to move on.
- The second use should be replaced by a minor mode which provides the
  same feature using overlays, but nobody bothered to do so.
  Maybe because this second use is very rarely useful at all.
  So maybe this second use should be just dropped (i.e. made obsolete
  without providing an alternative).


-- Stefan





  parent reply	other threads:[~2016-01-03  6:22 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 [this message]
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

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=jwvoad3192k.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=1092@debbugs.gnu.org \
    --cc=ahyatt@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).