From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jakub Szypulka <jakub@szypulka.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (8.3.1-16-gf6aa53-elpa @ /Users/cube/.emacs.d/elpa/org-20150810/)]
Date: Mon, 24 Aug 2015 16:38:35 +0200 [thread overview]
Message-ID: <87bndwbvkk.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m28u9097gf.fsf@szypulka.de> (Jakub Szypulka's message of "Mon, 24 Aug 2015 14:50:08 +0200")
Jakub Szypulka <jakub@szypulka.de> writes:
> In that case, using agenda view, how can I display all timestamps in a buffer when the oldest and newest are a long time apart?
> Must I define a custom agenda view first? (e.g. to encompass a large
> time frame and hide empty days)
I think so. You can try setting `org-agenda-span' to a large number.
Regards,
prev parent reply other threads:[~2015-08-24 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 4:00 Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (8.3.1-16-gf6aa53-elpa @ /Users/cube/.emacs.d/elpa/org-20150810/)] Jakub Szypulka
2015-08-23 22:16 ` Nicolas Goaziou
2015-08-24 9:07 ` document depreciation of timeline? (was: Re: Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (8.3.1-16-gf6aa53-elpa @ /Users/cube/.emacs.d/elpa/org-20150810/)]) Gregor Zattler
2015-08-24 20:54 ` document depreciation of timeline? Nicolas Goaziou
2015-08-24 12:50 ` Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (8.3.1-16-gf6aa53-elpa @ /Users/cube/.emacs.d/elpa/org-20150810/)] Jakub Szypulka
2015-08-24 14:38 ` 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
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=87bndwbvkk.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jakub@szypulka.de \
/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).