unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Sanford <pms.mail@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: compilation-next-error and hidden regions
Date: Sat, 04 Oct 2008 09:12:46 -0700	[thread overview]
Message-ID: <48E795FE.5020900@gmail.com> (raw)
In-Reply-To: <48E187A0.9070603@gmail.com>

Is there a better list to ask this question?

Peter Sanford wrote:
> I recently upgraded to emacs22. Now I have the problem that
> when I call compilation-next-error in a buffer that has a hidden region
> (from hide-copyleft.el), emacs jumps to the wrong spot (off by the 
> number of hidden lines in the copyright).
> 
> Can anyone shed some light onto this issue?
> Does compile.el ignore selective-display and it didn't before?
> 
> Thanks,
> Peter





  reply	other threads:[~2008-10-04 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30  1:57 compilation-next-error and hidden regions Peter Sanford
2008-10-04 16:12 ` Peter Sanford [this message]
2008-10-04 16:21   ` Drew Adams
2008-10-04 16:35   ` Lennart Borgman (gmail)
2008-10-04 16:43     ` Peter Sanford

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=48E795FE.5020900@gmail.com \
    --to=pms.mail@gmail.com \
    --cc=help-gnu-emacs@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.
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).