emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher J. White" <orgmode@grierwhite.com>
To: emacs-orgmode@gnu.org
Subject: Re: are super-hidden technical blocks required?
Date: Tue, 07 Aug 2012 09:39:00 -0400	[thread overview]
Message-ID: <50211A74.6070803@grierwhite.com> (raw)
In-Reply-To: <CAPaq-gNHAyihsRi+FtKYJMWL=HBCb8OY30X2E+e+JR4+o2H5VQ@mail.gmail.com>

Nice!  I like this approach.  The only slight change I would make is to 
the "All entries are unfolded one level".  If there are only "hidden" 
properties but there is other content, show the other content but not 
the PROPERTIES drawer:

    * All entries are unfolded one level
    ** Only "hidden" properties with other content
       This is more content

The ":PROPERTIES:" is not shown.

Question -- are you proposing a new step in cycling that opens all 
property drawers, or is this already available via some command or 
setting?  I've never seen a way to open everything including PROPERTIES 
via Tab or S-Tab cycling.

...cj


On 8/7/12 9:20 AM, Torsten Wagner wrote:
> Hey Bastien,
>
> On 7 August 2012 19:23, Bastien <bzg@gnu.org> wrote:
>> that a drawer doesn't make an
>> entry non-empty while cycling,
>
> ohhh you challenge us... "does not ... non-empty".... is in fact the
> same like "if there is only a drawer, the entry is still empty"....
> right ?!
>
> Yes, I agree that should be separated.
>
> Maybe an idea would be a rule like....
> if all properties in a drawer are marked as hidden and there is
> nothing else for the particular entry (no body), do not open the entry
> for the next cycling rounds.
> I just tested a bit and org-mode is clever enough already to avoid any
> text-insertion before the property drawer if text get added to a
> collapsed entry.
> Thus, this rule just might work and hide "technical" properties
> completely during cycling.
> Combined with a #+HIDDEN_PROP: line each and everyone can adjust
> individually how much and what he likes to hide.
>
> #+HIDDEN_PROP: * <----- all properties are hidden
> would be the extreme and all property drawers will be hidden in case
> they are the only element of a entry. In case other elements are
> included, they collapsed drawer line will be dimmed by a different
> face to indicate that only "hidden" properties are included
>
> #+HIDDEN_PROP:    <---- this means no properties are hidden
> would be the other extreme and nothing would be hidden (that
> essentially would represent the present state).
>
> I created two mock-ups. One shows the present solution and the other
> shows how certain properties can be marked "hidden" and which effect
> does this have on different level and combinations. Hope that helps
> within this discussion. I choose a arbitrary colour scheme to make it
> rather good visible.
>
> Torsten
>

  reply	other threads:[~2012-08-07 13:39 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30  2:26 are super-hidden technical blocks required? Torsten Wagner
2012-07-30  7:26 ` Bastien
2012-07-30 10:27   ` Rasmus
2012-07-30 14:27     ` Russell Adams
     [not found]   ` <CAPaq-gMV-+n6OAN4PnBsh1eiJ5wA=Ns_m_qwHqz1pxbOxeYCCQ@mail.gmail.com>
2012-07-31  2:04     ` Fwd: " Torsten Wagner
2012-07-30 14:42 ` Ivy Foster
2012-07-30 15:23   ` Jonathan Leech-Pepin
2012-07-31 13:23     ` Robert Horn
2012-07-31 13:47       ` Torsten Wagner
2012-08-04 18:10       ` Ilya Shlyakhter
2012-08-05  9:16         ` Bastien
2012-08-05 20:04           ` Ilya Shlyakhter
2012-08-05 22:20             ` Nicolas Goaziou
2012-08-05 22:50               ` Ilya Shlyakhter
2012-08-06  2:46                 ` Torsten Wagner
2012-08-06  3:01                   ` Ilya Shlyakhter
2012-08-06 12:12                     ` Jonathan Leech-Pepin
2012-08-06 17:25                       ` Ilya Shlyakhter
2012-08-06 18:16         ` Allen S. Rout
2012-08-06 19:01           ` Michael Brand
2012-08-07 21:29           ` Ilya Shlyakhter
2012-07-31  2:48 ` Torsten Wagner
2012-08-01 13:29   ` Bastien
2012-08-02  1:19     ` Torsten Wagner
2012-08-06 15:02       ` Christopher J. White
2012-08-01 17:11   ` Achim Gratz
2012-08-01 18:39     ` Bernt Hansen
2012-08-01 18:49       ` Achim Gratz
2012-08-02  1:16     ` Torsten Wagner
2012-08-02 15:10       ` Bastien
2012-08-07 21:33         ` Ilya Shlyakhter
2012-08-02 13:01   ` babel awk with table input: Code block produced no output Greg Minshall
2012-08-02 13:21     ` Sebastien Vauban
2012-08-03  2:08     ` [BUG] Traceback on Org-Export Luis Anaya
2012-08-03  7:19       ` Bastien
2012-08-03 10:27         ` Luis Anaya
2012-08-04 13:06           ` Achim Gratz
2012-08-04 14:13             ` Achim Gratz
2012-08-04 17:58             ` Bastien
2012-08-04 21:07               ` Achim Gratz
2012-08-05  9:44                 ` Bastien
2012-08-05 15:44                   ` Achim Gratz
2012-08-03 10:43         ` Luis Anaya
2012-08-03 11:17           ` Giovanni Ridolfi
2012-08-03 11:32             ` Luis Anaya
2012-08-03 14:34               ` Nick Dokos
2012-08-03 20:09           ` Achim Gratz
2012-08-05 23:57     ` babel awk with table input: Code block produced no output Greg Minshall
2012-08-06  1:36       ` Thomas S. Dye
2012-08-06  4:59         ` Greg Minshall
2012-08-06 15:37       ` Change: no longer automatically evaluate embedded elisp in code block output Was: " Eric Schulte
2012-08-08  5:00         ` Greg Minshall
2012-08-07  3:12 ` are super-hidden technical blocks required? Torsten Wagner
2012-08-07 10:23   ` Bastien
2012-08-07 13:20     ` Torsten Wagner
2012-08-07 13:39       ` Christopher J. White [this message]
2012-08-07 14:11         ` Torsten Wagner
2012-08-07 14:30           ` Robert Horn
2012-08-14  9:58       ` Bastien

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=50211A74.6070803@grierwhite.com \
    --to=orgmode@grierwhite.com \
    --cc=emacs-orgmode@gnu.org \
    /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).