From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: docstrings (was: Re: Add-on USB custom keypads)
Date: Fri, 17 Jun 2016 08:15:13 +0200 [thread overview]
Message-ID: <86vb185ojy.fsf_-_@student.uu.se> (raw)
In-Reply-To: 20160617020301.GE3431@mail.akwebsoft.com
Tim Johnson <tim@akwebsoft.com> writes:
> I grew up on a homestead. We just made
> things work.
Indeed. I have the gene as well. Make it work,
by out working the opposition...
> I find the whole concept of lisp (as in
> elisp, racket, clojure) associates with the
> minimalist (homestead) approach of right and
> left parens to be a study in
> simplistic beauty.
I prefer the Lisp syntax and extra power
compared to other languages - e.g., code as
data, data as code, almost complete freedom, no
explicit types, and many other examples - from
a practical point tho the thing I like the most
is the integration with Emacs (the quick fix)
so you immediately can see the result of your
actions. It is the most pleasant way of
programming. I have sort of the same in the
shell (zsh) but not exactly as the
infrastructure is much less developed, you have
to reload the code manually (even tho it takes
zero time, still annoying compared to the eval
of a single defun). Even so, compared to LaTeX
and C and such giants with feet of clay, the
shell seems like a bunch of thin clouds...
> And as for emacs, the help system is awesome,
> maybe the best thing. I also use python.
> Docstrings rock!
Indeed. Good example of infrastructure. I like
focusing on the form, making it perfect, and
then wait for the data to "catch up"...
It always feels like a loss of prestige when
you have to Google something like some mere
plebeian. To have a uniform interface is great.
Only sometimes the docstrings themselves are
incomplete - for example, not that seldom, the
function comes with arguments that aren't
mentioned in the docstring.
Here is an example of a bad docstring in
several ways:
(transpose-sexps ARG)
Like M-t but applies to sexps.
Does not work on a sexp that point is in the middle of
if it is a list or string.
--
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
- so far: 48 Blogomatic articles -
next prev parent reply other threads:[~2016-06-17 6:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 15:28 Add-on USB custom keypads Tom Browder
2016-06-16 19:04 ` Emanuel Berg
2016-06-16 19:05 ` Aaron Fischer
2016-06-16 20:00 ` Tim Johnson
2016-06-16 21:21 ` Emanuel Berg
2016-06-16 22:34 ` Tim Johnson
2016-06-16 22:44 ` Emanuel Berg
2016-06-17 0:40 ` Tim Johnson
2016-06-17 1:20 ` Emanuel Berg
2016-06-17 2:03 ` Tim Johnson
2016-06-17 6:15 ` Emanuel Berg [this message]
2016-06-16 22:05 ` Tom Browder
2016-06-16 22:39 ` Emanuel Berg
[not found] ` <mailman.1639.1466137040.1216.help-gnu-emacs@gnu.org>
2016-06-17 7:15 ` Joost Kremers
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=86vb185ojy.fsf_-_@student.uu.se \
--to=embe8573@student.uu.se \
--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.
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.