emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Stanton <rhstanton@berkeley.edu>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Has VISIBILITY property become case-sensitive?
Date: Thu, 4 Apr 2024 13:13:58 -0700	[thread overview]
Message-ID: <9DF2328B-9DA9-48AC-B7D5-196388AC6B76@berkeley.edu> (raw)
In-Reply-To: <CFA72CF3-060D-4D28-BF05-3ABD8B64D335@berkeley.edu>

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

Actually, it didn’t!

But now I’m not seeing the original behavior either, though I haven’t changed anything. Don’t spend any more time on this - I’ll report back if I learn anything else.

Best

Richard




> On Apr 4, 2024, at 12:42 PM, Richard Stanton <rhstanton@berkeley.edu> wrote:
> 
> Here’ s a very simple org file that exhibits the behavior I describe
> 
> -----------------
> 
> #+STARTUP: overview
> 
> * Hidden
> - This should not initially appear
> - Nor this
> 
> * Visible
> :PROPERTIES:
> :VISIBILITY: content
> :END:
> - This should appear
> - And this
> 
> ———————
> 
> Change the case of the word “VISIBILILTY” and the file's behavior on first loading changes.
> 
> When I load this file using emacs -Q (which loads org 9.6.15), both sections appear folded regardless of the case of “visibility”…! Is there some configuration variable I need to set?
> 
> 
> 
> 
> 
>> On Apr 4, 2024, at 12:34 PM, Ihor Radchenko <yantar92@posteo.net <mailto:yantar92@posteo.net>> wrote:
>> 
>> Richard Stanton <rhstanton@berkeley.edu <mailto:rhstanton@berkeley.edu>> writes:
>> 
>>> My org file has the header line 
>>> 
>>> #+STARTUP: overview
>>> 
>>> One section contains the properties drawer
>>> 
>>> :PROPERTIES:
>>> :Visibility: content
>>> :END:
>>> 
>>> This used to show the contents of that subtree on first loading the file, but it no longer does. Experimentation shows that it works if I change “Visibility” to “VISIBILITY”. Is it a deliberate change to require upper case here? By the way, this is using org version 9.7pre
>> 
>> I am unable to reproduce.
>> Please provide more details, preferably starting from emacs -Q.
>> See https://orgmode.org/manual/Feedback.html#Feedback <https://orgmode.org/manual/Feedback.html#Feedback>
>> 
>> -- 
>> Ihor Radchenko // yantar92,
>> Org mode contributor,
>> Learn more about Org mode at <https://orgmode.org/ <https://orgmode.org/>>.
>> Support Org development at <https://liberapay.com/org-mode <https://liberapay.com/org-mode>>,
>> or support my work at <https://liberapay.com/yantar92 <https://liberapay.com/yantar92>>
> 


[-- Attachment #2: Type: text/html, Size: 15486 bytes --]

      reply	other threads:[~2024-04-04 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 18:54 Has VISIBILITY property become case-sensitive? Richard Stanton
2024-04-04 19:34 ` Ihor Radchenko
2024-04-04 19:42   ` Richard Stanton
2024-04-04 20:13     ` Richard Stanton [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=9DF2328B-9DA9-48AC-B7D5-196388AC6B76@berkeley.edu \
    --to=rhstanton@berkeley.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).