From: James Harkins <jamshark70@zoho.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Sibling visibility when accessing an item from the agenda
Date: Sat, 16 Sep 2017 09:50:52 +0800 [thread overview]
Message-ID: <15e88619dbc.114233a1520441.9073821352604246248@zoho.com> (raw)
In-Reply-To: <15e885ec3b6.117021a3b20432.2368951057229264838@zoho.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
Sorry, I had meant to attach a screenshot. Here it is.
James
---- On Sat, 16 Sep 2017 09:47:45 +0800 James Harkins <jamshark70@zoho.com> wrote ----
> Hi,
>
> What is the setting to control the visibility of the 4th-level siblings here?
>
> How I got to this point:
>
> - All headings collapsed (only top-level visible)
>
> - Go to the agenda week view
>
> - Put the cursor on the entry for "Elec. 2a 01" and hit return.
>
> The catch is... my school requires me to take notes on every class session. That means I need to type plain text underneath this heading. But, org has "helpfully" marked this area to be invisible. If I put the cursor on the flush-left ellipsis and hit return to open up some space, I don't see the open space. Same if I put the cursor after the ellipsis for the properties drawer.
>
> That is, org thinks accessing an item from the agenda is a read-only operation, but I need to write into it -- org's assumption is invalid.
>
> So the only way I currently know to enter the text is to go up to the parent level, collapse it, and expand it to show all the siblings... for 14 class sessions every week. That is going to get really old.
>
> There must be a way to get org to show the sibling headings of the one that was selected from the agenda.
>
> Thanks,
> hjh
[-- Attachment #2: org-ellipses.png --]
[-- Type: image/png, Size: 11241 bytes --]
next prev parent reply other threads:[~2017-09-16 1:51 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 [this message]
2017-09-16 2:45 ` James Harkins
2017-09-16 7:30 ` Nicolas Goaziou
2017-09-16 9:23 ` James Harkins
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15e88619dbc.114233a1520441.9073821352604246248@zoho.com \
--to=jamshark70@zoho.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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.