unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 11:06:19 -0500	[thread overview]
Message-ID: <jwvpoxizm5b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83k2nqadd0.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Jan 2016 17:31:39 +0200")

>> 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.
> Why is that a problem?

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.

> I wish every rarely used display feature was so lightweight as
> selective-display.

It's not lightweight on the Elisp side where you need to add a lot of
extra code in ever more places to handle the special meaning of \r in
that rare case.

> Anyway, I don't see how this report of a minor bug should trigger such
> far-reaching conclusions.  It took me all of 5 minutes to fix it; we
> should have done this 7 years ago.  I'm sorry we didn't, but better
> late than never.

I think the fix is worse than the problem, personally.


        Stefan





  reply	other threads:[~2016-01-03 16:06 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 [this message]
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=jwvpoxizm5b.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 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).