From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Source code, git and cvs
Date: Fri, 21 Jul 2023 15:30:01 +0300 [thread overview]
Message-ID: <831qh11m7q.fsf@gnu.org> (raw)
In-Reply-To: <2OXFuuHTPJP6mJ3mHniuSKAerFOIIVchgVtgTIWwUfp-pGSQhZjIWbld1S33bnbjwTLSG2n9o2TIjTRmpMUPt0ju29vVaq77msn1KP-ycNU=@proton.me> (message from uzibalqa on Fri, 21 Jul 2023 11:18:23 +0000)
> Date: Fri, 21 Jul 2023 11:18:23 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: help-gnu-emacs@gnu.org
>
> Explain to me the benefit of having Cyclomatic Complexity in the documentation ?
> If you had a program to handle, perhaps there is a good point - still, try to
> get a human to understand an xml structure, will it be pleasant I ask.
>
> But you are forcing a human being (a user for that matter) to go through all the
> difficulties that often arise when dealing with nested or hierarchically placed
> information.
The way we deal with this is by providing extensive indexing. You
should learn to use the Info-index command (bound to 'i' inside Info)
much more.
next prev parent reply other threads:[~2023-07-21 12:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 12:01 Source code, git and cvs uzibalqa
2023-07-20 13:38 ` Po Lu
2023-07-20 13:58 ` uzibalqa
2023-07-20 14:23 ` Eli Zaretskii
2023-07-20 15:09 ` uzibalqa
2023-07-20 15:34 ` Robert Pluim
2023-07-20 15:36 ` Eli Zaretskii
2023-07-20 15:47 ` uzibalqa
2023-07-20 16:35 ` Eli Zaretskii
2023-07-20 17:33 ` uzibalqa
2023-07-20 18:31 ` Eli Zaretskii
2023-07-20 19:12 ` uzibalqa
2023-07-20 20:10 ` uzibalqa
2023-07-21 5:22 ` Eli Zaretskii
2023-07-21 6:12 ` Po Lu
2023-07-21 10:43 ` uzibalqa
2023-07-21 10:59 ` uzibalqa
2023-07-21 11:18 ` uzibalqa
2023-07-21 12:30 ` Eli Zaretskii [this message]
2023-07-21 12:40 ` uzibalqa
2023-07-21 12:51 ` Eli Zaretskii
2023-07-21 4:27 ` tomas
2023-07-21 10:35 ` uzibalqa
2023-07-21 12:12 ` Po Lu
2023-07-21 12:52 ` uzibalqa
2023-07-21 14:20 ` [External] : " Drew Adams
2023-07-21 15:30 ` uzibalqa
2023-07-20 16:05 ` uzibalqa
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=831qh11m7q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).