When I initially request an indirect buffer for an item (especially from the agenda) it shows up with all its drawers open. I'd prefer it if they were closed by default. Is there a way to do that? Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com
on Sat Oct 01 2011, Dave Abrahams <dave-AT-boostpro.com> wrote: > When I initially request an indirect buffer for an item (especially from > the agenda) it shows up with all its drawers open. I'd prefer it if > they were closed by default. Is there a way to do that? To follow up my own post... This is actually very surprising, because the entry shows up in a state that can't be reached by tabbing on its headline, with all the drawers open. If you run (org-show-entry) in the indirect buffer it goes into a less-noisy configuration. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
On Oct 2, 2011, at 9:36 PM, Dave Abrahams wrote:
>
> on Sat Oct 01 2011, Dave Abrahams <dave-AT-boostpro.com> wrote:
>
>> When I initially request an indirect buffer for an item (especially from
>> the agenda) it shows up with all its drawers open. I'd prefer it if
>> they were closed by default. Is there a way to do that?
>
> To follow up my own post...
>
> This is actually very surprising, because the entry shows up in a state
> that can't be reached by tabbing on its headline, with all the drawers
> open. If you run (org-show-entry) in the indirect buffer it goes into a
> less-noisy configuration.
This is indeed a bug, fixed now.
- Carsten
on Tue Oct 04 2011, Carsten Dominik <carsten.dominik-AT-gmail.com> wrote: > On Oct 2, 2011, at 9:36 PM, Dave Abrahams wrote: > >> >> on Sat Oct 01 2011, Dave Abrahams <dave-AT-boostpro.com> wrote: >> >>> When I initially request an indirect buffer for an item (especially from >>> the agenda) it shows up with all its drawers open. I'd prefer it if >>> they were closed by default. Is there a way to do that? >> >> To follow up my own post... >> >> This is actually very surprising, because the entry shows up in a state >> that can't be reached by tabbing on its headline, with all the drawers >> open. If you run (org-show-entry) in the indirect buffer it goes into a >> less-noisy configuration. > > This is indeed a bug, fixed now. Thanks. So, just for my education, can you explain why running `org-cycle-hook 'all' is superior to just `org-show-entry' (which was my workaround)? -- Dave Abrahams BoostPro Computing http://www.boostpro.com
On 4.10.2011, at 17:22, Dave Abrahams wrote: > > on Tue Oct 04 2011, Carsten Dominik <carsten.dominik-AT-gmail.com> wrote: > >> On Oct 2, 2011, at 9:36 PM, Dave Abrahams wrote: >> >>> >>> on Sat Oct 01 2011, Dave Abrahams <dave-AT-boostpro.com> wrote: >>> >>>> When I initially request an indirect buffer for an item (especially from >>>> the agenda) it shows up with all its drawers open. I'd prefer it if >>>> they were closed by default. Is there a way to do that? >>> >>> To follow up my own post... >>> >>> This is actually very surprising, because the entry shows up in a state >>> that can't be reached by tabbing on its headline, with all the drawers >>> open. If you run (org-show-entry) in the indirect buffer it goes into a >>> less-noisy configuration. >> >> This is indeed a bug, fixed now. > > Thanks. So, just for my education, can you explain why running > `org-cycle-hook 'all' is superior to just `org-show-entry' (which was my > workaround)? Because this would also show, for example, archived trees etc. - Carsten > > -- > Dave Abrahams > BoostPro Computing > http://www.boostpro.com