From: bolega <gnuist006@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: I find a mistake in "introduction to emacs lisp" in emacs 23
Date: Thu, 2 Jul 2009 18:36:19 -0700 (PDT) [thread overview]
Message-ID: <9615a48f-ab54-433b-8757-bed38f4fbbaf@24g2000yqm.googlegroups.com> (raw)
In-Reply-To: mailman.1671.1246508185.2239.help-gnu-emacs@gnu.org
On Jul 1, 6:33 pm, waterloo <waterloo2...@gmail.com> wrote:
> In "kill-new function" of 8.3.1.
>
> The critical lines are these:......
>
> (setq kill-ring (cons string kill-ring)) is needless .
>
> thanks
Can anyone else confirm this ? and explain if it is a minor issue or a
major one ?
next parent reply other threads:[~2009-07-03 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1671.1246508185.2239.help-gnu-emacs@gnu.org>
2009-07-03 1:36 ` bolega [this message]
2009-07-03 13:45 ` I find a mistake in "introduction to emacs lisp" in emacs 23 tyler
2009-07-02 1:33 waterloo
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=9615a48f-ab54-433b-8757-bed38f4fbbaf@24g2000yqm.googlegroups.com \
--to=gnuist006@gmail.com \
--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.
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).