From: pietru@caramail.com
To: 48580@debbugs.gnu.org
Subject: bug#48580: Outline Mode using Phylogenetic Tree Nomenclature
Date: Sat, 22 May 2021 09:56:15 +0200 [thread overview]
Message-ID: <trinity-eca8bb31-b181-44fc-90db-e4b4a05eb362-1621670175473@3c-app-mailcom-bs04> (raw)
Currently Outline Mode is confusing because (1) commands begin with describing a tree,
then shifts to describe human beings (body, children); and (2) nomenclature such as branches
and leaves challenge the formal nomenclature of evolutionary trees.
There are also problems with the use of leaves and branches. Formally, "leaves" are
end-nodes with no children; whereas "branches" are the lines connecting the nodes, their
lengths commonly interpreted as time estimates. Thusly, "branches" effectively describe
the "body", not nodes themselves.
I advise and lay out a system based on a formal Phylogenetic Tree that implement
Show-Hide Options.
Show All (currently: Show All [unchanged])
Show Offsprings (currently: Show Children)
Show Descendants (currently: Show Branches)
Show Sub-Tree (currently: Show Subtree [unchanged])
Show Common Level (currently: Hide Sublevels)
Hide Sub-Branches (currently: Hide Leaves - meaning Hide Body after heading)
Hide Branches (currently: Hide Body, leaves all headings visible)
Hide Current Branch (currently: Hide Entry - hide body of this heading)
Hide Sub-Tree (currently: Hide Subtree [unchanged])
Hide Other (currently: Hide Other [unchanged])
Regards
Peter
next reply other threads:[~2021-05-22 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 7:56 pietru [this message]
2021-05-22 8:10 ` bug#48580: Outline Mode using Phylogenetic Tree Nomenclature Eli Zaretskii
2021-05-22 8:41 ` pietru
2021-05-22 10:53 ` pietru
2021-05-22 11:47 ` Christopher Dimech
2021-05-25 20:09 ` Lars Ingebrigtsen
2021-05-25 20:15 ` pietru
2021-05-26 11:57 ` Eli Zaretskii
2021-05-26 12:23 ` pietru
2021-05-27 7:37 ` Eli Zaretskii
2021-05-27 7:42 ` pietru
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-eca8bb31-b181-44fc-90db-e4b4a05eb362-1621670175473@3c-app-mailcom-bs04 \
--to=pietru@caramail.com \
--cc=48580@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.