emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Wed, 06 Mar 2013 10:26:48 +0100	[thread overview]
Message-ID: <878v60515z.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ehgjgmiv.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 14 Feb 2013 12:31:04 +0100")

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

Hi Tassilo,

Tassilo Horn <tsdh@gnu.org> writes:

> Bastien <bzg@altern.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.
>
> Ok, the testfile looks like
>
> * The folded top-level headline
>
> ** TODO Some test todo headline 0
>
>    - also some contents
>
> ** TODO Some test todo headline 1
>
>    - also some contents
>
> and has 2000 such subheadlines.  File size is 127K.
> `org-startup-folded' is t.

That's not a very good test file, because you just need to unfold the
main headline to get all headlines visible.

I tested with a test.org file using this structure:

* Test
** TODO Test
*** Test

repeated 10k times.  Then run emacs -Q -l ~/test.el with the
attached test.el file, I get sensible results here.

I don't think it varies depending on the Emacs 23 vs 24 version,
but I believe we are using the same.

PS: I will revert `org-agenda-inhibit-startup' to nil as a default
and will explain why in another mail.


[-- Attachment #2: test.el --]
[-- Type: application/emacs-lisp, Size: 543 bytes --]

[-- Attachment #3: Type: text/plain, Size: 14 bytes --]


-- 
 Bastien

  reply	other threads:[~2013-03-06  9:26 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
2013-02-14 11:31           ` Tassilo Horn
2013-03-06  9:26             ` Bastien [this message]
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=878v60515z.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).