emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Samuel Wales <samologist@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: bug: isearch hides text that should be shown, ignoring all show variables
Date: Sat, 17 Jan 2015 12:50:32 -0700	[thread overview]
Message-ID: <CAJcAo8sKEteooHqokc-nOJvvqUuE-kz3mLQLi=YCJ=_dgaf0cA@mail.gmail.com> (raw)
In-Reply-To: <87a91hsp7p.fsf@nicolasgoaziou.fr>

On 1/17/15, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Anyway, the point here is that you can use `org-reveal' (C-c C-r) to get
> a more regular visibility.

i am pretty sure that no org variables allow specifying this so that
it happens without you doing that.

is it the case that doing org-reveal as an after defadvice to
org-show-context should guarantee canonical visibility?

if there are cases when it does not guarantee that, then what does?


  reply	other threads:[~2015-01-17 19:50 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
2015-01-17 19:50     ` Samuel Wales [this message]
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='CAJcAo8sKEteooHqokc-nOJvvqUuE-kz3mLQLi=YCJ=_dgaf0cA@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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