From: Jean-Christophe Helary <brandelune@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Robert J. Chassel reference in Intro to Emacs Lisp
Date: Sat, 18 May 2019 21:42:34 +0900 [thread overview]
Message-ID: <1BDA128C-4B61-49D1-93FD-78D25C2C1818@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
It's been almost 2 years since Chassel passed away and the "About the author" in the Introduction to Emacs Lisp reads as if he were still alive.
I've changed the tense of the paragraph and added 1 line to mention that he passed away and a link to the FSF's "Goodbye to Bob Chassell".
Let me know if that's useful and if I can improve the patch.
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
[-- Attachment #2: r.j.chassel.diff --]
[-- Type: application/octet-stream, Size: 1395 bytes --]
diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index 519decb1d0..00f220c3c1 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -21858,14 +21858,16 @@ About the Author
@end ifnottex
@quotation
-Robert J. Chassell has worked with GNU Emacs since 1985. He writes
-and edits, teaches Emacs and Emacs Lisp, and speaks throughout the
+Robert J. Chassell started working with GNU Emacs in 1985. He wrote
+and edited, taught Emacs and Emacs Lisp, and spoke throughout the
world on software freedom. Chassell was a founding Director and
-Treasurer of the Free Software Foundation, Inc. He is co-author of
-the @cite{Texinfo} manual, and has edited more than a dozen other
-books. He graduated from Cambridge University, in England. He has an
-abiding interest in social and economic history and flies his own
-airplane.
+Treasurer of the Free Software Foundation, Inc. He was co-author of
+the @cite{Texinfo} manual, and edited more than a dozen other
+books. He graduated from Cambridge University, in England. He had an
+abiding interest in social and economic history and flew his own
+airplane. In 2010, he was diagnosed with progressive supranuclear palsy, and died on 30 June 2017 as a result.
+
+@uref{https://www.fsf.org/licensing/gnu-press/, "Goodbye to Bob Chassell"}
@end quotation
@c @page
next reply other threads:[~2019-05-18 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 12:42 Jean-Christophe Helary [this message]
2019-05-18 13:15 ` Robert J. Chassel reference in Intro to Emacs Lisp Richard Copley
2019-05-18 14:03 ` Jean-Christophe Helary
2019-05-18 14:31 ` Jean-Christophe Helary
2019-05-18 18:08 ` Paul Eggert
2019-05-18 21:41 ` Richard Stallman
2019-05-19 1:55 ` Jean-Christophe Helary
2019-05-19 16:32 ` Omitting "Maintainer:" (was: Robert J. Chasell reference ...) Paul Eggert
2019-05-19 16:44 ` Omitting "Maintainer:" Stefan Monnier
2019-05-19 17:02 ` Eli Zaretskii
2019-05-19 19:18 ` Lars Ingebrigtsen
2019-05-20 4:38 ` Paul Eggert
2019-05-19 20:47 ` Omitting "Maintainer:" (was: Robert J. Chasell reference ...) Richard Stallman
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=1BDA128C-4B61-49D1-93FD-78D25C2C1818@gmail.com \
--to=brandelune@gmail.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).