From: "Jason A. Spiro" <jasonspiro4@gmail.com>
To: bug-emacs@gnu.org
Cc: Phil Sung <psung@alum.mit.edu>
Subject: bug#4962: Please include tour parts 2 and 3, and the slideshow version of tour part 1, on your website
Date: Wed, 18 Nov 2009 23:34:41 -0500 [thread overview]
Message-ID: <c241693f0911182034i79492dd8pca1efd4b02ef1d1c@mail.gmail.com> (raw)
Dear bug-emacs list,
Thank you for putting a version of Phil Sung's guided tour of Emacs on
your website at http://gnu.org/s/emacs/tour/ -- but I prefer Phil's
slideshow version. But AFAICT the slideshow version is not available
anywhere on gnu.org. I do admit that some people will prefer the
prose version. So you should offer both versions on your website.
Also, parts 2 and 3 of his tour are not available anywhere on gnu.org
either. They were last published in full in 2007. I don't recommend
that you link to the new 2009 part 2 he's published this year, because
it replaces 2007 part 2 and 2007 part 3 but is shorter and omits a lot
of material. Instead, link to 2007 part 2 and 2007 part 3.
So, could you please change http://gnu.org/s/emacs/tour/ to be not a
tour, but a menu, linking to six choices?:
* Part 1 -- an introduction to Emacs -- working quickly in Emacs;
modes; macros; useful features; acquiring emacs; how to learn more:
* Quick-to-watch slideshow version:
http://web.psung.name/emacs/2009/part1.html
* More detailed prose version: I suggest you relocate this to
http://gnu.org/s/emacs/tour-part-1-prose/
* Part 2 -- customization -- basic elisp; keybindings; variables;
hooks; the .emacs file; defining simple commands:
* OpenOffice.org Impress format:
http://web.psung.name/emacs/2007/emacs-slides-2.odp
* PDF: http://web.psung.name/emacs/2007/emacs-slides-2.pdf
* Part 3 -- extending Emacs -- elisp control flow; interactive
arguments; advice; defining new modes:
* OpenOffice.org Impress format:
http://web.psung.name/emacs/2007/emacs-slides-3.odp
* PDF: http://web.psung.name/emacs/2007/emacs-slides-3.pdf
Thanks in advance,
-Jason Spiro
P.S. If you wonder if this material is GFDLed, know that
http://web.psung.name/emacs/ says "Copyright © 2007, 2008, 2009 Free
Software Foundation or Phil Sung. You may use any of the material on
this site under the terms of the GFDL v1.3+ or the GPL v3+ [...]".
--
Jason Spiro: software/web developer, packager, trainer, IT consultant.
I support Linux, UNIX, Windows, and more. Contact me to discuss your needs.
+1 (416) 992-3445 / www.jspiro.com
next reply other threads:[~2009-11-19 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 4:34 Jason A. Spiro [this message]
2021-12-04 21:08 ` bug#4962: Please include tour parts 2 and 3, and the slideshow version of tour part 1, on your website Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2009-11-20 21:31 Jason A. Spiro
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=c241693f0911182034i79492dd8pca1efd4b02ef1d1c@mail.gmail.com \
--to=jasonspiro4@gmail.com \
--cc=4962@emacsbugs.donarmstrong.com \
--cc=bug-emacs@gnu.org \
--cc=psung@alum.mit.edu \
/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).