From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: BUG - org-agenda-show-future-repeats not mentioned in org.pdf
Date: Sat, 09 Sep 2017 10:05:00 +0100 [thread overview]
Message-ID: <87y3poqm2r.fsf@skimble.plus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
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!
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. I've tried -
--8<---------------cut here---------------start------------->8---
(setq org-agenda-show-future-repeats n)
OR
(setq org-agenda-show-future-repeats 0)
OR
(setq org-agenda-show-future-repeats 1)
--8<---------------cut here---------------end--------------->8---
But I still can't disable *all* my repeats showing for every day.
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?
I do have another bug that's irritating me, but that's for a separate post.
Thanks
Sharon.
--
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 --]
next reply other threads:[~2017-09-09 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 9:05 Sharon Kimble [this message]
2017-09-09 16:19 ` BUG - org-agenda-show-future-repeats not mentioned in org.pdf Nicolas Goaziou
2017-09-10 10:54 ` Sharon Kimble
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3poqm2r.fsf@skimble.plus.com \
--to=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.