From: Marco Wahl <marcowahlsoft@gmail.com>
To: Sebastian Miele <sebastian.miele@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Document level property drawer
Date: Mon, 13 Jan 2020 22:52:11 +0100 [thread overview]
Message-ID: <847e1vf2ic.fsf@gmail.com> (raw)
In-Reply-To: <87k19ovdxn.fsf@gmail.com> (Sebastian Miele's message of "Tue, 01 Oct 2019 12:38:12 +0000")
Sebastian Miele <sebastian.miele@gmail.com> writes:
> But for such properties to satisfactorily work for me, they would have
> to be visible by default. E.g. I would want the header-args to be
> immediately visible just like they are when they are written after
> #+BEGIN_SRC or #+HEADER. Otherwise I would find myself constantly
> wondering whether this or that property drawer contains something
> essential and every TAB on a collapsed headline would have be followed
> by an accompanying move to the property drawer and a TAB there.
>
> On the other hand, there are properties that are very good candidates
> for remaining hidden by default, like ID.
>
> I would like to be able to make a clear distinction between properties
> that are visible by default and properties that are not. Maybe it would
> be possible to allow some #+.. syntax following headings for subtree
> properties that are visible by default. A requirement could be made that
> such property specifications always have to be followed by a property
> drawer, even if that is empty. Then everything #+.. that is before the
> property drawer would belong to the heading/subtree, and everything #+..
> that follows the drawer would be treated as it is until now.
>
> Please tell me if I missed something and Org is already capable of
> something like that. If not, are there others who would like
> visible-by-default property specifications for headings/subtrees in
> addition to invisible-by-default property specifications in drawers,
> too?
I don't think Org is capable of this out of the box right now. Further
I don't feel the need for a visible-by-default property, but that's just
me.
> Finally, I would like to state an opinion: If there is
> visible-by-default (by #+..) and invisible-by-default (by drawers)
> syntax for headings/subtrees, including level 0, it may be viable to
> require them to be disjoint for each heading/subtree. Most probably it
> would be good practice, anyway. And the precedence question raised
> previously in this thread would be eliminated.
I may not feel the need for the visible/invisible-by-default properties
but actually I like the idea of #+ properties parallel to the property
drawers as visible by default properties. But since the #+ properties
may appear anywhere in the Org file and affect the whole file it would
be difficult or even impossible to give them reliable meaning for
subtrees AFAICS.
My 2ct,
--
Marco
next prev parent reply other threads:[~2020-01-13 21:52 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 10:27 [RFC] Document level property drawer Gustav Wikström
2019-09-29 19:13 ` Marco Wahl
2019-09-30 16:01 ` Adam Porter
2019-09-30 20:46 ` Marco Wahl
2019-10-01 12:38 ` Sebastian Miele
2020-01-13 21:52 ` Marco Wahl [this message]
2020-01-15 8:18 ` Sebastian Miele
2020-02-01 19:59 ` Marco Wahl
2019-10-01 13:55 ` Adam Porter
2019-10-02 10:29 ` Marco Wahl
2019-10-03 18:06 ` Adam Porter
2019-10-04 11:05 ` Marco Wahl
2019-10-06 1:05 ` Adam Porter
2019-10-06 5:10 ` Matt Price
2019-10-15 17:49 ` Gustav Wikström
2019-10-16 0:48 ` Adam Porter
2019-10-16 9:48 ` Marco Wahl
2020-01-20 3:27 ` [Question] adding document global properties drawer stardiviner
2020-01-21 16:40 ` Nicolas Goaziou
2020-01-22 16:28 ` stardiviner
2020-01-24 23:14 ` Nicolas Goaziou
2020-02-23 7:31 ` [SOLVED] " stardiviner
2020-02-23 13:14 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2019-09-30 22:09 [RFC] Document level property drawer Gustav Wikström
2019-10-03 18:31 ` Adam Porter
2019-10-04 10:38 ` Marco Wahl
2019-10-06 1:01 ` Adam Porter
2019-10-07 7:46 ` Marco Wahl
2019-10-02 20:29 Gustav Wikström
2019-10-05 18:20 Gustav Wikström
2019-10-06 0:51 ` Adam Porter
2019-10-06 5:35 Gustav Wikström
2019-10-06 6:02 Gustav Wikström
2019-10-20 2:28 Gustav Wikström
2019-10-22 21:24 ` Marco Wahl
2019-10-23 8:43 ` Marco Wahl
2019-10-23 8:59 ` Gustav Wikström
2019-10-24 21:01 ` Gustav Wikström
2019-10-25 12:58 ` Marco Wahl
2019-10-23 16:08 ` Adam Porter
2019-10-24 22:29 Gustav Wikström
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=847e1vf2ic.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian.miele@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).