From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Morally equivalent
Date: Mon, 17 Oct 2022 02:32:09 +0200 [thread overview]
Message-ID: <trinity-5f7912e7-6e83-498c-a7f2-a5ec724f9e62-1665966729391@3c-app-mailcom-bs10> (raw)
In-Reply-To: <8735bne2d4.fsf@web.de>
> Sent: Monday, October 17, 2022 at 12:10 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Morally equivalent
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > When people start wondering whether something is a technical term,
> > then it is a
> > big problem. Stefan like all of us, should learn from his mistakes.
>
> I think the bigger problem, rather than Stefan's ability to learn from
> mistakes, is to find people actually trying to improve the
> documentation.
Right. But I would say that the easiest thing is to write better documentation
(in source) as you are writing the code. At least that part should be good.
The source documentation is the biggest strength of this system.
> It's easy to find things that are not perfect. If you want to help,
> search for bug reports about documentation and work on them. It's not
> more fun for Stefan than for anyone else. Discussing that things are
> not perfect is trivial - that's clear to _all_ of us. All of us know
> that. We need more people to do the work, not people to remind and
> discuss that there is work to do.
>
> Michael.
The documentation is getting longer and longer. And many people do not have time
for that. They require shortcuts. From my experience, besides maintainers there
should be designers. So that in future, people would require less knowledge rather
than more, to achieve a task. Competent designers almost don't exist, this has
always been the case. Look at the documentation for latex, always gets worse as time
goes by.
next prev parent reply other threads:[~2022-10-17 0:32 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 2:45 Morally equivalent John Haman
2022-10-16 2:55 ` Eduardo Ochs
2022-10-16 3:39 ` Michael Heerdegen
2022-10-16 14:29 ` [External] : " Drew Adams
2022-10-16 14:34 ` Heime
2022-10-16 14:42 ` Dr Rainer Woitok
2022-10-16 15:02 ` Drew Adams
2022-10-16 16:20 ` tomas
2022-10-16 19:27 ` Bob Newell
2022-10-16 19:43 ` [External] : " Drew Adams
2022-10-16 20:24 ` Bob Newell
2022-10-16 19:58 ` Christopher Dimech
2022-10-16 23:10 ` Michael Heerdegen
2022-10-16 23:17 ` Christopher Dimech
2022-10-16 23:32 ` Michael Heerdegen
2022-10-16 23:47 ` Eduardo Ochs
2022-10-17 1:13 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-18 10:44 ` Dr Rainer Woitok
2022-10-17 0:00 ` Christopher Dimech
2022-10-17 0:10 ` Michael Heerdegen
2022-10-17 0:32 ` Christopher Dimech [this message]
2022-10-17 0:53 ` Michael Heerdegen
2022-10-17 1:18 ` Christopher Dimech
2022-10-17 4:52 ` tomas
2022-10-17 5:27 ` Christopher Dimech
2022-10-20 14:08 ` Akib Azmain Turja
2022-10-20 16:24 ` Christopher Dimech
2022-10-20 18:29 ` tomas
2022-10-20 19:54 ` Christopher Dimech
2022-10-17 4:49 ` Akib Azmain Turja
2022-10-17 6:44 ` Eli Zaretskii
2022-10-17 7:48 ` tomas
2022-10-17 9:15 ` Thibaut Verron
2022-10-17 23:01 ` Rudolf Adamkovič
2022-10-18 1:01 ` Michael Heerdegen
2022-10-18 1:07 ` Emanuel Berg
2022-10-18 2:39 ` Po Lu
2022-10-18 3:50 ` Michael Heerdegen
2022-10-18 14:11 ` Eli Zaretskii
2022-10-18 16:50 ` Christopher Dimech
2022-10-18 23:11 ` Emanuel Berg
2022-10-20 14:05 ` Akib Azmain Turja
2022-10-20 17:14 ` Christopher Dimech
2022-10-17 15:42 ` Christopher Dimech
2022-10-17 11:47 ` Alessandro Bertulli
2022-10-23 10:16 ` Will Mengarini
2022-10-24 14:46 ` Marcin Borkowski
2022-10-24 21:06 ` Emanuel Berg
2022-10-24 21:05 ` Emanuel Berg
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-5f7912e7-6e83-498c-a7f2-a5ec724f9e62-1665966729391@3c-app-mailcom-bs10 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.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.