From: Eli Zaretskii <eliz@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: van@scratch.space, emacs-devel@gnu.org, rms@gnu.org,
brandelune@gmail.com
Subject: Re: update intro to Emacs Lisp programming
Date: Sun, 20 May 2018 10:10:12 +0300 [thread overview]
Message-ID: <837enyhkff.fsf@gnu.org> (raw)
In-Reply-To: <87in7juhc6.fsf@mbork.pl> (message from Marcin Borkowski on Sun, 20 May 2018 05:38:33 +0200)
> From: Marcin Borkowski <mbork@mbork.pl>
> Date: Sun, 20 May 2018 05:38:33 +0200
> Cc: van@scratch.space, brandelune@gmail.com, emacs-devel@gnu.org
>
> I thought that was pretty clear.
FWIW, that post sounded pretty unclear, if not bizarre, to me as well.
I learned long ago that misunderstandings are abundant in Internet
discussions, and therefore one should never blame the reader nor the
writer for their existence. One should rather try to clarify the
intent to improve understanding and diminish misunderstandings.
next prev parent reply other threads:[~2018-05-20 7:10 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
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 [this message]
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=837enyhkff.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brandelune@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
--cc=rms@gnu.org \
--cc=van@scratch.space \
/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.