[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Completely hide properties drawer in 9.6
From: |
Ihor Radchenko |
Subject: |
Re: Completely hide properties drawer in 9.6 |
Date: |
Wed, 14 Dec 2022 18:40:01 +0000 |
Sterling Hooten <hooten@gmail.com> writes:
> (let* ((block (org-get-property-block))
> ;; Extremely hacky way to get the whole property drawer
> (beg (- (car block) 14))
> (end (+ (cdr block) 5)))
> (with-silent-modifications
> (org-fold-region beg end t 'org-hide-property-drawer))))
> #+end_src
>
> Is there a better way to get the beginning and end
> of the property drawer more robustly?
org-element-at-point
> This is a step in the right direction, but it seems too sensitive to
> accidental editing.
See :fragile in org-fold-core--specs.
> This should be impervious to most types of user interaction,
> and prevent accidentally deleting or abutting anything
> up against either the start or end of the properties box.
which is part of the reason why the proposal was rejected.
Though Org tries hard in org-catch-invisible-edits.
> I tried setting `org-fold-catch-invisible-edits' to different values, but even
> with set to nil I can backward delete and erase some invisible
> text. Is this dependent on their being an ellipsis? Or is there
> another way to make this impervious to most edits?
It's just because only a fixed set of folds is caught in the invisible
edits check now.
> When adding a property with `org-property-put’ this would need
> to be called again, is there a way to do that robustly?
I should not need to be called again once you set
:front-sticky/:rear-sticky folding spec property.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Re: Completely hide properties drawer in 9.6, Jean Louis, 2022/12/16