all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: [External] : Re: Setting value 1 when matching two strings
Date: Mon, 17 Oct 2022 03:40:18 +0200	[thread overview]
Message-ID: <trinity-2113c41e-7435-4f24-85bc-a149d91acf2c-1665970817863@3c-app-mailcom-bs10> (raw)
In-Reply-To: <87sfjncmbn.fsf@web.de>

> Sent: Monday, October 17, 2022 at 12:42 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: [External] : Re: Setting value 1 when matching two strings
>
> Heime <heimeborgia@protonmail.com> writes:
>
> > Have gone through "An Introduction to Programming in Emacs Lisp" but cannot
> > assimilate all that.
>
> That's good.  Nobody can assimilate that all at once.  You can leave out
> lots of things that are currently not important to you.
>
> > If there was some condensed article about important tools for the
> > elisp programmer, and a crash course on how to use them, that would be
> > very helpful.
>
> Dunno if that's possible.  Depends too much on the background of the
> reader.  And there is a lot of important stuff to know.  I doubt it fits
> in a condensed article, and I doubt even more that you would write good
> programs after reading that.  It would be a trap.  The manual is not
> that long because the authors were bad, it's full of important things.
> If you simplify, no matter where, you'll later regret it.  Waste a lot
> of time, and still have to read all of it.

You are quite correct.  What is needed is a tool that gives you a collection
of possible traverses of the manual for what you need, then goes on organising
them for you, and displays them.  That would be the next emacs breakthrough.

In many of the national labs, people don't bother organising things anymore.
It will take more than a lifetime.  Rather it is automated tools that traverse
through all that.  The problem is that one will miss a lot of things nevertheless.
So it is simply a matter of luck.  Have found very few people willing to take the
time to understand the fundamental parts.

> > What I did was look at the emacs website displaying everything on one
> > web page.  The Gnu Emacs Info Viewer, is that when you type "info" at
> > the shell command line?
>
> The command line program "info" is a reader for the Info documentation
> for the command line.  Emacs has its own integrated and very nice Info
> reader: type C-h i.
>
> Oh, now I see that you only read the introduction, not the Elisp
> reference manual.  I suggest to have a look at that one, too.
>
> Yeah sorry if we sometimes sound rude, but all shortcuts are traps,
> _all_ - sorry.  It's hard to defer what one actually wants to do and
> read that boring stuff instead.  I guess all of us tried some shortcuts.
> We all wasted lots of time more or less.
>
> Michael.




  reply	other threads:[~2022-10-17  1:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 15:51 Setting value 1 when matching two strings Heime via Users list for the GNU Emacs text editor
2022-10-16 16:23 ` Dr Rainer Woitok
2022-10-16 16:33   ` Heime
2022-10-16 20:21   ` Heime
2022-10-16 21:23     ` [External] : " Drew Adams
2022-10-16 22:33       ` Heime
2022-10-16 23:16         ` Michael Heerdegen
2022-10-16 23:21           ` Heime
2022-10-16 23:39             ` Michael Heerdegen
2022-10-17  0:17               ` Heime
2022-10-17  0:41                 ` Drew Adams
2022-10-17  0:57                   ` Michael Heerdegen
2022-10-17  1:06                     ` Drew Adams
2022-10-17  0:42                 ` Michael Heerdegen
2022-10-17  1:40                   ` Christopher Dimech [this message]
2022-10-17  1:46                     ` Michael Heerdegen
2022-10-17  2:17                   ` Heime
2022-10-17  0:42         ` Drew Adams
2022-10-17  4:31         ` Jean Louis

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-2113c41e-7435-4f24-85bc-a149d91acf2c-1665970817863@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.