unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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: [External] : help with Elisp
Date: Fri, 15 Oct 2021 11:52:13 +0200	[thread overview]
Message-ID: <877deefwdu.fsf@zoho.eu> (raw)
In-Reply-To: 87pms6n3qr.fsf@web.de

Michael Heerdegen wrote:

> And it's not equally useful at the same time? Can you keep
> syntax (argument order) of thousands of Elisp functions in
> your head?

Ha! Thanks, but I don't think I use that many :)

I wonder how many I used? You could count unique words in your
Elisp source I guess, and remove comments and strings.
Would that give a good estimate?

Not that it matters ...

> I could not live without it. For the cost that it covers the
> - otherwise empty - echo area.

Yep, I see the use case for people who like it, I don't want
the computer to do or say anything unless I push
a button first.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-10-15  9:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 22:18 help with Elisp Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-14 22:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-14 22:23 ` [External] : " Drew Adams
2021-10-14 22:34   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-14 22:39     ` Gregory Heytings
2021-10-14 22:48       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-15  4:01   ` Michael Heerdegen
2021-10-15  7:18     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-15  7:31       ` Michael Heerdegen
2021-10-15  9:52         ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-10-15 14:29     ` Drew Adams
2021-10-14 22:23 ` Gregory Heytings
2021-10-14 22:24 ` Óscar Fuentes

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=877deefwdu.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).