emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug: isearch hides text that should be shown, ignoring all show variables
Date: Sat, 17 Jan 2015 11:01:57 +0100	[thread overview]
Message-ID: <87a91hsp7p.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJcAo8tRTrHokyquLYnEEyEpGrExf9=1HpkXFs3_eBVnAPevoA@mail.gmail.com> (Samuel Wales's message of "Sat, 10 Jan 2015 18:12:43 -0700")


Samuel Wales <samologist@gmail.com> writes:

> a similar bug to "bug: isearch puts ellipses at top of window" [which
> has an ecm]:
> * aa
> * a
> text
> *** b
> text
> *** c
> text
> * d
> and isearch for text sometimes produces the output below at top of window:
> ...
> * a
> text
> ...
> * d
> and sometimes this:
> ...
> * a
> text
> *** b
> * d
> both are not what i want.  to me, nothing should ever be hidden in org
> unless it can be hidden using arrow keys and tab.

Indeed. I don't like it either, but it makes sense: to show the minimal
context around information. What you suggest means to show all top-level
children in the entry. This can be invasive when there are many

Anyway, the point here is that you can use `org-reveal' (C-c C-r) to get
a more regular visibility.


Nicolas Goaziou

  reply	other threads:[~2015-01-17 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJcAo8vbN7Gg=MLBubYXwPLcrG8bpnjnnKATOeNeSM2nYWH_VQ@mail.gmail.com>
2015-01-11  1:12 ` bug: isearch hides text that should be shown, ignoring all show variables Samuel Wales
2015-01-17 10:01   ` Nicolas Goaziou [this message]
2015-01-17 19:50     ` Samuel Wales
2015-01-18  9:20       ` Nicolas Goaziou

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a91hsp7p.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \


* 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


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).