emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 22734-done@debbugs.gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, Oleksandr Gavenko <gavenkoa@gmail.com>
Subject: bug#22734: 24.5; do not leave opened org-agenda-files on org-agenda-list, etc.
Date: Fri, 01 Dec 2017 20:00:57 +0100	[thread overview]
Message-ID: <87lgimff2u.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871t89kaep.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 18 Feb 2016 21:53:34 +0100")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Oleksandr Gavenko <gavenkoa@gmail.com>
>>> Date: Thu, 18 Feb 2016 16:23:05 +0200
>>> 
>>> TODO.org I visit only via `C-c a a'. But NOTE.org become unmaintainable with
>>> size greater then 1 MiB of plain text.
>
> It would be interesting to see a profile report about this.
>
>>> But now I have a lot of opened unused .org files after `C-c a a' which I
>>> should kill when they appear during buffer switches.
>>> 
>>> The right behavior is to preserve opened only files that already was opened
>>> and kill other files.
>
> AFAICT, Org expects that agenda files are always being visited. This may
> be related to speed issues. 
>
> In any case, you could filter out Org files from buffer list (e.g., with
> `ido-ignore-buffers' and alike), and use `org-buffer-list' whenever you
> need them.

Since there is no more answer from the OP, I'm closing this bug.

Regards,

      reply	other threads:[~2017-12-01 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y4aidrna.fsf@gavenkoa.example.com>
2016-02-18 17:04 ` bug#22734: 24.5; do not leave opened org-agenda-files on org-agenda-list, etc Eli Zaretskii
2016-02-18 20:53   ` Nicolas Goaziou
2017-12-01 19:00     ` 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=87lgimff2u.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=22734-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gavenkoa@gmail.com \
    /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).