emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Michaël Cadilhac" <michael@cadilhac.name>
Cc: Keith David Bershatsky <esq@lawlist.com>, emacs-orgmode@gnu.org
Subject: Re: Completely hide the :PROPERTIES: drawer in org-mode.
Date: Wed, 13 Feb 2019 15:32:28 +0100	[thread overview]
Message-ID: <875ztnu5c3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CADt3fpNwwPMB-BGdL3KMyv8cusnTXBUF-jAWeMLvWJ4KTFvf1Q@mail.gmail.com> ("Michaël Cadilhac"'s message of "Tue, 12 Feb 2019 20:17:13 +0000")

Hello,

Michaël Cadilhac <michael@cadilhac.name> writes:

> 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?

Since properties drawers are almost exclusively folded, I don't think
incriminated properties clutter display. Besides, I don't think any
property is irrelevant to every user. How would we know?

More generally, I feel uneasy about completely hiding stuff. Org format
is not meant to be opaque. I think the current situation is fine, as far
as /core/ Org is concerned. Of course, users are free to extend it to
their own needs.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2019-02-13 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 16:21 Completely hide the :PROPERTIES: drawer in org-mode Keith David Bershatsky
2019-02-12  8:37 ` Nicolas Goaziou
2019-02-12 20:17   ` Michaël Cadilhac
2019-02-13 14:32     ` Nicolas Goaziou [this message]
2019-02-13 15:11       ` Michaël Cadilhac
2019-02-13 15:55         ` Nicolas Goaziou
2019-02-14 14:16           ` Michaël Cadilhac
2019-02-14 16:11             ` Nicolas Goaziou
2019-02-14 16:21               ` Michaël Cadilhac
2019-02-14 23:15                 ` Nicolas Goaziou
2019-08-28 22:38                   ` Michaël Cadilhac
2019-09-05 16:54                     ` Nicolas Goaziou
2019-02-13 18:44       ` Marco Wahl

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=875ztnu5c3.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=esq@lawlist.com \
    --cc=michael@cadilhac.name \
    /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).