all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Po Lu <luangruo@yahoo.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Source code, git and cvs
Date: Fri, 21 Jul 2023 11:18:23 +0000	[thread overview]
Message-ID: <2OXFuuHTPJP6mJ3mHniuSKAerFOIIVchgVtgTIWwUfp-pGSQhZjIWbld1S33bnbjwTLSG2n9o2TIjTRmpMUPt0ju29vVaq77msn1KP-ycNU=@proton.me> (raw)
In-Reply-To: <87ilad4wuf.fsf@yahoo.com>


------- Original Message -------
On Friday, July 21st, 2023 at 6:12 PM, Po Lu <luangruo@yahoo.com> wrote:


> Eli Zaretskii eliz@gnu.org writes:
> 
> > > Date: Thu, 20 Jul 2023 20:10:56 +0000
> > > From: uzibalqa uzibalqa@proton.me
> > > Cc: Eli Zaretskii eliz@gnu.org, help-gnu-emacs@gnu.org
> > > 
> > > Yet you continue to refuse spending effort on making sure that future developers
> > > will be able to learn quickly.
> > 
> > You can write whatever you like: paper won't blush. But nothing is
> > farther from the truth, and if someone wants to have an independent
> > opinion, they should just look at my commit trail.
> 
> 
> fatiparty, uzibalqa, emacsq, goncholden, Christopher Dimech, whoever you
> are:
> 
> From March 2022 onwards, you have been sporadically posting to this list
> under various identities, seeking help with problems rising from
> incomplete or incorrect understandings of Emacs documentation, or
> unreasonable expectations thereof. Each time an Emacs developer tries
> to assist you, or points out the pertinent documentation, you find a
> contrived fault with that documentation or the behavior of said Emacs
> developer. Name-calling promptly follows, mostly from you.
> 
> Multiple individuals have already castigated you for this behavior,
> whatever the reason for it may be. Continuing to interact this way
> would be to your detriment, assuming that you want to continue receiving
> help from the readers of this list (which is doubtful.)

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.  

Such schemes constitute inefficient information retrieval or navigation.  Cannot see 
many to have enough sense to recognise this.




  parent reply	other threads:[~2023-07-21 11:18 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 [this message]
2023-07-21 12:30                             ` Eli Zaretskii
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

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

  git send-email \
    --in-reply-to='2OXFuuHTPJP6mJ3mHniuSKAerFOIIVchgVtgTIWwUfp-pGSQhZjIWbld1S33bnbjwTLSG2n9o2TIjTRmpMUPt0ju29vVaq77msn1KP-ycNU=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=help-gnu-emacs@gnu.org \
    --cc=luangruo@yahoo.com \
    /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.