From: Eli Zaretskii <eliz@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 31037@debbugs.gnu.org
Subject: bug#31037: 27.0.50; Misleading info in Introduction to Programming in Emacs Lisp
Date: Tue, 03 Apr 2018 10:34:28 +0300 [thread overview]
Message-ID: <83k1to68vv.fsf@gnu.org> (raw)
In-Reply-To: <878ta4n6ik.fsf@mbork.pl> (message from Marcin Borkowski on Tue, 03 Apr 2018 08:33:39 +0200)
> From: Marcin Borkowski <mbork@mbork.pl>
> Date: Tue, 03 Apr 2018 08:33:39 +0200
>
> (info "eintro")
>
> yields
>
> --8<---------------cut here---------------start------------->8---
> An Introduction to Programming in Emacs Lisp
> ********************************************
>
> This is an ‘Introduction to Programming in Emacs Lisp’, for people who
> --8<---------------cut here---------------end--------------->8---
>
> If I want to actually cite Chassell's book, it is (a) not obvious who
> the author is (the name can be found at the end of the preface and in
> the "About the author" section, but not on the title page, where it
> should be!), and (b) completely not obvious how to cite the book - is
> the official title "An Introduction to Programming in Emacs Lisp" or
> "Introduction to Programming in Emacs Lisp"?
You are looking in the wrong place for this information. The Info
format of a book is not a book, it's an on-line documentation file.
For the book details, you should either (a) look at the Texinfo
sources, or (b) produce a PDF or DVI/PS format, and look there. (The
former is much easier, of course, if you have the sources.)
next prev parent reply other threads:[~2018-04-03 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 6:33 bug#31037: 27.0.50; Misleading info in Introduction to Programming in Emacs Lisp Marcin Borkowski
2018-04-03 7:34 ` Eli Zaretskii [this message]
2018-04-05 10:38 ` Marcin Borkowski
2019-09-28 18:29 ` Stefan Kangas
2019-10-01 15:33 ` Marcin Borkowski
2019-10-08 16:31 ` Stefan Kangas
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=83k1to68vv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31037@debbugs.gnu.org \
--cc=mbork@mbork.pl \
/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.