unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Lisp help messages in echo area
Date: Mon, 17 Jul 2017 03:44:19 +0200	[thread overview]
Message-ID: <86bmojvnv0.fsf@zoho.com> (raw)
In-Reply-To: 87d1908ck2.fsf@ankarstrom.se

John Ankarström wrote:

> defun: (NAME ARGLIST &optional DOCSTRING DECL
> &rest BODY)

Knowing the interfaces of/to each component
(e.g., a function) is the key to all
programming and actually all *activity*.
Having immediate access to it is the one
advantage that will rule supreme.

Many people think programming makes you
practically inept - just staring at unworldly
code all night long...?! This might hold true
if you *only* do programming - such
one-dimensionalness is of course harmful
whatever field. But do programming *and*
something else as well - trust me, this soon
makes you better at doing "something else" than
the people who do that all day every day! (Or
at least just as good with much less effort.)

For example, go to your tool box and pick up
a combination spanner/wrench and a
combination plier. "Examine" those tools, in
the Shadowgate/Déjà Vu lingo, and identify
their properties and interfaces as would
a programmer.

Then, have the very pleasant realization that
having mastered programming - that is, the
craft, not every detail which would be
impossible - having mastered programming,
everything else is child's play :)

-- 
underground experts united
http://user.it.uu.se/~embe8573




      parent reply	other threads:[~2017-07-17  1:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16 18:24 Lisp help messages in echo area John Ankarström
2017-07-16 18:36 ` Kaushal Modi
2017-07-16 19:01   ` John Ankarström
2017-07-16 19:45     ` Kaushal Modi
2017-07-21 15:37     ` Kaushal Modi
2017-07-17  1:44 ` Emanuel Berg [this message]

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=86bmojvnv0.fsf@zoho.com \
    --to=moasen@zoho.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).