From: Christopher Dimech <dimech@gmx.com>
To: Arthur Miller <arthur.miller@live.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Eduardo Ochs <eduardoochs@gmail.com>,
Jean Louis <bugs@gnu.support>
Subject: How users start programming in Emacs Lisp...
Date: Tue, 1 Jun 2021 23:09:40 +0200 [thread overview]
Message-ID: <trinity-0c279296-e26a-40f5-a874-2cd31e256eea-1622581780219@3c-app-mailcom-bs03> (raw)
In-Reply-To: <AM9PR09MB4977A7945708D241F7F397BC963E9@AM9PR09MB4977.eurprd09.prod.outlook.com>
> Sent: Wednesday, June 02, 2021 at 2:09 AM
> From: "Arthur Miller" <arthur.miller@live.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Eduardo Ochs" <eduardoochs@gmail.com>, "help-gnu-emacs" <help-gnu-emacs@gnu.org>, "Jean Louis" <bugs@gnu.support>
> Subject: Re: How users start programming in Emacs Lisp...
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> >> Sent: Sunday, May 30, 2021 at 11:43 PM
> >> From: "Arthur Miller" <arthur.miller@live.com>
> >> To: "Eduardo Ochs" <eduardoochs@gmail.com>
> >> Cc: "Christopher Dimech" <dimech@gmx.com>, "help-gnu-emacs" <help-gnu-emacs@gnu.org>, "Jean Louis" <bugs@gnu.support>
> >> Subject: Re: How users start programming in Emacs Lisp...
> >>
> >> Eduardo Ochs <eduardoochs@gmail.com> writes:
> >>
> >> > On Sat, 29 May 2021 at 23:12, Christopher Dimech <dimech@gmx.com> wrote:
> >> >>
> >> >> > Sent: Sunday, May 30, 2021 at 10:37 AM
> >> >> > From: "Jean Louis" <bugs@gnu.support>
> >> >> > To: "Christopher Dimech" <dimech@gmx.com>
> >> >> > Cc: help-gnu-emacs@gnu.org
> >> >> > Subject: How users start programming in Emacs Lisp...
> >> >> >
> >> >> > (...)
> >> >> >
> >> >> > *scratch* buffer is famous for it.
> >> >> >
> >> >> > I just need more of them but *scratch*, so I do it this way:
> >> >
> >> >
> >> > Hi, just a curiosity...
> >> >
> >> > why do you prefer to use scratch buffers for elisp code instead of
> >> > using (semi-scratch?) files in which we record all our experiments?
> >> >
> >> > In the tutorials of eev I try to convince the new users to treat their
> >> > notes and scratch code as "field notes", and save everything they
> >> > can... one of my arguments is this:
> >> >
> >> > Learning eev is also like learning to use paper notebooks. It is
> >> > much easier to understand the notes and ideas what we wrote
> >> > ourselves in our notebooks than to understand what other people
> >> > wrote in their notebooks... when we go back to what _we_ wrote we
> >> > are able to reconnect with what we were thinking, even when our
> >> > notes are quite terse because we did not write down all details -
> >> > and we can't do that with other people's notes.
> >>
> >> I think you are probably correct about saving notes. Some vary famious
> >> scientists attribute almost everything to their notes.
> >
> > That is correct. Darwin and Fermi have done the same. But Stephen King
> > is famous for saying that notes are the best way to immortalise bad ideas.
>
> How could we know good ideas if it wasn't for bad ones?
>
> King is probably correct, but 90% or more ideas people get are probably
> bad, it is just that we remember the good ones (mostly :)). Also, some
> good ideas probably started as bad ideas. Socrates thought that writing
> is a bad idea. He never wrote a single note. :-(
>
> > Really good ideas stick around. Today, I get to agree with King in respect
> > to the experience with Fermi. But the same cannot be said about Darmin
> > during his trips.
> >
> > Thusly, in point of fact, there are no good rules, but just what works for you.
>
> That seems like a rule you are stating there? :)
The rule that there is no rule
next prev parent reply other threads:[~2021-06-01 21:09 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 20:08 Fortran Topics (outline-minor-mode, require, fixed format) ludvig-faddeev
2021-05-29 20:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 20:48 ` Jean Louis
2021-05-29 21:26 ` Christopher Dimech
2021-05-29 21:56 ` Jean Louis
2021-05-29 22:07 ` Christopher Dimech
2021-05-29 22:37 ` How users start programming in Emacs Lisp Jean Louis
2021-05-30 1:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 2:11 ` Christopher Dimech
2021-05-30 4:32 ` Eduardo Ochs
2021-05-30 7:05 ` Jean Louis
2021-05-30 7:51 ` Eduardo Ochs
2021-05-30 8:31 ` Jean Louis
2021-05-30 19:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 22:27 ` Jean Louis
2021-05-30 22:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 22:52 ` Jean Louis
2021-05-30 11:43 ` Arthur Miller
2021-05-30 12:08 ` Christopher Dimech
2021-05-30 19:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 21:54 ` Jean Louis
2021-05-30 22:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 22:38 ` Jean Louis
2021-05-30 22:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 22:56 ` Jean Louis
2021-05-30 23:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 23:35 ` Jean Louis
2021-05-31 0:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-01 14:09 ` Arthur Miller
2021-06-01 21:09 ` Christopher Dimech [this message]
2021-06-01 21:54 ` Christopher Dimech
2021-05-30 14:44 ` Tomas Hlavaty
2021-05-30 15:23 ` Eduardo Ochs
2021-05-30 19:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 19:59 ` Eduardo Ochs
2021-05-31 17:59 ` Tomas Hlavaty
2021-05-30 19:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-01 10:29 ` Arthur Miller
2021-06-01 11:40 ` Eduardo Ochs
2021-06-01 16:30 ` Jean Louis
2021-06-02 0:54 ` Eduardo Ochs
2021-06-02 3:43 ` Jean Louis
2021-05-30 15:35 ` Eduardo Ochs
2021-05-30 19:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-01 10:23 ` Arthur Miller
2021-05-30 19:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-01 10:22 ` Arthur Miller
2021-06-01 10:30 ` Christopher Dimech
2021-05-30 19:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 21:33 ` Jean Louis
2021-05-30 21:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 22:05 ` Jean Louis
2021-05-30 22:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 22:41 ` Jean Louis
2021-05-30 22:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 23:01 ` Jean Louis
2021-05-30 23:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 23:36 ` Jean Louis
2021-05-31 0:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-31 0:34 ` Eduardo Ochs
2021-05-31 8:09 ` Jean Louis
2021-05-30 22:49 ` Tomas Hlavaty
2021-05-30 22:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 22:50 ` Jean Louis
2021-05-30 22:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-30 23:25 ` Jean Louis
2021-05-30 5:46 ` Jean Louis
2021-05-30 10:32 ` Christopher Dimech
2021-05-30 10:35 ` Jean Louis
2021-05-30 11:08 ` Christopher Dimech
2021-05-30 11:19 ` Jean Louis
2021-05-30 13:55 ` Christopher Dimech
2021-05-30 15:54 ` Jean Louis
2021-05-30 17:22 ` Christopher Dimech
2021-05-30 18:57 ` Jean Louis
2021-05-30 19:48 ` Jean Louis
2021-05-31 20:30 ` Christopher Dimech
2021-05-31 21:53 ` Jean Louis
2021-05-29 20:36 ` Fortran Topics (outline-minor-mode, require, fixed format) Jean Louis
2021-05-29 20:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 21:00 ` Jean Louis
2021-05-29 21:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 22:00 ` Jean Louis
2021-05-30 2:04 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-30 2:06 ` Stefan Monnier via Users list for the GNU Emacs text editor
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=trinity-0c279296-e26a-40f5-a874-2cd31e256eea-1622581780219@3c-app-mailcom-bs03 \
--to=dimech@gmx.com \
--cc=arthur.miller@live.com \
--cc=bugs@gnu.support \
--cc=eduardoochs@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).