emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Devin Prater <r.d.t.prater@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Where has the manual on one html page gone?
Date: Tue, 16 Feb 2021 06:49:02 -0600	[thread overview]
Message-ID: <YCu/PtE0BNBUKWdn@gmail.com> (raw)
In-Reply-To: <87czx0jque.fsf@mbork.pl>

[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]

I like it when I just want to read through the whole document with my screen reader, not having to page through it. I also like being able to search the whole document. And, converting it to EPUB allows me to read it on my phone when I'm away from the computer, if I want to.

On Tue, Feb 16, 2021 at 10:37:29AM +0100, Marcin borkowski wrote:
>On 2021-02-15, at 23:45, Nick Dokos <ndokos@gmail.com> wrote:
>> Christine Köhn <christine@chark.eu> writes:
>>> Hi,
>>> I always used the manual online as one html page but it does not seem to
>>> be available since (?) the website revamp. I prefer the manual as one
>>> page for many reasons. Is it still available online?
>> I've always used the one-page per section version on the web (although
>> I tend to use Info much more often), primarily because I thought that
>> downloading the whole manual to just look at a section or two or five
>> would be inefficient - in fact, I've wondered why the single-page
>> versions of various manuals (particularly the larger ones: emacs and
>> elisp) are made available. So it is idle curiosity on my part, but
>> what are the the reasons for your preference?
>Converting to an ebook format to read on an ebook reader is one possible
>Marcin Borkowski

Devin Prater

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2021-02-16 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 16:13 Where has the manual on one html page gone? Christine Köhn
2021-02-12 16:24 ` Diego Zamboni
2021-02-12 16:43   ` Christine Köhn
2021-02-15 22:45 ` Nick Dokos
2021-02-16  9:22   ` Diego Zamboni
2021-02-16  9:37   ` Marcin Borkowski
2021-02-16 12:49     ` Devin Prater [this message]
2021-03-21  8:54   ` Christine Köhn
2021-03-21 14:48     ` Russell Adams

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YCu/PtE0BNBUKWdn@gmail.com \
    --to=r.d.t.prater@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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 public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).