emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: LOGBOOK opening
Date: Wed, 11 Jan 2012 18:59:11 +0100	[thread overview]
Message-ID: <80ipki6ryo.fsf@somewhere.org> (raw)
In-Reply-To: 877h0yb4ys.fsf@iro.umontreal.ca

Hi François,

François Pinard wrote:
> When using SPC in the Agenda buffer (org-agenda-show-and-scrollup), the
> LOGBOOK drawer is shown opened, which is not a big problem, yet a
> slightly annoying one, as I'm rarely interested to see its contents at
> this stage.  Moreover, the manual explains that one of the purposes of
> drawers is keeping information out of sight, unless the user takes
> specific action for opening it.
>
> The above command leave the cursor on the SCHEDULED: line in the Org
> buffer, which is above and outside the LOGBOOK drawer, so there is
> likely no need to open it.
>
> Is there some secret variable to prevent such opening?  (I begin to see
> the pattern on the Org mode list -- someone presents a problem, another
> gives the name of the variable that solves it!)

I don't _think_ this is customizable right now; though, please not that
RET'ing on en entry from the agenda jumps to the entry, without expanding the
drawer. Though, it reuses the agenda buffer to do so -- it's not the same
behavior as SPC'ing.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-01-11 17:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 16:04 LOGBOOK opening François Pinard
2012-01-11 17:59 ` Sebastien Vauban [this message]
2012-01-15 11:49   ` François Pinard
2012-01-15 14:03     ` Bernt Hansen
2012-01-16  1:59       ` François Pinard
2012-01-24 16:04         ` Bastien
2012-01-24 18:23           ` François Pinard
2012-01-24 23:24             ` Bernt Hansen
2012-01-25  6:13               ` Bastien
2012-01-25 11:49                 ` Bernt Hansen

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=80ipki6ryo.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@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).