From: Tim Cross <tcross@rapttech.com.au>
To: 6521@debbugs.gnu.org
Subject: bug#6521: 23.2; Elisp Manual Ommission
Date: Sun, 27 Jun 2010 19:02:52 +1000 [thread overview]
Message-ID: <87iq5497b7.fsf@lion.rapttech.com.au> (raw)
It appears the section from the emacs manual that use to describe the
old pre emacs 19.29 behavior with backquotes has been removed. In
previous versions of the manual, it use to describe what this old
behavior was and why it is no longer required. However, it now only
describes the use of backquote as it should now be used.
I think it would be a good idea to put the description of the old
section back into the manual. The reason is that
1. The compiler, when warning of code that still uses the old
backquote format references this node, but there is no reference
to the old behavior in the node anymore. This makes things less
clear to new users that perhaps it should be.
2. It may not be obvious to more recent users exactly what the
old behavior was, making it more difficult to identify the old
style and understand how it use to be formatted in order to
update the code to use the correct modern style.
3. This is likely to become a bigger issue now that emacs 24 is
changing to assume a backquote with a space following it is
modern style. I just encountered code which failed to compile
due to this. When wanting to clarify my understanding, I found
nothing relevant in the manual.
I was referencing version 3 of the elisp manual (for emacs version
24.0.50).
regards,
Tim
--
Tim Cross
tcross@rapttech.com.au
There are two types of people in IT - those who do not manage what they
understand and those who do not understand what they manage.
next reply other threads:[~2010-06-27 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 9:02 Tim Cross [this message]
2010-06-27 18:02 ` bug#6521: 23.2; Elisp Manual Ommission Drew Adams
2010-07-01 0:46 ` Stefan Monnier
2010-07-01 7:39 ` Tim Cross
2010-08-20 22:03 ` Stefan Monnier
2010-08-20 22:36 ` Tim Cross
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=87iq5497b7.fsf@lion.rapttech.com.au \
--to=tcross@rapttech.com.au \
--cc=6521@debbugs.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 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.