unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Hannu Koivisto <azure@iki.fi>
Subject: outline-next-visible-heading breaks with certain outline-regexps
Date: Fri, 06 Dec 2002 23:05:05 +0200	[thread overview]
Message-ID: <877kemj1tq.fsf@lynx.ionific.com> (raw)

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.2 (i686-pc-linux-gnu, X toolkit)
 of 2002-03-26 on lynx
configured using `configure  --prefix=/usr/local/emacs-21 --with-xpm --with-jpeg --with-tiff --with-gif'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: fi_FI@euro
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: iso-latin-9
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Concerning outline.el, if outline-regexp matches the entire heading
line and the heading line is visible but the heading entry itself
is hidden, outline-next-visible-heading (and thus also at least
outline-forward-same-level) skips the heading line as invisible
even though it should not.

This happens because outline-next-visible-heading moves to the next
heading line with

(re-search-forward (concat "^\\(" outline-regexp "\\)")
                   nil 'move)

, which in the described conditions leaves the point right before
the newline at the end of the heading line, and then tests whether
the heading line is not visible (i.e. one that should be skipped)
with

(not (outline-visible))

which again does the test by checking whether the character after
point is invisible.  It is invisible, if the heading entry is
hidden, even though the heading line itself is visible, which is
what outline-visible should be testing.

-- 
Hannu

                 reply	other threads:[~2002-12-06 21:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=877kemj1tq.fsf@lynx.ionific.com \
    --to=azure@iki.fi \
    /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).