From: uzibalqa <uzibalqa@proton.me>
To: Po Lu <luangruo@yahoo.com>
Cc: tomas@tuxteam.de, help-gnu-emacs@gnu.org
Subject: Re: Source code, git and cvs
Date: Fri, 21 Jul 2023 12:52:03 +0000 [thread overview]
Message-ID: <du7QslEK76Xx6sGLpDLkeHWd9h3_3e5XYcsqtytRswZoYDkCNiq9Byl6S8NLEAm7DkgCFQfL4y1Hse2Rg9MdSpQbJYgXNys7wOfc0pczVs0=@proton.me> (raw)
In-Reply-To: <s7ra5vplayu.fsf@yahoo.com>
------- Original Message -------
On Saturday, July 22nd, 2023 at 12:12 AM, Po Lu <luangruo@yahoo.com> wrote:
> uzibalqa uzibalqa@proton.me writes:
>
> > The claim I get that everything is properly done is a serious fallacy.
> > There should be a version of emacs where do not continually add to it,
> > but only to get to a point where things are well designed and capable
> > of being handle well by other programmers. Eli is getting in a
> > difficult position, because the next poor sod is going to suffer much
> > more or give up keep the whole thing together.
>
>
> From your perspective, everyone apart from yourself is an ``Emacs
> developer'', engaged in a wayward conspiracy to prevent users from
> understanding Emacs documentation. You, a crusader fighting for the
> rights of the oppressed masses of Emacs users, are being silenced by
> companies of the King's men.
>
> The situation you illustrate couldn't be further from the truth.
>
> Perhaps you should contemplate why everyone on this list -- aside from
> you and your other identities, of course -- finds your demands
> unreasonable, and is satisfied with our current practices for writing
> documentation.
Past the elisp basics, the language interaction with emacs is generally agreed
to be difficult and vast, and you'll likely get lost in a sea of details.
That is accepted, and you are mistaking memory with intelligence. An automated
tool would be able to do it better than you. Otherwise the way the documentation
is designed has to change.
next prev parent reply other threads:[~2023-07-21 12:52 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
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 [this message]
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='du7QslEK76Xx6sGLpDLkeHWd9h3_3e5XYcsqtytRswZoYDkCNiq9Byl6S8NLEAm7DkgCFQfL4y1Hse2Rg9MdSpQbJYgXNys7wOfc0pczVs0=@proton.me' \
--to=uzibalqa@proton.me \
--cc=help-gnu-emacs@gnu.org \
--cc=luangruo@yahoo.com \
--cc=tomas@tuxteam.de \
/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.