all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sharon Kimble <boudiccas@skimble.plus.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: BUG - org-agenda-show-future-repeats not mentioned in org.pdf
Date: Sun, 10 Sep 2017 13:45:41 +0200	[thread overview]
Message-ID: <87377u22vu.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87vakqzuv3.fsf@skimble.plus.com> (Sharon Kimble's message of "Sun, 10 Sep 2017 11:54:56 +0100")

Sharon Kimble <boudiccas@skimble.plus.com> writes:

> You are assuming that everyone knows what a 'docstring' is, and how to
> get it or find out about it. Unfortunately, I don't fit into that
> category, so when I saw on "http://orgmode.org/Changes.html" 'See
> docstring for details.' I was, and still am, completely flummoxed by it,
> which is why I looked for it in an updated 'org.pdf'.

Emacs has an extensive help system. For example <F1> <F1> displays
a list of all help you can get. In particular, in this menu, you can see

  v VARIABLE  Display the given variable's documentation and value.

So if you hit `v', you can select `org-agenda-show-future-repeats' and
read its documentation string, or "docstring".

A shortcut for this is

  <F1> v org-agenda-show-future-repeats RET

Another way to look at it is to use the Customization system Emacs
offers. To get there, you can use

 M-x customize-group RET org RET

You can then browse variables by category, or directly search for the
one you're looking for in the search bar at the top of the buffer.

HTH.

Regards,

      reply	other threads:[~2017-09-10 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-09  9:05 BUG - org-agenda-show-future-repeats not mentioned in org.pdf Sharon Kimble
2017-09-09 16:19 ` Nicolas Goaziou
2017-09-10 10:54   ` Sharon Kimble
2017-09-10 11:45     ` Nicolas Goaziou [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87377u22vu.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=boudiccas@skimble.plus.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.