From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>,
"'Le Wang'" <l26wang@gmail.com>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>, 9469@debbugs.gnu.org
Subject: bug#9469: buffer-local variables seem to remember previous values
Date: Mon, 12 Sep 2011 07:30:24 -0700 [thread overview]
Message-ID: <16AB56A492D74B3E9BC8D548CD71C6F3@us.oracle.com> (raw)
In-Reply-To: <m3r53m5fas.fsf@hase.home>
> > My point is that the manual would be more helpful to someone in my
> > position if it had an example saying don't modify quoted
> > objects, and why.
>
> This has nothing at all to do with quoting. Don't use destructive
> functions if you don't know what you are doing.
Everything that people have said in the thread is true. That doesn't mean that
we can't help users more in this regard.
What could perhaps be made clearer in the manual - and perhaps in the Lisp Intro
manual (e.g., with pedagogic examples), is the role of the Lisp reader in
creating list structure, symbols, etc. It is ignorance of or forgetting about
this feature of Lisp that confuses users (esp. newbies) when it comes to `quote'
etc.
Explanation of Lisp reading is far removed in the manual from the description of
`quote' (and they are not directly related, so there is nothing wrong with
this). It might help to (a) develop the reader-creates-objects subject in the
Lisp Intro manual and (b) put a reminder about this in the section about
`quote', with a caveat about modifying etc.
In sum, it's not about whether you or the manual or Le is right or wrong. It's
about helping users. And yes, this is a potential point of confusion. The
consequences of the Lisp reader creating things are not necessarily obvious to
newbies.
next prev parent reply other threads:[~2011-09-12 14:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 17:07 bug#9469: buffer-local variables seem to remember previous values Le Wang
2011-09-10 17:44 ` Drew Adams
2011-09-11 16:57 ` Le Wang
2011-09-11 17:56 ` Drew Adams
2011-09-11 18:08 ` Andreas Schwab
2011-09-11 18:49 ` Le Wang
2011-09-11 18:54 ` Lars Magne Ingebrigtsen
2011-09-11 19:18 ` Le Wang
2011-09-11 19:54 ` Lars Magne Ingebrigtsen
2011-09-12 4:39 ` Le Wang
2011-09-12 7:57 ` Andreas Schwab
2011-09-12 8:23 ` Le Wang
2011-09-12 8:35 ` Andreas Schwab
2011-09-12 14:30 ` Drew Adams [this message]
2011-09-12 15:06 ` Le Wang
2011-09-13 12:54 ` Stefan Monnier
2011-09-13 13:12 ` Le Wang
2011-09-13 15:00 ` Helmut Eller
2011-09-13 18:02 ` Johan Bockgård
2011-09-13 18:52 ` Drew Adams
2011-09-13 20:42 ` Helmut Eller
2011-09-15 18:14 ` Le Wang
2011-09-11 19:37 ` Helmut Eller
2011-09-11 19:46 ` Andreas Schwab
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=16AB56A492D74B3E9BC8D548CD71C6F3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9469@debbugs.gnu.org \
--cc=l26wang@gmail.com \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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.