From: "Tim Cross" <theophilusx@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: tcross@rapttech.com.au, 6521@debbugs.gnu.org
Subject: bug#6521: 23.2; Elisp Manual Ommission
Date: Sat, 21 Aug 2010 08:36:50 +1000 [thread overview]
Message-ID: <19567.898.422804.121281@puma.rapttech.com.au> (raw)
In-Reply-To: <jwvvd75t026.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
> [ Can't remember responding yet. ]
> >> Could you send it along, so we could see what it looks like (to
> >> better assess whether it means we have a serious problem, or if
> >> it's just bad luck).
> > The code which failed to compile was BBDB as bundled with Debian
> > testing. Do you want me to send the error message that was
> > generated? (note that the code still compiles with emacs23).
>
> AFAIK, this problem has been fixed a little while back.
Yes, the problem with compilation seems to have been fixed. However, there is
still a problem. Now it is a documentation issue rather than a compilation one.
The manual no longer has a section about the deprecated use of the old style
backquote. The warning message generated by the byte compiler still refers the
user to the backquote section of the elisp manual for more information, but
there is no reference to old style backquotes in that section. This makes it
very difficult for anyone who is not familiar with the change in style to
understand what use to be different and what needs to be changed in the code to
get rid of the warning. Given that this change in style happened many years
ago, there is likely a number of users who are unfamiliar with what the old
style was and they would probably benefit from some explanation/guidance.
I recommend that either a footnote be added to the backquote section of the
elisp reference manual or a new section be added about the old style backquotes
and what needs to be changed to make it compliant with modern usage. The
compiler warning message should probably also be updated to either direct users
to the footnote or new section.
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.
--
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.
prev parent reply other threads:[~2010-08-20 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 9:02 bug#6521: 23.2; Elisp Manual Ommission Tim Cross
2010-06-27 18:02 ` 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 [this message]
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=19567.898.422804.121281@puma.rapttech.com.au \
--to=theophilusx@gmail.com \
--cc=6521@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tcross@rapttech.com.au \
/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.