emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christine Köhn" <christine@chark.eu>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Where has the manual on one html page gone?
Date: Sun, 21 Mar 2021 09:54:48 +0100	[thread overview]
Message-ID: <87mtuwopif.fsf@chark.eu> (raw)
In-Reply-To: <877dn9x84w.fsf@alphaville.usersys.redhat.com>

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.

For me, it's easier to read a whole chapter/section if I just have to
scroll down. Especially if I only do cursory reading, e.g if I read
about spreadsheets after not having used them in a while. If I can just
scroll down, it's also easier to read on my smartphone (I'd like not to
do that but in the pandemic some things cannot be chosen).

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.

  parent reply	other threads:[~2021-03-21  8:56 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 [this message]
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=87mtuwopif.fsf@chark.eu \
    --to=christine@chark.eu \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \


* 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).