From: Marcin Borkowski <mbork@mbork.pl>
To: John Wiegley <johnw@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, brandelune@gmail.com
Subject: Re: update intro to Emacs Lisp programming
Date: Wed, 23 May 2018 17:06:30 +0200 [thread overview]
Message-ID: <87h8mybedl.fsf@mbork.pl> (raw)
In-Reply-To: <m2in7eigj9.fsf@newartisans.com>
On 2018-05-23, at 16:38, John Wiegley <johnw@gnu.org> wrote:
>>>>>> "MB" == Marcin Borkowski <mbork@mbork.pl> writes:
>
>>> > BTW, I once had an idea to write a "next step" book on Emacs Lisp, one >
>>> that could be read after the Intro.
>>>
>>> How about adding that mew material as the start of the Emacs Lisp Reference
>>> Manual?
>
> MB> There are several reasons I don't think this is a good idea.
>
> I have a reason why I disagree with this comment.
>
> ;)
Understood. ;-)
So, here are my reasons, in no particular order.
- style: The Lisp Reference is more in formal/impersonal style, Eintro
is much more casual. So is my writing. (You can visit my blog at
mbork.pl to see a sample.) It won't fit to the Reference.
- ambition: I'd like to have "my" book on Elisp. It's not only about
vanity, though - I would like to author more books on various stuff in
the future, and I'd like this to be part of my track record. (Note:
it is not going to be my first book, I coauthored a well-received
textbook on LaTeX (in Polish) and wrote a textbook about certain part
of mathematics (https://zbmath.org/?q=an:1362.54001), and I'm in the
process of writing yet another one.)
- money: I'd like to get some funding for the book. (I thought about
crowdfunding it.) I don't want to become a millionaire thanks to it,
but it will require considerable time from me, and I am now the sole
financial supporter of my family, so I have to be quite careful wrt
where I put my time in. (In an ideal world, I'd like to have, say
$8000 to cover all expenses of copyediting, proof-reading, printing
etc. and my time; in the real world, I think $2000 is a reasonable
minimum, which would mean this to be, say, a half-charity project.)
(Note: I am aware that this technically might not exclude rms' idea.)
- policy: While I do appreciate some of rms' and FSF's ideals, I don't
feel like I can identify with FSF's goals/policies to the extent of
authoring a big thing with them (as opposed to minor things like bug
fixes and small Emacs features).
- license: I explicitly do *not* want to release it under GFDL. One
possibility would be to have a small print-run of physical copies
(say, a few hundred at most) and a digital version (pdf and maybe epub
etc.) which would be sold, but also freely available (e.g. after some
short time, like a few months). While nothing is set in stone
(although I'd really want to have at least some physical copies),
I consider GFDL a very bad idea in case of (at least partially)
creative writing (as opposed to purely technical writing, like
a reference guide). I thought about e.g. CC-BY-ND, which explicitly
forbids distributing modified copies.
Does that make more sense?
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2018-05-23 15:06 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 12:03 Making Emacs Manuals Available as PDF Files Siraphob (Ben) Phipathananunth
2018-05-10 14:14 ` Jean-Christophe Helary
2018-05-11 4:32 ` Van L
2018-05-11 6:44 ` Eli Zaretskii
2018-05-11 21:44 ` Richard Stallman
2018-05-14 10:27 ` update intro to Emacs Lisp programming (was: Making Emacs Manuals Available as PDF Files) Van L
2018-05-15 3:59 ` Richard Stallman
2018-05-17 0:25 ` Van L
2018-05-17 1:12 ` update intro to Emacs Lisp programming Paul Eggert
2018-05-17 11:38 ` Jean-Christophe Helary
2018-05-18 2:33 ` Richard Stallman
2018-05-18 12:16 ` Jean-Christophe Helary
2018-05-18 13:39 ` Van L
2018-05-18 15:22 ` Marcin Borkowski
2018-05-19 0:00 ` Van L
2018-05-19 0:52 ` Jean-Christophe Helary
2018-05-20 1:38 ` Van L
2018-05-20 3:16 ` Richard Stallman
2018-05-20 3:38 ` Marcin Borkowski
2018-05-20 6:54 ` Jean-Christophe Helary
2018-05-20 10:49 ` Siraphob (Ben) Phipathananunth
2018-05-20 23:50 ` Van L
2018-05-21 4:12 ` Richard Stallman
2018-05-21 15:13 ` Eli Zaretskii
2018-05-21 15:55 ` Siraphob (Ben) Phipathananunth
2018-05-22 2:15 ` Richard Stallman
2018-05-22 2:43 ` Eli Zaretskii
2018-05-22 2:15 ` Richard Stallman
2018-05-21 4:11 ` Richard Stallman
2018-05-21 6:30 ` Van L
2018-05-22 2:14 ` Richard Stallman
2018-05-22 11:20 ` Jean-Christophe Helary
2018-05-22 18:07 ` Marcin Borkowski
2018-05-22 19:22 ` Filipp Gunbin
2018-05-23 3:27 ` Richard Stallman
2018-05-23 5:33 ` Marcin Borkowski
2018-05-23 14:38 ` John Wiegley
2018-05-23 15:06 ` Marcin Borkowski [this message]
2018-05-25 2:56 ` Richard Stallman
2018-05-24 2:49 ` Richard Stallman
2018-05-24 4:24 ` Marcin Borkowski
2018-05-26 3:51 ` Richard Stallman
2018-05-24 16:25 ` Thien-Thi Nguyen
2018-05-30 17:28 ` Marcin Borkowski
2018-05-30 18:58 ` Thien-Thi Nguyen
2018-05-30 20:17 ` John Wiegley
2018-06-02 17:44 ` Marcin Borkowski
2018-05-23 3:23 ` Richard Stallman
2018-05-20 7:10 ` Eli Zaretskii
2018-05-20 11:00 ` Van L
2018-05-21 4:10 ` Richard Stallman
2018-05-22 17:57 ` Marcin Borkowski
2018-05-23 1:53 ` Van L
2018-05-19 0:48 ` Jean-Christophe Helary
2018-05-20 3:15 ` Richard Stallman
2018-05-18 6:46 ` Van L
2018-05-19 3:20 ` Improve the Emacs Lisp Reference Manual with intro sections Richard Stallman
2018-05-20 1:04 ` Jean-Christophe Helary
2018-05-21 4:09 ` Richard Stallman
2018-05-18 2:31 ` update intro to Emacs Lisp programming (was: Making Emacs Manuals Available as PDF Files) Richard Stallman
2018-05-18 7:07 ` Van L
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=87h8mybedl.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=brandelune@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=rms@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.