emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@zoho.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Sibling visibility when accessing an item from the agenda
Date: Sat, 16 Sep 2017 17:23:22 +0800	[thread overview]
Message-ID: <15e89ffe63d.adf4a2a521581.4095334622066164236@zoho.com> (raw)
In-Reply-To: <87377naymr.fsf@nicolasgoaziou.fr>

---- On Sat, 16 Sep 2017 15:30:52 +0800 Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote ---- 
> Does customizing `org-show-context-detail' fix your issues? 

Hi,

Thanks, it would have taken me quite some time to find that.

The default was "ancestors." Changing it to "local" works well for me.

I'm puzzled because, for years, it was behaving as I wanted. I believe the former behavior was "local" -- I have a slight shred of a doubt only because, when things are working as you expect, you take the behavior for granted and don't pay attention to all of the details.

I'm 100% certain that I was seeing at least the next sibling when jumping to an item from the agenda. If I had been seeing the "ancestors" behavior all along, I would have asked this question years ago and set it explicitly.

So, again, somehow this morning, one minute I had good behavior, and literally five minutes later (no restart, no software update, no quit/relaunch Emacs), it was a different, inconvenient behavior. I don't understand how that could happen.

Thanks for the tip, though. The behavior now is much better.

hjh

      reply	other threads:[~2017-09-16  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16  1:47 Sibling visibility when accessing an item from the agenda James Harkins
2017-09-16  1:50 ` James Harkins
2017-09-16  2:45 ` James Harkins
2017-09-16  7:30   ` Nicolas Goaziou
2017-09-16  9:23     ` James Harkins [this message]

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=15e89ffe63d.adf4a2a521581.4095334622066164236@zoho.com \
    --to=jamshark70@zoho.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).