Hi there; Agreed, hiding properties entirely seems overkill and quite limited in use cases. However, I think this stems from a more general need to hide properties that are irrelevant to the user—for instance, UIDs created by ox-icalendar, or other internal properties. As a user, I see no need whatsoever to see—let alone edit—such a property, and feel that it clutters the display. Assuming that properties are edited using the suitable commands, no clash would be created by having a set P of properties such that drawers with only P-properties would be hidden. What do you think?
Cheers; M. On Tue, 12 Feb 2019 at 08:38, Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote: > > Hello, > > Keith David Bershatsky <e...@lawlist.com> writes: > > > A few years ago, I wrote up an answer to my own question on > > Stackoverflow to completely hide the :PROPERTIES: drawer, including > > the line that says :PROPERTIES:. Since then, it has received nearly > > 5,000 views, 11 stars, 17 upvotes on the initial question, and 15 > > upvotes on the answer. > > > > Today, a forum participant posted a comment underneath my answer asking why > > not send this upstream. So, here is the link to the answer: > > > > https://stackoverflow.com/a/17492723/2112489 > > Thank you for the suggestion. > > However, I think hiding completely stuff from the user is not great. How > would you edit it, or even know there are properties there? > > You can write ":properties:" instead of ":PROPERTIES:", dim them with an > appropriate face… > > Regards, > > -- > Nicolas Goaziou >