From: Bastien <bzg@altern.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: #+STARTUP: overview and org-startup-folded have no effect [7.9.3e (7.9.3e-1032-g791a8d @ /home/horn/Repos/el/org-mode/lisp/)]
Date: Thu, 14 Feb 2013 11:14:44 +0100 [thread overview]
Message-ID: <87vc9vdwx7.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87zjz7gqh4.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 14 Feb 2013 11:05:43 +0100")
Hi Tassilo,
Tassilo Horn <tsdh@gnu.org> writes:
> I have seven agenda files, all not too big (~10K on average), and I use
> an averagely performant computer (5 years old dual core laptop). For
> me, the difference between `org-agenda-inhibit-startup' set to t or nil
> is not noticable at all. In both cases, it's less than a second, and
> that's a time I can easily live with.
It really depends on what your agenda views are.
The real test is this: create a 50K file with folded one headline and
many second level TODO entries. Then have an agenda view search for
those TODO items. Do you get the same difference in this case?
If this difference is closer to 0 than to 1 sec, yes maybe we should
switch back to the default behavior. Tests are very welcome for this.
Let me know,
--
Bastien
next prev parent reply other threads:[~2013-02-14 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 9:08 Bug: #+STARTUP: overview and org-startup-folded have no effect [7.9.3e (7.9.3e-1032-g791a8d @ /home/horn/Repos/el/org-mode/lisp/)] Tassilo Horn
2013-02-14 9:12 ` Sebastien Vauban
2013-02-14 9:23 ` Bastien
2013-02-14 18:42 ` Tassilo Horn
2013-02-14 9:24 ` Tassilo Horn
2013-02-14 9:42 ` Bastien
2013-02-14 10:05 ` Tassilo Horn
2013-02-14 10:14 ` Bastien [this message]
2013-02-14 11:31 ` Tassilo Horn
2013-03-06 9:26 ` Bastien
2013-03-06 10:13 ` Tassilo Horn
2013-02-14 9:19 ` Tassilo Horn
2013-02-14 10:00 ` Bastien
2013-02-14 10:18 ` Tassilo Horn
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=87vc9vdwx7.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=tsdh@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 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).