all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Common Lisp Emulation vs Common Lisp Extensions
Date: Sun, 29 May 2016 22:20:27 +0200	[thread overview]
Message-ID: <871t4k62gk.fsf@mbork.pl> (raw)
In-Reply-To: <8360twyjvn.fsf@gnu.org>


On 2016-05-29, at 17:16, Eli Zaretskii <eliz@gnu.org> wrote:

> I don't think I see the mess.  You are looking for identical text
> where there shouldn't be one.  The assumption is that the reader uses
> the same format consistently for all the manuals.  This assumption is
> at the basis of the Texinfo documentation system, and has nothing to
> do with Emacs the project.  We just use Texinfo, that's all.

FWIW, I am a counterexample proving that that assumption is false.
I might read the Emacs Lisp Intro on my ebook reader (using a version
converted from HTML), then consult the Emacs Lisp Reference in an Info
buffer, and print out parts of the Emacs Manual from a pdf.  Not that
I did it all in this way, but it _might_ be that way (and indeed I used
all three of those formats - Info, pdf and HTML - at some point in
time).

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



  reply	other threads:[~2016-05-29 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 13:39 Common Lisp Emulation vs Common Lisp Extensions Jean-Christophe Helary
2016-05-28 15:59 ` Eli Zaretskii
2016-05-28 23:47   ` Jean-Christophe Helary
2016-05-29 15:16     ` Eli Zaretskii
2016-05-29 20:20       ` Marcin Borkowski [this message]
2016-05-30  5:33       ` Jean-Christophe Helary

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=871t4k62gk.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@gmail.com \
    /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.