suggestion : collapsed levels

suggestion : collapsed levels

[Richard G Riley]

Hopefully I haven't missed this in the docs.

Is it/could it be, possible to have "collapsed" marking "..." always to the
right of the left hand title column in an org file?

Currently if you have a TAG against a top level then the "..." appears
to the right of the tag on the far right. If there is no tag it is to
the right of the title (in other words the "..." is always to the
right of the last filled column.

This is not immediately obvious when browsing the titles and
expanding/collapsing sub tree.

Re: suggestion : collapsed levels

[Bastien]

Richard G Riley <rileyrgdev@googlemail.com> writes:

> Is it/could it be, possible to have "collapsed" marking "..." always
> to the right of the left hand title column in an org file?

Do you mean hiding the tags when collapsing the subtree?  

But if you hide tags when folding, how do you distinguish headlines 
with tags from headlines without tags?

For me having tags around is okay. Especially because I use a nearly
invisible font for them.

And if I were to hide them I'd better hide them in a :TAGS: property.
But it is good to keep the special properties (todo, tags, scheduled,
etc.) at special place.

-- 
Bastien

Re: suggestion : collapsed levels

[Richard G Riley]

Bastien <bzg@altern.org> writes:

> Richard G Riley <rileyrgdev@googlemail.com> writes:
>
>> Is it/could it be, possible to have "collapsed" marking "..." always
>> to the right of the left hand title column in an org file?
>
> Do you mean hiding the tags when collapsing the subtree?  

No. I mean having the collapsed marker to the right of the heading, not
to the right of the visible tags. It stops you having to scan all the
way to the right. I small usability tweak I think.

e.g

*title                :tag:
    ** subheading

When I collapse I get

*title                :tag: ....

I think it would be easier to scan the title column (which you are more
likely to do than scanning process orientated tags) if the decoration
was like this:

*title...                :tag:

>
> But if you hide tags when folding, how do you distinguish headlines 
> with tags from headlines without tags?
>
> For me having tags around is okay. Especially because I use a nearly
> invisible font for them.

And for me.

>
> And if I were to hide them I'd better hide them in a :TAGS: property.
> But it is good to keep the special properties (todo, tags, scheduled,
> etc.) at special place.

No, I am not asking for tags to be removed from view.

But, on that subject is it possible to see inherited tags (maybe in a
different face?)?. They would, I assume, be read only in the places they
are "inherited". I see an ALLTAGS property, but its not immediately
clear to me from the documentation how to use it or even if it is what I
want.

Something like this at the top of a file?

:PROPERTIES:
:ALLTAGS: True
:END:


or, better and more concistent

#+ALLTAGS

But maybe I misinterpret the meaning of this special property? Possibly
I need to provide my own column view? Or can I modify the existing one
by including ALLTAGS?

Re: suggestion : collapsed levels

[Bastien]

Richard G Riley <rileyrgdev@googlemail.com> writes:

> *title                :tag: ....

I think this is not a good idea.  It would breack the logical meaning of
"..." and the way it's used outside of Org.

> But, on that subject is it possible to see inherited tags (maybe in a
> different face?)?.

Use the column view:

,----
| * Links                                    :Read:
|   :PROPERTIES:
|   :COLUMNS:     %30ITEM %10TAGS %20ALLTAGS
|   :END:
|   
| ** Types of links                         :Write:
`----

Try to C-c C-x C-c on the second headline.

It will display the headlines as a row consisting in the headline's
title, the list of tags, and the list of inherited tags.

The ALLTAGS field is "read-only": while trying to edit it with `e' Org
bites: "The ALLTAGS property can not yet be set with `org-entry-put'"

> :PROPERTIES:
> :ALLTAGS: True
> :END:

You can define the #+COLUMNS: so that the default column view for a
particular file always show inherited tags.

HTH,

-- 
Bastien

Re: suggestion : collapsed levels

[Bastien]

Richard G Riley <rileyrgdev@googlemail.com> writes:

>> I think this is not a good idea.  It would breack the logical meaning of
>> "..." and the way it's used outside of Org.
>
> For readability we will have to agree to disagree on that one. When
> scanning headings I dont want to have to move the eyes right to check
> for potential tags (which might be in a hard to read font as you have)
> to locate the "...". 

Maybe your proposal is more readable in some ways, but I think the
*meaning* of "..." is more important and should not be ignored, even 
with good readability concerns.

BTW, the meaning of "readable" depends on what you *want* to read: some
people might want to easily read the tags as well... I think your issue
is more about visual uniformity than about readability.

> But livable with :-;

:)

-- 
Bastien