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: three bugs/misfeatures in org-reveal (or is org-reveal the wrong way to reveal around point?)
Date: Sat, 17 Jan 2015 12:46:12 -0700	[thread overview]
Message-ID: <CAJcAo8v9FB2Mtpk_yZLvwZdii2yqDLyf7ERxoQdcKoFbieS7+w@mail.gmail.com> (raw)
In-Reply-To: <87h9vpss6a.fsf@nicolasgoaziou.fr>

thanks for clarifying.  that seems to eliminate all possibility of
specifying canonical visibility using org show variables.

thus, this is a feature that is strangely missing in org, as opposed
to a bug.  [yet it is what i think would be a good default for
newcomers.]

canonical visibility roughly means a visibility state that can be
created at any time using org-cycle and arrow keys.

for example, if only the first child is showing, then it is not
canonical visibility.  the only things that should NOT show are
entirely folded headers, blocks, etc.

this is the only kind of visibility that i ever use unless i am doing
a sparse tree, which is extremely rare.

the lack of ability to specify canonical visibility is the  reason i
have spent many years trying to fix it.  i have actually have now
around-defadviced the isearch version of org-show-context, but i don't
know what i am doing and it is slow and there are other contexts that
need fixing.  i think i will have to eliminate org-show-context
entirely if i am to get canonical visibility.

next prev parent reply	other threads:[~2015-01-17 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 22:50 three bugs/misfeatures in org-reveal (or is org-reveal the wrong way to reveal around point?) Samuel Wales
2013-08-06  7:41 ` Sebastien Vauban
2013-08-07  3:37   ` Samuel Wales
2015-01-17  1:23 ` Samuel Wales
2015-01-17  8:54   ` Nicolas Goaziou
2015-01-17 19:46     ` Samuel Wales [this message]
2015-01-18  9:16       ` Nicolas Goaziou
2015-01-18 20:26         ` Samuel Wales
2015-01-21 21:24           ` Nicolas Goaziou
2015-01-23 21:52             ` Samuel Wales

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.orgmode.org/

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

  git send-email \
    --in-reply-to=CAJcAo8v9FB2Mtpk_yZLvwZdii2yqDLyf7ERxoQdcKoFbieS7+w@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).