From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: icomplete-vertical-mode not taking effect
Date: Sun, 20 Jun 2021 08:27:05 +0200 [thread overview]
Message-ID: <878s35jbk6.fsf@zoho.eu> (raw)
In-Reply-To: YM7bWr51T8IhHFpb@protected.localdomain
Jean Louis wrote:
> I would like that Emacs could develop itself on its own
> including to self-document itself, like you say.
>
> The term "self-documenting" it not in that context. IMHO, it
> refers to built-in documentation like docstrings, manuals,
> etc. There are editors not having documentation built-in.
Hydro disc brakes on bicycles are self-adjusting, they do that
themselves by their design, so the cyclist doesn't have to do
it.
This is what I think self-something should mean, you don't do
it as a user or operator, the thing does it for you, by and
to itself.
Self-learning AI algorithm. And so on. It learns to play
checkers by playing it one zillion times against another
instance of itself. And so forth.
Emacs maybe provide certain things to do documentation and
that's great but it doesn't do the documentation. So it is
misleading (or even untrue) IMO.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-06-20 6:27 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 21:42 icomplete-vertical-mode not taking effect arvid-harnack
2021-06-16 23:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-17 13:40 ` arvid-harnack
2021-06-18 11:54 ` Ergus
2021-06-18 16:52 ` arvid-harnack
2021-06-18 18:26 ` Jean Louis
2021-06-18 18:36 ` arvid-harnack
2021-06-18 18:45 ` Jean Louis
2021-06-18 19:01 ` arvid-harnack
2021-06-18 19:07 ` tomas
2021-06-18 19:51 ` arvid-harnack
2021-06-18 21:24 ` Philip Kaludercic
2021-06-18 21:58 ` arvid-harnack
2021-06-19 16:31 ` arvid-harnack
2021-06-19 16:43 ` Jean Louis
2021-06-19 17:08 ` arvid-harnack
2021-06-19 17:22 ` Jean Louis
2021-06-19 17:34 ` arvid-harnack
2021-06-19 18:33 ` Eli Zaretskii
2021-06-19 18:03 ` arvid-harnack
2021-06-19 21:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-19 23:04 ` arvid-harnack
2021-06-20 6:37 ` Jean Louis
2021-06-19 21:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-19 21:28 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-20 6:08 ` Jean Louis
2021-06-20 6:27 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-06-18 19:09 ` Jean Louis
2021-06-18 21:16 ` Philip Kaludercic
2021-06-19 17:04 ` 2QdxY4RzWzUUiLuE
2021-06-19 17:28 ` arvid-harnack
2021-06-19 18:32 ` Eli Zaretskii
2021-06-19 19:03 ` arvid-harnack
2021-06-19 19:09 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-19 19:47 ` tomas
2021-06-19 21:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-19 22:51 ` arvid-harnack
2021-06-20 6:51 ` Eli Zaretskii
2021-06-19 19:26 ` Yuri Khan
2021-06-19 19:38 ` arvid-harnack
2021-06-20 10:44 ` Philip Kaludercic
2021-06-20 11:03 ` Jean Louis
2021-06-20 11:20 ` arvid-harnack
2021-06-20 11:30 ` Jean Louis
2021-06-20 11:47 ` arvid-harnack
2021-06-20 11:21 ` Jean Louis
2021-06-20 11:34 ` arvid-harnack
2021-06-20 11:46 ` Jean Louis
2021-06-20 15:27 ` arvid-harnack
2021-06-20 15:44 ` 2QdxY4RzWzUUiLuE
2021-06-20 16:02 ` arvid-harnack
2021-06-20 16:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 20:23 ` arvid-harnack
2021-06-20 19:43 ` Jean Louis
2021-06-20 19:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 20:12 ` arvid-harnack
-- strict thread matches above, loose matches on Subject: below --
2021-06-19 19:24 arvid-harnack
2021-06-19 19:32 ` Eli Zaretskii
2021-06-19 19:43 ` arvid-harnack
2021-06-19 19:47 ` Eli Zaretskii
2021-06-19 20:17 ` arvid-harnack
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=878s35jbk6.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).