emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Charles Millar <millarc@verizon.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug - all org files open as if visibilty is set to "showeverything"
Date: Fri, 15 May 2020 22:21:44 +0200	[thread overview]
Message-ID: <87mu69vtif.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <33ac809e-38a7-cb48-4c5b-00678f21460a@verizon.net> (Charles Millar's message of "Wed, 13 May 2020 14:19:49 -0400")


Charles Millar <millarc@verizon.net> writes:

> I recall seeing these messages, but did not realize that this change
> was going to effect all org files and by default, use lots and lots of
> space when an org file is opened.

That's true. On large files, this is not the best set-up. But I assume
anyone opening very large Org files is able to configure Org to their

On small files, e.g., a couple of screens high, this is a decent value,
however. But, more importantly, this is the least surprising value.

I think it is not uncommon for an Emacs user to open an Org file without
knowing about this major mode, e.g., if a project provides a README.org
file. This change is (mostly) for them, not for you, or me.

> As dar as I am concerned,the past default was OK and it took only
> a brief time to learn the past behavior and the visibility settings on
> a per file basis.
> I may be only a user but if I had I would have voted no.

You can voice your opinion in the thread, which is not closed. I hope
the Org community can find a consensus about this change.


Nicolas Goaziou

  reply	other threads:[~2020-05-15 20:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a0847ce6-74f2-9a79-0de6-a9369f490a83.ref@verizon.net>
2020-05-13 17:17 ` Bug - all org files open as if visibilty is set to "showeverything" Charles Millar
2020-05-13 17:58   ` Josiah Schwab
2020-05-13 18:19     ` Charles Millar
2020-05-15 20:21       ` Nicolas Goaziou [this message]
2020-05-13 18:13   ` Nicolas Goaziou
2020-05-13 18:28     ` Charles Millar
2020-05-14  0:29   ` Nick Dokos
2020-05-14 12:20     ` Charles Millar

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:

  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=87mu69vtif.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=millarc@verizon.net \


* 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


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).