unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: pietru@caramail.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48580@debbugs.gnu.org
Subject: bug#48580: Outline Mode using Phylogenetic Tree Nomenclature
Date: Sat, 22 May 2021 12:53:40 +0200	[thread overview]
Message-ID: <trinity-ad4a42cc-ec95-4ac9-9869-da31f42c09dc-1621680820331@3c-app-mailcom-bs14> (raw)
In-Reply-To: <83fsyfkx3u.fsf@gnu.org>



> Sent: Saturday, May 22, 2021 at 8:10 PM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: pietru@caramail.com
> Cc: 48580@debbugs.gnu.org
> Subject: bug#48580: Outline Mode using Phylogenetic Tree Nomenclature
>
> > From: pietru@caramail.com
> > Date: Sat, 22 May 2021 09:56:15 +0200
> > Sensitivity: Normal
> >
> > 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])
>
> FWIW, if I were presented with the menu labels as you suggest, I'd be
> mightily confused by the unfamiliar terminology.  "Branches",
> "Levels", "Children", and "Tree" are familiar terms when dealing with
> tree structures, whereas "Offsprings", "Descendants" and
> "Sub-branches" aren't.

The problem is not much about Levels, Children, and Tree.

Things got problematic when people required additional words for showing and hiding
structures that go beyond Children, Levels and Tree.  My focus is mostly about "Entry"
and Leaves.

Leaves are always end-nodes, not related to the body ("hide leaves" means "hide bodies"
in outline.el [in addition to not being related to end-nodes either]).  In outline, leaves
are expected to be the bodies of headlines.  And even in standard tree nomenclature, branches
are not nodes (but "show branches means" "show nodes" in outline.el).

Regards
Peter


>
>
>





  parent reply	other threads:[~2021-05-22 10:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22  7:56 bug#48580: Outline Mode using Phylogenetic Tree Nomenclature pietru
2021-05-22  8:10 ` Eli Zaretskii
2021-05-22  8:41   ` pietru
2021-05-22 10:53   ` pietru [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-ad4a42cc-ec95-4ac9-9869-da31f42c09dc-1621680820331@3c-app-mailcom-bs14 \
    --to=pietru@caramail.com \
    --cc=48580@debbugs.gnu.org \
    --cc=eliz@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.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).