emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: three bugs/misfeatures in org-reveal (or is org-reveal the wrong way to reveal around point?)
Date: Tue, 06 Aug 2013 09:41:43 +0200	[thread overview]
Message-ID: <86a9kvuuyw.fsf@somewhere.org> (raw)
In-Reply-To: CAJcAo8uBKSJgr22K=oYZKeBRFvTtjHL42fKHD_PE1W2rCOyMqA@mail.gmail.com

Hi Samuel,

Samuel Wales wrote:
> I hope a kind soul can comment here.
>
> For years I have been trying to make it so that you can go
> to Org from Magit and have it reveal the way I want.
>
> [All I want is what for me is a normal visibility state, which means a
> visibility state that can be recreated using only arrow keys and TAB.]
>
> Is org-reveal the wrong tool for this job?  Is there another tool that
> works better for it?
>
> The apparent bugs are in the comments below.
>
> Thanks.
>
> Samuel
>
> P.S.  I am also hoping for the same effect upon going from the Org
> agenda to the Org outline.
>
> ===
>
> (defadvice magit-visit-item (after org-visibility activate compile)
>   "Make going to Org from Magit reveal canonically."
>   (when (eq major-mode 'org-mode)
>     (alpha-org-reveal-canonically)))
>
> (defun alpha-org-reveal-canonically ()
>   "Reveal around point canonically.
>
> Canonical visibility means that the buffer is always in a
> visibility state that can be created solely by arrow keys + TAB.
>
> Thus, merely showing the next header without all of its siblings
> is not canonical.  Also, showing children without showing the
> parent's entry text is not canonical."
>   (interactive)
>
>   ;; bug 1: when point is in entry text, the first child of that
>   ;; entry shows, but its siblings (i.e. the other children) do
>   ;; not show, even though i have org-show-siblings and
>   ;; org-show-hierarchy-above both set to t.
>   ;;
>   ;; the entry text must show because point is in it.  and
>   ;; because it must show, so must all children.  how do i get it
>   ;; to do this?
>   ;;
>   ;; bug 2: when point is on the first child headline, its
>   ;; siblings show, but the entry text of its parent does not
>   ;; show.  how do i get it to show the parent's entry text?
>   ;;
>   ;; bug 3: org-reveal takes several seconds to run.  is there a
>   ;; way to speed it up?
>
>   (org-reveal t)
>   ;; (if ...)
>   ;; (show-entry)
>   )

Just a question: did you play with the following settings?

--8<---------------cut here---------------start------------->8---
  ;; show full hierarchy when revealing a location
  (setq org-show-hierarchy-above t)

  ;; don't show following heading when revealing a location
  (setq org-show-following-heading nil)

  ;; don't show all sibling headings when revealing a location
  (setq org-show-siblings nil)

  ;; show the entry below a headline when revealing a location
  ;; (setq org-show-entry-below t)
  (setq org-show-entry-below '((org-goto . t)))
--8<---------------cut here---------------end--------------->8---

Do they impact or resolve some of the things you consider as bugs?

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2013-08-06  7:41 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 [this message]
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
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=86a9kvuuyw.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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.
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).