emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Where has the manual on one html page gone?
Date: Sun, 21 Mar 2021 15:48:29 +0100	[thread overview]
Message-ID: <20210321144829.GI17671@maokai> (raw)
In-Reply-To: <87mtuwopif.fsf@chark.eu>

On Sun, Mar 21, 2021 at 09:54:48AM +0100, Christine Köhn wrote:
> Here's why I prefer the one page manual:
> I can search it easily. Sometimes I do not find what I'm looking for
> where I would expect it to be. Also, searching is convenient way to find
> out if something *is not* in the manual.
> I'm used to reading and searching in a browser.

Searching and saving are both effective use cases.

> I agree that it's not efficient to download a whole manual but I guess
> that's what caching is for? Anyway, I thought about switching to
> accessing the manual offline but I haven't gotten to it yet.

I disagree. With transparent gzip compression its a few hundred K,
less than all the Javascript libraries that load when you open most
popular websites.

You are also less likely to reopen it repeatedly or reload it.

Perhaps the main link can goto a sectioned manual, but I'd like to see
a link to the one page manual preserved.

Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

      reply	other threads:[~2021-03-21 14: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
2021-03-21  8:54   ` Christine Köhn
2021-03-21 14:48     ` Russell Adams [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:

  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=20210321144829.GI17671@maokai \
    --to=rladams@adamsinfoserv.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).