emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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 11:54:56 +0100	[thread overview]
Message-ID: <87vakqzuv3.fsf@skimble.plus.com> (raw)
In-Reply-To: <87vakr3kw0.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 09 Sep 2017 18:19:11 +0200")

[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Sharon Kimble <boudiccas@skimble.plus.com> writes:
>
>> Seeing this new variable I've been trying to set it up to stop all the
>> future displays of each and every task being displayed in my 31 days
>> agenda.
>>
>> I've updated my git/org-mode and then built the new 'org.pdf', opened it
>> and then had a quick browse for 'org-agenda-show-future-repeats'. I then
>> did a search of the whole file and it isn't mentioned at all!
>
> The manual cannot possibly (and doesn't) contain a reference to every
> variable.
>
>> I was hoping to see something which showed how to use it, as currently I
>> have each and every repeat showing for each and every day of my 31-day
>> agenda. 
>
> You can know how to use it by looking at its docstring. I copy it here
> for reference:
>
>    Non-nil shows repeated entries in the future part of the agenda.
>    When set to the symbol ‘next’ only the first future repeat is
>    shown.

Thanks for replying.

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'.

Thanks
Sharon.

>
>> If we have changes, especially major ones like this, could they not be
>> mentioned in the org.pdf with perhaps a new chapter titled 'Changes' and
>> then giving details of how to use the new commands, please?
>
> The variable was introduced in <http://orgmode.org/Changes.html>
>
>
> Regards,

-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk  
Debian 9.0, fluxbox 1.3.5-2, emacs 25.1.1, org-mode 9.1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-09-10 10:55 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 [this message]
2017-09-10 11:45     ` Nicolas Goaziou

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=87vakqzuv3.fsf@skimble.plus.com \
    --to=boudiccas@skimble.plus.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).